Date   

Re: Creating a general FAQ for OpenChain

Kelly Williams
 

Thanks, Shane. If there are no objections, I will update the FAQ by the end of the week.

In addition, I updated the main page as suggested below.

Regards,
Kelly

-----Original Message-----
From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Shane Martin Coughlan
Sent: Tuesday, November 08, 2016 4:29 AM
To: openchain@...
Subject: Re: [OpenChain] Creating a general FAQ for OpenChain

Dear All

I am not sure if this was covered in the call today, but I would like to check if Mike or Kelly can update our General FAQ as proposed below to help with on-boarding new participants to OpenChain:

== Updated FAQ for Discussion ==

What is OpenChain?

The OpenChain Project helps to identify and share the core components of a high quality Free and Open Source Software (FOSS) compliance program. OpenChain conformance builds trust in the supply chain by describing how Open Source license requirements have been met in distributed software.

How does OpenChain work?

The OpenChain Project has three working groups open for anyone to contribute to:
* Specification Working Group - identifies and publishes a set of
core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are
adhering to the Specification requirements

There are also three governing committees with paid membership.
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth.
* Steering Committee - Development, management and updating of the
OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to
build an OpenChain compliance ecosystem throughout relevant supply
chains in collaboration with the Governing Board

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of FOSS in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance:
*
https://wiki.linuxfoundation.org/openchain/specification-questions-and
-answers
*
https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-an
swers
*
https://wiki.linuxfoundation.org/openchain/conformance-questions-and-a
nswers
Regards

Shane

On 2016 Nov 7, at 23:39, Shane Martin Coughlan <shane@...> wrote:

Hi Mark

Great points. Adjusted FAQ with some polishing for non-native speakers below for review if time permits on the call today.

I also wanted to note we may want to adjust the main website page. As you correctly pointed out in your mail below, OpenChain has yet to venture into best practices, but “What is OpenChain” on our landing page mentions companies addressing many friction points and re-creating processes before it talks about compliance. This may lead to some confusion about our emphasis:
<IMG_0090.PNG>
Perhaps we could adjust to “OpenChain was created to address FOSS-related friction points in the software supply chain. The focus of OpenChain today is helping to prevent companies redundantly recreating compliance work that upstream companies have already done or should have done."

== Updated FAQ for Discussion ==

What is OpenChain?

The OpenChain Project helps to identify and share the core components of a high quality Free and Open Source Software (FOSS) compliance program. OpenChain conformance builds trust in the supply chain by describing how Open Source license requirements have been met in distributed software.

How does OpenChain work?

The OpenChain Project has three working groups open for anyone to contribute to:
* Specification Working Group - identifies and publishes a set of
core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are
adhering to the Specification requirements

There are also three governing committees with paid membership.
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth.
* Steering Committee - Development, management and updating of the
OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to
build an OpenChain compliance ecosystem throughout relevant supply
chains in collaboration with the Governing Board

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of FOSS in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance:
*
https://wiki.linuxfoundation.org/openchain/specification-questions-and
-answers
*
https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-an
swers
*
https://wiki.linuxfoundation.org/openchain/conformance-questions-and-a
nswers

Regards

Shane

On 2016 Oct 31, at 14:53, Gisi, Mark <Mark.Gisi@...> wrote:

What is OpenChain?

The OpenChain Project is focused on identifying common best
practices that should be applied across a supply chain for
efficient and effective compliance with Open Source licenses.
OpenChain has yet to venture to far into providing best practices. And although it will in due time I believe it is a secondary objective. I attempted to describe the current objective as follows:

Q: What is OpenChain?

A: The OpenChain Project identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy. Program requirement conformance fosters trust among software supply chain participates that the open source license compliance obligations have been met for the software that one distributes and/or receives.

This is more technical and could benefit from further wordsmithing. It combines the first two questions into one (What is + Mission). It was not my intent to combined them into one question, but I felt a need to mention the mission in order to answer the question "What is OpenChain"

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance
This is another important question to address. I suggest providing a little more detail as follows:

Q: How is the OpenChain Project Organized?

A: The OpenChain Project consists of the following three working groups which are open for anyone to contribute to:
* Specification Working Group - identifies and publishes a set of
core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are
adhering to the Specification requirements

And three governing committees that are determined by paid membership.
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth.
* Steering Committee - Development, management and updating of the
OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to
build an OpenChain compliance ecosystem throughout relevant supply
chains in collaboration with the Governing Board

- Mark


-----Original Message-----
From: openchain-bounces@...
[mailto:openchain-bounces@...] On Behalf Of
Shane Martin Coughlan
Sent: Sunday, October 30, 2016 7:59 PM
To: openchain@...
Subject: Re: [OpenChain] Creating a general FAQ for OpenChain

Dear all

I wanted to send a reminder on the General FAQ as outlined below. Mike from Linux Foundation is ready to activate this FAQ on our site if there is consensus that it fits requirements. Comments and suggestions welcome.

Regards

Shane

On 2016 Oct 21, at 16:26, Shane Martin Coughlan <shane@...> wrote:

Dear all

We currently have a great website with a link to a FAQ. However, our current FAQ is Specification-centric. Check it out here:
https://www.openchainproject.org/faq
Mark, Miriam and the rest of the team discussed the utility of creating a more general FAQ for our landing page that then leads to specific FAQs for Specification, Curriculum and Conformance. I have taken the liberty of creating a draft for how this general FAQ may look as well as populating the Specification and Curriculum FAQs on the wiki:

What is OpenChain?

The OpenChain Project is focused on identifying common best practices that should be applied across a supply chain for efficient and effective compliance with Open Source licenses.

What is OpenChain’s mission?

The OpenChain Project's mission is to establish requirements to achieve effective management of Free and Open Source Software (FOSS) for software supply chain participants.

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of Free and Open Source Software in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance:
*
https://wiki.linuxfoundation.org/openchain/specification-questions-a
nd-answers
*
https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-
answers
*
https://wiki.linuxfoundation.org/openchain/conformance-questions-and
-answers

Input, adjustments and improvements welcome!

Regards

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


Re: Creating a general FAQ for OpenChain

Shane Martin Coughlan <shane@...>
 

Dear All

I am not sure if this was covered in the call today, but I would like to check if Mike or Kelly can update our General FAQ as proposed below to help with on-boarding new participants to OpenChain:

== Updated FAQ for Discussion ==

What is OpenChain?

The OpenChain Project helps to identify and share the core components of a high quality Free and Open Source Software (FOSS) compliance program. OpenChain conformance builds trust in the supply chain by describing how Open Source license requirements have been met in distributed software.

How does OpenChain work?

The OpenChain Project has three working groups open for anyone to contribute to:
* Specification Working Group - identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are adhering to the Specification requirements

There are also three governing committees with paid membership.
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth.
* Steering Committee - Development, management and updating of the OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to build an OpenChain compliance ecosystem throughout relevant supply chains in collaboration with the Governing Board

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of FOSS in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance:
* https://wiki.linuxfoundation.org/openchain/specification-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/conformance-questions-and-answers
Regards

Shane

On 2016 Nov 7, at 23:39, Shane Martin Coughlan <shane@...> wrote:

Hi Mark

Great points. Adjusted FAQ with some polishing for non-native speakers below for review if time permits on the call today.

I also wanted to note we may want to adjust the main website page. As you correctly pointed out in your mail below, OpenChain has yet to venture into best practices, but “What is OpenChain” on our landing page mentions companies addressing many friction points and re-creating processes before it talks about compliance. This may lead to some confusion about our emphasis:
<IMG_0090.PNG>
Perhaps we could adjust to “OpenChain was created to address FOSS-related friction points in the software supply chain. The focus of OpenChain today is helping to prevent companies redundantly recreating compliance work that upstream companies have already done or should have done."

== Updated FAQ for Discussion ==

What is OpenChain?

The OpenChain Project helps to identify and share the core components of a high quality Free and Open Source Software (FOSS) compliance program. OpenChain conformance builds trust in the supply chain by describing how Open Source license requirements have been met in distributed software.

How does OpenChain work?

The OpenChain Project has three working groups open for anyone to contribute to:
* Specification Working Group - identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are adhering to the Specification requirements

There are also three governing committees with paid membership.
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth.
* Steering Committee - Development, management and updating of the OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to build an OpenChain compliance ecosystem throughout relevant supply chains in collaboration with the Governing Board

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of FOSS in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance:
* https://wiki.linuxfoundation.org/openchain/specification-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/conformance-questions-and-answers

Regards

Shane

On 2016 Oct 31, at 14:53, Gisi, Mark <Mark.Gisi@...> wrote:

What is OpenChain?

The OpenChain Project is focused on identifying common best practices that should be
applied across a supply chain for efficient and effective compliance with Open Source
licenses.
OpenChain has yet to venture to far into providing best practices. And although it will in due time I believe it is a secondary objective. I attempted to describe the current objective as follows:

Q: What is OpenChain?

A: The OpenChain Project identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy. Program requirement conformance fosters trust among software supply chain participates that the open source license compliance obligations have been met for the software that one distributes and/or receives.

This is more technical and could benefit from further wordsmithing. It combines the first two questions into one (What is + Mission). It was not my intent to combined them into one question, but I felt a need to mention the mission in order to answer the question "What is OpenChain"

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance
This is another important question to address. I suggest providing a little more detail as follows:

Q: How is the OpenChain Project Organized?

A: The OpenChain Project consists of the following three working groups which are open for anyone to contribute to:
* Specification Working Group - identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are adhering to the Specification requirements

And three governing committees that are determined by paid membership.
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth.
* Steering Committee - Development, management and updating of the OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to build an OpenChain compliance ecosystem throughout relevant supply chains in collaboration with the Governing Board

- Mark


-----Original Message-----
From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Shane Martin Coughlan
Sent: Sunday, October 30, 2016 7:59 PM
To: openchain@...
Subject: Re: [OpenChain] Creating a general FAQ for OpenChain

Dear all

I wanted to send a reminder on the General FAQ as outlined below. Mike from Linux Foundation is ready to activate this FAQ on our site if there is consensus that it fits requirements. Comments and suggestions welcome.

Regards

Shane

On 2016 Oct 21, at 16:26, Shane Martin Coughlan <shane@...> wrote:

Dear all

We currently have a great website with a link to a FAQ. However, our current FAQ is Specification-centric. Check it out here:
https://www.openchainproject.org/faq
Mark, Miriam and the rest of the team discussed the utility of creating a more general FAQ for our landing page that then leads to specific FAQs for Specification, Curriculum and Conformance. I have taken the liberty of creating a draft for how this general FAQ may look as well as populating the Specification and Curriculum FAQs on the wiki:

What is OpenChain?

The OpenChain Project is focused on identifying common best practices that should be applied across a supply chain for efficient and effective compliance with Open Source licenses.

What is OpenChain’s mission?

The OpenChain Project's mission is to establish requirements to achieve effective management of Free and Open Source Software (FOSS) for software supply chain participants.

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of Free and Open Source Software in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance:
* https://wiki.linuxfoundation.org/openchain/specification-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/conformance-questions-and-answers

Input, adjustments and improvements welcome!

Regards

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


Background on a compliance program

Jeremiah Foster <jeremiah.foster@...>
 

Hi,

Thanks everyone for the OpenChain call today. I wanted to follow up with some background on my experience with a compliance program and the pitfalls and benefits we found in GENIVI. 

Firstly, I have to again express sincere thanks to the folks on the call. There is an amazing amount of experience and knowledge in the group and I feel it has produced a specification of real value. Many of you come from large companies and this kind of knowledge often is only found there. Making this knowledge available to SMEs will truly help FOSS in the marketplace since OpenChain provides the framework for a business model to SMEs. I hope they adopt it.

While GENIVI's compliance program is somewhat different than OpenChain's proposed conformance program, it shares more similarities than differences -- it even has something of a Linux Foundation pedigree. GENIVI's specification was designed on the "Carrier Grade Linux" model. (0)  CGL was all about bringing GNU/Linux to the carrier ecosystem. It designed a spec and granted compliance if you fulfilled the spec. GENIVI was fortunate to have one of the CGL leads, Dan Cauchy (then at Monta Vista, today at the Linux Foundation) design GENIVI's program. GENIVI inherited a lot from CGL. 

Like CGL our spec is paper-based. (1) You fill out a spreadsheet with information on how you're compliant and submit that spreadsheet to a mailing list that hold all the members of the compliance team. The compliance team members are the keepers of the spec, they're software architects, so they quickly understand the domain and can ask pertinent questions about the submission, but there is only so much you can do with a paper-based process. Even if you have an automated system that checks the input, if you don't have a means to actually introspect the process. Be it software or artifacts, you'll never have an ability to truly determine compliance. This is fine. As Eben Moglen says, you want a culture of voluntary compliance around the GPL, you don't want a harsh, introspective enforcement regime. OpenChain gives companies a great start on voluntary compliance, I would trust the process and plug holes that may appear as you go. Starting out with something really heavyweight and expensive will be counterproductive to OpenChain's goals IMHO.

How would one strike that balance between enough structure and enforcement as to be credible, and a lightweight process? I feel strongly that OpenChain has already taken steps in that direction. Having the collection of artifacts and data able to be done online is going to be highly effective -- no gatekeepers in the way. Also, the fact that software can analyze the submissions to check for accuracy and completeness is going to be valuable. What I think can't be replaced is the human judgement needed to ensure that everything adds up. 

In GENIVI, we use a private mailing list for compliance. Only those who've submitted their registration and the compliance team on allowed. Once a registration is sent to GENIVI's mailing list two reviewers are assigned to go through the submission in some detail. They can query those who submitted the registration and nitpick. Then they recommend the submission for approval to the whole compliance team who vote using a majority system with quorum. Most of the time the vote follows the recommendation of the reviewers, nearly always the compliance team is unanimous. Reviewing compliance registrations becomes fairly easy after a while. We promise a turn-around in a couple weeks but the time it takes the engineers to actually review the spreadsheet is only hours. Some folks can quickly suss out if the spreadsheet is actually possible to build in software, but most of the time all we can do is trust that those who've submitted the information aren't lying. The alternative, as we've discussed on many occasions, is a software tool that actually runs on the target hardware. We've seen limited interest in that. 

I strongly suspect that a review process involving humans in combination with software will be the fastest and easiest for OpenChain. 

Cheers,

Jeremiah



--
Jeremiah C. Foster
GENIVI COMMUNITY MANAGER

Pelagicore AB
Ekelundsgatan 4, 6tr, SE-411 18
Gothenburg, Sweden
M: +1.860.772.9242


Re: Slides for today's meeting

Gary O'Neall
 

Hi Miriam and team,

 

There are a number of process related open items for the conformance check website that need resolution before the site can go live.  In listing out the issues, I realized that many of these would need to be resolved even if we were doing the questionnaires manually via documents in email.

 

If there is time on today’s call it would be great to get closure on a few of these issues or discuss a forum and plan to gain closure on the items.

 

The use cases status and open items are documented on the etherpad at https://etherpad.wikimedia.org/p/OpenChainConformance

 

Below is a summary of open items which I believe need resolution prior to going live:

·         Privacy policy – What is required for a privacy policy since we are collecting and storing information provided by businesses?

·         Terms of service – Do we need any terms of service or policy for submitters to follow?

