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

Difference between revisions of "Legal Team/Current Projects and Issues"

From SPDX Wiki
Jump to: navigation, search
Line 1: Line 1:
−
<p><strong>Current issues/topics (this is a general list and may not touch upon everything)&nbsp;</strong></p><p><strong>1) Mission/Vision statement</strong> <br />A) Legal Work Group - revised version posted in 5/16 meeting minutes - to be finalized on 5/30 call --&gt; DONE (posted on main legal page)</p><p>B) License List description and overview -revised version posted in 5/16 meeting minutes - to be finalized on 5/30 call --&gt; DONE (posted on main License List page)</p><p><strong>2) Website updates and refresh</strong> <br />A) aligning language and updates on various parts of the current site:</p><ol><li>Specification refers to the license list as "Standard Short Names" &nbsp;- should be consistently referred to as the "SPDX License List"; also, the description needs to be revised and one of the links is probably not correct --&gt; QUASI-DONE, changes for 1.1 of Spec sent to Kate</li><li>License List info page&nbsp;http://spdx.org/wiki/spdx-license-list - updated as needed, Jilayne --&gt; DONE, needs to be reviewed by rest of team</li><li>License List main page&nbsp;http://spdx.org/licenses/ - calls it the "SPDX Open Source License Registry" - needs to be changed to "SPDX License List" &nbsp;- Gary or Martin? (add description (goal/vision) here too?)</li><li>add something about how we are coordinating or aligning with other license lists? (e.g. OSI, FSF, Debian, etc.) - either in its own section or FAQ?</li></ol><p>B) Website refresh - fill in pages, link over content ?? need update from Mark Gisi on this</p><p><strong>3) License List&nbsp;</strong> <br />A) License List updates for v1.16</p><ol><li>Add MPL 2.0 other header version (for time being to be consistent with GPL)</li><li>finish license text review of .txt files -DONE</li><li>formatting/text issue for Cecill licenses in French - checked, seems to show up fine now on website - DONE</li><li>add US Gov't works - add short identifier to list; see email from David Wheeler</li><li>proposal to add some kind of short identifier for copyright notice only (and "all rights reserved"?" - Fedora has this, maybe adopt what they use?</li><li><span style="color: #4d4d4d; font-family: Arial, Helvetica, sans-serif; font-size: 12px;">add in Notes field for all GNU licenses that short identifier "GPL-2.0" = GPL v2 only and vice versa</span></li></ol><p>B) OSI updates from emails (changes to v1.16) and then summarize outstanding issues &nbsp;- Jilayne - DONE</p><p>C) Other issues (see issues column on latest License List download for details - to start covering with v1.16 update)</p><ol><li>GPL exceptions - we don't have them all, list some of the others and variations on text - can someone do some research on this issue?</li><li>various other more issues - see spreadsheet</li></ol><p>D) Community outreach and list coordination</p><ol><li>FSF license list match-up; found here:&nbsp;http://www.gnu.org/licenses/license-list.html -- licenses that need to be added? Jilayne has done initial pass - Paul to do further research and come up with list of those on FSF and not on SPDX for approval to be added or not</li><li>Fedora license list -- Jilayne has begun discussion with Tom Calloway, needs follow-up</li><li>Debian</li><li>Gentoo</li></ol><p><strong>3) License Match Guidelines &nbsp;</strong>- pick up where we left off and complete</p><p><strong>4) Formatting and "master list" for License List (i.e. actual license text files)</strong>&nbsp;&nbsp;<br />Currently the "master" consists of spreadsheet with list + individual .txt files for license text field = downloadable zip file.&nbsp; This is then converted into html pages for website.&nbsp; Peter, Gary, and Jilayne have had initial discussion on this issue; to be discussed further with more fleshed out proposal</p><p>A) PROPOSAL: License text files formatted in HTML instead of .txt files as default; can convert from there into text file with tool if people want that too;&nbsp; Option to use HTML to indicate some of matching rules?</p><p>B) For back-end management of License List overall: proposal to use and GIT repository in background for management &nbsp;- easier tracking of changes and gets it off Jilayne's desktop</p><p><strong>4) Recommendations or guidance on how to best determine license for a particular file</strong><br />how to identify the license for an open source project - ex. Within the file versus whether there's a copying file on top of the directory → provide guidance/suggstion (industry practice?) that license in the file is more determinate than the license in the directory</p><p>Should the legal group aggregate industry best practices and come up with a group of guidelines and provide some influence on that?</p>
+
<p><strong>Current issues/topics (this is a general list and may not touch upon everything)&nbsp;</strong></p><p><strong>1) License Match Guidelines</strong><br />First draft to be completed during 6/27 legal call and ready for Spec 1.1 publication by 6/30</p><p><strong>2) Website updates and refresh</strong> <br />A) Need to identify missing bits and assign folks to populate - ASSIGN</p><p>B) update new site pages that have been updated since last move? - ASSIGN</p><p>C) FAQs? needs more work... - ASSIGN</p><p><strong>3) License List&nbsp;</strong> <br />A) v1.16 posted on 6/20; &nbsp;updates for v1.17:</p><ol><li>add US Gov't works - add short identifier to list; see email from David Wheeler</li><li>proposal to add some kind of short identifier for copyright notice only (and "all rights reserved"?" - Fedora has this, maybe adopt what they use?</li><li>add in Notes field for all GNU licenses that short identifier "GPL-2.0" = GPL v2 only and vice versa - more discussion on this?</li><li>go through issues in issues column</li></ol><p>B) OSI outstanding issues:</p><ol><li>Artistic license issue</li><li>futher clarification on a few previous issues (were APSL-1.0, APSL-1.1, and GPL-2.0 ever approved?)</li><li>zlib/ libpng license clarification</li></ol><p>C)&nbsp;GPL exceptions - we don't have them all, list some of the others and variations on text - can someone do some research on this issue? need to hammer through how to deal with them - ASSIGN</p><p>D) Community outreach and list coordination</p><ol><li>FSF license list match-up; found here:&nbsp;http://www.gnu.org/licenses/license-list.html -- licenses that need to be added? Jilayne has done initial pass - Paul has done first pass - need to discuss possible additions to list</li><li>Fedora license list -- Jilayne has begun discussion with Tom Calloway, needs follow-up</li><li>Debian</li><li>Gentoo</li></ol><p><strong>4) Formatting and "master list" for License List (i.e. actual license text files)</strong>&nbsp;&nbsp;<br />Currently the "master" consists of spreadsheet with list + individual .txt files for license text field = downloadable zip file.&nbsp; This is then converted into html pages for website.&nbsp; Peter, Gary, and Jilayne have had initial discussion on this issue; to be discussed further with more fleshed out proposal</p><p>A) PROPOSAL: License text files formatted in HTML instead of .txt files as default; can convert from there into text file with tool if people want that too;&nbsp; Option to use HTML to indicate some of matching rules?</p><p>B) For back-end management of License List overall: proposal to use and GIT repository in background for management &nbsp;- easier tracking of changes and gets it off Jilayne's desktop</p><p><strong>5) Recommendations or guidance on how to best determine license for a particular file</strong><br />how to identify the license for an open source project - ex. Within the file versus whether there's a copying file on top of the directory → provide guidance/suggstion (industry practice?) that license in the file is more determinate than the license in the directory</p><p>Should the legal group aggregate industry best practices and come up with a group of guidelines and provide some influence on that?</p>

