THE SPDX WIKI IS NO LONGER ACTIVE. ALL CONTENT HAS BEEN MOVED TO https://github.com/spdx
Search results
Page title matches
- {| border="1" See Exception 121 KB (3,218 words) - 15:47, 6 March 2013
- ** Should we allow the + to be applied to any license? For example, EPL-1.0+? ...o long run. The inclusion of the LicenseListVersion field in the SPDX spec 1.2 does allow this to be done in a relatively clean way.7 KB (1,145 words) - 05:35, 14 March 2014
- ** 1 new exception * Lined up speakers for next 1-2 meetings2 KB (352 words) - 16:35, 7 January 2016
- == SPDX 2.1 Model == Below is the current SPDX 2.1 UML model.98 B (14 words) - 17:13, 1 April 2016
Page text matches
- {| border="1" See Exception 121 KB (3,218 words) - 15:47, 6 March 2013
- 1. Fedora builds versions into the short name, but it is done in a non-standa * ASL 1.0 (for Apache 1.0)4 KB (703 words) - 15:35, 6 March 2013
- * Canada +1 647 558 05881 KB (163 words) - 15:30, 8 September 2022
- ...ndbox_for_Sharing_Examples/OpenLogic_SPDX_1.0_beta_examples|OpenLogic SPDX 1.0 beta examples]] ...hnical_Team/Old/Sandbox_for_Sharing_Examples/SPDX_Use_Case_1|SPDX Use Case 1]]863 B (124 words) - 15:37, 6 March 2013
- * Open World Forum (September 30 and October 1 2010): Kim Weins talked about SPDX in the governance session at Open World * '''Debconf10''' (Aug 1-7 2010): Daniel German gave a talk on licenses in the Debian distribution a4 KB (514 words) - 14:06, 7 March 2013
- ...figure out and document how to add a license (ie. When you add a license - 1) create separate page; raw template text, user visible text - here's out ho * Target to have spec at 1.0 in 2010Q43 KB (513 words) - 10:59, 6 March 2013
- ...to include the SPDX file in a package but also wanting it to include a SHA-1 for the package) there has been a proposal based off of the SHA-1s of all t6 KB (985 words) - 10:59, 6 March 2013
- ...from spec versioning, process for including new licenses, list for version 1, etc.4 KB (579 words) - 10:59, 6 March 2013
- == Proposals for v1.1 == * [[Technical_Team/Proposals/2010-10-21/License_URLs|2010-10-21-1: License URLs]]3 KB (346 words) - 18:13, 17 November 2015
- ** we'll be adopting the 1 page per license proposal that Callaway put forward.2 KB (297 words) - 10:59, 6 March 2013
- ...m meets every other Thursday at 18:00 GMT (10:00AM PT, 11:00 MT, 12:00 CT, 1:00PM ET) starting on 14 January 2016. Call this number: (United States): +1-857-216-2871923 B (130 words) - 15:34, 8 September 2022
- ...corporating the inevitable feedback before we release the official version 1.0. The group is assembling a list of key projects for which to create SPDX( ...ter, there is information on how to participate available on our web site [1],[2]. Sub-groups with their own mail lists have recently formed around tech8 KB (1,228 words) - 14:47, 7 March 2013
- "(1) In the earlier days of Python, employee contracts and related law ensured2 KB (337 words) - 17:40, 5 March 2013
- ===Example 1: Simple SPDX file with non-standard license=== SPDXVersion: SPDX-1.06 KB (897 words) - 11:50, 7 March 2013
- ** Current lists, Technical- 10 (up 2), Business- 7 (up 1), Legal- 12 (up 5)2 KB (367 words) - 11:02, 6 March 2013
- {| width="650" border="1" -Finalize spec for 1.0 Final3 KB (367 words) - 11:28, 6 March 2013
- * Copyright - just a string for release 1 of SPDX3 KB (452 words) - 12:56, 6 March 2013
- 1 - Must be resolved for beta 2 - Want to resolve for beta, but is a must for the release 1 of the spec (e.g. can be resolved after the start of beta)2 KB (303 words) - 12:56, 6 March 2013
- Gary will be calling from Hawaii - we agreed to move the call to 1:00 Eastern time to accommodate the time zone differences.2 KB (251 words) - 13:58, 6 March 2013
- Note: Next weeks meeting will be at 1:00 Eastern time4 KB (646 words) - 13:56, 6 March 2013
- ...majority vote for people that attended the meeting (at least 5 people and 1 legal)3 KB (445 words) - 20:52, 28 February 2013
- ** 1/2 day track on legal related issues Thursday morning4 KB (646 words) - 11:02, 6 March 2013
- *** 1/2 day track on legal related issues Thursday morning3 KB (513 words) - 11:02, 6 March 2013
- ...majority vote for people that attended the meeting (at least 5 people and 1 legal)4 KB (746 words) - 20:52, 28 February 2013
- * Ready for presentation to other teams in the next 1-2 months ** 1/2 day track on legal related issues Thursday morning3 KB (497 words) - 11:44, 6 March 2013
- * Discussion on if we should prepend property names with cardinality of 1 to N with “has” – we will decide after completing the rest of the spr3 KB (419 words) - 13:56, 6 March 2013
- ** sub-section 2.1 SPDX Specification Version Number ...e future reference to format and define it to be just a string for version 14 KB (601 words) - 13:02, 6 March 2013
- * LicenseInfo fields – add the new syntax for license sets and mandatory 1 * Section 5.2 is currently 4.1 – renumber/format issue3 KB (484 words) - 13:03, 6 March 2013
- * 1) analyzed and data is insufficient to draw a conclusion * Cardinality of licenseInfoFromFile is 1 .. n2 KB (326 words) - 13:54, 6 March 2013
- ...pddl/1.0/|Open Data Commons PDDL 1.0] as a potential candidate to resolve #1 above.1 KB (166 words) - 18:48, 5 March 2013
- * A third delivery model – 1) SPDX is a sidecar to the package archive, 2) SPDX is embedded in the packa3 KB (416 words) - 13:12, 6 March 2013
- ...review (and clean up) bugs. Decide which ones need to be fixed for release 1.2 KB (237 words) - 13:13, 6 March 2013
- Version 1 shows the SPDX Home Page with 9 proposed child pages that would be availabl2 KB (313 words) - 11:59, 6 March 2013
- * Proposal – cardinality 1, String format2 KB (274 words) - 14:16, 6 March 2013
- ** Phil has speaking slot, JimZ should mention in Keynote, 1 pg handout, table2 KB (232 words) - 10:59, 6 March 2013
- ...' - probably more for informing new people than real working session, only 1 hour. Very few people from technical team attending event, so not enough ti2 KB (377 words) - 18:49, 5 March 2013
- ** SPDX booth staffing in progress; John Ellis working schedule; 1 pg handout will be available ...statement will be included in SPDX file at this time; we will revisit post 1.0 GA3 KB (449 words) - 11:22, 6 March 2013
- *** Use Case 1: In comparing an SPDX document to the files, the algorithm would need to be *** Use Case 2 would likely be done in a scenario where Use Case 1 would also be done (or in a scenario where the SPDX is used in a “side-ca3 KB (429 words) - 13:18, 6 March 2013
- [[Image:spdxdoodle2-1.jpg]] * '''Creator (Annotation): '''Equivalent to SPDX 1.0 Creation Information Creator10 KB (1,455 words) - 12:17, 7 March 2013
- *** Goal: At least 1 major community announcing support2 KB (350 words) - 20:52, 28 February 2013
- * Goal: Get cheat sheet out by General Team 1/122 KB (259 words) - 20:52, 28 February 2013
- == Version 1.1 == Tools need to be updated to the latest spec, Gary will review 1.1 draft once completed and update the Java tools to the latest spec2 KB (392 words) - 13:21, 6 March 2013
- ...majority vote for people that attended the meeting (at least 5 people and 1 legal)3 KB (572 words) - 22:16, 28 February 2013
- ....gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/profiles/license_groups?revision=1.102&view=markup (the above only covers 252 out of the 614 licenses presentl ** This would be a 1 day meeting in person with people involved in the software supply chain to4 KB (648 words) - 22:25, 28 February 2013
- * Work of tech team is focused on the 1.1 spec. * They did a review of the draft 1.1 spec and there were a few follow up items.2 KB (367 words) - 10:59, 6 March 2013
- ...tely a work in progress. Most of the class definitions can be found in the 1.0 spec in the RDF appendix (model) or in [[Technical_Team/Proposals/Rough_p See the attached document for the mapping between the SPDX 1.0 properties and this proposal.2 KB (284 words) - 18:13, 29 July 2014
- ** This would be a 1 day meeting in person with people involved in the software supply chain to2 KB (336 words) - 20:52, 28 February 2013
- * Date for version 1.1 == Date for 1.1 ==2 KB (287 words) - 14:13, 6 March 2013
- ** End User Panel: How SPDX fits into a Corporate Compliance Program -- 1 hrs2 KB (318 words) - 20:53, 28 February 2013
- * Minutes for 2011/1/26 approved * 1.1 is very close. Gate is validating the verification algorithm.2 KB (251 words) - 10:59, 6 March 2013
- * agenda seems to be broken down into two types of audiences: 1) what is it, how do I get started; 2) what is it, not interested in it now,3 KB (513 words) - 17:40, 5 March 2013
- ** End User Panel: How SPDX fits into a Corporate Compliance Program -- 1 hrs3 KB (451 words) - 20:53, 28 February 2013
- ===Example 1=== ...<filename>.spdx.zip files will not be backward compatible with SPDX 1.0 tooling. However, the SPDX Data Files they contain can be, and can be eas2 KB (245 words) - 11:32, 7 March 2013
- * 12:15-1:45 Discussion: Challenges and Approaches to Implementing SPDX led by SPDX E * 1:45-2:00 Break874 B (119 words) - 12:00, 6 March 2013
- ** not going to worry about 1 and 2 for now, but 3 could be used for listing items to be discussed on thu6 KB (974 words) - 13:56, 7 March 2013
- == Steps needed to close on v 1.1 of the spec == ** Appendix 1 will be updated to reflect what’s on the website as of date -- Kate4 KB (549 words) - 13:28, 6 March 2013
- * A)PROPOSAL 1: leave 'as is' on license list now which is that these scenarios are captur **** (1)But then, what about when you aren't sure - which short identifier do you u4 KB (732 words) - 18:52, 5 March 2013
- Collecting use cases – concern on the deadline – 1 ½ weeks isn’t enough. Suggest 5 from today deadline. Agreed to 5 weeks.615 B (91 words) - 13:29, 6 March 2013
- ...ovide link to OSI license, verify that it is the same text as supplied in #1 above.4 KB (652 words) - 18:52, 5 March 2013
- 1) Discuss status of Adding Licenses proces3 KB (416 words) - 18:08, 5 March 2013
- * Spec 1.1 Charter: * Spec 1.2 Why is a common format for data exchange needed?7 KB (1,114 words) - 22:17, 28 February 2013
- == 1.1 Discussion == ** Discussion on tag name. Two proposals for the definition of the term – 1) a reference to the canonical form of the license as the source of the lice2 KB (245 words) - 14:11, 6 March 2013
- * 1.1 update == 1.1 Discussion ==2 KB (216 words) - 13:32, 6 March 2013
- * item #1 completed, will be removed ...license list to be uploaded and published by 6/20 for inclusion in Spec 1.15 KB (810 words) - 18:10, 5 March 2013
- == Guideline 1. Verbatim Text == ** not going to happen for 1.1, but for 2.0? is this as simple as return status indication or would we nee4 KB (604 words) - 17:40, 5 March 2013
- <nowiki>1) Matching text – indicating replaceable or omitable text. Last call we de3 KB (568 words) - 17:40, 5 March 2013
- 1) discussed various aspects of recent mailing lists posts in regards to lice1 KB (178 words) - 17:41, 5 March 2013
- 1) New License Request for GNU Affero General Public License v3.0 or later (A3 KB (532 words) - 17:41, 5 March 2013
- == Linuxcon (Panel, Working group meeting, 1.1 PR?) == Working group meeting on Tuesday from 1-6pm will focus on 2.0. The first hour will be reserved to provide an SPDX i2 KB (346 words) - 20:53, 28 February 2013
- ...faster path of success and it is critical to get to that point. Otherwise, 1) recruiting other companies into this WG will be a mission impossible chall ...nce a lot of folks are expected to attend, then it would make sense to add 1 more day to the meeting to cover these items.5 KB (870 words) - 11:28, 6 March 2013
- {| style="width: 637px" border="1" 111 KB (1,751 words) - 09:53, 11 April 2013
- * The volunteer based model worked well to get SPDX to 1.x. Going forward there is a need to have a different model. This will be co ...content in the form of practical papers - tutorial style, doing more than 1 F2F (for all of SPDX WG) and inviting target companies to attend a 0.5 day3 KB (450 words) - 14:04, 7 March 2013
- * comment (by creator) 0:1 '''WORKFLOW''' is a 3.1 issue.2 KB (317 words) - 18:20, 23 April 2013
- ...name in third clause of BSD; third, fourth, and fifth clauses of Apache 1.1; or in disclaimer clauses). And, if the latter, how to provide such markup The group supported option #1 above, and suggested using markups such as the following:6 KB (976 words) - 20:06, 6 June 2013
- * 1.2 release ** Could be handled by regex (e.g. 0:1)2 KB (281 words) - 15:25, 2 May 2013
- ...dular and can be assembled into configurations from a 1 slide version to a 1 hour presentations254 B (40 words) - 12:09, 20 May 2013
- ...b.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681 <br /> ...b.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=0 <br />13 KB (1,920 words) - 17:11, 16 September 2017
- 1) new page for tracking licenses – Jack added a table format for ease of u2 KB (371 words) - 17:46, 9 May 2013
- ...age for the license - thus allowing the license list to be maintained with 1 file per license (instead of two)3 KB (546 words) - 20:06, 6 June 2013
- 1) review changes to License Request page here: http://spdx.org/spdx-license-3 KB (433 words) - 20:08, 6 June 2013
- == Version 1.17 of the SPDX License List == Version 1.17 of the SPDX License List has been released (finally)!! .zip file is post3 KB (481 words) - 20:07, 6 June 2013
- 1 License Template 1.1 Standard License List Template Download2 KB (327 words) - 17:13, 17 June 2013
- '''1) License tracking table''' – need an owner (Dennis was volunteered by Mic * BSD, Apache, GPL, LGPL, Eclipse, MIT, MPL v1.1, CDDL, CPL,4 KB (614 words) - 18:33, 20 June 2013
- '''1) Standard Headers issues''' * Mark will do this work: 1) general review of Standard Headers for correctness; 2) add markup (variabl2 KB (366 words) - 18:08, 14 May 2015
- '''1) LinuxCon is coming up! September 16-18 in New Orleans''' ...) SISSL license issue brought on list by Camille: we have SISSL (version 1.1), but there is also a v1.2'''3 KB (535 words) - 18:04, 21 July 2013
- '''1) LinuxCon, various other updates, administrative stuff'''4 KB (594 words) - 18:38, 1 August 2013
- '''1) License Matching Guidelines: status update, go over any questions for new3 KB (568 words) - 19:24, 29 August 2013
- {| class="wikitable sortable" border="1" {| class="wikitable sortable" border="1"8 KB (1,185 words) - 16:03, 25 January 2016
- 1) Ruby License: Ruby has a notice at the top of the license stating the dis ...rs that other text changed incrementally, much earlier (in between 1.4 and 1.6 of Ruby) making it hard to determine where to call it different versions.3 KB (449 words) - 18:06, 12 September 2013
- as defined by the Linux Foundation's SPDX project [1]. For example, :* SPDX-License-Identifier: (LGPL-2.1 AND BSD-2-CLAUSE)7 KB (1,017 words) - 15:45, 14 June 2016
- '''1) Summary of LinuxCon happenings'''2 KB (387 words) - 18:22, 26 September 2013
- Oct. 1, 2013 * SPDX 1.22 KB (257 words) - 19:05, 1 October 2013
- {| class="wikitable sortable" border="1" | SPDX 2.0 RC 17 KB (1,051 words) - 15:41, 13 February 2015
- '''1) License Matching Guidelines'''2 KB (419 words) - 20:33, 10 October 2013
- {| class="wikitable sortable" border="1" | SPDX-TR-2014-14 KB (674 words) - 06:48, 17 September 2014
- 1) License Matching Guidelines2 KB (236 words) - 21:45, 6 November 2013
- '''1) License Matching Guidelines (Jilayne)''' - The SPDX License List Matching ...sion numbering for license list - does it need to follow spec (in terms of 1.x and 2.x)? or can it follow it's own numbering? does it matter?4 KB (731 words) - 19:12, 7 November 2013
- 1) Fedora list (Zac) - went through next set of licenses to view and made not ...ribution - it is verbatim 3-clause, plus another clause; sort of Apache 1.1-ish; ADD, but will use different short identifier than Fedora to better lin2 KB (317 words) - 19:07, 21 November 2013
- ...Ref-1 , :LicenseRef-4 , :LicenseRef-2 , Apache-1.0 , :LicenseRef-3 , MPL-1.1 , Apache-2.0 ...mber :LicenseRef-1 , :LicenseRef-4 , :LicenseRef-2 , :LicenseRef-3 , MPL-1.1 , Apache-2.03 KB (447 words) - 19:44, 9 February 2014
- 1) what on the plate?4 KB (620 words) - 20:59, 5 December 2013
- ** Working through real examples in 1.2 and 2.0 * [[Legal Team/License Expression Review 1|License Expression Syntax]] - MarkG2 KB (339 words) - 19:17, 18 February 2014
- 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? -->4 KB (712 words) - 17:45, 6 February 2014
- '''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 team3 KB (603 words) - 19:33, 21 January 2016
- ** Disadvantage, there is not a 1:1 mapping6 KB (1,021 words) - 05:18, 18 February 2016
- '''1) Discuss 2014 priorities'''913 B (135 words) - 15:16, 4 March 2014
- '''1) Bzip2 license request''' – accepted; will be added as of next release of2 KB (286 words) - 16:19, 4 March 2014
- '''1) new license requests''': Microsoft Patterns & Practices License (MSPPL)1 KB (215 words) - 19:18, 6 March 2014
- == 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)''31 KB (4,385 words) - 17:36, 13 November 2014
- * [[Legal Team/License Expression Review 1|License Expression Syntax]] - MarkG2 KB (334 words) - 15:51, 10 March 2014
- * Number of people - 2 from W.R., 2-3 from Black Duck, 1 Source Auditor, Kate, others?2 KB (261 words) - 19:04, 11 March 2014
- == 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''3 KB (413 words) - 16:54, 19 June 2014
- '''1) Collab Summit agenda''' - discussed time allotted on Friday for License Ex ...e.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dENVVHFNeG5hQjAyYjQ3bm1VVUdjOFE#gid=1933 B (152 words) - 17:38, 20 March 2014
- April 1, 20142 KB (257 words) - 19:04, 1 April 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 analysis2 KB (284 words) - 19:02, 15 April 2014
- '''1) LF Collaboration Summit Review'''449 B (62 words) - 06:36, 1 May 2014
- '''1) LinuxCon (Phil)'''757 B (99 words) - 06:40, 1 May 2014
- '''1) Discussion re: priorities and the release of SPDX 2.0'''1 KB (195 words) - 18:12, 15 May 2014
- '''1) License Expression''' - Mark Gisi drafting new license expression for the3 KB (524 words) - 18:12, 15 May 2014
- '''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 later4 KB (628 words) - 17:59, 29 May 2014
- '''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 ev6 KB (868 words) - 03:40, 15 June 2018
- 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 regarding2 KB (413 words) - 18:21, 26 June 2014
- July 1, 20141 KB (221 words) - 00:38, 4 July 2014
- '''1) Fedora List''' – Reviewed questions regarding the below licenses.3 KB (412 words) - 05:31, 24 July 2014
- 1) The next release of the license list is coming together and almost ready!3 KB (457 words) - 22:43, 24 July 2014
- '''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 closer5 KB (880 words) - 19:44, 7 August 2014
- ** Not a 1:1 mapping of usage to relationshiptypes - so we really shouldn't change the n2 KB (256 words) - 20:51, 9 September 2014
- {| class="wikitable sortable" border="1" | SPDX-TR-2014-15 KB (698 words) - 15:50, 11 October 2016
- == 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''3 KB (413 words) - 00:31, 18 September 2014
- '''1) Fedora License List'''1 KB (186 words) - 22:26, 24 September 2014
- '''1) License expression syntax'''1 KB (204 words) - 23:37, 24 September 2014
- '''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?5 KB (830 words) - 17:29, 2 October 2014
- ** Dec 1. Deadline for feedback ** Dec. 1-17 incorporate feedback3 KB (423 words) - 01:38, 8 October 2014
- * December 1 - deadline for feedback * Dec 1-17: incorporate feedback2 KB (305 words) - 16:44, 22 October 2014
- '''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?6 KB (1,032 words) - 21:23, 30 October 2014
- '''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 t7 KB (1,273 words) - 22:48, 30 October 2014
- '''1) Explanation text for deprecated licenses''' - made minor revisions and tal * OpenChain - 1/2 day - Friday morning2 KB (331 words) - 19:13, 11 December 2014
- 1) discussed standard header field - had previously discussed removing this f680 B (103 words) - 16:02, 24 November 2014
- '''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, bu7 KB (1,113 words) - 19:09, 24 November 2014
- ** Near term schedule: Draft Nov 14, feedback by Dec 1.2 KB (261 words) - 13:20, 27 November 2014
- ** Coordinating with Open Chain who will share our room for 1/2 day1 KB (151 words) - 16:28, 4 December 2014
- * Rooms for Wednesday, Thursday, and 1/2 of Friday.1 KB (176 words) - 18:34, 31 December 2014
- '''1) SPDX License List 2.0-release candidate is up!!''' see: http://spdx.org/li4 KB (624 words) - 20:47, 8 January 2015
- January 1, 2015 ...the meeting times going forward to every Tuesday at 10:00AM Pacific time, 1:00PM Eastern2 KB (227 words) - 19:42, 13 January 2015
- ...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=6952126813 KB (476 words) - 19:38, 22 January 2015
- '''1) Licenses Under Consideration''' ...b.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=6952126811 KB (162 words) - 18:55, 5 February 2015
- 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 encouragi10 KB (1,529 words) - 18:56, 26 January 2017
- '''1) Collab Summit - quick update''': See links here to various updates, includ2 KB (386 words) - 16:52, 19 March 2015
- 1) Went over the following updated pages made changes or revisions as needed. * will add, no template needed, short identifier = UPL-1.01 KB (201 words) - 18:04, 19 March 2015
- 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 l1 KB (167 words) - 16:05, 5 May 2015
- '''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.12 KB (421 words) - 16:32, 5 May 2015
- ...any, but the snippet is a byte range in a specific file, so it needs to be 1 file to many snippets1 KB (216 words) - 16:55, 5 June 2015
- ...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=0 * discussed use of numbers in existing exceptions and the ones to add for 2.1 - decided to not use a version number unless there is one for the exception3 KB (562 words) - 21:57, 11 June 2015
- '''1) Update on joint call with Tech team regarding NONE and NOASSERTION''' - ...f licenses to add to the License List''' - OBSD license approved, Cecil 2.1 approved, Open Government License still under consideration since multiple846 B (131 words) - 04:11, 9 July 2015
- '''1) status of v2.1''' - up now. quality control? release notes? ...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=01 KB (165 words) - 17:45, 9 July 2015
- 1) update from last week's call from Mark:3 KB (516 words) - 04:30, 7 August 2015
- ...e discussion concerning SPDX. Jilayne created a spreadsheet providing a 1:1 match between SPDX and Fedora short identifiers. Developers are looking fo1 KB (203 words) - 04:38, 7 August 2015
- ...37be4de78152fbd3ed54761627c960010ce26a3/src/licensedcode/data/rules/apache-1.1_38.RULE#L17 ...78152fbd3ed54761627c960010ce26a3/src/licensedcode/data/rules/bzip2-libbzip-1.0.5_1.RULE#L123 KB (3,832 words) - 17:49, 20 July 2017
- 1) Update from LinuxCon - quick thoughts from Mark, but will do bigger update2 KB (368 words) - 00:55, 21 August 2015
- Sept 1, 2015 * Kate to research byte offset starting with 1 rather than 01 KB (168 words) - 18:16, 1 September 2015
- ** Decided to make the change for 2.1 and not rev in 2.0 ...and files as a scenario for a Snippet Comment on License into section X.5.12 KB (295 words) - 19:23, 15 September 2015
- '''1) Announcements/updates:''' ...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=0 for potentially adding to v2.2 (see spreadsheet for full info, summ6 KB (1,053 words) - 18:58, 17 October 2015
- Sept 1, 2015878 B (109 words) - 16:20, 23 September 2015
- '''1) LinuxCon Europe update:''' ...go from there, but as to overall timing - would be good to line up for v2.1 aiming to have that ready for Collab Summit (end of March). Note: Kate is w3 KB (565 words) - 18:59, 17 October 2015
- ...d process can create a canonical "correct" form of the text to-match, thus 1) obviating implementations from the need to write boilerplate parsing code ...urrent markup – but I observe two elements in the current markup syntax: 1) entity replacement and 2) optional section blocks. These are quite readily13 KB (2,025 words) - 16:19, 27 October 2015
- * Bytes ranges - start at 1 or 0 ** The RDF standard states 11 KB (228 words) - 19:10, 3 November 2015
- 1) v2.3 items: ...ore "contribution-friendly" infrastructure (e.g., Github) should be number 1 priority for 20163 KB (530 words) - 19:04, 10 December 2015
- ** 1 new exception * Lined up speakers for next 1-2 meetings2 KB (352 words) - 16:35, 7 January 2016
- 1) A discussion came up on the tech team regarding how to identify when there4 KB (671 words) - 19:54, 7 January 2016
- 1) Quick update from general call; good agenda shaping up for Collab Summit f2 KB (325 words) - 18:50, 4 February 2016
- * Planning for Collab Summit: 1/2 day Tech team and 1/2 day Legal, with SPDX “Office Hours” for folks to bring questions, iss6 KB (939 words) - 11:48, 16 February 2016
- '''1) License List templatizing proposal''': update/review from Kris on state of ...l have a room for work group all day on Wednesday: morning for review of 2.1 spec and afternoon for license templatizing work - would be great to have a3 KB (554 words) - 19:18, 18 February 2016
- <p><strong>1. How These Guidelines Are Applied</strong></p> <p style="padding-left: 30px;"><span style="text-decoration: underline;">1.1 Purpose:</span> To ensure consistent results by different SPDX docume19 KB (2,883 words) - 00:36, 31 March 2016
- ** 1 new exception * Lined up speakers for next 1-2 meetings2 KB (352 words) - 13:08, 1 March 2016
- March 1, 20161 KB (158 words) - 18:59, 1 March 2016
- ...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681 * Free Art License 1.3 - approved for 2.4, but need to resolve different language/versions quest5 KB (841 words) - 14:29, 4 March 2016
- 1) Review proposed draft for new appendix to the spec: Appendix V - Using SPD * OSET Public License version 2.1 - short identifier issue, hoping to hear back from Heather Meeker by Monday4 KB (660 words) - 18:13, 17 March 2016
- 1) update from Collab Summit: * went over 2.1 spec, Appendix V will be included - can view now as part of entire spec, so2 KB (404 words) - 02:01, 8 April 2016
- 1) New license requests and related topics:3 KB (480 words) - 18:11, 28 April 2016
- ...ussion on this latter item with legal team, but not pushing to do so for 2.1 release. Mark can try to start collecting use cases so we can assess soluti3 KB (466 words) - 19:06, 12 May 2016
- 1) Normal business/updates:3 KB (489 words) - 18:45, 26 May 2016
- 1) review of to-do items for 2.5 release and what's "on hold'1 KB (229 words) - 18:16, 23 June 2016
- 1) nuclear license discussion for addition to v2.5 release- there are 3 varia1 KB (178 words) - 22:44, 7 July 2016
- '''1) v2.5 is now live'''3 KB (495 words) - 20:46, 21 July 2016
- Next call is Aug 18, then Sept 1 - so we may schedule an additional call the week of Aug 22nd if need be2 KB (327 words) - 18:20, 4 August 2016
- 1) Went through all items in Github repo that were tagged "needs legal discus ...use it and what guidelines we use to make this call. Matching Guidelines 2.1.4 is starting point, explaining the omitable text means text marked as such1 KB (219 words) - 19:27, 18 August 2016
- *** Appendix 1 is list of licenses - check8 KB (1,422 words) - 20:21, 4 August 2017
- * SPDX 2.1 all comment incorporated * 1 1/2 month feedback cycle2 KB (312 words) - 15:39, 1 September 2016
- ** This would allow a 1:1 mapping to RDFa1,005 B (148 words) - 18:12, 27 September 2016
- ...is non-conformant UTF-8 an error? Gary - Yes, it should be an error. +1 Kris.3 KB (611 words) - 20:07, 26 October 2016
- 1) Update from joint call with tech team, Oct 25th, to go over XML tag names.3 KB (489 words) - 17:29, 3 November 2016
- 1) Reviewed Dennis' draft document of process for Github management of licens2 KB (318 words) - 19:08, 10 November 2016
- ...e.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681 * see notes for LPG-Bolivia-1.0 and Unicode licenses in spreadsheet (to add)2 KB (378 words) - 19:27, 22 December 2016
- ** should the SPDX License List and all it entails (e.g. Appendix 1, 2, 4) be its own spec, which would enable development at a different pace4 KB (680 words) - 17:30, 23 February 2017
- * 12:00-1:00 Lunch * 1:00-2:00 File formats discussion (tech) – Yev will provide some examples o2 KB (359 words) - 21:08, 31 January 2017
- 1) Open Source Leadership Summit, Feb 14-16 at Squaw Valley, Lake Tahoe, CA923 B (145 words) - 22:30, 20 January 2017
- 1. Use a comment statement5 KB (725 words) - 21:11, 31 January 2017
- *** Remaining differences are centered on (1) naming things and (2) external references5 KB (755 words) - 13:12, 2 March 2021
- 1-5 ...urage them to continue to contribute and maintain ongoing dialog through 1:1 emails with the mentors, inclusion in the SPDX mailing lists, and encouragi7 KB (1,088 words) - 18:34, 16 February 2017
- ** At the outset Yocto build only supported SPDX 1.0 and uses FOSSology for scanning *** Based on LiD Scores (1-perfect)4 KB (643 words) - 16:59, 2 March 2017
- 1) SPDX License List v2.6 - remaining things to tie up before release3 KB (528 words) - 19:23, 16 February 2017
- 1) GSoC - https://wiki.spdx.org/view/GSOC/GSOC_ProjectIdeas - Process: SPDX a4 KB (701 words) - 17:13, 11 January 2019
- 1) 3.1 release: as it's already end of Feb, we will just aim for quarterly release2 KB (374 words) - 14:58, 27 February 2018
- ==SPDX 2.1.1 == * Context: This should be the same as 2.1 other than typos, bugs and formatting fixes.2 KB (256 words) - 22:19, 23 January 2018
- 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 added4 KB (678 words) - 03:07, 12 January 2018
- 1) Brad’s presentation to ABA, IP Law section, subcommittee on computer pro1 KB (206 words) - 18:39, 30 March 2017
- 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 X1 KB (168 words) - 18:42, 30 March 2017
- ** At least 3 or 4 are very promising, only 1 or 2 that aren’t that great2 KB (277 words) - 15:30, 6 April 2017
- ** Time expectations low as couple hours a week as much as 1 to 2 days a weeks ** Gary – 1 student, Java1 KB (139 words) - 12:23, 13 April 2017
- 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 resolved2 KB (303 words) - 08:38, 26 April 2017
- version 0.1 {| class="wikitable sortable" border="1"2 KB (240 words) - 17:26, 1 June 2017
- ...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 found26 KB (4,214 words) - 09:16, 14 November 2017
- 1) update on presentation Jilayne and Kate did at FSFE workshop on non-Englis1 KB (167 words) - 22:33, 22 May 2017
- # Assign a short identifier based on 1 * (0) Is the license an English written original? (YES=0 | NO=1)14 KB (2,314 words) - 04:08, 1 June 2017
- * Thomas still moving over, Appendix 1. Base content is there. see:3 KB (426 words) - 21:04, 13 July 2017
- 1) Gary has been working on 2 things:2 KB (274 words) - 06:23, 9 June 2017
- 1) XML Update:3 KB (449 words) - 20:08, 5 July 2017
- * Copyright proposal - agreed to change cardinality to 1 or more - target 2.2856 B (121 words) - 03:57, 26 July 2017
- 1) Tracking of new licenses in Google sheet1 KB (159 words) - 03:35, 28 July 2017
- 1) Linus’ note identifier conversation continuation from last call2 KB (370 words) - 18:24, 6 July 2017
- * 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, SNIA7 KB (1,125 words) - 16:51, 8 August 2017
- August 1, 20171 KB (159 words) - 20:43, 1 August 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 call2 KB (243 words) - 23:06, 3 August 2017
- ...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 wh7 KB (1,031 words) - 18:10, 10 August 2017
- ** 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+.3 KB (531 words) - 20:55, 17 August 2017
- ...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 stand13 KB (2,051 words) - 01:25, 30 September 2017
- 1) as stated in email: the only operator discussion is not exhausted, but not2 KB (405 words) - 20:39, 14 September 2017
- 1) only / or later clarification and proposal:4 KB (740 words) - 19:54, 12 October 2017
- '''1) XML update & next steps'''3 KB (492 words) - 20:16, 12 October 2017
- * More than 1 open source projects1 KB (158 words) - 00:34, 1 November 2017
- '''1) revisit the [[Legal_Team/or-later-vs-unclear-disambiguation|only/or later/3 KB (563 words) - 09:17, 14 November 2017
- ## EUPL-1.2 needs to be added to XML files '''''(Matija & Alexios to review)''''' ## BSD-1-Clause - to add '''''(Alexios)'''''4 KB (618 words) - 00:59, 12 December 2017
- 1) 2018 meetings: will pick up again in January 11th - same time or any chang2 KB (416 words) - 06:49, 22 December 2017
- 1) Open Source Leadership Summit 2) Release 3.12 KB (258 words) - 17:04, 31 January 2018
- * 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 links6 KB (939 words) - 20:02, 9 March 2018
- 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 release1,016 B (160 words) - 17:33, 5 April 2018
- ...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 and718 B (113 words) - 17:33, 5 April 2018
- ...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 are3 KB (532 words) - 19:22, 5 April 2018
- 1) discussed Google SoC project:3 KB (588 words) - 17:25, 17 May 2018
- 1) GSoC update:2 KB (431 words) - 17:16, 17 May 2018
- ==2.1.1== Thomas still working on the .pdf printing for 2.1.1, getting images inserted is problematic.3 KB (415 words) - 02:05, 23 May 2018
- 1) question re: upgrade spec license from CC-BY-3.0 to 4.0? (Issue 3 in spdx3 KB (478 words) - 18:29, 14 June 2018
- 1) 3.2 release2 KB (257 words) - 21:19, 5 July 2018
- 1) Monthly SPDX General call was earlier today and GSoC student, Tushar Mitta1 KB (219 words) - 17:08, 26 July 2018
- 1) General updates: GSoC is in last stretch, coordinate with Gary to have Tus2 KB (326 words) - 17:10, 26 July 2018
- 1) need to sort out emails that are not coming through unless approved and ap1 KB (185 words) - 16:02, 24 September 2018
- 1) Update on tooling that came out of GSoC:873 B (147 words) - 16:05, 24 September 2018
- 1) license list tooling update from Gary - https://spdxtools.sourceauditor.co1 KB (179 words) - 20:41, 10 October 2018
- 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, done2 KB (291 words) - 16:41, 23 October 2018
- 1) 3.3 is out and new RELEASE NOTES have been added to the repo, see: https:/4 KB (622 words) - 21:47, 1 November 2018
- 1) discussion of “license exceptions” description and particular requests3 KB (508 words) - 18:23, 29 November 2018
- 1) Contributing updates and license submission tool:2 KB (342 words) - 18:58, 13 December 2018
- ** Proposed: In new XML format, any new property where cardinality is >1, will have two properties: singular to represent the individual element, an1 KB (176 words) - 01:38, 5 February 2020
- 1) Open Source Leadership Summit coming up, March 12-14. SPDX face2face on th1 KB (252 words) - 04:19, 22 February 2019
- 1) Open Source Leadership Summit agenda * SPDX f2f time is Monday afternoon 1-5pm3 KB (506 words) - 04:21, 22 February 2019
- 1) go through outstanding issues for 3.5 release and update: ...to have all tied up by next Friday, Mar 29 then do actual release on April 12 KB (336 words) - 18:13, 21 March 2019
- ** Merged some of the external repository features as a library into 4.1 * 1 draft – not sure which one this is1 KB (194 words) - 18:11, 9 April 2019
- ** Porting license expression library: 12 KB (217 words) - 18:05, 16 April 2019
- 1) Steve and Gary gave a great presentation on the general call prior to this2 KB (364 words) - 14:46, 2 May 2019
- 1) meetings posted for April 4th; most of work from April 18th are mostly in5 KB (931 words) - 23:26, 2 May 2019
- 1) Update on GSoC - maybe next call have Gary update us on which projects are ...iew, see: https://github.com/spdx/license-list-XML/blob/jlovejoy-inclusion-1/DOCS/what-why-how.md2 KB (427 words) - 17:35, 16 May 2019
- 1) GSoC update from Umang who is working on a project to enhance the workflow * 1 week prior: all PRs have been merged that are going to be part of release a4 KB (633 words) - 18:28, 30 May 2019
- ...ibe “ALL” the license that apply to a distinct package. If more than 1 separate work, it becomes confusing.3 KB (422 words) - 18:03, 4 June 2019
- 1) Joint tech/legal team calls:4 KB (700 words) - 03:50, 18 July 2019
- 1) Follow-up conversation re: “SPDX-Copyright:” or related tags – sugge ...ion on whether or not to add a license to the list. If >= 3 people give a +1 and no objections, then fine, easy to add. If complicated issues, then labe2 KB (354 words) - 18:11, 5 August 2019
- *** 1 Unskilled suppliers3 KB (495 words) - 18:52, 5 September 2019
- * 1 repository still needs to be moved – JavaScript project799 B (108 words) - 21:26, 17 September 2019
- * NTIA phase 1 documents are published at https://www.ntia.gov/sbom (SPDX is a recognized * Pushing Jan meeting to 1/9.2 KB (279 words) - 16:29, 5 December 2019
- ** Many to many? 1:1? 1:*, *:1?1 KB (175 words) - 02:20, 29 April 2020
- ==SPDX 2.2.1== * 1 to 2 weeks we should be “throwing the switch”3 KB (412 words) - 18:04, 12 May 2020
- ==SPDX 2.2.1== ...nging back one of student proposals through community bridge, update June 1.4 KB (603 words) - 19:38, 19 May 2020
- * The project is scheduled to start July 1 and run through end of September2 KB (335 words) - 20:27, 7 June 2020
- ** 2.1 is in good shape *** We are through phase 1 (funding for this year)1 KB (217 words) - 15:35, 6 August 2020
- * Will be turn on Sept. 13 KB (427 words) - 18:06, 18 August 2020
- *** pushed first draft of fields for (1) vulnerabilities, and (2) defects => impact on packages, false positives, e *** 1 for transitioning / updating online SPDX tools4 KB (561 words) - 18:15, 7 May 2021
- * [https://github.com/spdx/spdx-spec/blob/development/v2.2.1/ontology/spdx-ontology.owl.xml Current RDF/OWL document for SPDX spec] 1. Enable developers with a "code view" of tool-generated SPDX document close14 KB (2,166 words) - 14:36, 7 February 2022
