On Apr 22, 2015, at 12:15 PM, Jilayne Lovejoy <Jilayne.Lovejoy@...> wrote:

Thanks Mike!

Hate to say it, but… the invite for the third Monday is appearing on Tuesday in my calendar… 

Jilayne

From: Mike Dolan <mdolan@...>
Date: Wednesday, April 22, 2015 at 9:55 AM
To: "openchain@..." <openchain@...>
Subject: [OpenChain] OpenChain Working Group Meeting Rescheduling

Hi everyone, you should have a few meeting notices in your inbox. The Working Group decided to move the bi-weekly calls from Tuesday to Monday at 9am PT. I have sent two new invites for both the first Monday and third Monday meetings. I have also canceled both of the Tuesday meeting invites (one was for the first Tuesday, the second for the third Tuesday). 

I am aware there are often issues with calendar invites and competing calendaring platforms (e.g. Google Calendar, Outlook, Lotus Notes, etc). If any of those issues show up, just let me know and we can try to find a fix/resolution.

Thanks,

Mike

---
Mike Dolan
Sr. Director of Strategic Programs, The Linux Foundation

Office: +1.330.460.3250   Cell: +1.440.552.5322  Skype: michaelkdolan
Email / Google Talk: mdolan@...
---

-- IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

ARM Limited, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2557590
ARM Holdings plc, Registered office 110 Fulbourn Road, Cambridge CB1 9NJ, Registered in England & Wales, Company No: 2548782

Hi everyone,

 

during yesterday’s meeting we spent some time talking about FOSS policies. Essentially, some bullet points were moved from G4 to G1 to avoid redundancies (which is necessary). I have been wondering, if the points were actually redundant.                 While under G1 we try and describe how everyone can know their FOSS responsibilities (by telling them through a FOSS policy), G4 could be designed as a sort of checklist (first, write a policy; second, define use cases, quality gates and such; …).

 

At the end of the meeting we discussed the two different approaches that are taken under G4 – SP4.2 and SP4.3. I have been wondering, if we could integrate these two approaches by (re-) sorting the bullet points into two groups:

 

1.                  What to do to generate/extract all the information that enables suppliers to actually be compliant

 

Most of the bullet points that are currently under SP4.3 could go here; most of the bullet points I added under SP4.2 would probably fit here, too.

 

2.                  What to do with this information once you have it.

 

Under this topic we could define the use cases (Internal Use vs. External Distribution/Availability etc.). For each use case we could describe how to further use the extracted information.

 

I am looking forward to discussing these thoughts during the next meeting!

 

Best

Miriam

______________________________________________________________

Dr. Miriam Ballhausen

Rechtsanwältin

 

JBB Rechtsanwälte

Jaschinski Biere Brexl Partnerschaft mbB

Christinenstraße 18/19 | 10119 Berlin

Tel. +49.30.443 765 0  |  Fax +49.30.443 765 22

Sitz der Gesellschaft: Berlin | Registergericht AG Charlottenburg | PR 609 B

www.jbb.de

 

 

 

 

 

Von: openchain-bounces@... [mailto:openchain-bounces@...] Im Auftrag von Williams, Kelly
Gesendet: Mittwoch, 22. April 2015 00:36
An: openchain@...
Betreff: Re: [OpenChain] OpenChain meeting agenda 4/21

 

Hi –

 

Thanks for meeting today.  It was good discussion around “Internal Procedures” and the role of a review board.  The agenda presentation and meeting minutes are posted on the wiki at https://wiki.linuxfoundation.org/openchain/start?&#meeting-materials. 

 

Please note the new date/time for our next meeting will be Mon, 5/4  at 9am PT, 12pm ET, 4pm UTC, 6pm CEST.

 

Let me know if I missed anything and if you have any questions.

 

Thanks,

Kelly

 

 

From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Williams, Kelly
Sent: Monday, April 20, 2015 4:29 PM
To: openchain@...
Subject: [OpenChain] OpenChain meeting agenda 4/21

 

Hi Everyone,

 

Here’s the agenda for the meeting tomorrow at 8am PT, 11am ET, 3pm UTC, 5pm CEST.

 

•       Update from ELN

•       New poll time results

•       Continue on Etherpad – G4: “How” (Team Discussion)

 

Phone bridge info:

Conference Number: +1 (415) 906-5657 Pin: 88326
UberConference URL: http://uberconference.com/mdolan

For international call instructions, please visit the website below. Please note you will have to enter the US Conference number as part of the instructions:
http://www.uberconference.com/international/access

Screen share (if used): go to http://uberconference.com/mdolan

 

Let me know if you have any additional proposed topics.

 

Regards,

Kelly

 

 

 

_______________________________________________
OpenChain mailing list
OpenChain@...
https://lists.linuxfoundation.org/mailman/listinfo/openchain

Hi everyone,

 

