THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx

Difference between revisions of "Business Team/Minutes/2011-09-01"

From SPDX Wiki
Jump to: navigation, search
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
−
<p>Attendees</p><ul><li>Michael Herzog</li><li>Phil Odence</li><li>Kirsten Newcomer</li><li>Jilayne Lovejoy</li><li>Steve Cropper</li><li>Scott Lamons</li></ul><p>Notes</p><ul><li>Web site content<ul><li>Mapping of old site to new site is 90% complete</li><li>Content is 60-70% complete</li><li>Steve and Martin have a plan for how to migrate sandbox to live</li><li>We need to add some more content.</li><li>Team will set cutover date and notify people of it</li></ul></li><li>Process to add licenses to list<ul><li>Fedora has an additional couple of hundred licenses</li><li>Need to work with Spot Calloway to add these</li><li>Jilayne had carl with Tom Incorvia and Carl from OSI re Python and other issues to align list<ul><li>OSI has board meeting Sept 15th -- may have some updates</li></ul></li><li>Need to make sure that the licenses aren't variations that will be covered by templatizing</li><li>Jilayne to work with spot to do their list en masse</li></ul></li><li>Reach out to key communities<ul><li>Need to reach out to key communities to engage them</li><li>Communities have said they want tooling to create the SPDX file and gather the info<br /><ul><li>Some communities have standardized way to do license info and just want to transform it to SPDX<ul><li>They may just need a toolkit</li></ul></li><li>Other communities haven't done this at all and you need a product to get it from start</li></ul></li><li>Need to define requirements by getting feeback from communites<br /><ul><li>Ask technical team for some ideas about approaches</li><li>Ask the communities what requirements they want for toolkit or tools</li><li>Talk to them about process and what we are looking for</li></ul></li><li>Use the requirements to refine the tools requirements</li><li>To Do<ul><li>Create deck to present to communities (15 minutes) - Michael Herzog - shoot for draft Sep 15</li><li>Have a tech/biz call</li><li>Reach out and set up meeting to present to few key communities<ul><li>Linux distros - Debian/Fedora +</li><li>Linux kernel</li><li>Apache</li><li>Eclipse</li></ul></li><li>2nd tier -- Source Forge, GitHub</li></ul></li></ul></li><li>FAQs<ul><li>Add to it when we get queries</li><li>How do we have a quick review cycle</li></ul></li></ul>
+
== Attendees ==
 +
 
 +
* Michael Herzog
 +
* Phil Odence
 +
* Kirsten Newcomer
 +
* Jilayne Lovejoy
 +
* Steve Cropper
 +
* Scott Lamons
 +
 
 +
== Notes ==
 +
 
 +
* Web site content
 +
** Mapping of old site to new site is 90% complete
 +
** Content is 60-70% complete
 +
** Steve and Martin have a plan for how to migrate sandbox to live
 +
** We need to add some more content.
 +
** Team will set cutover date and notify people of it
 +
* Process to add licenses to list
 +
** Fedora has an additional couple of hundred licenses
 +
** Need to work with Spot Calloway to add these
 +
** Jilayne had carl with Tom Incorvia and Carl from OSI re Python and other issues to align list
 +
*** OSI has board meeting Sept 15th -- may have some updates
 +
** Need to make sure that the licenses aren't variations that will be covered by templatizing
 +
** Jilayne to work with spot to do their list en masse
 +
* Reach out to key communities
 +
** Need to reach out to key communities to engage them
 +
** Communities have said they want tooling to create the SPDX file and gather the info
 +
*** Some communities have standardized way to do license info and just want to transform it to SPDX
 +
**** They may just need a toolkit
 +
*** Other communities haven't done this at all and you need a product to get it from start
 +
** Need to define requirements by getting feeback from communites
 +
*** Ask technical team for some ideas about approaches
 +
*** Ask the communities what requirements they want for toolkit or tools
 +
*** Talk to them about process and what we are looking for
 +
** Use the requirements to refine the tools requirements
 +
** To Do
 +
*** Create deck to present to communities (15 minutes) - Michael Herzog - shoot for draft Sep 15
 +
*** Have a tech/biz call
 +
*** Reach out and set up meeting to present to few key communities
 +
**** Linux distros - Debian/Fedora +
 +
**** Linux kernel
 +
**** Apache
 +
**** Eclipse
 +
*** 2nd tier -- Source Forge, GitHub
 +
* FAQs
 +
** Add to it when we get queries
 +
** How do we have a quick review cycle
 +
 
 +
[[Category:Business|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 18:49, 5 March 2013

Attendees

  • Michael Herzog
  • Phil Odence
  • Kirsten Newcomer
  • Jilayne Lovejoy
  • Steve Cropper
  • Scott Lamons

Notes

  • Web site content
    • Mapping of old site to new site is 90% complete
    • Content is 60-70% complete
    • Steve and Martin have a plan for how to migrate sandbox to live
    • We need to add some more content.
    • Team will set cutover date and notify people of it
  • Process to add licenses to list
    • Fedora has an additional couple of hundred licenses
    • Need to work with Spot Calloway to add these
    • Jilayne had carl with Tom Incorvia and Carl from OSI re Python and other issues to align list
      • OSI has board meeting Sept 15th -- may have some updates
    • Need to make sure that the licenses aren't variations that will be covered by templatizing
    • Jilayne to work with spot to do their list en masse
  • Reach out to key communities
    • Need to reach out to key communities to engage them
    • Communities have said they want tooling to create the SPDX file and gather the info
      • Some communities have standardized way to do license info and just want to transform it to SPDX
        • They may just need a toolkit
      • Other communities haven't done this at all and you need a product to get it from start
    • Need to define requirements by getting feeback from communites
      • Ask technical team for some ideas about approaches
      • Ask the communities what requirements they want for toolkit or tools
      • Talk to them about process and what we are looking for
    • Use the requirements to refine the tools requirements
    • To Do
      • Create deck to present to communities (15 minutes) - Michael Herzog - shoot for draft Sep 15
      • Have a tech/biz call
      • Reach out and set up meeting to present to few key communities
        • Linux distros - Debian/Fedora +
        • Linux kernel
        • Apache
        • Eclipse
      • 2nd tier -- Source Forge, GitHub
  • FAQs
    • Add to it when we get queries
    • How do we have a quick review cycle
Retrieved from "https://wiki.spdx.org/index.php?title=Business_Team/Minutes/2011-09-01&oldid=1228"