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)&nbsp;</strong></p><p><strong>1) License Match Guidelines</strong><br />not enough people on 6/27 legal call for quorum/to complete; see meeting minute for 6/27 and severl prior meetings. &nbsp;Matching guidelines updated as of 6/27, see http://spdx.org/wiki/spdx-license-list-match-guidelines</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>