during yesterday’s meeting we spent some time talking about FOSS policies. Essentially, some bullet points were moved from G4 to G1 to avoid redundancies (which is necessary). I have been wondering, if the points were actually redundant.                 While under G1 we try and describe how everyone can know their FOSS responsibilities (by telling them through a FOSS policy), G4 could be designed as a sort of checklist (first, write a policy; second, define use cases, quality gates and such; …).

 

At the end of the meeting we discussed the two different approaches that are taken under G4 – SP4.2 and SP4.3. I have been wondering, if we could integrate these two approaches by (re-) sorting the bullet points into two groups:

 

1.                  What to do to generate/extract all the information that enables suppliers to actually be compliant

 

Most of the bullet points that are currently under SP4.3 could go here; most of the bullet points I added under SP4.2 would probably fit here, too.

 

2.                  What to do with this information once you have it.

 

Under this topic we could define the use cases (Internal Use vs. External Distribution/Availability etc.). For each use case we could describe how to further use the extracted information.

 

I am looking forward to discussing these thoughts during the next meeting!

 

Best

Miriam

______________________________________________________________

Dr. Miriam Ballhausen

Rechtsanwältin

 

JBB Rechtsanwälte

Jaschinski Biere Brexl Partnerschaft mbB

Christinenstraße 18/19 | 10119 Berlin

Tel. +49.30.443 765 0  |  Fax +49.30.443 765 22

Sitz der Gesellschaft: Berlin | Registergericht AG Charlottenburg | PR 609 B

www.jbb.de

 

 

 

 

 

Von: openchain-bounces@... [mailto:openchain-bounces@...] Im Auftrag von Williams, Kelly
Gesendet: Mittwoch, 22. April 2015 00:36
An: openchain@...
Betreff: Re: [OpenChain] OpenChain meeting agenda 4/21

 

Hi –

 

Thanks for meeting today.  It was good discussion around “Internal Procedures” and the role of a review board.  The agenda presentation and meeting minutes are posted on the wiki at https://wiki.linuxfoundation.org/openchain/start?&#meeting-materials. 

 

Please note the new date/time for our next meeting will be Mon, 5/4  at 9am PT, 12pm ET, 4pm UTC, 6pm CEST.

 

Let me know if I missed anything and if you have any questions.

 

Thanks,

Kelly

 

 

From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Williams, Kelly
Sent: Monday, April 20, 2015 4:29 PM
To: openchain@...
Subject: [OpenChain] OpenChain meeting agenda 4/21

 

Hi Everyone,

 

Here’s the agenda for the meeting tomorrow at 8am PT, 11am ET, 3pm UTC, 5pm CEST.

 

•       Update from ELN

•       New poll time results

•       Continue on Etherpad – G4: “How” (Team Discussion)

 

Phone bridge info:

Conference Number: +1 (415) 906-5657 Pin: 88326
UberConference URL: http://uberconference.com/mdolan

For international call instructions, please visit the website below. Please note you will have to enter the US Conference number as part of the instructions:
http://www.uberconference.com/international/access

Screen share (if used): go to http://uberconference.com/mdolan

 

Let me know if you have any additional proposed topics.

 

Regards,

Kelly

 

 

 

_______________________________________________
OpenChain mailing list
OpenChain@...
https://lists.linuxfoundation.org/mailman/listinfo/openchain

Hi everyone,

 

during yesterday’s meeting we spent some time talking about FOSS policies. Essentially, some bullet points were moved from G4 to G1 to avoid redundancies (which is necessary). I have been wondering, if the points were actually redundant.                 While under G1 we try and describe how everyone can know their FOSS responsibilities (by telling them through a FOSS policy), G4 could be designed as a sort of checklist (first, write a policy; second, define use cases, quality gates and such; …).

 

At the end of the meeting we discussed the two different approaches that are taken under G4 – SP4.2 and SP4.3. I have been wondering, if we could integrate these two approaches by (re-) sorting the bullet points into two groups:

 

1.                  What to do to generate/extract all the information that enables suppliers to actually be compliant

 

Most of the bullet points that are currently under SP4.3 could go here; most of the bullet points I added under SP4.2 would probably fit here, too.

 

2.                  What to do with this information once you have it.

 

Under this topic we could define the use cases (Internal Use vs. External Distribution/Availability etc.). For each use case we could describe how to further use the extracted information.

 

I am looking forward to discussing these thoughts during the next meeting!

 

Best

Miriam

______________________________________________________________

Dr. Miriam Ballhausen

Rechtsanwältin

 

JBB Rechtsanwälte

Jaschinski Biere Brexl Partnerschaft mbB

Christinenstraße 18/19 | 10119 Berlin

Tel. +49.30.443 765 0  |  Fax +49.30.443 765 22

Sitz der Gesellschaft: Berlin | Registergericht AG Charlottenburg | PR 609 B

