THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Difference between revisions of "Legal Team/Minutes/2016-01-21"
From SPDX Wiki
< Legal Team | Minutes
(Created page with "=== Attendees === * Dennis Clark * Kyle Mitchell * Mark Gisi * Jilayne Lovejoy === Agenda === 1) summary from joint call on Jan 19 with tech team 2) new licenses on OSI li...") |
|||
| Line 5: | Line 5: | ||
* Mark Gisi | * Mark Gisi | ||
* Jilayne Lovejoy | * Jilayne Lovejoy | ||
| + | * Alas Tse | ||
| + | * Eric Weddington | ||
=== Agenda === | === Agenda === | ||
| − | 1) | + | 1) Summary from joint call on Jan 19 with tech team - see notes posted |
| + | * Kyle able to help; added point that anything that enables people to contribute is a good thing (not everyone can make calls, etc.), but be careful at opening the fire hose on the license list via Github; mailing list might be better for some things, whereas Github may create "drive-by" pull requests | ||
| + | * Gary O'Neall has put up a Google doc | ||
| + | * Collab Summit is Mar 29-31, Squaw Valley, CA - would be good to have as many people there as possible | ||
| + | * | ||
2) new licenses on OSI list: review to add to SPDX, need short identifiers | 2) new licenses on OSI list: review to add to SPDX, need short identifiers | ||
| − | http://opensource.org/licenses/OPL-2.1 | + | * is OSI adds a license, automatically should be added to SPDX list, just a matter of coming up with short identifier and mechanics of getting it on license list. Need to add a sentence to this effect on the overview page: http://spdx.org/spdx-license-list/license-list-overview (Jilayne to come up proposed text to add and where to add it - email to group for vetting). |
| − | http://opensource.org/licenses/LiLiQ-P-1.1 | + | * maybe good to give OSI something to put in parenthesis, e.g., (SPDX identifier to come) and something to put on the page itself, e.g., a notification that SPDX identifier is coming and that URL might change. Kyle to provide Kate with some proposed language. |
| − | http://opensource.org/licenses/LiLiQ-R-1.1 | + | * http://opensource.org/licenses/OPL-2.1 - somewhat problematic because OSET Public License in their exhibit uses "OPL" but this is already an abbreviation and short identifier for the Open Public License, which is on SPDX and Fedora list. Suggestion to reach out to OSET authors to ask to change short identifiers. Eric volunteered to do this. We will also let OSI that we are undertaking this route. |
| − | http://opensource.org/licenses/LiLiQ-Rplus-1.1 | + | * http://opensource.org/licenses/LiLiQ-P-1.1 - accept for next SPDX License List with LiLiQ-P-1.1 as short identifier, no markup, in French with link to English |
| + | http://opensource.org/licenses/LiLiQ-R-1.1 - accept for next SPDX License List with LiLiQ-R-1.1 as short identifier, no markup, in French with link to English | ||
| + | http://opensource.org/licenses/LiLiQ-Rplus-1.1 - accept for next SPDX License List, don't want "+" in short identifier b/c of LiLiQ-Rplus-1.1, no markup | ||
Revision as of 19:01, 21 January 2016
Attendees
- Dennis Clark
- Kyle Mitchell
- Mark Gisi
- Jilayne Lovejoy
- Alas Tse
- Eric Weddington
Agenda
1) Summary from joint call on Jan 19 with tech team - see notes posted
- Kyle able to help; added point that anything that enables people to contribute is a good thing (not everyone can make calls, etc.), but be careful at opening the fire hose on the license list via Github; mailing list might be better for some things, whereas Github may create "drive-by" pull requests
- Gary O'Neall has put up a Google doc
- Collab Summit is Mar 29-31, Squaw Valley, CA - would be good to have as many people there as possible
2) new licenses on OSI list: review to add to SPDX, need short identifiers
- is OSI adds a license, automatically should be added to SPDX list, just a matter of coming up with short identifier and mechanics of getting it on license list. Need to add a sentence to this effect on the overview page: http://spdx.org/spdx-license-list/license-list-overview (Jilayne to come up proposed text to add and where to add it - email to group for vetting).
- maybe good to give OSI something to put in parenthesis, e.g., (SPDX identifier to come) and something to put on the page itself, e.g., a notification that SPDX identifier is coming and that URL might change. Kyle to provide Kate with some proposed language.
- http://opensource.org/licenses/OPL-2.1 - somewhat problematic because OSET Public License in their exhibit uses "OPL" but this is already an abbreviation and short identifier for the Open Public License, which is on SPDX and Fedora list. Suggestion to reach out to OSET authors to ask to change short identifiers. Eric volunteered to do this. We will also let OSI that we are undertaking this route.
- http://opensource.org/licenses/LiLiQ-P-1.1 - accept for next SPDX License List with LiLiQ-P-1.1 as short identifier, no markup, in French with link to English
http://opensource.org/licenses/LiLiQ-R-1.1 - accept for next SPDX License List with LiLiQ-R-1.1 as short identifier, no markup, in French with link to English http://opensource.org/licenses/LiLiQ-Rplus-1.1 - accept for next SPDX License List, don't want "+" in short identifier b/c of LiLiQ-Rplus-1.1, no markup
3) 2016 tasks - follow-up license stuff, etc., get “owners"
4) New license / exception requests: - License Metadata Exception 1.0 - Kyle Mitchell (see: http://lists.spdx.org/pipermail/spdx-legal/2015-December/001611.html )
- Norwegian Licence for Open Gov’t Data
