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

Legal Team/Current Projects and Issues

From SPDX Wiki
Jump to: navigation, search

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

1) Mission/Vision statement

A) for Legal Work Group - Paul submitted to group for comment

B) License List description and overview - Jilayne to do

 

2) Website updates and refresh

A) aligning language and updates on various parts of the current site:

  1. Specification refers to the license list as "Standard Short Names"  - 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
  2. Spec webpage links and info http://spdx.org/spec - updated by Jilayne, DONE
  3. License List info page http://spdx.org/wiki/spdx-license-list - updated as needed, Jilayne
  4. License List main page http://spdx.org/licenses/ - calls it the "SPDX Open Source License Registry" - needs to be changed to "SPDX License List"  - Gary or Martin?
    • add description (goal/vision) here too?
B) Website refresh - fill in pages, link over content ?? 
 

3) License List 

A) License List updates for v1.16

  1. Add MPL 2.0 other header version (for time being to be consistent with GPL)
  2. finish license text review of .txt files - still some to do
  3. formatting/text issue for Cecill licenses in French
  4. add US Gov't works - add short identifier to list; see email from David Wheeler
  5. proposal to add some kind of short identifier for copyright notice only (and "all rights reserved"?" - Fedora has this, maybe adopt what they use?

B) OSI updates from emails (changes to v1.16) and then summarize outstanding issues  - Jilayne, in progress

C) Other issues (see issues column on latest License List download for details)

  1. 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?
  2. eCos is really a GPL header with an exception... (see bigger issue above)
  3. Lucent Public License - naming issues - see notes in spreadsheet
  4. Sugar CRM license - see notes in spreadsheet
  5. OSI issues - waiting on them
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 - needs further research, could someone else take this on?
  2. Fedora license list reach-out via email (he won't be at LF Collab Summit)
    • Jilayne has begun discussion with Tom Calloway, needs follow-up
  3. Debian
  4. Gentoo

 

3) 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; 

  1. Option to use HTML to indicate some of matching rules?

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

 


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