Search results

** Working through real examples in 1.2 and 2.0 * [[Legal Team/License Expression Review 1|License Expression Syntax]] - MarkG

1) Welcome Paul Madick from HP as our new Legal Team co-lead!! * Adaptive Public License 1.0 - http://spdx.org/licenses/APL-1.0 - extra clauses allowed at end? -->

'''1) Summary from joint call on Jan 19 with tech team''' - see notes posted her ...Tuesday, Feb 2 @ Tuesdays at 18:00 GMT (10:00AM PT, 11:00 MT, 12:00PM CT, 1:00PM ET) - Jilayne to send invite to Legal team

** Disadvantage, there is not a 1:1 mapping

'''1) Discuss 2014 priorities'''

'''1) Bzip2 license request''' – accepted; will be added as of next release of

'''1) new license requests''': Microsoft Patterns & Practices License (MSPPL)

== GPL-1.0+ == '''Present:''' '' '+' as an operator example 1 (also see EPL-1.0+ AGPL-2.0+ examples to understand why '+' was made an operator)''

* [[Legal Team/License Expression Review 1|License Expression Syntax]] - MarkG

* Number of people - 2 from W.R., 2-3 from Black Duck, 1 Source Auditor, Kate, others?

== Rationale for Choosing the CC0 1.0 for SPDX File Data (SPDX-TR-2014-1)== '''Title''': ''Rationale for Choosing the CC0 1.0 for SPDX File Data''

'''1) Collab Summit agenda''' - discussed time allotted on Friday for License Ex ...e.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dENVVHFNeG5hQjAyYjQ3bm1VVUdjOFE#gid=1

April 1, 2014

*** Agree to remove - can come back to this in 2.1 ** Gary to send out 1 line descriptions for each relationship/usage type in the use case analysis

'''1) LF Collaboration Summit Review'''

'''1) LinuxCon (Phil)'''

'''1) Discussion re: priorities and the release of SPDX 2.0'''

'''1) License Expression''' - Mark Gisi drafting new license expression for the

'''1) Fedora List''' * Dennis to tag ones that were on list previously as 2.0, tagging 2.1 as those that seem next priority, and others beyond that; can decide later

'''1)''' “+” to be added to the SPDX Specification as an operator to denote ...would also be a valid license expression as well: EPL-1.0+ which means EPL-1.0 or a later version. The change of the “+” to an operator will make ev

1) dial-in info is going to change as per the next meeting; the invite will ...ng that the link we had from the request states it's version 1.0.5 but the 1.0.6 (current) download includes a license with the last sentence regarding

July 1, 2014

'''1) Fedora List''' – Reviewed questions regarding the below licenses.

1) The next release of the license list is coming together and almost ready!

'''1) SPDX License List v1.20 will be live tomorrow, Aug 8!!''' ** Dennis has identified suggested next round additions with a "2.1" in the release field - to be discussed as 2.0 release gets closer

** Not a 1:1 mapping of usage to relationshiptypes - so we really shouldn't change the n

{| class="wikitable sortable" border="1" | SPDX-TR-2014-1

== Rationale for Choosing the CC0 1.0 for SPDX File Data (SPDX-TR-2014-1)== '''Title''': ''Rationale for Choosing the CC0 1.0 for SPDX File Data''

'''1) Fedora License List'''

'''1) License expression syntax'''

'''1) Revised schedule for 2.0 update''' - SPDX Core Team met and discussed the * http://spdx.org/licenses/RHeCos-1.1 - review for template need?

** Dec 1. Deadline for feedback ** Dec. 1-17 incorporate feedback

* December 1 - deadline for feedback * Dec 1-17: incorporate feedback

'''1) Revised schedule for 2.0 update''' - SPDX Core Team met and discussed the * http://spdx.org/licenses/RHeCos-1.1 - review for template need?

'''1) Revised schedule for 2.0 update''' - Tech Team has sent out revised schedu ...do 2.0 for pre-release and have option/consider more of the ones marked 2.1 for official release in Feb but need to check with tech team to make sure t

'''1) Explanation text for deprecated licenses''' - made minor revisions and tal * OpenChain - 1/2 day - Friday morning

1) discussed standard header field - had previously discussed removing this f

'''1) New license requests:''' ...ptions currently on the License List) and then add the ones marked as “2.1” for the official release in February. FTLK is on the exception list, bu

** Near term schedule: Draft Nov 14, feedback by Dec 1.

** Coordinating with Open Chain who will share our room for 1/2 day

* Rooms for Wednesday, Thursday, and 1/2 of Friday.

'''1) SPDX License List 2.0-release candidate is up!!''' see: http://spdx.org/li

January 1, 2015 ...the meeting times going forward to every Tuesday at 10:00AM Pacific time, 1:00PM Eastern

...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681

'''1) Licenses Under Consideration''' ...b.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681

1-5 ...urage them to continue to contribute and maintain ongoing dialog through 1:1 emails from the mentors, inclusion in the SPDX mailing lists, and encouragi

'''1) Collab Summit - quick update''': See links here to various updates, includ

1) Went over the following updated pages made changes or revisions as needed. * will add, no template needed, short identifier = UPL-1.0

1. Feedback regarding SPDX v2.0: Mark Gisi provided an update includi ...b.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681: Approved the spencer license, need to decide on names for l

'''1) SPDX 2.0 is on the verge of release'''. Mark had made recommendations in ...xt. Sorts by upper case, then lower case - see if that can be fixed for 2.1