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
| Line 1: | Line 1: | ||
| − | <p><span style="text-decoration: underline;"><strong>Current issues/topics (this is a general list and may not touch upon everything) -- <em>updated | + | <p><span style="text-decoration: underline;"><strong>Current issues/topics (this is a general list and may not touch upon everything) -- <em>updated May 15</em></strong></span></p><p class="p1"><strong>1) Mission/Vision statement</strong></p><p class="p1">A) for Legal Work Group - Paul submitted to group for comment</p><p class="p1">B) License List description and overview - Jilayne to do</p><p class="p1"> </p><p class="p1"><strong>2) Website updates and refresh</strong></p><p class="p1">A) aligning language and updates on various parts of the current site:</p><ol><li><span style="text-decoration: underline;">Specification</span> 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</li><li>Spec webpage links and info http://spdx.org/spec - updated by Jilayne, DONE</li><li>License List info page http://spdx.org/wiki/spdx-license-list - updated as needed, Jilayne</li><li>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?</li><ul><li>add description (goal/vision) here too?</li></ul></ol><div>B) Website refresh - fill in pages, link over content ?? </div><div> </div><p class="p1"><strong></strong><strong>3) License List </strong></p><p>A) License List updates for v1.16</p><ol class="ol1"><li class="li2">Add MPL 2.0 other header version (for time being to be consistent with GPL)</li><li class="li2">finish license text review of .txt files - still some to do</li><li class="li2">formatting/text issue for Cecill licenses in French</li><li class="li2">add US Gov't works - add short identifier to list; see email from David Wheeler</li><li class="li2">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></ol><p>B) OSI updates from emails (changes to v1.16) and then summarize outstanding issues - Jilayne, in progress</p><p>C) Other issues (see issues column on latest License List download for details)</p><ol class="ol1"><li class="li2">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 class="li2">eCos is really a GPL header with an exception... (see bigger issue above)</li><li class="li2">Lucent Public License - naming issues - see notes in spreadsheet</li><li class="li2">Sugar CRM license - see notes in spreadsheet</li><li class="li2">OSI issues - waiting on them</li></ol><div>D) Community outreach and list coordination</div><ol class="ol1"><li class="li2">FSF license list match-up - found here: http://www.gnu.org/licenses/license-list.html</li><ul class="ul1"><li>licenses that need to be added?</li><li class="li2">Jilayne has done initial pass - needs further research, could someone else take this on?</li></ul><li class="li2">Fedora license list reach-out via email (he won't be at LF Collab Summit)</li><ul class="ul1"><li class="li2">Jilayne has begun discussion with Tom Calloway, needs follow-up</li></ul><li>Debian</li><li>Gentoo</li></ol><p> </p><p class="p2"><strong>3) Formatting and "master list" for License List (i.e. actual license text files)</strong></p><p class="p2">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</p><p>A) <span style="text-decoration: underline;"><span class="s1">PROPOSAL</span></span>: 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; </p><ol class="ol1"><li>Option to use HTML to indicate some of matching rules?</li></ol><p>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<br /><br /></p><p> </p><p class="p1"><strong><br /></strong></p> |
Revision as of 03:48, 16 May 2012
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:
- 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
- Spec webpage links and info http://spdx.org/spec - updated by Jilayne, DONE
- License List info page http://spdx.org/wiki/spdx-license-list - updated as needed, Jilayne
- 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
- Add MPL 2.0 other header version (for time being to be consistent with GPL)
- finish license text review of .txt files - still some to do
- formatting/text issue for Cecill licenses in French
- add US Gov't works - add short identifier to list; see email from David Wheeler
- 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)
- 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?
- eCos is really a GPL header with an exception... (see bigger issue above)
- Lucent Public License - naming issues - see notes in spreadsheet
- Sugar CRM license - see notes in spreadsheet
- OSI issues - waiting on them
D) Community outreach and list coordination
- 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?
- 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
- Debian
- 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;
- 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