www.jbb.de

 

 

 

 

 

Von: openchain-bounces@... [mailto:openchain-bounces@...] Im Auftrag von Williams, Kelly
Gesendet: Mittwoch, 22. April 2015 00:36
An: openchain@...
Betreff: Re: [OpenChain] OpenChain meeting agenda 4/21

 

Hi –

 

Thanks for meeting today.  It was good discussion around “Internal Procedures” and the role of a review board.  The agenda presentation and meeting minutes are posted on the wiki at https://wiki.linuxfoundation.org/openchain/start?&#meeting-materials. 

 

Please note the new date/time for our next meeting will be Mon, 5/4  at 9am PT, 12pm ET, 4pm UTC, 6pm CEST.

 

Let me know if I missed anything and if you have any questions.

 

Thanks,

Kelly

 

 

From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Williams, Kelly
Sent: Monday, April 20, 2015 4:29 PM
To: openchain@...
Subject: [OpenChain] OpenChain meeting agenda 4/21

 

Hi Everyone,

 

Here’s the agenda for the meeting tomorrow at 8am PT, 11am ET, 3pm UTC, 5pm CEST.

 

•       Update from ELN

•       New poll time results

•       Continue on Etherpad – G4: “How” (Team Discussion)

 

Phone bridge info:

Conference Number: +1 (415) 906-5657 Pin: 88326
UberConference URL: http://uberconference.com/mdolan

For international call instructions, please visit the website below. Please note you will have to enter the US Conference number as part of the instructions:
http://www.uberconference.com/international/access

Screen share (if used): go to http://uberconference.com/mdolan

 

Let me know if you have any additional proposed topics.

 

Regards,

Kelly

 

 

 

_______________________________________________
OpenChain mailing list
OpenChain@...
https://lists.linuxfoundation.org/mailman/listinfo/openchain

On May 21, 2015, at 5:30 PM, RUFFIN, MICHEL (MICHEL) <michel.ruffin@...> wrote:

Dear all I have just discover OpenChain today

 

I look at your criteria for good practice, and I think (I will have to cross check in detail) but Alcatel-Lucent is compliant to G1 to G6 and even to  RP1 and more.

 

But it appears to me that you are still missing several things (sorry if I am wrong I have not checked all discussion and results)

1)      Handling outsourcing, divertissement and merge and acquisition (this could be called RP2)

2)       Handling new/quite recent technologies: DRM, Bit torrent, Saas, IaaS, PaaS, Maven, …

3)      Measuring the level of implementation of the FOSS governance process: I am currently working on this in a company of 60 000 people so it is not yet well done in ALU but I have ideas like having internal audits, having certificate of compliance for ALU products, blocking the general availability of new products if they are not compliant (we already do that partially) etc.

 

FYI the FOSS governance process of ALU is  a set of 120 pages of information addressing all (20 page on how to package an ALU product with FOSS); We have a FOSS executive committee that meet all weeks during 1h30 since 2007 with lawyers, procurement technical people, we have 180 FOSS evaluators in the company (coach by the FOSS EC), which corresponds to your FOSS compliance officers, we have registered tutorials, we have a process to contribute to open source, …. We have plan to issue a compliance alert in the company in September to inform people on FOSS in which training will be mandatory even for high executives, We have launched a recognition program for FOSS evaluator with Human resource, and quality group to be sure that they are empowered.

 

I am not too sure, that I can participate to your meetings (too much things to do), but this need to be addressed.

 

Now I am curious to know if you have some plans to make this like a CCMi certification program and in what timeframe

 

To provide you a small contribution, I send you the FOSS clauses that we put in ALL our suppliers contracts (I would like to standardize that). It is a public document that has already been sent to the FTF Europe legal network and to the SPDX group. Note that clause 5 needs to be reworked, because it does not exactly means what we intend to do. The legal phrasing is asking too much compared to what we expect. We also plan to change this clauses to impose the SPDX format rather that “electronic form”. Our internal tools are SPDX compliant (not perhaps yet to SPDX 2 yet , but to SPDX 1.2)

 

Now I have another important comment to your group. The criteria that you define are Ok for Alcatel-lucent, we can already claim that we are compliant with the highest criteria and I can prove it. But for companies which are far from this level of compliance, it is freighting, I do not know how this can be solved, but you should think a little bit about that.  Because an open source process in a company needs steps to be acceptable and you need to put resource in place to face the demands. 

 

My two cents, like we say in US

 

Michel

Michel.Ruffin@..., PhD
Software Coordination Manager, COO - Business transformation
Distinguished Member of Technical Staff 
Tel +33 6 75 25 21 94
Alcatel-Lucent International, Centre de Villarceau - France

 

<FOSS_clauses_rationale_150508.doc>_______________________________________________
OpenChain mailing list
OpenChain@...
https://lists.linuxfoundation.org/mailman/listinfo/openchain