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
Jump to: navigation, search
(Fix broken link)
Line 1: Line 1:
−
LAST UPDATED: 17 Jan 2013
+
LAST UPDATED: 25 April 2013
  
−
'''1) License List'''
+
== SPDX Legal Team projects for 2013 ==
  
−
'''1A) Licenses to add? ''(Kirstin Newcomer to track progress and lead; GROUP to make decisions; may need to delegate research on particular licenses to others - ongoing, check in on this each call)'''''
+
=== License List requests/additions tracking page ===
 +
owner: Jack Manbeck (goal to get this up and current by end of May)
 +
# create wiki page with table for tracking, with relevant/appropriate columns
 +
# propagate with recent and outstanding requests
 +
# update going forward
  
−
# "old" MIT? see http://blog.gmane.org/gmane.comp.licenses.spdx.legal/day=20121201
+
===Review process for requesting a new license webpage===
−
# 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
+
owner: Jason (first pass by 5/3, team to review at 5/10 meeting
−
# Unlicense - see thread here: http://search.gmane.org/?query=unlicense&group=gmane.comp.licenses.spdx.legal
+
−
# add US Gov't works - add short identifier to list; see email from David Wheeler
+
−
# add in Notes field for all GNU licenses that short identifier "GPL-2.0" = GPL v2 only and vice versa - more discussion on this?
+
−
 
+
−
'''1B) OSI outstanding issues: ''(Jilayne - goal to have these resolved by end of June or next rev of SPDX-LL)'''''
+
  
 +
===OSI outstanding issues===
 +
owner: Jilayne
 +
# various OSI approved (but old or deprecated) licenses don't have corresponding link on OSI site; OSI to update and then SPDX to add link to SPDX-LL
 
# Artistic license issue
 
# Artistic license issue
 
# futher clarification on a few previous issues (were APSL-1.0, APSL-1.1, and GPL-2.0 ever approved?)
 
# futher clarification on a few previous issues (were APSL-1.0, APSL-1.1, and GPL-2.0 ever approved?)
 
# zlib/ libpng license clarification
 
# zlib/ libpng license clarification
−
# Jabber Open Source License v1.0 -
+
# Jabber Open Source License v1.0 – archived text here (http://archive.jabber.org/core/JOSL.pdf) is not the same as the OSI has on their site (it was OSI approved). What do we do about this? need to resolve with OSI (with goal of having on list b/c it was OSI approved and we endeavored to have all OSI licenses on SPDX list, even if old). license text also can be found at: http://code.google.com/p/jabber-net/wiki/FAQ_License
−
# Jabber Open Source License v1.0 – decided to add and in doing so noticed the archived text here (http://archive.jabber.org/core/JOSL.pdf) is not the same as the OSI has on their site (it was OSI approved). What do we do about this? (see attached .doc file for comparison. text says "draft" at bottom... decided because it's an old license to hold off and not add to list yet - and resolve with OSI (with goal of having on list b/c it was OSI approved and we endeavored to have all OSI licenses on SPDX list, even if old). license text also can be found at: http://code.google.com/p/jabber-net/wiki/FAQ_License
+
−
 
+
−
'''1C) GPL exceptions: ''(Tom Vidal - goal to have this reasonably done by end of June)'' ''' We don't have them all and there are 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?)
+
−
 
+
−
'''1D) Better system for saving/updating SPDX License List ''(Jilayne to coordinate with Gary - goal to have this done by end of February)'' '''<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).
+
−
 
+
−
'''2) Community outreach and list coordination:'''Goal of coordinating with various other license lists to make sure SPDX has licenses from these lists and check short name matching (or create "translation" document if different)
+
−
 
+
−
'''2A) Fedora license list ''(Paul Madick - goal for first pass by end of first quarter?? TBD, Paul to report on timing next call)'''''<br />will need to check lists for discrepancies, i.e. are there licenses on Fedora list that are not on SPDX-LL and if so, decide to add; also need to create short-name matching matrix due to Fedora using different type of categorization for its short names. Coordinate and communicate with Tom Calloway throughout.
+
−
 
+
−
'''2B) Fossology (''ASSIGN)'''''<br />coordinate with Bob Gobeille, see http://www.fossology.org/projects/fossology/wiki/MatchSPDXLicenceIDs
+
−
 
+
−
'''2C) Gentoo - ''(ASSIGN)'''''
+
−
 
+
−
'''2D) Suse ''(ASSIGN)'''''<br />list found here: https://docs.google.com/spreadsheet/pub?key=0AqPp4y2wyQsbdGQ1V3pRRDg5NEpGVWpubzdRZ0tjUWc (courtesy of Ciaran Farrell from 6/27/12 email list thread)
+
−
 
+
−
'''2E) FSF license list match-up''' from http://www.gnu.org/licenses/license-list.html. completed for v1.17. any outstanding license questions were added to #1(A)
+
  
−
'''3) General guidelines for what licenses are included on the SPDX License List ''(Tom Vidal - conclude by end of March)'''''<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 fo r 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 [[Legal_Team/License_List/Inclusion_Guidelines_(Background)]] for overview of issue and latest revision - To Be Continued with larger group
+
===License Matching Guidelines - implement markup===
 +
