Legal Team/Current Projects and Issues

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

1) License Match Guidelines
First draft to be completed during 6/27 legal call and ready for Spec 1.1 publication by 6/30

2) Website updates and refresh
A) Need to identify missing bits and assign folks to populate - ASSIGN

B) update new site pages that have been updated since last move? - ASSIGN

C) FAQs? needs more work... - ASSIGN

3) License List 
A) v1.16 posted on 6/20;  updates for v1.17:

1. add US Gov't works - add short identifier to list; see email from David Wheeler
2. proposal to add some kind of short identifier for copyright notice only (and "all rights reserved"?" - Fedora has this, maybe adopt what they use?
3. add in Notes field for all GNU licenses that short identifier "GPL-2.0" = GPL v2 only and vice versa - more discussion on this?
4. go through issues in issues column

B) OSI outstanding issues:

1. Artistic license issue
2. futher clarification on a few previous issues (were APSL-1.0, APSL-1.1, and GPL-2.0 ever approved?)
3. zlib/ libpng license clarification

C) 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

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 - Paul has done first pass - need to discuss possible additions to list
2. Fedora license list -- Jilayne has begun discussion with Tom Calloway, needs follow-up
3. Debian
4. Gentoo

4) 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 and GIT repository in background for management  - easier tracking of changes and gets it off Jilayne's desktop

5) Recommendations or guidance on how to best determine license for a particular file
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

Should the legal group aggregate industry best practices and come up with a group of guidelines and provide some influence on that?