·         Do we need any kind of “click-through” or notice when signing up or when submitting an application (e.g. when submitting, user agrees that it is correct to their knowledge and artifacts can be provided under ?circumstances?)?

·         Should everyone be able to view an accepted certification (see http://openchaindeploy.m6rqmtrixp.us-west-1.elasticbeanstalk.com/certified.html - the site also needs text explanation).

·         What process do we want to put in place to review and confirm submittals?

o   Should we have a distribution list that is notified on new submittals?

o   Do we have one person or a rotating responsibility to review and respond to submittals?

o   Who are the “admins” of the website?

o   What expectations should we have on response time?

o   How automated should it be?

·         Do we need to implement a confirmation that artifacts can be provided or will that be part of the manual confirmation process?

·         How do we handle editing answers after a questionnaire has been submitted?  Do we disallow editing after submittal?

·         Do we need a “printing function”? (note: there is a download to CSV currently)

 

I can also give a 10 minute tour of the questionnaire and admin functions if there is time and interest.

 

Thanks,
Gary

 

From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Miriam Ballhausen
Sent: Monday, November 7, 2016 7:19 AM
To: openchain@...
Subject: [OpenChain] Slides for today's meeting

 

Hi everyone,

 

please find the slides for today’s call attached to this email.

 

Kind regards,

Miriam

 

--

Dr. Miriam Ballhausen

Legal Counsel

 

Telefon: +49 30 200 566 205

Mobil: +49 173 38 567 56
miriam.ballhausen@...

 

 

Alte Jakobstraße 85/86,
10179 Berlin
Deutschland

Telefonzentrale +49 30 200 566 0 Fax +49 30 200 566 1 


www.lumesse.de

 

 

Lumesse

 

 

Lumesse GmbH,
Sitz der Gesellschaft: Flughafenstraße 103, 40474 Düsseldorf
Amtsgericht Düsseldorf, HRB 40857
Geschäftsführer: Dr. Carsten Busch, Michael Hunt.

 


Slides for today's meeting

Miriam Ballhausen <Miriam.Ballhausen@...>
 

Hi everyone,

 

please find the slides for today’s call attached to this email.

 

Kind regards,

Miriam

 

--

Dr. Miriam Ballhausen

Legal Counsel

 

Telefon: +49 30 200 566 205

Mobil: +49 173 38 567 56
miriam.ballhausen@...

 

 

Alte Jakobstraße 85/86,
10179 Berlin
Deutschland

Telefonzentrale +49 30 200 566 0 Fax +49 30 200 566 1 


www.lumesse.de

 

 

Lumesse

 

 

Lumesse GmbH,
Sitz der Gesellschaft: Flughafenstraße 103, 40474 Düsseldorf
Amtsgericht Düsseldorf, HRB 40857
Geschäftsführer: Dr. Carsten Busch, Michael Hunt.

 


Re: Creating a general FAQ for OpenChain

Shane Martin Coughlan <shane@...>
 

Hi Mark

Great points. Adjusted FAQ with some polishing for non-native speakers below for review if time permits on the call today. 

I also wanted to note we may want to adjust the main website page. As you correctly pointed out in your mail below, OpenChain has yet to venture into best practices, but “What is OpenChain” on our landing page mentions companies addressing many friction points and re-creating processes before it talks about compliance. This may lead to some confusion about our emphasis:
Perhaps we could adjust to “OpenChain was created to address FOSS-related friction points in the software supply chain. The focus of OpenChain today is helping to prevent companies redundantly recreating compliance work that upstream companies have already done or should have done."

== Updated FAQ for Discussion ==

What is OpenChain?

The OpenChain Project helps to identify and share the core components of a high quality Free and Open Source Software (FOSS) compliance program. OpenChain conformance builds trust in the supply chain by describing how Open Source license requirements have been met in distributed software.

How does OpenChain work?

The OpenChain Project has three working groups open for anyone to contribute to:
* Specification Working Group - identifies and publishes  a set of core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are adhering to the Specification requirements

There are also three governing committees with paid membership. 
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth. 
* Steering Committee - Development, management and updating of the OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to build an OpenChain compliance ecosystem throughout relevant supply chains in collaboration with the Governing Board

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of FOSS in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance: 
 * https://wiki.linuxfoundation.org/openchain/specification-questions-and-answers
 * https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-answers
 * https://wiki.linuxfoundation.org/openchain/conformance-questions-and-answers

Regards

Shane

On 2016 Oct 31, at 14:53, Gisi, Mark <Mark.Gisi@...> wrote:

What is OpenChain?

The OpenChain Project is focused on identifying common best practices that should be 
applied across a supply chain for efficient and effective compliance with Open Source 
licenses.

OpenChain has yet to venture to far into providing best practices. And although it will in due time I believe it is a secondary objective. I attempted to describe the current objective as follows:

Q: What is OpenChain?

A: The OpenChain Project identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy. Program requirement conformance fosters trust among software supply chain participates that the open source license compliance obligations have been met for the software that one distributes and/or receives.

This is more technical and could benefit from further wordsmithing. It combines the first two questions into one (What is + Mission). It was not my intent to combined them into one question, but I felt a need to mention the mission in order to answer the question "What is OpenChain"

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance

This is another important question to address. I suggest providing a little more detail as follows:

Q: How is the OpenChain Project Organized?

A: The OpenChain Project consists of the following three working groups which are open for anyone to contribute to:
* Specification Working Group - identifies and publishes  a set of core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are adhering to the Specification requirements

And three governing committees that are determined by paid membership. 
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth. 
* Steering Committee - Development, management and updating of the OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to build an OpenChain compliance ecosystem throughout relevant supply chains in collaboration with the Governing Board

- Mark


-----Original Message-----
From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Shane Martin Coughlan
Sent: Sunday, October 30, 2016 7:59 PM
To: openchain@...
Subject: Re: [OpenChain] Creating a general FAQ for OpenChain

Dear all

I wanted to send a reminder on the General FAQ as outlined below. Mike from Linux Foundation is ready to activate this FAQ on our site if there is consensus that it fits requirements. Comments and suggestions welcome.

Regards

Shane

On 2016 Oct 21, at 16:26, Shane Martin Coughlan <shane@...> wrote:

Dear all

We currently have a great website with a link to a FAQ. However, our current FAQ is Specification-centric. Check it out here:
https://www.openchainproject.org/faq
Mark, Miriam and the rest of the team discussed the utility of creating a more general FAQ for our landing page that then leads to specific FAQs for Specification, Curriculum and Conformance. I have taken the liberty of creating a draft for how this general FAQ may look as well as populating the Specification and Curriculum FAQs on the wiki:

What is OpenChain?

The OpenChain Project is focused on identifying common best practices that should be applied across a supply chain for efficient and effective compliance with Open Source licenses.

What is OpenChain’s mission?

The OpenChain Project's mission is to establish requirements to achieve effective management of Free and Open Source Software (FOSS) for software supply chain participants.

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of Free and Open Source Software in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance: 
* https://wiki.linuxfoundation.org/openchain/specification-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/conformance-questions-and-answers

Input, adjustments and improvements welcome!

Regards

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

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


OpenChain (Specification & Curriculum)

Kelly Williams
 

Join the call: https://www.uberconference.com/kellyw
Optional dial in number: 855-889-3011
No PIN needed
If you need to use a local phone number, please consult:
https://www.uberconference.com/international for the specific country numbers.
1. Dial the local number based on your location.
2. Enter 855 889 3011, then #.
 
 


OpenChain (Specification and Conformance)

Kelly Williams
 

Join the call: https://www.uberconference.com/kellyw
Optional dial in number: 855-889-3011
No PIN needed
If you need to use a local phone number, please consult:
https://www.uberconference.com/international for the specific country numbers.
1. Dial the local number based on your location.
2. Enter 855 889 3011, then #.
 
 


Updated Invitation: OpenChain (Specification & Curriculum) @ Monthly from 7pm to 8pm on the third Monday from Mon Jun 20 to Mon Oct 17 (CDT) (kstewart@linuxfoundation.org)

Kate Stewart
 

This event has been changed.

OpenChain (Specification & Curriculum)

Welcome to the Open Chain call on the Specification & Curriculum working group

Agenda and Minutes: https://wiki.linuxfoundation.org/openchain/minutes

Join the call: https://www.uberconference.com/katestewart
Optional dial in number: 877-297-7470
Alternate number: 512-910-4433
No PIN needed

If you need to use a local phone number, please consult:
https://www.uberconference.com/international
for the specific country numbers.

1. Dial the local number based on your location.
2. Enter 512 910 4433, then #.

When
Changed: Monthly from 7pm to 8pm on the third Monday from Mon Jun 20 to Mon Oct 17 Central Time
Where
https://www.uberconference.com/katestewart (map)
Calendar
kstewart@...
Who
Kate Stewart - organizer
Mark.Gisi@...
ballhausen@...
ibrahim.h@...
Michael Dolan
eileen.evans@...
cmaracke@...
jbuttura@...
dmarr@...
shane@...
jilayne.lovejoy@...
Mans Gunnarsson
oliver.fendt@...
kellyw@...
hung.chang@...
mikeyang@...
gunnar.nilsson@...
openchain@...

Going?   All events in this series:   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account openchain@... because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More.


[Update] OpenChain (Specification & Curriculum)

Kate Stewart
 

Hi all, This meeting series is being cancelled, and a replacement invitation will be sent out by Kelly. Please keep an eye open for it, and accept it. Thanks, Kate

OpenChain (Specification & Curriculum)

Welcome to the Open Chain call on the Specification & Curriculum working group

Agenda and Minutes: https://wiki.linuxfoundation.org/openchain/minutes

Join the call: https://www.uberconference.com/katestewart
Optional dial in number: 877-297-7470
Alternate number: 512-910-4433
No PIN needed

If you need to use a local phone number, please consult:
https://www.uberconference.com/international
for the specific country numbers.

1. Dial the local number based on your location.
2. Enter 512 910 4433, then #.

When
Mon Nov 21, 2016 7pm – 8pm Central Time
Where
https://www.uberconference.com/katestewart (map)
Who
Kate Stewart - organizer
oliver.fendt@...
Mans Gunnarsson
cmaracke@...
Michael Dolan
ibrahim.h@...
kellyw@...
openchain@...
hung.chang@...
Mark.Gisi@...
dmarr@...
eileen.evans@...
ballhausen@...
mikeyang@...
gunnar.nilsson@...
jilayne.lovejoy@...
jbuttura@...
shane@...


Updated Invitation: OpenChain (Specification & Conformance ) @ Monthly from 11am to 12pm on the first Monday from Mon Oct 3 to Mon Oct 3 (CDT) (kstewart@linuxfoundation.org)

Kate Stewart
 

This event has been changed.

OpenChain (Specification & Conformance )

Welcome to the Open Chain call for the Specification & Certification working groups

Agenda and Minutes: https://wiki.linuxfoundation.org/openchain/minutes

Join the call: https://www.uberconference.com/katestewart
Optional dial in number: 877-297-7470
Alternate number: 512-910-4433
No PIN needed

If you need to use a local phone number, please consult:
https://www.uberconference.com/international
for the specific country numbers.

1. Dial the local number based on your location.
2. Enter 512 910 4433, then #.

When
Changed: Monthly from 11am to 12pm on the first Monday from Mon Oct 3 to Mon Oct 3 Central Time
Where
https://www.uberconference.com/katestewart (map)
Calendar
kstewart@...
Who
Kate Stewart - organizer
openchain@...
oliver.fendt@...
cmaracke@...
dmarr@...
kellyw@...
gunnar.nilsson@...
mikeyang@...
jbuttura@...
hung.chang@...
jilayne.lovejoy@...
Mans Gunnarsson
miriam.ballhausen@...
ibrahim.h@...
shane@...
eileen.evans@...
Mark.Gisi@...
mans.gunnerson@...

Going?   All events in this series:   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account openchain@... because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

Forwarding this invitation could allow any recipient to modify your RSVP response. Learn More.


[Update] OpenChain (Specification & Conformance )

Kate Stewart
 

cancelling this meeting - a replacement will be sent by Kelly. Please look for it. Thanks, Kate

OpenChain (Specification & Conformance )

Welcome to the Open Chain call for the Specification & Certification working groups

Agenda and Minutes: https://wiki.linuxfoundation.org/openchain/minutes

Join the call: https://www.uberconference.com/katestewart
Optional dial in number: 877-297-7470
Alternate number: 512-910-4433
No PIN needed

If you need to use a local phone number, please consult:
https://www.uberconference.com/international
for the specific country numbers.

1. Dial the local number based on your location.
2. Enter 512 910 4433, then #.

When
Mon Nov 7, 2016 11am – 12pm Central Time
Where
https://www.uberconference.com/katestewart (map)
Who
Kate Stewart - organizer
mikeyang@...
eileen.evans@...
ibrahim.h@...
Mark.Gisi@...
dmarr@...
kellyw@...
gunnar.nilsson@...
jilayne.lovejoy@...
mans.gunnerson@...
hung.chang@...
Mans Gunnarsson
shane@...
cmaracke@...
jbuttura@...
oliver.fendt@...
miriam.ballhausen@...
openchain@...


Updated UberConference

Kelly Williams
 

Hi Everyone,

 

You will receive shortly updated meeting invites for the OpenChain meetings as we are moving to a new UberConference line.  Kate Stewart will send out a cancellation and I will send out the updated invites with the new link.

 

Thanks,
Kelly


Re: Creating a general FAQ for OpenChain

Mark Gisi
 

What is OpenChain?

The OpenChain Project is focused on identifying common best practices that should be
applied across a supply chain for efficient and effective compliance with Open Source
licenses.
OpenChain has yet to venture to far into providing best practices. And although it will in due time I believe it is a secondary objective. I attempted to describe the current objective as follows:

Q: What is OpenChain?

A: The OpenChain Project identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy. Program requirement conformance fosters trust among software supply chain participates that the open source license compliance obligations have been met for the software that one distributes and/or receives.

This is more technical and could benefit from further wordsmithing. It combines the first two questions into one (What is + Mission). It was not my intent to combined them into one question, but I felt a need to mention the mission in order to answer the question "What is OpenChain"

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance
This is another important question to address. I suggest providing a little more detail as follows:

Q: How is the OpenChain Project Organized?

A: The OpenChain Project consists of the following three working groups which are open for anyone to contribute to:
* Specification Working Group - identifies and publishes a set of core requirements a quality FOSS compliance program should satisfy
* Curriculum Working Group - provides training material to help companies meeting the Specification education requirements.
* Conformance Working Group - helps companies check that they are adhering to the Specification requirements

And three governing committees that are determined by paid membership.
* Governing Board - Manage policies or rules and procedures for the Project, fund raising, budgeting and so forth.
* Steering Committee - Development, management and updating of the OpenChain Compliance Specification
* Outreach Committee - designing, developing and executing efforts to build an OpenChain compliance ecosystem throughout relevant supply chains in collaboration with the Governing Board

- Mark


-----Original Message-----
From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Shane Martin Coughlan
Sent: Sunday, October 30, 2016 7:59 PM
To: openchain@...
Subject: Re: [OpenChain] Creating a general FAQ for OpenChain

Dear all

I wanted to send a reminder on the General FAQ as outlined below. Mike from Linux Foundation is ready to activate this FAQ on our site if there is consensus that it fits requirements. Comments and suggestions welcome.

Regards

Shane

On 2016 Oct 21, at 16:26, Shane Martin Coughlan <shane@...> wrote:

Dear all

We currently have a great website with a link to a FAQ. However, our current FAQ is Specification-centric. Check it out here:
https://www.openchainproject.org/faq
Mark, Miriam and the rest of the team discussed the utility of creating a more general FAQ for our landing page that then leads to specific FAQs for Specification, Curriculum and Conformance. I have taken the liberty of creating a draft for how this general FAQ may look as well as populating the Specification and Curriculum FAQs on the wiki:

What is OpenChain?

The OpenChain Project is focused on identifying common best practices that should be applied across a supply chain for efficient and effective compliance with Open Source licenses.

What is OpenChain’s mission?

The OpenChain Project's mission is to establish requirements to achieve effective management of Free and Open Source Software (FOSS) for software supply chain participants.

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of Free and Open Source Software in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance:
* https://wiki.linuxfoundation.org/openchain/specification-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/conformance-questions-and-answers

Input, adjustments and improvements welcome!

Regards

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


Re: Creating a general FAQ for OpenChain

Shane Martin Coughlan <shane@...>
 

Dear all

I wanted to send a reminder on the General FAQ as outlined below. Mike from Linux Foundation is ready to activate this FAQ on our site if there is consensus that it fits requirements. Comments and suggestions welcome.

Regards

Shane

On 2016 Oct 21, at 16:26, Shane Martin Coughlan <shane@...> wrote:

Dear all

We currently have a great website with a link to a FAQ. However, our current FAQ is Specification-centric. Check it out here:
https://www.openchainproject.org/faq
Mark, Miriam and the rest of the team discussed the utility of creating a more general FAQ for our landing page that then leads to specific FAQs for Specification, Curriculum and Conformance. I have taken the liberty of creating a draft for how this general FAQ may look as well as populating the Specification and Curriculum FAQs on the wiki:

What is OpenChain?

The OpenChain Project is focused on identifying common best practices that should be applied across a supply chain for efficient and effective compliance with Open Source licenses.

What is OpenChain’s mission?

The OpenChain Project's mission is to establish requirements to achieve effective management of Free and Open Source Software (FOSS) for software supply chain participants.

How does OpenChain work?

There are three parts to the OpenChain Project:
* OpenChain Specification
* OpenChain Curriculum
* OpenChain Conformance

The Specification is the heart of OpenChain. It describes the processes required to achieve effective management of Free and Open Source Software in the supply chain. OpenChain Curriculum provides training material to help companies meeting the Specification requirements. OpenChain Conformance helps companies check that they are adhering to the Specification requirements.

Where can I learn more about each aspect of OpenChain?

There are Frequently Asked Question (FAQ) pages for Specification, Curriculum and Conformance:
* https://wiki.linuxfoundation.org/openchain/specification-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/curriculum-questions-and-answers
* https://wiki.linuxfoundation.org/openchain/conformance-questions-and-answers

Input, adjustments and improvements welcome!

Regards

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


Re: Does the openchain-curriculum-release-1.pptx have CONFIDENTIAL of OpenLogic ?

Shane Martin Coughlan <shane@...>
 

Hi fu7mu4

Thank you for reporting an issue. We have fixed the issue. It was simply an “artifact” from old slides. OpenChain’s material is made from many different contributors. We have worked to remove all identifying material and will continue to fix any issues identified.

It looks like you want to help with our project. That is deeply appreciated. We are always glad to have new contributors. However, there are a couple of points I would like to make about our “Open Source” work practice:

(1) We prefer bugs to be reported on our lists or on our calls. It is not our normal practice to post bugs on private blogs. There is a very simple reason for this: the bug you reported is now fixed, but your blog post remains, so it is no longer accurate. For this reason, I would appreciate if you could remove that post, and report future bugs direct to this list.

(2) We also prefer to use real names. This is a wonderful community of contributors from many companies. Some of us have known each other for years. Some of us only met recently. However, we like to use our real names in emails and calls so that we can build great professional relationships. If you could let us know who you are that would be appreciated too. Actually, I live in Japan, and may have a chance to meet you at events there.

Thank you for your understanding and I look forward to collaborating with you on our first translation of the OpenChain slides into Japanese.

Regards

Shane

On 2016 Oct 23, at 6:08, J Lovejoy <opensource@...> wrote:

Hi,

This artifact appearing in the footer is a mistake, which we’ll fix. Thanks for bringing it to our attention.


Jilayne


On Oct 22, 2016, at 9:56 AM, fu7mu4 <fu7mu4@...> wrote:

Hi

I found the notice "CONFIDENTIAL - (C) OpenLogic" at the footer in bottom of note on each slides in openchain-curriculum-release-1.pptx

Is it okey ?

see my blog short article for images.
http://d.hatena.ne.jp/fu7mu4/20161022/1477149930

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


Re: What is the license of the openchain comformance specification 1.0 ?

Mark Gisi
 

Thank you Matija and Joseph for your input on the spec licensing. We will discuss it at the next working meeting  on November 7 @ 9am Pacific Standard Time (PST). All are welcome. After having a discussion and obtaining guidance from the Linux Foundation we will present the license choice and the rationale to this group.

 

How to Participate: For those new to the OpenChain project we meet on the first and third Monday of each month. On the first Monday we meet at 9am PST to accommodate EMEA (Europe, the Middle East and Africa) and discuss the spec and spec conformance. For the third Monday we meet at 5pm PST to accommodate Asia and discuss the spec and curriculum.

 

Best,

- Mark

 

 

From: openchain-bounces@... [mailto:openchain-bounces@...] On Behalf Of Joseph Potvin
Sent: Sunday, October 23, 2016 2:22 AM
To: openchain@...
Subject: Re: [OpenChain] What is the license of the openchain comformance specification 1.0 ?

 

RE: CC-BY 3.0

Should it not be updated to CC-BY 4.0?
https://creativecommons.org/licenses/by/4.0/

(BTW, Kudos to all for advancing this to v1.0, and apologies for going from active participant at the beginning to just a quiet observer due to workload. Wonderful to see it's now an industry reference.)


Joseph Potvin
Operations Manager | Gestionnaire des opérations
The Opman Company | La compagnie Opman
jpotvin@...
Mobile: 819-593-5983

 

On Sat, Oct 22, 2016 at 5:02 PM, Matija Šuklje <matija@...> wrote:

Die 21. 10. 16 et hora 19.53.35 fu7mu4 scripsit:
> I want to translate the specification into Japanese.
> But I could not find the license of the specification.
> Please tell me the license of that.

According to the standard LF’s ToS <https://www.linuxfoundation.org/terms>
that the website seems to be under:

“Except as otherwise provided, Content on this site, including all materials
posted by the The Linux Foundation, is licensed under a Creative Commons
Attribution 3.0 License.”

As the specification’s PDF doesn’t seem to mention any other licence I’d say
it’s under CC-By 3.0.

I’d be very happy to be corrected by people who are much more involved than I.


cheers,
Matija
--
gsm:    tel:+386.41.849.552
www:    http://matija.suklje.name
xmpp:   matija.suklje@...
sip:    sip:matija_suklje@...

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

 


Re: What is the license of the openchain comformance specification 1.0 ?

Joseph Potvin
 

RE: CC-BY 3.0

Should it not be updated to CC-BY 4.0?
https://creativecommons.org/licenses/by/4.0/

(BTW, Kudos to all for advancing this to v1.0, and apologies for going from active participant at the beginning to just a quiet observer due to workload. Wonderful to see it's now an industry reference.)

Joseph Potvin
Operations Manager | Gestionnaire des opérations
The Opman Company | La compagnie Opman
jpotvin@...
Mobile: 819-593-5983

On Sat, Oct 22, 2016 at 5:02 PM, Matija Šuklje <matija@...> wrote:
Die 21. 10. 16 et hora 19.53.35 fu7mu4 scripsit:
> I want to translate the specification into Japanese.
> But I could not find the license of the specification.
> Please tell me the license of that.

According to the standard LF’s ToS <https://www.linuxfoundation.org/terms>
that the website seems to be under:

“Except as otherwise provided, Content on this site, including all materials
posted by the The Linux Foundation, is licensed under a Creative Commons
Attribution 3.0 License.”

As the specification’s PDF doesn’t seem to mention any other licence I’d say
it’s under CC-By 3.0.

I’d be very happy to be corrected by people who are much more involved than I.


cheers,
Matija
--
gsm:    tel:+386.41.849.552
www:    http://matija.suklje.name
xmpp:   matija.suklje@...
sip:    sip:matija_suklje@...

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



Re: Does the openchain-curriculum-release-1.pptx have CONFIDENTIAL of OpenLogic ?

J Lovejoy
 

Hi,

This artifact appearing in the footer is a mistake, which we’ll fix. Thanks for bringing it to our attention.


Jilayne


On Oct 22, 2016, at 9:56 AM, fu7mu4 <fu7mu4@...> wrote:

Hi

I found the notice "CONFIDENTIAL - (C) OpenLogic" at the footer in bottom of note on each slides in openchain-curriculum-release-1.pptx

Is it okey ?

see my blog short article for images.
http://d.hatena.ne.jp/fu7mu4/20161022/1477149930

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


Re: What is the license of the openchain comformance specification 1.0 ?

Matija Šuklje
 

Die 21. 10. 16 et hora 19.53.35 fu7mu4 scripsit:
I want to translate the specification into Japanese.
But I could not find the license of the specification.
Please tell me the license of that.
According to the standard LF’s ToS <https://www.linuxfoundation.org/terms>
that the website seems to be under:

“Except as otherwise provided, Content on this site, including all materials
posted by the The Linux Foundation, is licensed under a Creative Commons
Attribution 3.0 License.”

As the specification’s PDF doesn’t seem to mention any other licence I’d say
it’s under CC-By 3.0.

I’d be very happy to be corrected by people who are much more involved than I.


cheers,
Matija
--
gsm: tel:+386.41.849.552
www: http://matija.suklje.name
xmpp: matija.suklje@...
sip: sip:matija_suklje@...

4281 - 4300 of 4814