once final method for markup has been decided upon, we will need to go through all licenses on current list and create appropriate markup files for each.  Legal team will divvy up work and may ask for help from technical team as well.  We will invariably find issues that will need to be discussed along the way - using the legal team bi-weekly calls for such discusssion
  
−
'''3A) Also review process for requesting a new license''' once above is done to see if anything should be updated as we refine the process, etc.
+
===GPL exceptions ===
 +
owner: Tom Vidal  (goal to have this reasonably done by end of June)
 +
* We don't have them all and there are 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?)
  
−
'''4) License Match Guidelines ''(GROUP - needs an owner and would like to make a priority)'''''<br />not enough people on 6/27 legal call for quorum/to complete; see meeting minute for 6/27 and several prior meetings. Matching guidelines updated as of 6/27, see [[Legal_Team/License_List/License_Matching_Guidelines]]
+
===Community outreach and list coordination===
 +
Goal of coordinating with various other license lists to make sure SPDX has licenses from these lists and check short name matching (or create "translation" document if different)
  
−
'''5) Website updates ''(Jilayne - time frame TBD)'''''
+
====Fedora license list====
 +
owner: Paul Madick (goal to have first pass for Legal Team to begin reviewing by mid-June)
 +
*will need to check lists for discrepancies, i.e. are there licenses on Fedora list that are not on SPDX-LL and if so, decide to add; also need to create short-name matching matrix due to Fedora using different type of categorization for its short names
  
−
# add page for explaining public domain discussion
+
====Fossology====
−
# update page re: change of "data license" from PddL to MIT
+
owner: TBD assigned
−
# add page to wiki that outlines progress regarding varioud license list coordination (OSI, FSF, Fedora, etc.) we have or have yet to coordinate with
+
*coordinate with Bob Gobeille, see http://www.fossology.org/projects/fossology/wiki/MatchSPDXLicenceIDs
−
# other past decisions further explained?
+
  
−
'''6) Formatting and "master list" for License List (i.e. actual license text files) ''(Phil)'''''<br />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
+
====Gentoo====
 +
owner: TBD assigned
  
−
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?
+
====Suse====
 +
owner: TBD assigned
 +
*list found here: https://docs.google.com/spreadsheet/pub?key=0AqPp4y2wyQsbdGQ1V3pRRDg5NEpGVWpubzdRZ0tjUWc (courtesy of Ciaran Farrell from 6/27/12 email list thread)
  
−
'''7) Recommendations or guidance on how to best determine license for a particular file'''<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 directoryShould the legal group aggregate industry best practices and come up with a group of guidelines and provide some influence on that?
+
=== 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 directoryShould the legal group aggregate industry best practices and come up with a group of guidelines and provide some influence on that?
  
 
[[Category:Legal]]
 
[[Category:Legal]]

Revision as of 22:51, 25 April 2013

LAST UPDATED: 25 April 2013

SPDX Legal Team projects for 2013

License List requests/additions tracking page

owner: Jack Manbeck (goal to get this up and current by end of May)

  1. create wiki page with table for tracking, with relevant/appropriate columns
  2. propagate with recent and outstanding requests
  3. update going forward

Review process for requesting a new license webpage

owner: Jason (first pass by 5/3, team to review at 5/10 meeting

OSI outstanding issues

owner: Jilayne

  1. various OSI approved (but old or deprecated) licenses don't have corresponding link on OSI site; OSI to update and then SPDX to add link to SPDX-LL
  2. Artistic license issue
  3. futher clarification on a few previous issues (were APSL-1.0, APSL-1.1, and GPL-2.0 ever approved?)
  4. zlib/ libpng license clarification
  5. Jabber Open Source License v1.0 – archived text here (http://archive.jabber.org/core/JOSL.pdf) is not the same as the OSI has on their site (it was OSI approved). What do we do about this? need to resolve with OSI (with goal of having on list b/c it was OSI approved and we endeavored to have all OSI licenses on SPDX list, even if old). license text also can be found at: http://code.google.com/p/jabber-net/wiki/FAQ_License

License Matching Guidelines - implement markup

once final method for markup has been decided upon, we will need to go through all licenses on current list and create appropriate markup files for each. Legal team will divvy up work and may ask for help from technical team as well. We will invariably find issues that will need to be discussed along the way - using the legal team bi-weekly calls for such discusssion

GPL exceptions

owner: Tom Vidal (goal to have this reasonably done by end of June)

  • We don't have them all and there are 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?)

Community outreach and list coordination

Goal of coordinating with various other license lists to make sure SPDX has licenses from these lists and check short name matching (or create "translation" document if different)

Fedora license list

owner: Paul Madick (goal to have first pass for Legal Team to begin reviewing by mid-June)

  • will need to check lists for discrepancies, i.e. are there licenses on Fedora list that are not on SPDX-LL and if so, decide to add; also need to create short-name matching matrix due to Fedora using different type of categorization for its short names

Fossology

owner: TBD assigned

Gentoo

owner: TBD assigned

Suse

owner: TBD assigned

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 directoryShould the legal group aggregate industry best practices and come up with a group of guidelines and provide some influence on that?

Retrieved from "https://wiki.spdx.org/index.php?title=Legal_Team/Current_Projects_and_Issues&oldid=2462"