|
|
| (43 intermediate revisions by 6 users not shown) |
| Line 1: |
Line 1: |
| − | <p>The Legal Team meets every other Wednesday at 8am Pacific Time US / 11am Eastern Time US time during the same weeks as the General Meeting. If you have any questions, email Jilayne Lovejoy at: <a href="mailto:jlovejoy@openlogic.com">jlovejoy@openlogic.com</a></p><ul><li>You can sign up for the <a href="http://lists.spdx.org/mailman/listinfo/spdx-legal">mailing list here</a></li><li>The next Legal Team meeting will be on Wednesday, April 18, 2012.</li></ul><p><span style="text-decoration: underline;"><strong>Current issues/topics (this is a general list and may not touch upon everything) -- <em>updated April 6</em></strong></span></p><p></p><p class="p1"><b>1) License addition process</b></p><p></p><p>A) Legal team has taken this back over from business team; see Adam Cohn's email summarizing current proposal - To be discussed on next legal call 4/18</p><p></p><p class="p2"><b>2) Formatting and "master list" for License List (i.e. actual license text files)</b></p><p></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></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><ol class="ol1"></ol><p></p><p class="p1"><b>3) Other administrative to-dos </b></p><p></p><p>A) Add licenses to list or other updates ("DONE" indicates completed for v1.15; rest some will be done for v1.16)</p><ol class="ol1"><ol class="ol1"><li class="li2">Add FreeBSD - DONE</li><li class="li2">Add NetBSD licenses - DONE</li><li class="li2">Add 4-clause UC BSD license - DONE</li><li class="li2">Add CDDL v1.1 - DONE</li><li class="li2">AGPL full name is "v3" not "v3.0" like everything else (short identifier is correct) - DONE</li><li class="li2">PHP license issue (see email) - DONE</li><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">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></ol><ol class="ol1"></ol><p>B) Other to-dos</p><ol class="ol1"></ol><p></p><ol class="ol1"><ul class="ul1"><li class="li2">update License List fields protocol on website</li></ul></ol><p></p><p class="p4"><span class="Apple-tab-span"> </span><span class="Apple-tab-span"> </span></p><p>C) Other issues (some to be discussed over next legal calls upcoming)</p><ol class="ol1"></ol><p></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">Propose short identifier for copyright notice only "all rights reserved"</li><li class="li2">OSI issues - waiting on them</li><li class="li2">FSF license list match-up - licenses that need to be added?</li><ul class="ul1"><li class="li2">JL has done initial pass - needs further research</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">JL has begun discussion with Tom Calloway</li></ul></ol><p></p><p><em><br /></em></p>
| + | This is the working area for the Legal Team. The SPDX Legal Team supports and provides recommendations to the SPDX working groups regarding licensing issues for the specification itself; maintains the [http://spdx.org/licenses/ SPDX License List]; and promotes the SPDX specification to the legal community at-large. |
| | + | |
| | + | Work and discussion is primarily done via: |
| | + | |
| | + | * [https://lists.spdx.org/g/spdx-legal Mailing list]: our traditional form of communication. Meeting reminders, minutes, updates are posted there, as well as discussion. |
| | + | * [https://github.com/spdx/license-list-XML SPDX License List Github repo]: comments and issues and PRs related to specific changes to the files that comprise the SPDX License List, e.g., update a URL, recommend additional markup for matching purposes. In particular, new license requests are tracked here. |
| | + | * Bi-weekly calls: used to discuss topics and issues that may be difficult to only discuss via email or via Github. |
| | + | |
| | + | The Legal Team meets '''every other Thursday at 17:00 GMT (9:00AM PT, 10:00 MT, 11:00 CT, 12:00PM ET)'''. |
| | + | * [https://github.com/spdx/meetings/tree/master/legal Meeting Minutes of the Legal Team - June 2020 onward] |
| | + | * [[Legal_Team/Minutes|Meeting Minutes of the Legal Team - prior to March 2020]] |
| | + | * [[Legal_Team/Resources|Resources]] |
| | + | * [[Legal_Team/Decisions|Decisions of the Legal Team]] - summaries of past significant decisions of the SPDX Legal Team |
| | + | * [[Legal_Team/Archive|Archive]] |
| | + | |
| | + | '''Working pages for project in progress:''' |
| | + | * [[Legal_Team/non-English-licenses|Working page for policy on how to handle non-English licenses and matching]] |
| | + | |
| | + | <!-- * [[Legal_Team/Old|Older Items for the Legal Team]] nothing there, so hiding this link --> |
| | + | <!--* [[Legal_Team/Priorities|Current Priorities and Work in Progress for the Legal Team]] link not really useful--> |
| | + | |
| | + | [[Category:Legal]] |
Revision as of 02:45, 6 July 2020
This is the working area for the Legal Team. The SPDX Legal Team supports and provides recommendations to the SPDX working groups regarding licensing issues for the specification itself; maintains the SPDX License List; and promotes the SPDX specification to the legal community at-large.
Work and discussion is primarily done via:
- Mailing list: our traditional form of communication. Meeting reminders, minutes, updates are posted there, as well as discussion.
- SPDX License List Github repo: comments and issues and PRs related to specific changes to the files that comprise the SPDX License List, e.g., update a URL, recommend additional markup for matching purposes. In particular, new license requests are tracked here.
- Bi-weekly calls: used to discuss topics and issues that may be difficult to only discuss via email or via Github.
The Legal Team meets every other Thursday at 17:00 GMT (9:00AM PT, 10:00 MT, 11:00 CT, 12:00PM ET).
Working pages for project in progress:
