|
Specification 3.0 Draft/Review Meeting - June 8th @ 9am PST
As Shane announced last week - we will be meeting today (9am PST) to discuss the next version of the OpenChain specification (3.0) Note – there is a password (123456) Join Zoom Meeting https://windriv
As Shane announced last week - we will be meeting today (9am PST) to discuss the next version of the OpenChain specification (3.0) Note – there is a password (123456) Join Zoom Meeting https://windriv
|
By
Mark Gisi
· #3193
·
|
|
It is official – we are now seeking public comments for ISO submission version 2.1 of the Specification
Dear OpenChain Community, We are now seeking broader public comments for ISO submission version 2.1 of the Specification which will conclude on December 10th. This is the last major step in the spec d
Dear OpenChain Community, We are now seeking broader public comments for ISO submission version 2.1 of the Specification which will conclude on December 10th. This is the last major step in the spec d
|
By
Mark Gisi
· #2675
·
|
|
OpenChain’s value proposition is bigger than you think
Shane - Ok. Sounds good.
By
Mark Gisi
· #2654
·
|
|
Spec Version 2.1 release schedule and status
We will continue to accept feedback on version 2.1 of specification up through Thursday October 31st. We will be holding a F2F meeting/workshop at the Open Source Summit conference in Lyon tomorrow (O
We will continue to accept feedback on version 2.1 of specification up through Thursday October 31st. We will be holding a F2F meeting/workshop at the Open Source Summit conference in Lyon tomorrow (O
|
By
Mark Gisi
· #2651
·
|
|
OpenChain’s value proposition is bigger than you think
OpenChain specification conformance extends trust to security vulnerability assurance. That is, OpenChain conforming suppliers are better positioned to manage security vulnerabilities because of the b
OpenChain specification conformance extends trust to security vulnerability assurance. That is, OpenChain conforming suppliers are better positioned to manage security vulnerabilities because of the b
|
By
Mark Gisi
· #2648
·
|
|
Latest draft of the next spec verision 2.1 - Last call for feeback.
Reminder: the next version of the specification (spec) will largely involve converting the current 2.0 version into an ISO format for submission for ISO adoption. Therefore we are only considering sma
Reminder: the next version of the specification (spec) will largely involve converting the current 2.0 version into an ISO format for submission for ISO adoption. Therefore we are only considering sma
|
By
Mark Gisi
· #2642
·
|
|
Latest OpenChain Specification 2.1 ISO draft (Sept 1st)
The latest draft of the next version of OpenChain Specification can be found here: https://wiki.linuxfoundation.org/_media/openchain/OpenChainSpec-2.1.draft.MarkUp.pdf Our objective is to make only mi
The latest draft of the next version of OpenChain Specification can be found here: https://wiki.linuxfoundation.org/_media/openchain/OpenChainSpec-2.1.draft.MarkUp.pdf Our objective is to make only mi
|
By
Mark Gisi
· #2547
·
|
|
Reminder: Spec development takes place on the spec mailiing list
Reminder: If you would like to actively contribute to the development of the next version of the spec (or just follow along) you should subscribe to the spec mailing list: https://lists.linuxfoundatio
Reminder: If you would like to actively contribute to the development of the next version of the spec (or just follow along) you should subscribe to the spec mailing list: https://lists.linuxfoundatio
|
By
Mark Gisi
· #2477
·
|
|
Question: Difference between “attribution notices” and “attribution requirements”
This is a reasonable objective. We need to formally commit to that. If we are going to keep the "2" in the version I would be reluctant to change anything other than formatting. That is, the semantics
This is a reasonable objective. We need to formally commit to that. If we are going to keep the "2" in the version I would be reluctant to change anything other than formatting. That is, the semantics
|
By
Mark Gisi
· #2472
·
|
|
Question: Difference between “attribution notices” and “attribution requirements”
I will queue the items up in the github wiki so that we can begin to review each in turn. I attached the latest format. I accepts Rex’s comments (seem reasonable -e.g., might vs may, ...). I did adjus
I will queue the items up in the github wiki so that we can begin to review each in turn. I attached the latest format. I accepts Rex’s comments (seem reasonable -e.g., might vs may, ...). I did adjus
|
By
Mark Gisi
· #2469
·
|
|
How do we encourage collaborative development INTERNALLY? (so far)
Hi Masao, Sorry for the delayed follow up. We have had success employing Open Development principles to solve a similar problem. I would not categorize it so much as Inner Source, but more as Open Inn
Hi Masao, Sorry for the delayed follow up. We have had success employing Open Development principles to solve a similar problem. I would not categorize it so much as Inner Source, but more as Open Inn
|
By
Mark Gisi
· #2253
·
|
|
OpenChain Spec 2.0 (Draft) in Word Format
Hi Shoken, Shane is in the process of reorganizing the translation repositories on github. Once that is settled we could give directions how to upload your draft. If you want to temporarily place a dr
Hi Shoken, Shane is in the process of reorganizing the translation repositories on github. Once that is settled we could give directions how to upload your draft. If you want to temporarily place a dr
|
By
Mark Gisi
· #2207
·
|
|
A substantial OpenChain Proposal - Unifying our GitHub Library of Material
Alexios - good point. The repo use grew during the version 2.0 drafting and see that trend continuing with the next version (which will mean more pull requests). Another consideration could be a hybri
Alexios - good point. The repo use grew during the version 2.0 drafting and see that trend continuing with the next version (which will mean more pull requests). Another consideration could be a hybri
|
By
Mark Gisi
· #2203
·
|
|
OpenChain Specification 2.0 - 5 days to go ...
The OpenChain Specification version 2.0 is nearly ready as we enter the last 5 days of the 14 day freeze period. This period provides everyone the chance to review the final draft - where we can accep
The OpenChain Specification version 2.0 is nearly ready as we enter the last 5 days of the 14 day freeze period. This period provides everyone the chance to review the final draft - where we can accep
|
By
Mark Gisi
· #2188
·
|
|
OpenChain Spec 2.0 (Draft) in Word Format
Thank you Haksung. I added the markdown template to the spec’s github repo: https://github.com/OpenChain-Project/Specification/tree/master/version/2.0 - Mark
Thank you Haksung. I added the markdown template to the spec’s github repo: https://github.com/OpenChain-Project/Specification/tree/master/version/2.0 - Mark
|
By
Mark Gisi
· #2185
·
|
|
OpenChain Spec 2.0 (Draft) in Word Format
The spec translation templates can be found on github: https://github.com/OpenChain-Project/Specification The 2.0 template specifically can be found here: https://github.com/OpenChain-Project/Specific
The spec translation templates can be found on github: https://github.com/OpenChain-Project/Specification The 2.0 template specifically can be found here: https://github.com/OpenChain-Project/Specific
|
By
Mark Gisi
· #2177
·
|
|
OpenChain 2.0 draft has entered the final 14 day freeze period
The OpenChain Specification version 2.0 draft is nearly ready as we enter the 14 day freeze period. This period provides everyone the chance to review the final draft which includes feedback incorpora
The OpenChain Specification version 2.0 draft is nearly ready as we enter the 14 day freeze period. This period provides everyone the chance to review the final draft which includes feedback incorpora
|
By
Mark Gisi
· #2159
·
|
|
2 days left - Latest OpenChain Specification 2.0 draft (March 20th)
Only 2 days remain - this is YOUR last opportunity to suggest changes to versions 2.0 of the spec. The latest draft of the next version of OpenChain Specification can be found here: https://wiki.linux
Only 2 days remain - this is YOUR last opportunity to suggest changes to versions 2.0 of the spec. The latest draft of the next version of OpenChain Specification can be found here: https://wiki.linux
|
By
Mark Gisi
· #2155
·
|
|
Latest OpenChain Specification 2.0 draft (March 10th)
Time is running out - this is the last opportunity to contribute suggestions for materials changes to versions 2.0 of the spec. The latest draft of the next version of OpenChain Specification can be f
Time is running out - this is the last opportunity to contribute suggestions for materials changes to versions 2.0 of the spec. The latest draft of the next version of OpenChain Specification can be f
|
By
Mark Gisi
· #2131
·
|
|
Latest OpenChain Specification 2.0 draft (March 2nd)
The latest draft of the next version of OpenChain Specification can be found here: https://wiki.linuxfoundation.org/_media/openchain/openchainspec-2.0.draft.pdf A marked up version can be found here:
The latest draft of the next version of OpenChain Specification can be found here: https://wiki.linuxfoundation.org/_media/openchain/openchainspec-2.0.draft.pdf A marked up version can be found here:
|
By
Mark Gisi
· #2116
·
|