Thank you Kelly. I will be participating in an offsite starting tomorrow for 3 days. I won’t be able to join the call. However, I will be in JP the week after and I am available to discuss with the

Sorry I am at the OpenStack Summit and will not make it Sent from my BlackBerry 10 smartphone. From: Williams, Kelly Sent: Monday, November 3, 2014 11:33 PM To: Williams, Kelly; OpenChain@... Subject:

Hi Everyone, Here’s the agenda for the meeting tomorrow at 8am PT, 11am ET, 3pm UTC, 5pm CEST. Upcoming meeting topics Proposed future topics SPDX 101 primer (Phil Odence, BlackDuck) Follow

Ibrahim, I’ll be at the Compliance Summit and can provide you an update. All, as a possible thought exercise for tomorrow, one idea is to take a look at the materials from last week through the

Hi All, I just uploaded an .odp and .odt version of Ibrahim’s slide deck and document from last call. I checked the view and all looked the same in both formats as the originals that Ibrahim

Many thanks Jilayne! I appreciate the difficulty of changing document formats in the middle of negotiations and I wouldn't ask anyone to go through that. But I'm not going to give up here that easily.

Hello all, In today's OpenChain call I offered the following: 1. Prepare a couple of sample License Interaction Diagrams (LIDs ...To whom to we credit that clever name??) based on appropriate UML

Hi Jeremiah, Very well said. I’d love to work with open formats, too. But experience tells me that it is just not practical unless all of my peers would also switch. Interoperability is bad,

Items 2 and 3... 2. I've adapted a diagram that helps to visualize the role of a compliance management system in relation to reducing uncertainty and managing risk.

In your first diagram, the implication is that there is no way to ever be 100% certain about the delivered code base, there will always be residual uncertainty. But code is finite, so theoretically

Hi Joseph, Thanks for following up on the action items. All, I’ve posted the meeting notes and an example of a license interaction diagram on the

I think that 100% certainty about license compliance of a given code base is not possible. Even if you use the most sophisticated tools available today, there is no 100% certainty that they are able

It is possible. You have a finite set. You can determine, concretely, exactly what you have. The exercise of then assigning a one-to-one corresponding license on your finite code base can then be

Hi all, [Oliver] I fully agree to Claus-Peter. Looking at an existing code base you never can be sure whether you know the real origin of every line of code and the "real" License of it. You can't be

I'm glad you chose Chromium. :-) I would argue that there are humans able to identify *all* licenses associated with Chromium. I would argue that this person or persons could be identified were it not

RE: "What I will say is that the vagueness of the terminology and the chart is misleading and that it is not accurate in measuring residual risk." If that's a bug report about the terminology, let's

Reasonable and fair. But if we can at all convey the *possibility* of completeness (to use a term other than risk,) I feel that would send a more positive, accurate message. Point taken. :-)

RE: "if we can at all convey the *possibility* of completeness" Well, that's about as deep a philosophical matter as we might get into! To briefly segway into the deep end of that pool, permit me to

Hi Everyone, Here’s the agenda for the meeting tomorrow at 8am PT, 11am ET, 3pm UTC, 5pm CEST. Upcoming meeting topics (Jim Hutchison, QTI) – 5 mins Proposed future topics (input

Hi Everyone, For the discussion on the draft FOSS compliance program that Ibrahim introduced two meetings ago, I would encourage you all to look at the document version of Ibrahim’s materials