Revision as of 01:02, 27 June 2012

Current issues/topics (this is a general list and may not touch upon everything) 

1) License Match Guidelines
First draft to be completed during 6/27 legal call and ready for Spec 1.1 publication by 6/30

2) Website updates and refresh
A) Need to identify missing bits and assign folks to populate - ASSIGN

B) update new site pages that have been updated since last move? - ASSIGN

C) FAQs? needs more work... - ASSIGN

3) License List 
A) v1.16 posted on 6/20;  updates for v1.17:

  1. add US Gov't works - add short identifier to list; see email from David Wheeler
  2. proposal to add some kind of short identifier for copyright notice only (and "all rights reserved"?" - Fedora has this, maybe adopt what they use?
  3. add in Notes field for all GNU licenses that short identifier "GPL-2.0" = GPL v2 only and vice versa - more discussion on this?
  4. go through issues in issues column

B) OSI outstanding issues:

  1. Artistic license issue
  2. futher clarification on a few previous issues (were APSL-1.0, APSL-1.1, and GPL-2.0 ever approved?)
  3. zlib/ libpng license clarification

C) GPL exceptions - we don't have them all, list some of the others and variations on text - can someone do some research on this issue? need to hammer through how to deal with them - ASSIGN

D) Community outreach and list coordination

  1. FSF license list match-up; found here: http://www.gnu.org/licenses/license-list.html -- licenses that need to be added? Jilayne has done initial pass - Paul has done first pass - need to discuss possible additions to list
  2. Fedora license list -- Jilayne has begun discussion with Tom Calloway, needs follow-up
  3. Debian
  4. Gentoo

4) Formatting and "master list" for License List (i.e. actual license text files)  
Currently the "master" consists of spreadsheet with list + individual .txt files for license text field = downloadable zip file.  This is then converted into html pages for website.  Peter, Gary, and Jilayne have had initial discussion on this issue; to be discussed further with more fleshed out proposal

A) PROPOSAL: License text files formatted in HTML instead of .txt files as default; can convert from there into text file with tool if people want that too;  Option to use HTML to indicate some of matching rules?

B) For back-end management of License List overall: proposal to use and GIT repository in background for management  - easier tracking of changes and gets it off Jilayne's desktop

5) Recommendations or guidance on how to best determine license for a particular file
how to identify the license for an open source project - ex. Within the file versus whether there's a copying file on top of the directory → provide guidance/suggstion (industry practice?) that license in the file is more determinate than the license in the directory

Should the legal group aggregate industry best practices and come up with a group of guidelines and provide some influence on that?

Retrieved from "https://wiki.spdx.org/index.php?title=Legal_Team/Current_Projects_and_Issues&oldid=1782"