General Meeting/Minutes/2010-08-11 - Revision history

MartinMichlmayr: Convert to MediaWiki syntax

2013-03-06T10:59:20Z

Convert to MediaWiki syntax

Show changes

Podence at 11:27, 10 September 2010

2010-09-10T11:27:27Z

Podence at 13:15, 30 August 2010

2010-08-30T13:15:58Z

Podence at 13:15, 30 August 2010

2010-08-30T13:15:08Z

Show changes

Podence at 13:14, 30 August 2010

2010-08-30T13:14:11Z

Podence at 13:12, 30 August 2010

2010-08-30T13:12:33Z

New page

Minutes - 2010/08/11 LinuxCon2010 Boston SPDX BOF Current status:  - need to focus on goals for next 3 months - SPDX.org rollout,  shadows fossbazaar.org for data. - mail list transfering to spdx@fossbazaar.org with  self subscription to mail list now possible, and  public archives. - package-facts@fossbazaar.org now depreciated,  mail list there will remain private, per original  commitment.   Web site overview:  - site design is still evolving, participation welcome.  - log in to comment on wiki etc. - anyone can blog on site, and postings on topic welcome. - presentation material available on site for outreach support. - AI: Phil/Martin - update on participation page where to join       (suggestion was to put link in text, not just at top,        consider "I want to use the spec, vs. I want to contribute       to the spec). - AI: Kate to transfer document (.pdf) back to WIKI. - AI: Phil update standard presentation with LinuxCon2010 input - AI: Kate clean up the sharing analysis to what is accurate - AI: Kate publish the current version number of the specification             in brackets behind reference.   - License Discussion: - Look at Fedora's approach as a single page.   Example license text - canonical form.     Good from tooling perspective.  Suck info off the pages.     HTML at low technical level is easy.  RDF? - see fedoraproject.org/wiki/License- licenses table.  - Used License Text - uses tag to identify in page  Fedora provide notes, and canonical text. - For SPDX problem is where store templated version?  Suggestion is to use come up with standardized naming  of the sections, and embed the text of the licence  "template" version, so it shows up on the "official"  license page. (example to consider, verify that BSD  hasn't been modified and do it with a template). - Fields to put on each "web license WIKI page"  - short form name  - long form name  - link to formal license  - notes on license  - full license text  - template version - Note: need to figure out and document how to add a license  (ie. When you add a license - 1) create separate page;           raw template text, user visible text - here's out how         embed this text.  etc.) - AI: Tom to define a proposal for user front page.         Decide section names to correspond to spec - AI: Group: discuss further following questions: - what does it mean to be "on the list" for a license. - what is it going to take to add and maintain a license. - Consider when english isn't spoken language?  (what can be translated, what can't, work into template) - roll out - operational aspects - what do we want to get accomplished? - divy out and how get accomplished? - Target to have spec at 1.0 in 2010Q4 - What are building blocks needed?   Consider: documenting tooling;  training;  how to use..... - Strong feeling one shot to get this right, want  free and comercial tool support available for supply chain. - AI:  Kim & John to work on operationalize plan.    (including a date can tell supply chain people?      GOAL is understand a date to have industry   changing/financially impacting.   Tie to next LinuxCon??)

← Older revision		Revision as of 13:15, 30 August 2010
Line 1:		Line 1:
−	<p>Minutes - 2010/08/11 LinuxCon2010 Boston SPDX BOF</p>	+	<p>Scuse the lousy formatting. I'm working on it. Phil</p><p> </p><p>Minutes - 2010/08/11 LinuxCon2010 Boston SPDX BOF</p>

	<p> </p>		<p> </p>

← Older revision		Revision as of 13:14, 30 August 2010
Line 1:		Line 1:
−	<p><p>Minutes - 2010/08/11 LinuxCon2010 Boston SPDX BOF</p><p>~~ ~~</p><p>Current status: </p><~~p><span style="white-space: pre;"> </span~~>- need to focus on goals for next 3 months</p><~~p><span style="white-space: pre;"> </span~~>- SPDX.org rollout,  shadows fossbazaar.org for data.</p><~~p><span style="white-space: pre;"> </span~~>- mail list transfering to spdx@fossbazaar.org with</p><~~p><span style="white-space: pre;"> </span~~>  self subscription to mail list now possible, and</p><~~p><span style="white-space: pre;"> </span~~>  public archives.</p><~~p><span style="white-space: pre;"> </span~~>- package-facts@fossbazaar.org now depreciated,</p><~~p><span style="white-space: pre;"> </span~~>  mail list there will remain private, per original</p><~~p><span style="white-space: pre;"> </span~~>  commitment.</p><p>~~ ~~</p><~~p> </p><p> </p><p~~>Web site overview: </p><~~p><span style="white-space: pre;"> </span~~>- site design is still evolving, participation welcome. </p><~~p><span style="white-space: pre;"> </span~~>- log in to comment on wiki etc.</p><~~p><span style="white-space: pre;"> </span~~>- anyone can blog on site, and postings on topic welcome.</p><~~p><span style="white-space: pre;"> </span~~>- presentation material available on site for outreach support.</p><~~p><span style="white-space: pre;"> </span~~>- AI: Phil/Martin - update on participation page where to join </p><~~p><span style="white-space: pre;"> </span~~>      (suggestion was to put link in text, not just at top, </p><~~p><span style="white-space: pre;"> </span~~>       consider "I want to use the spec, vs. I want to contribute</p><~~p><span style="white-space: pre;"> </span~~>       to the spec).</p><~~p><span style="white-space: pre;"> </span~~>- AI: Kate to transfer document (.pdf) back to WIKI.</p><~~p><span style="white-space: pre;"> </span~~>- AI: Phil update standard presentation with LinuxCon2010 input</p><~~p><span style="white-space: pre;"> </span~~>- AI: Kate clean up the sharing analysis to what is accurate</p><~~p><span style="white-space: pre;"> </span~~>- AI: Kate publish the current version number of the specification</p><p>             in brackets behind reference. </p><p>~~ ~~</p><~~p> </p><p~~>- License Discussion:</p><~~p><span style="white-space: pre;"> </span~~>- Look at Fedora's approach as a single page. </p><~~p><span style="white-space: pre;"> </span~~>  Example license text - canonical form.   </p><~~p><span style="white-space: pre;"> </span~~>  Good from tooling perspective.  Suck info off the pages.   </p><~~p><span style="white-space: pre;"> </span~~>  HTML at low technical level is easy.  RDF?</p><~~p><span style="white-space: pre;"> </span~~>- see fedoraproject.org/wiki/License- licenses table. </p><~~p><span style="white-space: pre;"> </span~~>- Used License Text - uses tag to identify in page</p><~~p><span style="white-space: pre;"> </span~~>  Fedora provide notes, and canonical text.</p><~~p><span style="white-space: pre;"> </span~~>- For SPDX problem is where store templated version?</p><~~p><span style="white-space: pre;"> </span~~>  Suggestion is to use come up with standardized naming</p><~~p><span style="white-space: pre;"> </span~~>  of the sections, and embed the text of the licence</p><~~p><span style="white-space: pre;"> </span~~>  "template" version, so it shows up on the "official"</p><~~p><span style="white-space: pre;"> </span~~>  license page. (example to consider, verify that BSD</p><~~p><span style="white-space: pre;"> </span~~>  hasn't been modified and do it with a template).</p><~~p><span style="white-space: pre;"> </span~~>- Fields to put on each "web license WIKI page"</p><~~p><span style="white-space: pre;"> </span~~>  - short form name</p><~~p><span style="white-space: pre;"> </span~~>  - long form name</p><~~p><span style="white-space: pre;"> </span~~>  - link to formal license</p><~~p><span style="white-space: pre;"> </span~~>  - notes on license</p><~~p><span style="white-space: pre;"> </span~~>  - full license text</p><~~p><span style="white-space: pre;"> </span~~>  - template version</p><~~p><span style="white-space: pre;"> </span~~>- Note: need to figure out and document how to add a license</p><~~p><span style="white-space: pre;"> </span~~>  (ie. When you add a license - 1) create separate page;  </p><p>         raw template text, user visible text - here's out how</p><p>         embed this text.  etc.)</p><~~p><span style="white-space: pre;"> </span~~>- AI: Tom to define a proposal for user front page.</p><p>         Decide section names to correspond to spec</p><~~p><span style="white-space: pre;"> </span~~>- AI: Group: discuss further following questions:</p><~~p><span style="white-space: pre;"~~> ~~</span>~~- what does it mean to be "on the list" for a license.</p><~~p><span style="white-space: pre;"~~> ~~</span>~~- what is it going to take to add and maintain a license.</p><~~p><span style="white-space: pre;"~~> ~~</span>~~- Consider when english isn't spoken language?</p><~~p><span style="white-space: pre;"> </span~~>  (what can be translated, what can't, work into template)</p><p>~~ ~~</p><p>- roll out - operational aspects</p><~~p><span style="white-space: pre;"> </span~~>- what do we want to get accomplished?</p><~~p><span style="white-space: pre;"> </span~~>- divy out and how get accomplished?</p><~~p><span style="white-space: pre;"> </span~~>- Target to have spec at 1.0 in 2010Q4</p><~~p><span style="white-space: pre;"> </span~~>- What are building blocks needed? </p><~~p><span style="white-space: pre;"> </span~~>  Consider: documenting tooling;  training;  how to use.....</p><~~p><span style="white-space: pre;"> </span~~>- Strong feeling one shot to get this right, want</p><~~p><span style="white-space: pre;"> </span~~>  free and comercial tool support available for supply chain.</p><~~p><span style="white-space: pre;"> </span~~>- AI:  Kim & John to work on operationalize plan.  </p><~~p><span style="white-space: pre;"> </span~~>  (including a date can tell supply chain people?    </p><~~p><span style="white-space: pre;"> </span~~>  GOAL is understand a date to have industry </p><~~p><span style="white-space: pre;"> </span~~>  changing/financially impacting.   Tie to next LinuxCon??)</p></p>	+	<p> </p><p><div>Minutes - 2010/08/11 LinuxCon2010 Boston SPDX BOF</div><div></div><div>Current status: </div><div> - need to focus on goals for next 3 months</div><div> - SPDX.org rollout,  shadows fossbazaar.org for data.</div><div> - mail list transfering to spdx@fossbazaar.org with</div><div>  self subscription to mail list now possible, and</div><div>  public archives.</div><div> - package-facts@fossbazaar.org now depreciated,</div><div>  mail list there will remain private, per original</div><div>  commitment.</div><div></div><div>Web site overview: </div><div> - site design is still evolving, participation welcome. </div><div> - log in to comment on wiki etc.</div><div> - anyone can blog on site, and postings on topic welcome.</div><div> - presentation material available on site for outreach support.</div><div> - AI: Phil/Martin - update on participation page where to join </div><div>      (suggestion was to put link in text, not just at top, </div><div>       consider "I want to use the spec, vs. I want to contribute</div><div>       to the spec).</div><div> - AI: Kate to transfer document (.pdf) back to WIKI.</div><div> - AI: Phil update standard presentation with LinuxCon2010 input</div><div> - AI: Kate clean up the sharing analysis to what is accurate</div><div> - AI: Kate publish the current version number of the specification</div><div>             in brackets behind reference. </div><div></div><div>- License Discussion:</div><div> - Look at Fedora's approach as a single page. </div><div>  Example license text - canonical form.   </div><div>  Good from tooling perspective.  Suck info off the pages.   </div><div>  HTML at low technical level is easy.  RDF?</div><div> - see fedoraproject.org/wiki/License- licenses table. </div><div> - Used License Text - uses tag to identify in page</div><div>  Fedora provide notes, and canonical text.</div><div> - For SPDX problem is where store templated version?</div><div>  Suggestion is to use come up with standardized naming</div><div>  of the sections, and embed the text of the licence</div><div>  "template" version, so it shows up on the "official"</div><div>  license page. (example to consider, verify that BSD</div><div>  hasn't been modified and do it with a template).</div><div> - Fields to put on each "web license WIKI page"</div><div>  - short form name</div><div>  - long form name</div><div>  - link to formal license</div><div>  - notes on license</div><div>  - full license text</div><div>  - template version</div><div> - Note: need to figure out and document how to add a license</div><div>  (ie. When you add a license - 1) create separate page;  </div><div>         raw template text, user visible text - here's out how</div><div>         embed this text.  etc.)</div><div> - AI: Tom to define a proposal for user front page.</div><div>         Decide section names to correspond to spec</div><div> - AI: Group: discuss further following questions:</div><div> - what does it mean to be "on the list" for a license.</div><div> - what is it going to take to add and maintain a license.</div><div> - Consider when english isn't spoken language?</div><div>  (what can be translated, what can't, work into template)</div><div></div><div></div><div>- roll out - operational aspects</div><div> - what do we want to get accomplished?</div><div> - divy out and how get accomplished?</div><div> - Target to have spec at 1.0 in 2010Q4</div><div> - What are building blocks needed? </div><div>  Consider: documenting tooling;  training;  how to use.....</div><div> - Strong feeling one shot to get this right, want</div><div>  free and comercial tool support available for supply chain.</div><div> - AI:  Kim & John to work on operationalize plan.  </div><div>  (including a date can tell supply chain people?    </div><div>  GOAL is understand a date to have industry </div><div>  changing/financially impacting.   Tie to next LinuxCon??)</div></p><p> </p>

← Older revision	Revision as of 11:27, 10 September 2010
(No difference)