Search results

1) GSoC - https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas - Process: SPDX a

1) 3.1 release: as it's already end of Feb, we will just aim for quarterly release

==SPDX 2.1.1 == * Context: This should be the same as 2.1 other than typos, bugs and formatting fixes.

1) 3.0 release - plan to do 3.1 around end of Jan, what should we aim to tidy up? * AGPL-1.0-only and AGPL-or-later need to be added

1) Brad’s presentation to ABA, IP Law section, subcommittee on computer pro

1) Brad’s ABA presentation: 20-25 people, including range of people/compani * fixes in Apache 1.0 and 1.1 licenses from Richard - will be part of next release, Brad added issue in X

** At least 3 or 4 are very promising, only 1 or 2 that aren’t that great

** Time expectations low as couple hours a week as much as 1 to 2 days a weeks ** Gary – 1 student, Java

1) welcome to Stephanie and issue of full access to pull requests? may need ....1 - added markup to names (add issue to 1.0), made attempt at change in 1.1 - now resolved

version 0.1 {| class="wikitable sortable" border="1"

...9 some illumos userspace tools]) do not (and are therefore presumably CDDL-1.0+). ...text of GPL-2.0 and still provides option for Concluded License to be GPL-1.0+ if no other info is found

1) update on presentation Jilayne and Kate did at FSFE workshop on non-Englis

# Assign a short identifier based on 1 * (0) Is the license an English written original? (YES=0 | NO=1)

* Thomas still moving over, Appendix 1. Base content is there. see:

1) Gary has been working on 2 things:

1) XML Update:

* Copyright proposal - agreed to change cardinality to 1 or more - target 2.2

1) Tracking of new licenses in Google sheet

1) Linus’ note identifier conversation continuation from last call

* EPL family = EPL-1.0, CPL-1.0, IPL-1.0 * NPL family = Nokia, NOSL, NPL-1.0, Motosoto, MPL-1.0, MPL-1.1, RSCPL, SISSL-1.2, SNIA

August 1, 2017

1) Went through the licenses under consideration / new requests: ...n German and English side-by-side; have some questions on sections 1.4 and 1.5 - will ask for more info from requestor and revisit on next call

...gives guidance, but looking outside the license text is needed. 5 files, 1 with text of GPL 2.0 license and 4 source files without any license info wh * Jilayne: 5 files, 1 with text of GPL 2.0 license and 4 source files without any license info wh

** 5 file example: 1 license file with full text of GPLv2, 4 source code files with no license i ...at least - includes common case. If any version of GPL, its denoted GPL-1.0+.

...some illumos userspace tools]) does not (and is therefore presumably CDDL-1.0+). # '''you find: 1 text file with the license text of GPLv2; and 4 source files with the stand

1) as stated in email: the only operator discussion is not exhausted, but not

1) only / or later clarification and proposal:

'''1) XML update & next steps'''

* More than 1 open source projects

'''1) revisit the [[Legal_Team/or-later-vs-unclear-disambiguation|only/or later/

## EUPL-1.2 needs to be added to XML files '''''(Matija & Alexios to review)''''' ## BSD-1-Clause - to add '''''(Alexios)'''''

1) 2018 meetings: will pick up again in January 11th - same time or any chang

1) Open Source Leadership Summit 2) Release 3.1

* last merges on 2.1.1 are pretty close; Thomas doing last merges then ready. Main change is from * Appendix 1 of spec(and one-pager on website) would have summary of above and links

1) Discussed proposal for Google Summer of Code: https://wiki.spdx.org/view/G 2) Looked at PRs and Issues (new license/exception requests) for pending 3.1 release

...Tagged anything else for 3.2 or later release. Did same with issues. the 3.1 release will now proceed: Gary will prepare the HTML pages for preview and

...generate a review version to send out. Expect the review time frame to be 1-2 weeks long. * 3.1 license list is still pending. Need to make sure all open issues on it are

1) discussed Google SoC project:

1) GSoC update:

==2.1.1== Thomas still working on the .pdf printing for 2.1.1, getting images inserted is problematic.

1) question re: upgrade spec license from CC-BY-3.0 to 4.0? (Issue 3 in spdx

1) 3.2 release

1) Monthly SPDX General call was earlier today and GSoC student, Tushar Mitta

1) General updates: GSoC is in last stretch, coordinate with Gary to have Tus

1) need to sort out emails that are not coming through unless approved and ap

1) Update on tooling that came out of GSoC:

1) license list tooling update from Gary - https://spdxtools.sourceauditor.co

1) 3.3 final PRs to merge before release: * license for source files associated with SPDX License List - changed to CC0-1.0 - no further comments, done

1) 3.3 is out and new RELEASE NOTES have been added to the repo, see: https:/

1) discussion of “license exceptions” description and particular requests