more details » OpenChain Workgroup Initial Meeting Audio portion: Conference Number: +1 (415) 906-5657 Pin: 88326 UberConference URL: http://uberconference.com/mdolan For international call

Hello, Firstly, and most importantly, I'd really like to thank those who've done the organization and brainstorming to get this list and idea off the ground. I know there are a lot of people behind

Echoing the thanks to the LF for kindly hosting the WG. Could not agree more. BTW in addition to Mike’s support on hosting the discussion, we already have a PM on this list. Kelly Williams is not

This event has been changed. more details » Changed: OpenChain Workgroup Weekly Meeting Audio portion: Conference Number: +1 (415) 906-5657 Pin: 88326 UberConference URL:

HiJeremiah, >>> Secondly, I have some concern around cadence. I am ok with either a weekly or biweekly cadence. >>> Lastly, I'd strongly urge all of us to kill our darlings. We need to not

Jeremiah raised some common concerns about SPDX that, as an early adopter, I wanted to share my experiences. >> while SPDX looks great, its not widely adopted. Debian has its own format and Yocto

On Thu, Aug 28, 2014 at 8:39 PM, Gisi, Mark <Mark.Gisi@...> wrote: > > Hi Jeremiah, > > > > >>> Secondly, I have some concern around cadence. > > > > I am ok with either a weekly or biweekly

On Thu, Aug 28, 2014 at 3:28 PM, Marr, David <dmarr@...> wrote: > > > On Aug 28, 2014, at 1:39 AM, Jeremiah Foster <jeremiah.foster@...> wrote: > > > Hello, > > > > Firstly, and most importantly, I'd

On Fri, Aug 29, 2014 at 7:37 AM, Gisi, Mark <Mark.Gisi@...> wrote: Jeremiah raised some common concerns about SPDX that, as an early adopter, I wanted to share my experiences. >> while SPDX looks

Hey Jeremiah, It’s been a while. Forgive me for doing a lousy job educating you on SPDX. Thanks, MarkG for filling in. Having been involved in SPDX from the outset, I can tell you that there are

Based on feedback rec'd offline (time commitment; also some specific folks who are out next week as they extend their US holiday week) it was suggested we move our OpenChain calls to every other week.

I'd agree that every other week is a good idea. Perhaps for the schedule of topics, we might take your list of sub-components and flesh out what they mean, what kinds of materials or information is

I also support meeting bi-weekly instead of weekly. Best, Eileen Eileen Evans Vice President & Deputy General Counsel, Cloud & Open Source Hewlett-Packard Company Mobile:

Thanks for raising the question, Jeremiah, and to Mark for providing the excellent clarification – both to the benefit of all! Jilayne

There seems to be support for every other week, with one request we do it on the first and third Tuesdays each month, but skipping next week due to close-of-summer vacations. Mike, would you mind

This event has been canceled and removed from your calendar. OpenChain Workgroup Weekly Meeting Audio portion: Conference Number: +1 (415) 906-5657 Pin: 88326 UberConference URL:

Hi everyone, I meant to set up the meeting invite for bi-weekly calls but accidentally setup weekly calls. We will not be meeting today and will resume calls on the first and third Tuesday of every

This event has been canceled and removed from your calendar. OpenChain Workgroup Weekly Meeting Audio portion: Conference Number: +1 (415) 906-5657 Pin: 88326 UberConference URL:

more details » OpenChain Working Group (First and Third Tuesday each month) Audio portion: Conference Number: +1 (415) 906-5657 Pin: 88326 UberConference URL: http://uberconference.com/mdolan For