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
