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

<p><strong>Current issues/topics (this is a general list and may not touch upon everything).</strong></p><p>LAST UPDATED: 7 Jan 2013</p><p><strong>1) License List</strong> <br />A) Licenses to add? <em>(GROUP)</em></p><ol><li>"old" MIT? see http://blog.gmane.org/gmane.comp.licenses.spdx.legal/day=20121201</li><li>FLORA License - decided not to add at this point in time, pending guidelines mentioned in #3 below. see http://blog.gmane.org/gmane.comp.licenses.spdx.legal/month=20121101 for most recent thread on the topic</li><li>Unlicense - see thread here: http://search.gmane.org/?query=unlicense&amp;group=gmane.comp.licenses.spdx.legal</li><li>add US Gov't works - add short identifier to list; see email from David Wheeler</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></ol><p>B) OSI outstanding issues: <em>(Jilayne)</em></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) GPL exceptions: <em>(ASSIGN)</em> <br />We don't have them all, there is also the issue of inconsistencies "in the wild" among named exceptions and actual text (i.e. not all exceptions found called Foo exception have the exact same text; how do we deal with this? <br />someone needs to take this on as a project...</p><p>D) Better system for saving/updating SPDX License List <em>(Jilayne to coordinate with Gary)</em> <br />Currently the SPDX-LL is kept and updated by Jilayne. This is not an optimal system (hit by a bus factor not accounted for). Need to change to some kind of respository that tracks changes and can be viewed by all (But not edited by all).</p><p><strong>2) Community outreach and list coordination</strong></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? -- in progress DONE?</li><li>Fedora license list -- Jilayne has begun discussion with Tom Calloway, needs follow-up - <em>(ASSIGN)</em></li><li>Fossology - coordinate with Bob Gobeille, see http://www.fossology.org/projects/fossology/wiki/MatchSPDXLicenceIDs - ASSIGN</li><li>Gentoo - <em>(ASSIGN)</em></li><li>Suse list found here: https://docs.google.com/spreadsheet/pub?key=0AqPp4y2wyQsbdGQ1V3pRRDg5NEpGVWpubzdRZ0tjUWc (courtesy of Ciaran Farrell from 6/27/12 email list thread) - <em>(ASSIGN)</em></li><li>add page to wiki that outlines progress to this end and other lists we have or have yet to coordinate with - ASSIGN</li></ol><p><strong>3) General guidelines for what licenses are included on the SPDX License List <em>(GROUP)</em></strong> <br />General statement or guidelines needed in regards to the types of license that are to be included on the SPDX-LL; in particular in regards to requests for adding a new license. e.g., only open source licenses? what about freeware licenses? see meeting minutes from 31-Oct and 13-Nov for background and discussion thus far. draft of guidelines began by Tom Vidal <br />see http://spdx.org/wiki/spdx-license-list-guidelines-regarding-addition-or-rejection-licenses-proposed-add for overview of issue and latest revision - To Be Continued with larger group</p><p><strong>4) License Match Guidelines <em>(GROUP)</em></strong> <br />not enough people on 6/27 legal call for quorum/to complete; see meeting minute for 6/27 and several prior meetings. &nbsp;Matching guidelines updated as of 6/27, see http://spdx.org/wiki/spdx-license-list-match-guidelines</p><p><strong>5) Website updates <em>(Jilayne)</em></strong></p><ol><li>add page for explaining public domain discussion</li><li>update page re: change of "data license" from PddL to MIT</li><li>other past decisions further explained?</li></ol><p><strong>6) Formatting and "master list" for License List (i.e. actual license text files)</strong> <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>7) 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>