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-03-03"

From SPDX Wiki
Jump to: navigation, search
 
(Convert to MediaWiki syntax)
 
Line 1: Line 1:
−
<p>Attendees</p><ul><li>Kim Weins</li><li>Phil Odence</li><li>Kate Stewart</li><li>Gary O'Neall</li><li>Jilayne Lovejoy</li><li>Scott Lamons</li><li>Michael Herzog</li><li>Phil Koltun</li><li>Kirsten Newcomer</li></ul><p><strong>Process for Adding New Standard Licenses.</strong></p><p>We did not finish discussion, so will continue at next meeting.&nbsp; Notes so far are below.</p><ul><li>Anyone can request license to be added through a web form (possibly Bugzilla).</li><li>Information<ul><li>Person Name</li><li>Email</li><li>Organization - community/company</li><li>License name</li><li>Actual license text</li><li>URL for where they found license text</li><li>Comments -- why they want it</li><li>Example(s) of open source packages/files that use it</li><li>Why they want it -- is it their own license or is it something they have encountered in audits</li><li>Is it going thru OSI approval?</li><li>Other notes or we need to know</li></ul></li><li>Process<ul><li>First validation/vetting for complete/correct info - contact person who submitted it</li><li>&nbsp;Decision making by group<ul><li>Allow comments in a timeline</li><li>Start with an open ended time</li><li>Have business team make decision initially until we see what the volume is <br /><ul><li>Shoot for doing this first year unless it's getting out of hand</li></ul></li><li>Way to batch it - handle at biz team meetings</li><li>Can have some where we decide to "defer" for now.</li><li>Business team will decide -- likely based on majority vote for people that attended the meeting (at least 5 people and 1 legal)</li><li>Publish the ones we will vote on 2 weeks in advance to full list.&nbsp; Discussion/comments on biz list.<br /><ul><li>Set up a separate wiki page to keep the list tracked of what we are voting on when</li></ul></li></ul></li><li>Later -- Have a more formal committee that makes a decision - 5-7 people<br /><ul><li>Should have 2 legal spots on community</li><li>Might want at least one community spot</li><li>Nominations (including self nominations) make clear the requirements</li><li>Way to adjust if someone is not participating</li></ul></li><li></li><li>Assignment of standard name</li><li>Data entered into repo and templatizing is done</li><li>Review/QA of the data in the repo</li></ul></li><li>Suggested Criteria<ul><li>Center of gravity is OSS license but will consider freeware or other licenses that are widely encountered.&nbsp; For example would consider Sun Binary Licenses.&nbsp; Things that share many/all of OSI attributes - but may have additional requirements</li><li>Not for purely commercial licenses (ex EULA, or Oracle license)</li><li>License must be publicly accessible</li><li>License that is seen across multiple projects or on a heavily used project</li><li>License that will be popular in future (eg new version of GPL, Apache)</li></ul></li><li>Need a statement that we don't necessarily consider all these licenses to be open source - just trying to facilitate a way to refer to them.&nbsp; Check how Fedora does this (talk to Spot)</li><li>Timeframe<ul><li>Will need to set expectations for turnaround time</li></ul></li></ul><p>&nbsp;</p>
+
== Attendees ==
 +
 
 +
* Kim Weins
 +
* Phil Odence
 +
* Kate Stewart
 +
* Gary O'Neall
 +
* Jilayne Lovejoy
 +
* Scott Lamons
 +
* Michael Herzog
 +
* Phil Koltun
 +
* Kirsten Newcomer
 +
 
 +
== Process for Adding New Standard Licenses. ==
 +
 
 +
We did not finish discussion, so will continue at next meeting. Notes so far are below.
 +
 
 +
* Anyone can request license to be added through a web form (possibly Bugzilla).
 +
* Information
 +
** Person Name
 +
** Email
 +
** Organization - community/company
 +
** License name
 +
** Actual license text
 +
** URL for where they found license text
 +
** Comments -- why they want it
 +
** Example(s) of open source packages/files that use it
 +
** Why they want it -- is it their own license or is it something they have encountered in audits
 +
** Is it going thru OSI approval?
 +
** Other notes or we need to know
 +
* Process
 +
** First validation/vetting for complete/correct info - contact person who submitted it
 +
** Decision making by group
 +
*** Allow comments in a timeline
 +
*** Start with an open ended time
 +
*** Have business team make decision initially until we see what the volume is
 +
**** Shoot for doing this first year unless it's getting out of hand
 +
*** Way to batch it - handle at biz team meetings
 +
*** Can have some where we decide to "defer" for now.
 +
*** Business team will decide -- likely based on majority vote for people that attended the meeting (at least 5 people and 1 legal)
 +
*** Publish the ones we will vote on 2 weeks in advance to full list. Discussion/comments on biz list.
 +
**** Set up a separate wiki page to keep the list tracked of what we are voting on when
 +
** Later -- Have a more formal committee that makes a decision - 5-7 people
 +
*** Should have 2 legal spots on community
 +
*** Might want at least one community spot
 +
*** Nominations (including self nominations) make clear the requirements
 +
*** Way to adjust if someone is not participating
 +
** Assignment of standard name
 +
** Data entered into repo and templatizing is done
 +
** Review/QA of the data in the repo
 +
* Suggested Criteria
 +
** Center of gravity is OSS license but will consider freeware or other licenses that are widely encountered. For example would consider Sun Binary Licenses. Things that share many/all of OSI attributes - but may have additional requirements
 +
** Not for purely commercial licenses (ex EULA, or Oracle license)
 +
** License must be publicly accessible
 +
** License that is seen across multiple projects or on a heavily used project
 +
** License that will be popular in future (eg new version of GPL, Apache)
 +
* Need a statement that we don't necessarily consider all these licenses to be open source - just trying to facilitate a way to refer to them. Check how Fedora does this (talk to Spot)
 +
* Timeframe
 +
** Will need to set expectations for turnaround time
 +
 
 +
[[Category:Business|Minutes]]
 +
[[Category:Minutes]]

Latest revision as of 20:52, 28 February 2013

Attendees

  • Kim Weins
  • Phil Odence
  • Kate Stewart
  • Gary O'Neall
  • Jilayne Lovejoy
  • Scott Lamons
  • Michael Herzog
  • Phil Koltun
  • Kirsten Newcomer

Process for Adding New Standard Licenses.

We did not finish discussion, so will continue at next meeting. Notes so far are below.

  • Anyone can request license to be added through a web form (possibly Bugzilla).
  • Information
    • Person Name
    • Email
    • Organization - community/company
    • License name
    • Actual license text
    • URL for where they found license text
    • Comments -- why they want it
    • Example(s) of open source packages/files that use it
    • Why they want it -- is it their own license or is it something they have encountered in audits
    • Is it going thru OSI approval?
    • Other notes or we need to know
  • Process
    • First validation/vetting for complete/correct info - contact person who submitted it
    • Decision making by group
      • Allow comments in a timeline
      • Start with an open ended time
      • Have business team make decision initially until we see what the volume is
        • Shoot for doing this first year unless it's getting out of hand
      • Way to batch it - handle at biz team meetings
      • Can have some where we decide to "defer" for now.
      • Business team will decide -- likely based on majority vote for people that attended the meeting (at least 5 people and 1 legal)
      • Publish the ones we will vote on 2 weeks in advance to full list. Discussion/comments on biz list.
        • Set up a separate wiki page to keep the list tracked of what we are voting on when
    • Later -- Have a more formal committee that makes a decision - 5-7 people
      • Should have 2 legal spots on community
      • Might want at least one community spot
      • Nominations (including self nominations) make clear the requirements
      • Way to adjust if someone is not participating
    • Assignment of standard name
    • Data entered into repo and templatizing is done
    • Review/QA of the data in the repo
  • Suggested Criteria
    • Center of gravity is OSS license but will consider freeware or other licenses that are widely encountered. For example would consider Sun Binary Licenses. Things that share many/all of OSI attributes - but may have additional requirements
    • Not for purely commercial licenses (ex EULA, or Oracle license)
    • License must be publicly accessible
    • License that is seen across multiple projects or on a heavily used project
    • License that will be popular in future (eg new version of GPL, Apache)
  • Need a statement that we don't necessarily consider all these licenses to be open source - just trying to facilitate a way to refer to them. Check how Fedora does this (talk to Spot)
  • Timeframe
    • Will need to set expectations for turnaround time
Retrieved from "https://wiki.spdx.org/index.php?title=Business_Team/Minutes/2011-03-03&oldid=942"