2013 meeting schedule for Legal Team
Our meeting time and day will be changing to every other Thursday, 10am PT / 11am MT / 1pm ET (alternating with the Business Team calls). Dial-in info remains the same. I will send a new invite shortly. Thanks much, Jilayne ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: BSD-2|3-Clause-Clear typo
Good catch, Camille! I have made the change in the master file, but it may not show up on the website until we push another version. This could be a few months, as v1.17 was just released. I'll see about making an incremental change in the meantime... Thanks! Jilayne On 1/24/13 7:07 AM, Camille Moulin camille.mou...@alterway.fr wrote: Hi all, I think there is a typo on http://spdx.org/licenses/BSD-3-Clause-Clear : the licence has BSD-3-Clause-Clear as ID but BSD 2-clause Clear License as full name (also on http://spdx.org/licenses/ ). Cheers, Camille ___ Spdx mailing list s...@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: OSI and SPDX license list
Martin - you read my mind, as I was just about to send an update of the outstanding OSI-SPDX License List issues. I'm copying Karl Fogel, John Cowan, as they are on the original string helping with these issues, as well as the license-discuss list for OSI. Complete list (combining yours and mine) of outstanding issues as follows, with past commentary and questions indicated with-- 1) Apple Public Source License 1.0 Apple Public Source License 1.1 Was this ever OSI approved? Note at top of fedora url says: This license is non-free. At one point, it could be found at http://www.opensource.apple.com/apsl/1.0.txt, but that link now redirects to APSL 2.0. A copy of the license text has been taken from archive.org's October 01, 2007 revision. The Archive shows that APSL 1.2 was approved. Wikipedia claims that APSL 1.0 was also approved, but gives no authority for this statement. That also matches my recollections (there was a considerable fuss at the time, because it was OSI-approved but not FSF-free, the first of the new licenses with that property). -- do I understand correctly that neither 1.0 nor 1.1 were OSI approved? A little confused by email comments/string, can someone from OSI clarify? 2) Artistic License 1.0 Karl/John/OSI: OSI approved, but only can find license on the superseded licenses category list. Also note that Perl link has 10 clause version of license, whereas OSI link has 9 clause with note at top about additional clause. for searching/templating reasons, these should probably be listed as two different licenses. Suggest naming as follows: Artistic License 1.0 (Perl) // Artistic-Perl-1.0 Artistic License 1.0 // Artistic-1.0 thoughts? Excellent idea, except maybe we should put the (Perl) before the version number, since Perl describes a flavor of the license and that flavor could conceivably happen to other versions, though we hope not. That would also match the proposed SPDX short name. Thus Artistic License (Perl) 1.0 // Artistic-Perl-1.0 Artistic License 1.0// Artistic-1.0 Would that work for you? For now I've renamed http://opensource.org/licenses/artistic-license-1.0 to opensource.org/licenses/Artistic-1.0, edited it to link correctly to the superseding version (Artistic-2.0), and to link to a new page opensource.org/licenses/Artistic-Perl-1.0. Now, independently of the above, there is a serious bug in the Perl clause, and while I understand why it was OSI-approved, I think the OSI approved its *intended* meaning rather than its textual meaning. This should really be a separate thread, but I want to at least write it down here now, so there's a record of it somewhere: The OSI page above says: | Some versions of the artistic license contain the following clause: | | 8. Aggregation of this Package with a commercial distribution is | always permitted provided that the use of this Package is | embedded; that is, when no overt attempt is made to make this | Package's interfaces visible to the end user of the commercial | distribution. Such use shall not be construed as a distribution of | this Package. | | With or without this clause, the license is approved by OSI for | certifying software as OSI Certified Open Source. That's great, except s/commercial/proprietary/ :-(. What the text obviously means is proprietary, and furthermore, if it were to be interpreted literally as commercial, then it would (to my mind) be clearly not open source. I'm not sure what to do about this now. I just wanted to mention it. Any review of old licenses, such as you have done, is bound to turn up issues like this. Thank goodness it's an issue with Artistic-Perl-1.0 and not with, say, GPL-2.0 :-). JL/SPDX: in regards to adding a new license/version for Artistic License (Perl) 1.0 this is a good idea and your naming suggestions are inline with the naming protocol for SPDX, so that's all good. BUT one problemŠ the actual license on the Perl site (http://dev.perl.org/licenses/artistic.html ) is not the same as the one here (http://www.opensource.org/licenses/Artistic-Perl-1.0) -- the OSI perl version is simply the Artistic License 1.0 verbatim with the additional clause. However, the license on the Perl site has other differences. I'm attaching a Word document with a merge and compare between the OSI Artistic Perl and the Perl site Artistic Perl licenses -- anyone know what to do about this? I feel like the one on the Perl site should be captured, but what about the OSI variation? For the moment, I'm not adding the Artistic Perl license to the SPDX License List until this is sorted out, as I don't want to add one and then have to change it later. -- There also appears to be a Clarified Artistic License which is different yet again. That is on the SPDX license list already (and assumed to NOT be OSI approved) 3) GNU Library General Public License v2 Was this ever OSI approved?
Re: New License Request
Thanks Till! We will begin review of this license on the next SPDX Legal call, which is this Thursday. Cheers, Jilayne Lovejoy SPDX Legal Team co-lead Corporate Counsel | OpenLogic, Inc. jlove...@openlogic.com | 720 240 4545 On 2/25/13 11:10 AM, Till Jaeger jae...@jbb.de wrote: Dear Ladies and Gentleman, Please find all information in the attached files 8and below). 1. German Free Software License 2. D-FSL-1.0 3. http://www.dipp.nrw.de/d-fsl/index_html/lizenzen/en/D-FSL-1_0_en.txt http://www.dipp.nrw.de/d-fsl/index_html/lizenzen/de/D-FSL-1_0_de.txt (see http://www.dipp.nrw.de/d-fsl/lizenzen/ for other formats) 4. attached 5. 6. It was created for and is backed by a German state. See http://www.dipp.nrw.de/d-fsl/nutzer/ for a list of users. 7. Copyright (C) 20[yy] [Name of the Entitled Person]. This Program may be used by anyone in accordance with the terms of the German Free Software License. The License may be obtained under http://www.d-fsl.org. If you have any questions please do not hesitate to contact me. Best regards, Till Jaeger -- _ Institut für Rechtsfragen der Freien und Open Source Software (ifrOSS) Bredowstraße 3 | 10551 Berlin Tel.: +49.30.443 765 0 | www.ifross.org Dr. Till Jaeger _ ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Linux Collab Summit, April 15-17
Hi all, There will be an SPDX track at the upcoming Linux Collab Summit on April 15-17 in San Francisco. I'd like to have a face-to-face for the legal team, but need to get an idea of who will be there. Can you please respond to this email as to whether you are going? Thanks, Jilayne Lovejoy SPDX Legal Team co-lead Corporate Counsel | OpenLogic, Inc. jlove...@openlogic.comapplewebdata://EAA1F861-B11E-4827-976F-55756901A796/jlove...@openlogic.com | 720 240 4545 ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: agenda for today's SPDX Legal Team call
Oh, and the time zone was incorrect – 11 am Rocky Mtn / 1pm EST As in now. Sorry for any confusion From: J Lovejoy jilayne.love...@openlogic.commailto:jilayne.love...@openlogic.com Date: Thursday, February 28, 2013 11:50 AM To: J Lovejoy jilayne.love...@openlogic.commailto:jilayne.love...@openlogic.com, SPDX-legal spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org Subject: Re: agenda for today's SPDX Legal Team call Might be good if I added the link for item #4: http://spdx.org/wiki/dealing-public-domain-within-spdx-files-draft From: J Lovejoy jilayne.love...@openlogic.commailto:jilayne.love...@openlogic.com Date: Thursday, February 28, 2013 11:36 AM To: SPDX-legal spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org Subject: agenda for today's SPDX Legal Team call 11am EST Dial-in: 1.866. 740.1260 Access code: 2404545 Lots to cover today, so here's a preview, so we can be as efficient as possible!! 1) Linux Collab Summit, April 15-17 in SF - who's going? (so far, affirmative responses from: Paul M., Adam C., Jason B., Mark G., Dennis C., Jilayne) - time for face-to-face meeting on Tuesday afternoon – topics? 2) Licenses to add to SPDX-LL: any feedback for Kirsten's proposal for tracking? - Affero 1.0 - German Free Software License (http://www.dipp.nrw.de/d-fsl/index_html/lizenzen/en/D-FSL-1_0_en.txt); see email from Till Jaeger) - MITRE Collaborative Virtual Workspace License (OSI approved, but not on SPDX-LL, see email from Tom Incorvia) - Reciprocal Public License v1.1 (OSI approved, but not on SPDX-LL, see email from Tom Incorvia) 3) License Inclusion Guidelines – discuss latest revision; see email and attachment sent by Tom Vidal yesterday 4) page added to explain discussion that has occurred several times regarding the idea of having a generic public domain short identifier. Review if there's time, otherwise, submit feedback to Jilayne via email. ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
SPDX Legal Team face-to-face at Linux Collab Summit
The SPDX Legal Team will be have a face-to-face meeting Tuesday afternoon at the Linux Collab Summit in San Francisco. (exact time, TBD) We will endeavor to finish work on the License Matching Guidelines, which stalled last spring. The current License Matching Guidelines are located here: http://spdx.org/wiki/spdx-ll-license-matching-guidelines Below are links to meeting minutes during which this topic was discussed: http://spdx.org/wiki/legal-team-meeting-minutes-2012-01-25 http://spdx.org/wiki/legal-team-meeting-minutes-2012-02-08 http://spdx.org/wiki/legal-team-meeting-minutes-2012-06-13 http://spdx.org/wiki/legal-team-meeting-minutes-2012-06-21-special-mtng-license-list-matching-guidelines http://spdx.org/wiki/legal-team-meeting-minutes-2012-06-27 Please review all of the above prior to the face-to-face. I will send out an agenda with specific items of focus a few days or so prior to the meeting. Thanks and hope to see many of you there. Cheers, Jilayne Lovejoy SPDX Legal Team co-lead Corporate Counsel | OpenLogic, Inc. jlove...@openlogic.comapplewebdata://EAA1F861-B11E-4827-976F-55756901A796/jlove...@openlogic.com | 720 240 4545 ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: A non-standard permissive license
Ok, so let me see if I can sum up the issues that have been brought up on this thread… 1) Scott asks if anyone has seen this license 2) should we add it to list? 3) possible need for allowing other list maintainers to use a short identifier that works with SPDX and SPDX LIcense List 4) statement on license proliferation needed? 5) freeware licenses suggested added to SPDX License List Um, where do I begin? As for the original question – no, Scott, I haven't seen this one, as far as I can remember; but I have seen many licenses like this; what I mean by that is a short, very permissive license text that does not match to any specific license (such as MIT or BSD). In terms of whether this one (or this type in general) should be added to the list, I would defer to the same process and criteria as any license to be added. I agree with Tom AND Philippe in regards to how broad the SPDX License LIst should be. That is, it should be broad, but with limitation. The goal is clearly stated (see first paragraph at top of this page: http://spdx.org/content/license-list) and the intention is not to endorse any particular license, but rather the license list should serve a very practical purpose. That being said and given the vast number of licenses like this (short, varied, permissive), a balance must be struck to not bloat the list to the point of being difficult to use. One very practical matter with these kinds of license is how to name them, as they often have no name, thus forcing us to make one up… problems here, as you can imagine… considering we are currently discussing the license list guidelines (for how to decide what to include or not include), I would recommend all on this thread to check out the last couple meeting minutes on the topic and weigh in there. As for Guillaume's idea of having a letter reserved for short identifiers for other license lists to use (M would not work – MPL!! We might have to use a symbol or X? Would have to check current short identifiers for a letter not being used… :) - this is an interesting idea that seems rather easy to implement, but could also cause other problems. I was not aware of the use case cited and we'll have to check with the tech team on that. ?? As for a statement regarding license proliferation – this might be a good clarification in our literature, not sure if necessary, but certainly would not hurt. If someone wants to take a first stab at drafting a short (no more than a few sentences) explanation, the legal team can then review. Finally, in regards to freeware licenses (e.g. Oracle Binary Code License) - we have discussed this several times and has been part of on-going discussion on license list guidelines (see comment above), so I'm not going to repeat it here, but again, please review those notes and join that discussion on the calls. So, in sum – we have a bunch of different threads that came out of one curious license!! Perhaps we can separate these into a few sub-threads for ease of following? We have set out various projects for the legal team to work on (with project owners) this year, so if there is a new project that we should try to add, then let's look into doing that so it gets proper attention going forward. Thanks for all the interest!!! - Jilayne From: Meier, Roger r.me...@siemens.commailto:r.me...@siemens.com Date: Tuesday, March 5, 2013 5:16 AM To: Tom Incorvia tom.incor...@microfocus.commailto:tom.incor...@microfocus.com, guillaume.rouss...@antelink.commailto:guillaume.rouss...@antelink.com guillaume.rouss...@antelink.commailto:guillaume.rouss...@antelink.com, SPDX-legal spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org, spdx-t...@fossbazaar.orgmailto:spdx-t...@fossbazaar.org spdx-t...@fossbazaar.orgmailto:spdx-t...@fossbazaar.org Subject: RE: A non-standard permissive license I fully agree on this, all licenses should be on the list (including Licenses such as Oracle Binary License). A prefix to identify local/private maintained licenses would be great. == use one license database -roger From: spdx-tech-boun...@lists.spdx.orgmailto:spdx-tech-boun...@lists.spdx.org [mailto:spdx-tech-boun...@lists.spdx.org] On Behalf Of Tom Incorvia Sent: Dienstag, 5. März 2013 12:38 To: guillaume.rouss...@antelink.commailto:guillaume.rouss...@antelink.com; spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org; spdx-t...@fossbazaar.orgmailto:spdx-t...@fossbazaar.org Subject: RE: A non-standard permissive license Hi Guillaume and SPDX Legal, I believe that we will be best served by having as broad a license list as possible, and to have every license on the list be supported. If the Leptonica license occurs in the wild and has consistent, matchable license text, lets vet it an put it into the SPDX list just like any other license. Thanks, Tom Tom Incorvia tom.incor...@microfocus.commailto:tom.incor...@microfocus.com Direct: (512) 340-1336 Mobile: (408) 499 6850
today's call (in 15 minutes!)
Apologies for not getting this out sooner, please review the following draft page: http://spdx.org/wiki/spdx-ll-overview-and-license-inclusion-guidelines-draft-review Other agenda items: * update on various projects * Review of tasks and projects * Need help with a few things… Dial in : 1.866.740.1260 Access code: 2404545 - Jilayne ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Collab Summit materials for Tuesday afternoon
Hi all, If you are attending the Tuesday afternoon SPDX Legal Team working session on the License List Matching Guidelines (see http://collaborationsummit2013.sched.org/event/326f57fa95d4705e90f297edc67b9ab2#.UWzm4Ss6Vxg for schedule), please review the attached .pdf for the background info, so that we can dive in right away. Thanks and look forward to seeing many of you tomorrow. Cheers, Jilayne SPDX Legal Team co-lead ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
meeting today
At 10am PT / 11am MT / 1pm ET Agenda: 1) report from Collab Summit (minutes from legal team working session on license matching guidelines have been posted: http://wiki.spdx.org/view/Legal_Team/Minutes/2013-04-16 2) go over priorities and update list, set time lines, etc. see: http://wiki.spdx.org/view/Legal_Team/Current_Projects_and_Issues Dial in: 1.866.740.1260 Access code: 2404545 Jilayne Lovejoy | Corporate Counsel OpenLogic, Inc. jlove...@openlogic.comapplewebdata://EAA1F861-B11E-4827-976F-55756901A796/jlove...@openlogic.com | 720 240 4545 ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Legal call today in half hour
Agenda: 1) review changes to License Request page here: http://spdx.org/spdx-license-list/request-new-license 2) review table for tracking new licenses here: http://wiki.spdx.org/view/Legal_Team/License_List/Licenses_Under_Consideration 2a) discuss various outstanding licenses on list: new request for Artistic Perl, others that need research, etc. Dial-in: 1.866.740.1260 Access code: 2404545 Jilayne Lovejoy SPDX Legal Team | Co-lead OpenLogic, Inc. | Corporate Counsel jlove...@openlogic.comapplewebdata://EAA1F861-B11E-4827-976F-55756901A796/jlove...@openlogic.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: Spdx-legal Digest, Vol 30, Issue 6
Thanks Michael! My bad typo!! Jilayne On 6/20/13 10:59 AM, Michael J Herzog mjher...@nexb.com wrote: The correct access code for the call is 2404545..regards, Michael Michael J. Herzog +1 650 380 0680 | mjherzog_at_nexB.com DejaCode Enterprise http://www.dejacode.com nexB Inc. at http://www.nexb.com CONFIDENTIALITY NOTICE: This e-mail (including attachments) may contain information that is proprietary or confidential. If you are not the intended recipient or a person responsible for its delivery to the intended recipient, do not copy or distribute it. Please permanently delete the e-mail and any attachments, and notify us immediately at (650) 380-0680. On 6/20/2013 5:00 AM, spdx-legal-requ...@lists.spdx.org wrote: Send Spdx-legal mailing list submissions to spdx-legal@lists.spdx.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.spdx.org/mailman/listinfo/spdx-legal or, via email, send a message with subject or body 'help' to spdx-legal-requ...@lists.spdx.org You can reach the person managing the list at spdx-legal-ow...@lists.spdx.org When replying, please edit your Subject line so it is more specific than Re: Contents of Spdx-legal digest... Today's Topics: 1. agenda for tomorrow's legal call (Jilayne Lovejoy) -- Message: 1 Date: Wed, 19 Jun 2013 20:23:02 + From: Jilayne Lovejoy jilayne.love...@openlogic.com To: SPDX-legal spdx-legal@lists.spdx.org Subject: agenda for tomorrow's legal call Message-ID: cde76f43.175ed%jilayne.love...@openlogic.com Content-Type: text/plain; charset=iso-8859-1 1) License tracking table - need an owner (Dennis was volunteered by Michael last call...) 2) GPL Exceptions - update from Tom V. 3) Fedora List - update from Paul M. - can we start looking at licenses that are on Fedora list, but not on SPDX list? 4) license matching guidelines - update on progress there (from Gary if on call) 10am PST / 11am MST / 1pm EST 1.866.740.1260 Access code: 2454545 Jilayne Lovejoy SPDX Legal Team | Co-lead OpenLogic, Inc. | Corporate Counsel jlove...@openlogic.comapplewebdata://EAA1F861-B11E-4827-976F-55756901A79 6/jlove...@openlogic.com -- next part -- An HTML attachment was scrubbed... URL: http://lists.spdx.org/pipermail/spdx-legal/attachments/20130619/8509114f /attachment-0001.html -- ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal End of Spdx-legal Digest, Vol 30, Issue 6 * ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
agenda for today's call at 10am PT / 11am MT / 1pm ET
Hi All, Sorry for the late notice, but a quick reminder and agenda for today's call: 1) LinuxCon is coming up! September 16-18 in New Orleans 2) License matching guidelines update - see new page created re: process/instructions here: http://wiki.spdx.org/view/Legal_Team/License_List/License-templates Daniel has posted the first few templates to a Google Drive with some questions (easier than uploading to the wiki), so I'll set up a web conference and we'll go over those. Web conference: readytalk.com Access code: 2404545 2) Updates on Fedora list (Paul) and GPL exceptions (Tom V.) 3) Ruby License - two versions but not versioned; how to capture this? see: http://spdx.org/licenses/Ruby and http://www.ruby-lang.org/en/about/license.txt 4) SISSL license issue brought on list by Camille: we have SISSL (version 1.1), but there is also a v1.2 see: http://spdx.org/licenses/SISSL http://www.openoffice.org/licenses/sissl_license.html http://gridscheduler.sourceforge.net/Gridengine_SISSL_license.html Cheers, Jilayne Lovejoy SPDX Legal Team | Co-lead OpenLogic, Inc. | Corporate Counsel ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
meeting minutes for 7/18
Have been posted: http://wiki.spdx.org/view/Legal_Team/Minutes/2013-07-18 Jilayne Lovejoy SPDX Legal Team | Co-lead OpenLogic, Inc. | Corporate Counsel jlove...@openlogic.comapplewebdata://EAA1F861-B11E-4827-976F-55756901A796/jlove...@openlogic.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
license templates for matching guidelines - update
I have updated this page a bit as per our meeting this past Thursday: http://wiki.spdx.org/view/Legal_Team/License_List/License-templates I have also updated the first 4 templates in the shared Google Drive folder to reflect the discussions during the meeting and added the email addresses of those of you who are working on this project to have access. Daniel - can you please take a look and confirm this is consistent with your needs? For those who previously emailed the templates - can you please add yours to the google folder? If anyone has any questions or comments, please respond to this email and/or bring to next call. Cheers, Jilayne Lovejoy SPDX Legal Team | Co-lead OpenLogic, Inc. | Corporate Counsel jlove...@openlogic.comapplewebdata://EAA1F861-B11E-4827-976F-55756901A796/jlove...@openlogic.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: U-Boot: short license headers using SPDX Identifier
YES Yes, yes, yes. Thank you for being the trail blazer :) We have talked about this idea quite a bit. I'm posting to the Legal Team as well, in case some are not also on the General list. Jilayne Lovejoy SPDX Legal Team | Co-lead OpenLogic, Inc. | Corporate Counsel jlove...@openlogic.com On 7/26/13 7:20 AM, Wolfgang Denk w...@denx.de wrote: Dear Roger, In message 045001ce89f0$e6805710$b3810530$@bufferoverflow.ch you wrote: I had a discussion with U-Boot Creator and Core Developer Wolfgang Denk. He made some patches, they were accepted and the result is this header: # (C) Copyright 2000-2013 # Wolfgang Denk, DENX Software Engineering, w...@denx.de. # SPDX-License-Identifier: GPL-2.0+ Thanks (again) for poinin me in this direction. I really like the idea of consistent, automatically parsable Unique License Identifiers. and a Licenses folder with a README, Exception and the Licenses: http://git.denx.de/?p=u-boot.git;a=tree;f=Licenses;hb=HEAD see also mailing list details here: http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/165416 or this web site: http://www.denx.de/wiki/U-Boot/Licensing It is not applied to all files of U-Boot. However, more than 5760 files already use this new header. I would like to point out that this is just a not yet; this is still work in progress - unfortunately the conversion requires careful inspection and manual operation for a significant part of the files. But then, this just makes all the more clear how urgently such an improvement was needed. a very resourceful way to simplify the license topic and an important step towards adoption of SPDX usage within projects and SPDX files provided with OSS releases. The most interesting thing now is to watch if other projects pick up the idea... Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de Drawing on my fine command of language, I said nothing. ___ Spdx mailing list s...@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: 4Suite License
Great, thanks for checking this. I'll make a note as such on the spreadsheet! Jilayne From: Tom Incorvia tom.incor...@microfocus.commailto:tom.incor...@microfocus.com Date: Thursday, August 1, 2013 12:18 PM To: SPDX-legal spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org Cc: J Lovejoy jilayne.love...@openlogic.commailto:jilayne.love...@openlogic.com Subject: RE: 4Suite License Hi Folks, as Dennis Clark suspected, the 4Suite license is just Apache 1.1. I have attached the compare. So we would normally not assign this a unique license identifier. Tom Tom Incorvia; tom.incor...@microfocus.commailto:tom.incor...@microfocus.com; O: (512) 340-1336; M: (408) 499 6850 From: spdx-legal-boun...@lists.spdx.orgmailto:spdx-legal-boun...@lists.spdx.org [mailto:spdx-legal-boun...@lists.spdx.org] On Behalf Of Lamons, Scott (Open Source Program Office) Sent: Thursday, August 01, 2013 1:04 PM To: Dennis Clark; spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org Subject: RE: 4Suite License A google search for 4suite license yields the following URL... http://www.stlinux.com/node/142 From:spdx-legal-boun...@lists.spdx.orgmailto:spdx-legal-boun...@lists.spdx.org [mailto:spdx-legal-boun...@lists.spdx.org] On Behalf Of Dennis Clark Sent: Thursday, August 01, 2013 12:03 PM To: spdx-legal@lists.spdx.orgmailto:spdx-legal@lists.spdx.org Subject: 4Suite License Hi Legal Team, Text of the 4Suite License attached. Regards, Dennis Clark nexB __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ __ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com __ ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: GNU [?] Affero General Public License v1.0
that is an easy fix, as it only impacts the full name and not the short identifiers (which is AGPL-#.0) - thanks Camille for noticing and David and Bradley for the recollections. I will log this for the next version of the SPDX License List. We actually don't have AGPL version 2 on the SPDX License List - I think this might be because it does not really seem to be a separate license in and of itself ?? thoughts? Jilayne Lovejoy SPDX Legal Team lead lovejoyl...@gmail.com On Oct 1, 2013, at 10:29 AM, Bradley M. Kuhn bk...@ebb.org wrote: Wheeler, David A wrote: I believe you mean that version 1.0 doesn’t begin with “GNU”. That sounds correct; I agree, but the details, to my recollection, are different than explained by David below: I believe Affero had an idea, drafted it (with some help from GNU), and then put it out… but as their own license. Later it got folded in as a GNU license. Anyway, that’s the history as I (poorly?) remember it. Granted, the below is based on my own personal recollection of events, backed up by my personal email archives. I've told the story of the creation of the AGPLv1 a few times: http://www.socallinuxexpo.org/scale11x/presentations/affero-gplv3-why-it-exists-who-its (slides at: http://ebb.org/bkuhn/talks/SCALE-2013/agplv3.html ) This story is told in the Wikipedia entry as well: http://en.wikipedia.org/wiki/Affero_General_Public_License#History (but, full disclosure: I've made edits to that Wikipedia entry myself.) Anyway, to answer the main question at hand: AGPLv1 was a derivative of the GPLv2 published by Affero, Inc. (now defunct) with the permission of Free Software Foundation. See: http://www.gnu.org/press/2002-03-19-Affero.html Thus, I suggest its full name is accurately: Affero General Public License, version 1. AGPLv2 was also published by the defunct Affero, Inc.: http://www.affero.org/agpl2.html to make it possible for AGPLv1 works to transition to the AGPLv3. AGPLv2's full name is thus Affero General Public License, version 2. In other words, you should therefore not use the GNU moniker in the full names of AGPLv1 and AGPLv2, but *should* use it in the name of AGPLv3, found at http://www.gnu.org/licenses/agpl-3.0.html -- bkuhn ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: License: spdx-license=IDENTIFIER
comments inline below On Oct 1, 2013, at 10:44 AM, Bradley M. Kuhn bk...@ebb.org wrote: I wasn't at the SPDX meetings at LinuxCon last month, but multiple people approached me at the conference to ask my opinion on the issue, with regard to file-by-file license notice inventory, if I felt the text: spdx-license=IDENTIFIER would be adequate. I'm told that dmg suggested that it'd be better to say something like: License of this file is: spdx-license=IDENTIFIER and while I agreed with dmg, but I further suggested: License: spdx-license=IDENTIFIER would be adequate. However, I don't see anything about this documented in these minutes: Jilayne Lovejoy wrote at 14:37 (EDT) on Thursday: http://wiki.spdx.org/view/Legal_Team/Minutes/2013-09-25 these minutes are for the legal team meeting on 9/25 during which I did a brief recap of the various meetings that occurred (a full day's worth) at LinuxCon. Naturally, there is more focus on the content for the meeting that I led (having to do with the license matching guidelines). I don't believe there are minutes specifically from the other meetings, but am sure it will be also summarized during the monthly general call tomorrow, so I'd encourage people to join that. I am posting about this now because I may be about to make a bombing-run patch to one of Conservancy's member projects to add a license notice to each file, and I'd be happy use that format if it's going to be an official recommendation of the SPDX project. That is great news, Bradley! Obviously, there are a few details to sort out, but the support is very much appreciated. However, I will have to register my complaint again that GPL-2.0 is a *horrible* identifier for GPLv2-only, mainly because of how GPLv2§9 works. Saying GPL-2.0 to refer to GPLv2-only is misleading and confusing and should be corrected. yes, I actually agree. I have long thought that the short identifiers would be better served as: GPL-2.0+ and GPL-2.0-only And logged this as something to bring up, but we have been busy with trying to finish other tasks and it hasn't risen to the surface. Of course, the worry is that changing the short identifiers will screw up people who are already using the SPDX License List (we endeavored to try to never change them…) There is a good number of companies already using it and probably more than we even know of. In any case, if it is going to help reduce confusion or ambiguity and we can figure out a way to make sure this change is well documented, then we need to consider making the change. I will be sure to bring this up at the General Meeting tomorrow and on the next legal call (next Thursday) Cheers, Jilayne Lovejoy SPDX Legal Team lead lovejoyl...@gmail.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
call today (now)...
I just realized that I did not send an invite for the Legal Team call this week. I will still dial-in at the below number in the hopes that people still had a reminder on their calendars Audio Conferencing Call this number: (United States) 1-415-363-0849 Enter this PIN: 336247 Jilayne Lovejoy SPDX Legal Team lead lovejoyl...@gmail.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: GNU [?] Affero General Public License v1.0
Hey Bradley, just sorting through emails and wanted to make sure we came to some consensus on this. If I understand correctly then, there really isn't a need for a short identifier for AGPLv2 because it doesn't exist as a individual license in the sense that it simply allows something under AGPLv1 to be licensed under AGPLv3 (which, as far as I can tell, AGPLv1 already did…), so if someone did find AGPLv2, it would really be AGPLv1 or AGPLv3 in terms of what actual license text applies… For whatever it's worth, I have never seen the text on this page - http://www.affero.org/agpl2.html - or any other reference to AGPLv2 in the wild as far as I can remember, but others might want to weigh in on that. If the above is a (somewhat) correct characterization (albeit perhaps not elegantly stated due to fuzzy, post-holiday brain!) then it would seem that we are okay to do without a AGPLv2 on the SPDX License List. If anyone disagrees, please speak up :) Cheers, Jilayne Lovejoy SPDX Legal Team lead lovejoyl...@gmail.com On Oct 7, 2013, at 4:15 PM, Bradley M. Kuhn bk...@ebb.org wrote: Jilayne Lovejoy wrote at 00:55 (EDT) on Thursday: We actually don't have AGPL version 2 on the SPDX License List - I think this might be because it does not really seem to be a separate license in and of itself ?? thoughts? The whole point of AGPLv2 was to auto-relicense AGPLv1 works immediately to AGPLv3, so if you saw AGPLv2 applied in the wild, then it'd be similar to the situation of the transitional GPL-incompatible Python license back in the very early 2000's, for those that remember that. It's theoretically possible you could see it in the wild, I suppose, if a licensor was confused about how to use AGPLv2. Perhaps that information is worth capturing in an SPDX file, although I doubt it. -- -- bkuhn ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: Fedora license list review
I added some notes as well, but I think I colored outside the green lines… :) I also added a column regarding the short identifiers to indicate when they are different from Fedora's. This is a key part of this task; that is, to track where they are different (which is inevitable) so that some kind of equivalency or translation document can be created. Cheers, Jilayne SPDX Legal Team lead lovejoyl...@gmail.com On Nov 6, 2013, at 1:26 PM, Dennis Clark dmcl...@nexb.com wrote: Hi Legal Group, I added a few comments on the latest green-highlighted group on the Fedora list. These are pretty obscure! Looking forward to other comments. Regards, Dennis Clark nexB, Inc. On Fri, Oct 25, 2013 at 4:22 PM, zwh...@ententesoftware.com wrote: Thank you to everyone who participated in the review of the below-referenced licenses on the SPDX Legal call this week. 7 licenses were approved for inclusion in the SPDX List and one was deferred for further discussion. The next 8 licenses for review are now highlighted in green on our shared document linked below. Please insert your comments for review at the 11/7 meeting. Thanks! https://docs.google.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dENVVHFNeG5hQjAyYjQ3bm1VVUdjOFEusp=sharing Zak White Entente Software LLC 570 El Camino Real #150-103 Redwood City, CA 94065 Phone: (650) 489-6851 zwh...@ententesoftware.com Original Message Subject: RE: Fedora license list review From: zwh...@ententesoftware.com Date: Mon, October 21, 2013 5:48 pm To: SPDX-legal spdx-legal@lists.spdx.org Cc: Tom Callaway tcall...@redhat.com SPDX Legal Team, We have 8 licenses from the Fedora License List that are current candidates for inclusion in the SPDX License List. Prior to Thursday's call, please review the Fedora Good List working document (https://docs.google.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dENVVHFNeG5hQjAyYjQ3bm1VVUdjOFEusp=sharing) and insert your comments/questions/recommendations in the Comments column for each of the 8 green-highlighted items. We will include additional licenses from the Fedora License List in future rounds. SPDX guidelines for license inclusion are available on the License List Overview page: http://spdx.org/spdx-license-list/license-list-overview I look forward to reviewing with the team. Zak White Entente Software LLC 570 El Camino Real #150-103 Redwood City, CA 94065 Phone: (650) 489-6851 zwh...@ententesoftware.com Original Message Subject: Fedora license list review From: Jilayne Lovejoy lovejoyl...@gmail.com Date: Fri, September 27, 2013 11:45 am To: SPDX-legal spdx-legal@lists.spdx.org Cc: Tom Callaway tcall...@redhat.com To speed up progress on reviewing the Fedora license list for licenses that are not on the SPDX License List and should be added, we will undertake the following process: Legal Team members to review a set of licenses on the list and provide comments in the shared Google spreadsheet. A new set of licenses will be added (via color highlighting in the spreadsheet) each week If all commenters agree the license should be added, it will be marked to be added to the SPDX License List and a short identifier determined Any discussion needed about a particular license will be done at the next scheduled Legal Team meeting Final decisions on short identifiers will be done at the next scheduled Legal Team meeting PLEASE read the license list overview information first: http://spdx.org/spdx-license-list/license-list-overview The Google spreadsheet is located here: https://docs.google.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dENVVHFNeG5hQjAyYjQ3bm1VVUdjOFEusp=sharing Current licenses to be reviewed are highlighted in green rows. Please add comments in one of the columns with a red highlighted header call, putting your name at the top; add more comment columns as needed (so each person who comments has their own column) -- follow my example Please add suggestions re: short identifiers in that appropriate column (red highlighting in header cell) Questions? Need access to the Google spreadsheet? let me know. Cheers. Jilayne Lovejoy SPDX Legal Team lead lovejoyl...@gmail.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal
Re: SPDX license clarification - artistic
Hi Bob, In short, the answer is that there are actually three different variations of Artistic 1.0, as follows: - the one on OSI site with clause 8 - the one on OSI site without clause 8 - the one on the Perl site After conferring with the OSI on how to deal with this for purposes of the SPDX License List, we created a different short identifier for each. I will forward you the email I sent to the SPDX legal list and OSI list on this issue separately. SPDX Legal Team lead lovejoyl...@gmail.com On Oct 25, 2013, at 4:41 PM, Gobeille, Robert bob.gobei...@hp.com wrote: Looking over http://spdx.org/licenses/, we see Artistic-1.0-cl8 and Artistic-1.0-Perl. The cl8 points to http://opensource.org/licenses/Artistic-1.0 and makes sense. However, http://spdx.org/licenses/Artistic-1.0-Perl#licenseText points to http://dev.perl.org/licenses/artistic.html for the license text. This text has the Clause 8. 8.Aggregation of this Package with a commercial distribution is always permitted provided that the use of this Package is embedded; that is, when no overt attempt is made to make this Package's interfaces visible to the end user of the commercial distribution. Such use shall not be construed as a distribution of this Package. So what is the difference between Artistic-1.0-cl8 and Artistic-1.0-Perl? Thanks, Bob Gobeille ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: SPDX - license inconsistency
Hi Bob, Yes, this is an issue! In looking more closely at the Ruby license, we also realized that the text has varied over the years as well. (see some of discussion captured here: http://wiki.spdx.org/view/Legal_Team/Minutes/2013-09-12 ) The solution for v1.19 (released last month) of the SPDX License List was to remove the Ruby license and sort out how to best represent it by collaborating with the Ruby project and then put it back on the list for the next license list release with a more accurate representation. As it was, it felt like the SPDX short identifier was only adding to or at least, perpetuating confusion, which is not optimal. This is the first time we have removed a license, which admittedly felt a bit draconian, but only with the goal of capturing the license variations in a way that makes more sense. Hope that helps (for now). Cheers, Jilayne SPDX Legal Team lead lovejoyl...@gmail.com On Oct 25, 2013, at 1:10 AM, Philip Odence pode...@blackducksoftware.com wrote: Legal Team, Sorry this (and I) missed yesterday's meeting. Could someone raise their hand to look at this? Thanks from LinuxCon Europe, Phil On 10/24/13 11:10 PM, Gobeille, Robert bob.gobei...@hp.com wrote: Hello Phil, Could you tell me which list or person to direct this to? The SPDX license list (http://spdx.org/licenses/) entry for Ruby has a reference to ³Other web pages for this license², which refers to https://www.ruby-lang.org/en/about/license.txt. However, the SPDX page and the ruby-lang.org page show different dual licenses. The former has: You can redistribute it and/or modify it under either the terms of the GPL (see COPYING.txt file), or the conditions below: and the latter has: You can redistribute it and/or modify it under either the terms of the 2-clause BSDL (see the file BSDL), or the conditions below: Could someone reconcile this for me? Thank you, Bob Gobeille Hewlett Packard Open Source Program Office ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
SPDX Legal Team meeting tomorrow (thursday)
Hi All! Thanks to Paul Madick for running the last legal team meeting while I was gone. Meeting minutes have been posted here: http://wiki.spdx.org/view/Legal_Team/Minutes/2013-10-24 For tomorrow's call, it will follow a similar pattern in terms of updates on the following topics: 1) License Matching Guidelines (Jilayne) - The SPDX License List Matching Guidelines have been updated as per previous feedback, please have a look here: http://spdx.org/spdx-license-list/matching-guidelines for one last proof read, as there were a couple changes that no one commented on.\ 2) or later and other license short identifier modifiers (Mark Gisi) - discussion has been going on via list; Mark in process of scheduling a special meeting for this topic 3) GPL exceptions (Tom V. Mark Gisi) - update on progress 4) Fedora list (Zac) - update, new licenses to cover, and some discussion about short identifiers Thursday, 7 November 10am PT / 11am MT / 1pm ET Call this number: (United States) 1-415-363-0849 Enter this PIN: 336247 Alternative Numbers: http://www.yuuguu.com/audio SPDX Legal Team lead lovejoyl...@gmail.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
meeting minutes posted
We were missing some key folks to go over other stuff, so focused on the next round of licenses from the Fedora list. Minutes posted here: http://wiki.spdx.org/view/Legal_Team/Minutes/2013-11-21 - Jilayne SPDX Legal Team lead lovejoyl...@gmail.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Fedora list: in regards to Crystal Stacker license
I was looking at the next set of Fedora licenses to review. I did a bit of research on the Crystal Stacker license, which was too much to include in the comments cell of the spreadsheet. Upon downloading v1.5 of the project (from here: http://www.t3-i.com/pages/project.php?id=crystal_stacker) I found that the license listed on Fedora's site does not match (exactly) what is included in the download. In addition, there appears to be two variations in the download - one for the source code and one generally. While they are essentially the same in terms of compliance efforts, the text is not the same. I've included the text of what I found in the download, including the path and filenames (2 files have the same name, but are different) and a summary below with suggested resolution. -- from: Fedora site: Crystal Stacker is freeware. This means you can pass copies around freely provided you include this document in it's original form in your distribution. Please see the Contacting Us section of this document if you need to contact us for any reason. The source code is provided as-is and you may do with it whatsoever you please provided that you include this file in its unmodified form with any new distribution. NewCreature Design makes no gaurantees regarding the usability of the source but are willing to help with any problems you might run into. Please see the Contacting Us section of this document if you need to get in touch with us about any issues you have regarding the source. 1 -- from: crystal_stacker-1.5-src/cs/readme.txt Crystal Stacker (c) 2006 NewCreature Design --- Crystal Stacker is freeware. This means you can pass copies around freely provided you include this document in it's original form in your distribution. Please see the Contacting Us section of this document if you need to contact us for any reason. Disclaimer -- NewCreature Design makes no guarantees regarding the Crystal Stacker software. We are not responsible for damages caused by it, though the software is not known to cause any problems. If you have trouble with the software, see the Contacting Us section of this document. 2 -- crystal_stacker-1.5-src/ce/ce.txt Crystal Edit (c) 2006 NewCreature Design Crystal Edit is freeware. This means you can pass copies around freely provided you include this document in it's original form in your distribution. Please see the Contacting Us section of this document if you need to contact us for any reason. Disclaimer -- NewCreature Design makes no guarantees regarding the Crystal Edit software. We are not responsible for damages caused by it, though the software is not known to cause any problems. If you have trouble with the software, see the Contacting Us section of this document. 3 -- from: crystal_stacker-1.5-src/cs/source.txt Crystal Stacker Source (c) 2006 NewCreature Design -- License --- The source code is provided as-is and you may do with it whatsoever you please provided that you include this file in its unmodified form with any new distri- bution. NewCreature Design makes no gaurantees regarding the usability of the source but are willing to help with any problems you might run into. Please see the Contacting Us section of this document if you need to get in touch with us about any issues you have regarding the source. 4 -- crystal_stacker-1.5-src/ce/readme.txt Crystal Edit Source (c) 2006 NewCreature Design --- License --- The source code is provided as-is and you may do with it whatsoever you please provided that you include this file in its unmodified form with any new distri- bution. NewCreature Design makes no gaurantees regarding the usability of the source but are willing to help with any problems you might run into. Please see the Contacting Us section of this document if you need to get in touch with us about any issues you have regarding the source. - SUMMARY: - The download has two main directories: ce and cs - which I presume correlates to Crystal Stacker and Crystal Edit - Although the .txt file naming in each directory is not consistent, each contains two different licenses - i.e. 1 and 3 in the cs directory; 2 and 4 in the ce directory - 1 and 2 are the same save for the project name (which can be accommodated via the licensing matching template) and very close to what Fedora has on their site, but not exactly. I did not download older versions, but judging from the history.txt file, I would guess that the license Fedora has is from an earlier version and the slight changes were made for v1.5 of the distribution. - 3 and 4 are identical (including spelling error) and seem to apply to the source code specifically, as they are both named Crystal Stacker/Edit Source Recommendation: - Add 1
legal call today!!
As scheduled and the last one for 2013! Agenda: 1) Creative Commons v4 license family - to add to list? We booted this to this meeting, as no one had had a chance to read them yet. JL note: I see no reason not to add them, but do want to discuss the template for license matching purposes. specifically, should the three paragraphs (two at the top and one at the bottom) in the light gray boxes be considered part of the license for matching purposes? see: http://creativecommons.org/licenses/by-nc/4.0/legalcode 2) Fedora List - continue as far as we can get today!! the next set of licenses for review are highlighted in green and marked as Review in process in Google Docs (https://docs.google.com/spreadsheet/ccc?key=0AmVnI0dGKEo1dENVVHFNeG5hQjAyYjQ3bm1VVUdjOFE#gid=1). Those of you on the last call know that we ran out of time before we got to the last batch of licenses, so next week we will have two batches! Please follow the above link to review the designated licenses (starting at Line 33) and insert your feedback in the Comments column. 10am PT / 11am Mtn Time / 1pm ET Call this number: (United States) 1-415-363-0849 Enter this PIN: 336247 Alternative Numbers: http://www.yuuguu.com/audio Jilayne SPDX Legal Team lead lovejoyl...@gmail.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
meeting minutes
not much of a meeting, as there were only 3 of us. Posted minutes (as follows) anyway: http://wiki.spdx.org/view/Legal_Team/Minutes/2013-12-19 Attendees Jilayne Lovejoy Phil Odence Paul Madick [edit]Agenda All agreed three people is not enough to make any major decisions. All agreed that Creative Commons version 4 licenses should be added to list. Next rev of SPDX License List slated for January, although there may be issues to discuss by the legal team (on the next call) before publishing it. In regard to the CC v4 licenses, we need to discuss the template for license matching purposes. Specifically, should the three paragraphs (two at the top and one at the bottom) in the light gray boxes be considered part of the license for matching purposes? Likewise, in the older versions, there is a similar paragraph at the beginning and end. see: http://creativecommons.org/licenses/by-nc/4.0/legalcode, also see: http://creativecommons.org/licenses/by/3.0/legalcode the last paragraph states that it is not part of the license the second paragraph in the new versions seems to be akin to a preamble the first paragraph (in new and old) is more of a disclaimer specific to CC for providing the licenses Is the inclusion of any or all of these parts required to make it a positive match for the license? Conversely, if these bits were not included would it still be a match? Happy Holidays and hope to pick up where we left off and with momentum on January 16th!! Cheers, Jilayne SPDX Legal Team lead lovejoyl...@gmail.com ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Re: SPDX meta-tag for implicit license terms
I would agree with Oliver's point, as well as Kate's - that we should be consistent with what is already defined in the standard. Oliver has concisely summarized the information you would expect to find in the SPDX document for the file level information for a file that has no license info in it - that is, as Kate also pointed out, the LicenseInfoInFile would be NONE or NOASSERTION and then the Concluded License field would be used to declare the license based upon extrinsic (e.g. directly level license) information. The question here seems to be a matter of order: can the fields of the spec also be used for meta-tagging preemptively? And if so, would such information then be dumped into the SPDX file for the project. Or the other way around, could information from an SPDX file for an entire project be used to generate file-level meta-tags? While I completely agree with Mark that file-level licensing information is the way to go ultimately, the concept of someone determining the license for unmarked files and then inserting some license information seems to be treading in potentially dangerous water - if someone is incredibly diligent in this process, it could be incredibly helpful; but if they are sloppy in even the slightest bit (perhaps, unknowingly so), then you have license information that is wrong. It might be safer to just leave this info, that is, the concluded license for files with no explicit license info, in the SPDX document that will go with the package (and its files) and leave the preemptive meta-tagging to project/file authors. If someone really wanted to, I suppose they could generate the tags from the SPDX document as suggested below, but then that seems a bit like replacing or duplicating some of the SPDX file… just my off-the-top of my head (and late) thoughts on the matter… (which I reserve the right to alter upon further discussion) Jilayne SPDX Legal Team lead lovejoyl...@gmail.com On Dec 10, 2013, at 4:45 AM, Fendt, Oliver oliver.fe...@siemens.com wrote: Hi, As far as I under stood the standard one would express this kind of association (file without license information - is assumed to be licensed under the conluded license of the package) with the following elements on file level: LicenseInfoInFile: NONE License concluded: SPDX Identifier of the concluded license of the package Would it be possible to transfer the information from the SDPX file to the package. Meaning that those files will receive (or better to say: these files will be modified with) the Strings: LicenseInfoInFile: NONE License concluded: SPDX Identifier of the concluded license of the package This is just a suggestion Best Regards Oliver Fendt Siemens AG Corporate Technology Corporate Standards Guidance CT CSG SWI OSS Otto-Hahn-Ring 6 81739 München, Deutschland Tel: +49 89 636-46033 mailto:oliver.fe...@siemens.com -Ursprüngliche Nachricht- Von: spdx-tech-boun...@lists.spdx.org [mailto:spdx-tech-boun...@lists.spdx.org] Im Auftrag von Wolfgang Denk Gesendet: Dienstag, 10. Dezember 2013 11:10 An: spdx-t...@lists.spdx.org; spdx-legal@lists.spdx.org Betreff: SPDX meta-tag for implicit license terms Hello, after converting the U-Boot project to use SPDX meta-tags, we now started working on another Open Source project; here we face a somewhat different situation: a large number of the individual source files do not contain any per-file license header at all. Instead, they rerely on the fact that they inherit the global, project-wide license as defined in the top level README and COPYING files. My understanding is that this is technically and legally clean as is. However, I see a handling problem here: the conversion of the project to use SPDX meta-tags will probably be an incremental process, and there will be some period of time (eventually even a long one) where still files exist that have not been converted yet. I would like to define a way to mark such files where implicit licensing applies, so that we do not have to check these again and again. Of course we could insert a license tag corresponding to the actual project-wide license, but such a modification is considered intrusive by some of affected people. I think it would be better (and easier acceptable by the respective copyright holders) to have some neutral SPDX meta-tag that reflects the fact that this file inherits the project's global license terms. Would such a meta-tag be acceptable to the SPDX team? I'm still looking for a good name for such a tag; suggestions we have so far include: SPDX-License-Identifier: implicit SPDX-License-Identifier: inherit SPDX-License-Identifier: none SPDX-License-Identifier: - Suggestions and comments welcome... Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk Detlev Zundel HRB 165235
Re: WTFPL(-2.0) license entry
got another link as well. thanks! Jilayne SPDX Legal Team lead lovejoyl...@gmail.com On Jan 4, 2014, at 10:06 PM, Jan Engelhardt jeng...@inai.de wrote: On Sunday 2014-01-05 00:09, Jilayne Lovejoy wrote: Thanks for pointing this out, Jan. I have not been able to find previous versions - have you? If the Wikipedia entry (with citations) is credible enough, then right here: http://en.wikipedia.org/wiki/WTFPL (Usually, if something is called version N (for N0), there is a strong chance there may have been a version N-1 of the same entity.) ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
SPDX Legal Business Team Meetings
Hi all, We will be having the first legal team meeting on the 23rd of January (not the 16th, as I had stated previously) at the same time as before. The business team will meet on the 16th and we will alternate Thursday from there. Please put a placeholder on your calendar for now. Recurring invite with dial-in information will come soon. In the meantime - what would you like to see the SPDX Legal Team tackle in 2014? Let’s get some discussion going via email ahead of our call on Jan 23rd!! Cheers, Jilayne SPDX Legal Team lead lovejoyl...@gmail.com Begin forwarded message: From: Manbeck, Jack j-manbe...@ti.com Subject: Business Team Meetings Date: January 7, 2014 at 11:05:55 AM MST To: spdx-...@lists.spdx.org spdx-...@lists.spdx.org All, Our business team bi-weekly meeting will start on the 16th of January. I was planning on keeping the same time but if we get a co-chair from Europe we may look for times that are earlier. Stay tuned. Jack Manbeck Business Team Co-Chair ___ Spdx-biz mailing list spdx-...@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-biz ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Invitation: SPDX Legal Team call @ Every 2 weeks from 11am to 12pm on Thursday from Thu Jan 23 to Thu Feb 6 (lovejoyl...@gmail.com)
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:DAYLIGHT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 TZNAME:MDT DTSTART:19700308T02 RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:-0600 TZOFFSETTO:-0700 TZNAME:MST DTSTART:19701101T02 RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTART;TZID=America/Denver:20140123T11 DTEND;TZID=America/Denver:20140123T12 RRULE:FREQ=WEEKLY;UNTIL=20140206T18Z;INTERVAL=2;BYDAY=TH DTSTAMP:20140117T193346Z ORGANIZER;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com UID:r5i77nolmioch4074l8cun7...@google.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE ;CN=Jilayne Lovejoy;X-NUM-GUESTS=0:mailto:lovejoyl...@gmail.com ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP= TRUE;CN=spdx-legal@lists.spdx.org;X-NUM-GUESTS=0:mailto:spdx-le...@lists.sp dx.org CREATED:20140117T193345Z DESCRIPTION:bi-weekly SPDX Legal Team conference call\nCall this number: (U nited States) 1-415-363-0849\nEnter this PIN: 336247\nAlternative Numbers: http://www.yuuguu.com/audio\n\nView your event at http://www.google.com/cal endar/event?action=VIEWeid=cjVpNzdub2xtaW9jaDQwNzRsOGN1bjdiZXMgc3BkeC1sZWd hbEBsaXN0cy5zcGR4Lm9yZwtok=MjEjbG92ZWpveWxpZHNAZ21haWwuY29tODM3MmZkNzdmZTV mOTE0MjVmYWQwMmUxNzcxYTI1ODVmYzRmODEwNQctz=America/Denverhl=en. LAST-MODIFIED:20140117T193346Z LOCATION:1-415-363-0849 PIN: 336247 SEQUENCE:0 STATUS:CONFIRMED SUMMARY:SPDX Legal Team call TRANSP:OPAQUE BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:This is an event reminder TRIGGER:-P0DT0H15M0S END:VALARM END:VEVENT END:VCALENDAR invite.ics Description: application/ics ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
first call on Thursday, Jan 23
Hi All and Happy New Year!! I just sent an invite for the first two SPDX Legal Team calls for 2014 - on Jan 23 and Feb 6, at the usual time (10am PT / 1pm ET) I only sent the invite for the first couple meetings because there is a possibility the Business Team will change their meeting time. If so, we might want to consider whether to change ours to align (to keep the same time, alternating Business / Legal team meetings) or not. We will be using the same dial-in for now as well: 1-415-363-0849 Enter this PIN: 336247 Meeting agenda to come a day or so prior. In the meantime, please review the update Current Projects and Priorites page here: http://wiki.spdx.org/view/Legal_Team/Current_Projects_and_Issues Cheers, Jilayne SPDX Legal Team co-lead___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Jilayne Lovejoy invited you to “SPDX Legal Team bi-weekly call”.
Jilayne Lovejoy invited you to “SPDX Legal Team bi-weekly call”. when: Thursday, January 8, 2015, 11:00 AM - 12:00 PM location: 1-415-363-0849 PIN: 336247 invitees: You note: Call this number: (United States): +1-857-216-2871 User PIN: 38633 International: visit the URL at http://uberconference.com/SPDXTeam reply: Accept – https://www.icloud.com/calendar/eventreply/?t=2_FNNN6WRDNPZXTP6Z2ZYBWBAJRRFUEYZ6ULOIDZW3DQMZ6EPAIJUOXXSIVOB6IMZYGLVHPE4KYP2TUp=p07cc=US#reply=accept Decline – https://www.icloud.com/calendar/eventreply/?t=2_FNNN6WRDNPZXTP6Z2ZYBWBAJRRFUEYZ6ULOIDZW3DQMZ6EPAIJUOXXSIVOB6IMZYGLVHPE4KYP2TUp=p07cc=US#reply=decline Maybe – https://www.icloud.com/calendar/eventreply/?t=2_FNNN6WRDNPZXTP6Z2ZYBWBAJRRFUEYZ6ULOIDZW3DQMZ6EPAIJUOXXSIVOB6IMZYGLVHPE4KYP2TUp=p07cc=US#reply=tentative --- iCloud is a service provided by Apple. My Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2015 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT TRANSP:OPAQUE DTEND;TZID=America/Denver:20150108T12 UID:D6F352E9-728A-485F-978C-CD0C58E111C2 LOCATION:1-415-363-0849\nPIN: 336247\n DESCRIPTION:Call this number: (United States): +1-857-216-2871 \n User PIN: 38633 \n International: visit the URL at http: //uberconference.com/SPDXTeam\n SEQUENCE:0 SUMMARY:SPDX Legal Team bi-weekly call DTSTART;TZID=America/Denver:20150108T11 CREATED:20150107T051045Z ATTENDEE;CN=Jilayne Lovejoy;CUTYPE=INDIVIDUAL;PARTSTAT=ACCEPTED; ROLE=CHAIR;EMAIL=lovejoyl...@gmail.com:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:spdx-legal@lists.spdx.org DTSTAMP:20150107T051135Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto
Jilayne Lovejoy invited you to “SPDX Tech/Legal teams joint call”.
Jilayne Lovejoy invited you to “SPDX Tech/Legal teams joint call”. when: Tuesday, June 16, 2015, 11:00 AM MDT - 12:00 PM MDT location: Dial-in number: 877.435.0230 (U.S. and Canada) or 1.253.336.6732 (International) Conference code: 7833942033 invitees: You note: Dial-in number: 877.435.0230 (U.S. and Canada) or 1.253.336.6732 (International) Conference code: 7833942033 To discuss field that use NONE / NOASSERTION in the spec. Details on the topic will be emailed the day before that call reply: Accept – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDC6C647IGXDM42FEH3H4YP2UTM2TXAG3L7XK3RXKIXDIVRGRTUE2p=p07cc=US#reply=accept Decline – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDC6C647IGXDM42FEH3H4YP2UTM2TXAG3L7XK3RXKIXDIVRGRTUE2p=p07cc=US#reply=decline Maybe – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDC6C647IGXDM42FEH3H4YP2UTM2TXAG3L7XK3RXKIXDIVRGRTUE2p=p07cc=US#reply=tentative --- iCloud is a service provided by Apple. My Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2015 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT TRANSP:OPAQUE DTEND;TZID=America/Denver:20150616T12 UID:BFDFA2DF-29A8-4A5F-B791-EFAB3C20D330 LOCATION:Dial-in number: 877.435.0230 (U.S. and Canada) or 1.253.336.6732 (International)\n Conference code: 7833942033 DESCRIPTION:Dial-in number: 877.435.0230 (U.S. and Canada) or 1.253.336.6732 (International)\n Conference code: 7833942033\n\nTo discuss field that use NONE / NOASSERTION in the spec. Details on the topic will be emailed the day before that call SEQUENCE:0 SUMMARY:SPDX Tech/Legal teams joint call DTSTART;TZID=America/Denver:20150616T11 CREATED:20150528T135841Z ATTENDEE;CUTYPE
Re: New License/Exception Request: BSD-1-Clause
Thanks for your request, Pedro. I thought this looked familiar to a variant we have on the SPDX License List - https://spdx.org/licenses/BSD-Source-Code.html - but the one you have found is indeed just the one clause! I'm curious, are you seeing this a lot in FreeBSD? I would assume we would add markup for the name/copyright holder text in the copyright notice and disclaimer as per the other BSD variants to avoid a mis-match based on the SPDX Matching Guidelines for text that is not substantive. Agree? All – while we have a meeting coming up this week, can we get a feel as to adding this to the SPDX License List next release via email in advance? As we are currently working on the next release, I think this might be the last new license we can squeeze in, so would like to get it sorted as soon as possible. To that end, if Pedro is seeing this repeatedly in a distribution as large as FreeBSD, it seems sensible to add it. Thanks, Jilayne From:on behalf of Pedro Giffuni Organization: FreeBSD Project Date: Thursday, 30 November 2017 at 20:16 To: Subject: New License/Exception Request: BSD-1-Clause Hello SPDX License gurus ;) I hereby propose the following license variant. 1) Proposed Full name: BSD 1 Clause License 2) Proposed Short Identifier: BSD-1-Clause 3) Example URL: https://svnweb.freebsd.org/base/head/include/ifaddrs.h?revision=250887=markup 4) License text: Copyright (c) [Copyright year] [Name of Copyright Owner] All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. THIS SOFTWARE IS PROVIDED BY [Name of Copyright Owner], Inc. ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL [Name of Copyright Owner] BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 5) The license has not been submitted to OSI, although it is a subset of the 2-Clause BSD license. 6) Explanation. While looking at adopting SPDX tagging for FreeBSD's source tree, I was unable to find references for many BSD license variants. The one-clause variant seems a logical extrapolation of the 3-Clause and 2-Clause BSD licenses. In the case of the URL, the file originated in Berkeley Software Design, Inc., a company set up by Berkeley CSRG alumni. The number (1) is likely unnecessary but serves the historical purpose of denoting the historic BSD ancestry. best regards, Pedro. ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Legal call shortly!
Sorry for the late reminder! As for agenda: Update on GSoC project related to legal team work (as applicable) Go through issues tagged with “needs legal discussion” Usual dialin: Web conference: http://uberconference.com/SPDXTeam Optional dial in number: 415-881-1586 No PIN needed Talk soon! Jilayne ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Meeting in 2 minutes!
Sorry all, forgot to send a reminder last night. We will be meeting at the usual conference bridge… now. Thanks, Jilayne ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Open Source Leadership Summit; minutes, meeting Thursday
Hi all, The meeting minutes from our last call are here: https://wiki.spdx.org/view/Legal_Team/Minutes/2018-01-25 Please note: The Open Source Leadership Summit is March 6-8 in Sonoma, CA. We will have a room Friday, March 9th for an SPDX working session (approx. from 9am to lunch). Who will be there? Call for things to work on? On the last call, we came up with a few ideas, as per below, but wanted to put a call here for other potential topics! We have our next legal call this Thursday at the NEW TIME (an hour earlier than last year). I won’t be there, so Paul will be in charge. Update on my follow-up item re: 3.1 release: I have not gotten an update from LLVM. Will ping again and keep you posted. Cheers, Jilayne ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Meeting today (in approx an hour)
Hi all, Quick reminder of our call today. We’ll discuss the agenda for the face-to-face in a couple weeks and update on 3.1 release. Dial in info is here: https://wiki.spdx.org/view/Legal_Team Thanks, Jilayne ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
update
Hi all, My apologies, but I got buried with other work and have not kept up on the 3.1 release tasks this week. I’ll get caught up and we’ll get this out next week. Sorry to be the logjam. Jilayne ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Jilayne Lovejoy invited you to “SPDX Legal call”.
Jilayne Lovejoy invited you to “SPDX Legal call”. when: Thursday, January 7, 2016, 11:00 AM MST - 12:00 PM MST Repeating event. View details – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGBZ7GUNEPOQB65SZ33EN5GW6EF2IO6LCQ3HZEO6TUJFQOJOCMJVXO=p07=US invitees: You note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 reply: Accept – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGBZ7GUNEPOQB65SZ33EN5GW6EF2IO6LCQ3HZEO6TUJFQOJOCMJVXO=p07=US#reply=accept Decline – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGBZ7GUNEPOQB65SZ33EN5GW6EF2IO6LCQ3HZEO6TUJFQOJOCMJVXO=p07=US#reply=decline Maybe – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGBZ7GUNEPOQB65SZ33EN5GW6EF2IO6LCQ3HZEO6TUJFQOJOCMJVXO=p07=US#reply=tentative --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:spdx-legal@lists.spdx.org DTEND;TZID=America/Denver:20160107T12 TRANSP:OPAQUE UID:FC1A0588-FFD1-4BA6-99D1-81D1A0018C34 DESCRIPTION:Join the call: https: //www.uberconference.com/spdxteam\nOptional dial in number: 857-216-2871\nPIN: 38633 SEQUENCE:0 SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20160107T11 CREATED:20160106T180341Z RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TH;WKST=SU DTSTAMP:20160106T180525Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl
“SPDX Legal call” has been updated.
“SPDX Legal call” has been updated. when: Thursday, January 7, 2016, 11:00 AM MST - 12:00 PM MST Repeating event. View details – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCMFSUV6GYCCWMLMLR5BJEUAWXU2C65THUVTUYJVTC3QT6ZKIDB4C=p44 invitees: You note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 updated by: Jilayne Lovejoy reply: Accepted View Event - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCMFSUV6GYCCWMLMLR5BJEUAWXU2C65THUVTUYJVTC3QT6ZKIDB4C=p44 --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR CALSCALE:GREGORIAN VERSION:2.0 PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=ACCEPTED:mailto:spdx-legal@lists.spdx.org CREATED:20160106T180341Z DESCRIPTION:Join the call: https: //www.uberconference.com/spdxteam\nOptional dial in number: 857-216-2871\nPIN: 38633 DTEND;TZID=America/Denver:20160107T12 DTSTART;TZID=America/Denver:20160107T11 EXDATE;TZID=America/Denver:20160331T11 LAST-MODIFIED:20160623T160759Z RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TH;WKST=SU SEQUENCE:0 SUMMARY:SPDX Legal call TRANSP:OPAQUE UID:FC1A0588-FFD1-4BA6-99D1-81D1A0018C34 DTSTAMP:20160623T160802Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: 2_GE3TQNZUGQYDCMBRG44DONBUGCMFSUV6GYCCWMLMLR5BJEUAWXU2C65THUVTUYJVTC3QT6ZK id...@imip.me.com END:VEVENT BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl
“SPDX Legal call” has been updated.
“SPDX Legal call” has been updated. when: Thursday, January 7, 2016, 11:00 AM MST - 12:00 PM MST Repeating event. View details – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCWT7VDEOSPB34BM2TJIEYNULKXZPHBTKV36E7QYR2KDCNHHPEM54=p44 invitees: You note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 updated by: Jilayne Lovejoy reply: Accepted View Event - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCWT7VDEOSPB34BM2TJIEYNULKXZPHBTKV36E7QYR2KDCNHHPEM54=p44 --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=ACCEPTED:mailto:spdx-legal@lists.spdx.org DTEND;TZID=America/Denver:20160107T12 TRANSP:OPAQUE UID:FC1A0588-FFD1-4BA6-99D1-81D1A0018C34 EXDATE;TZID=America/Denver:20160331T11 DESCRIPTION:Join the call: https: //www.uberconference.com/spdxteam\nOptional dial in number: 857-216-2871\nPIN: 38633 SEQUENCE:0 SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20160107T11 LAST-MODIFIED:20160623T160759Z CREATED:20160106T180341Z RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TH;WKST=SU DTSTAMP:20160623T164906Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: 2_GE3TQNZUGQYDCMBRG44DONBUGCWT7VDEOSPB34BM2TJIEYNULKXZPHBTKV36E7QYR2KDCNHH pe...@imip.me.com END:VEVENT BEGIN:VEVENT TRANSP:OPAQUE DTEND;TZID=America/Denver:20160512T12 ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto
“SPDX Legal call” has been updated.
“SPDX Legal call” has been updated. when: Thursday, January 7, 2016, 11:00 AM MST - 12:00 PM MST Repeating event. View details – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCYS4R5MHS2X436YPLNI2JIYEBQPWAPXKLBPZR362ZWHR27XZP2QU=p07 invitees: You note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 updated by: Jilayne Lovejoy reply: Accepted View Event - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCYS4R5MHS2X436YPLNI2JIYEBQPWAPXKLBPZR362ZWHR27XZP2QU=p07 --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=ACCEPTED:mailto:spdx-legal@lists.spdx.org DTEND;TZID=America/Denver:20160107T12 TRANSP:OPAQUE UID:FC1A0588-FFD1-4BA6-99D1-81D1A0018C34 DESCRIPTION:Join the call: https: //www.uberconference.com/spdxteam\nOptional dial in number: 857-216-2871\nPIN: 38633 SEQUENCE:0 SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20160107T11 CREATED:20160106T180341Z RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TH;WKST=SU DTSTAMP:20160121T180058Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: 2_GE3TQNZUGQYDCMBRG44DONBUGCYS4R5MHS2X436YPLNI2JIYEBQPWAPXKLBPZR362ZWHR27X zp...@imip.me.com END:VEVENT END:VCALENDAR ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
“SPDX Tech/Legal joint call” has been updated.
“SPDX Tech/Legal joint call” has been updated. time changed: Tuesday, February 2, 2016, 11:00 AM MST - 12:00 PM MST location: https://www.uberconference.com/katestewart invitees: You note: this call is to further discuss the proposal for a new format for the SPDX LIcense List template markup, please review: http://wiki.spdx.org/view/Legal_Team/Templatizing and relevant links Join the call: https://www.uberconference.com/katestewart Optional dial in number: 877-297-7470 Alternate number: 512-910-4433 No PIN needed updated by: Jilayne Lovejoy reply: Accept – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDGUFWUJJT4DP7JLDH7AUIP7VQLPXLFURNTEBUNOR45GLHTDSFVHW=p07=US#reply=accept Decline – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDGUFWUJJT4DP7JLDH7AUIP7VQLPXLFURNTEBUNOR45GLHTDSFVHW=p07=US#reply=decline Maybe – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDGUFWUJJT4DP7JLDH7AUIP7VQLPXLFURNTEBUNOR45GLHTDSFVHW=p07=US#reply=tentative --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT TRANSP:OPAQUE DTEND;TZID=America/Denver:20160202T12 UID:4792DD0C-194B-4816-B4ED-63822B43F057 LOCATION:https://www.uberconference.com/katestewart DESCRIPTION:this call is to further discuss the proposal for a new format for the SPDX LIcense List template markup\, please review: http: //wiki.spdx.org/view/Legal_Team/Templatizing and relevant links\n\nJoin the call: https://www.uberconference.com/katestewart\nOptional dial in number: 877-297-7470\nAlternate number: 512-910-4433\nNo PIN needed SEQUENCE:0 SUMMARY:SPDX Tech/Legal joint call DTSTART;TZID=America
“SPDX Legal call” has been canceled.
“SPDX Legal call” has been canceled. when: Thursday, March 31, 2016, 11:00 AM MDT - 12:00 PM MDT note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 deleted by: Jilayne Lovejoy --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:CANCEL BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTAMP:20160317T181849Z UID:FC1A0588-FFD1-4BA6-99D1-81D1A0018C34 SEQUENCE:1 ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: lovejoyl...@gmail.com RECURRENCE-ID:20160331T17Z SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20160331T11 DTEND;TZID=America/Denver:20160331T12 ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=ACCEPTED:mailto:spdx-legal@lists.spdx.org END:VEVENT END:VCALENDAR ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
Jilayne Lovejoy invited you to “SPDX Legal call”.
Jilayne Lovejoy invited you to “SPDX Legal call”. when: Thursday, April 7, 2016, 10:00 AM MDT - 11:00 AM MDT invitees: You note: special time due to conference interferance http://uberconference.com/SPDXTeam User PIN: 38633 or call this number: (United States): +1-857-216-2871 reply: Accept – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAZKLW5VOBXYFVCRLSYSX2KKXO7R2U256AGAY3K2XJN73WKDLS5YC=p07=US#reply=accept Decline – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAZKLW5VOBXYFVCRLSYSX2KKXO7R2U256AGAY3K2XJN73WKDLS5YC=p07=US#reply=decline Maybe – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAZKLW5VOBXYFVCRLSYSX2KKXO7R2U256AGAY3K2XJN73WKDLS5YC=p07=US#reply=tentative --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT CREATED:20160319T171643Z UID:D970D395-2F3A-4242-B268-702238EBB8E4 DTEND;TZID=America/Denver:20160407T11 TRANSP:OPAQUE ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:spdx-legal@lists.spdx.org SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20160407T10 SEQUENCE:0 DESCRIPTION:special time due to conference interferance \nhttp: //uberconference.com/SPDXTeam\n User PIN: 38633 \n\nor call this number: (United States): +1-857-216-2871 \n DTSTAMP:20160319T171755Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: 2_GE3TQNZUGQYDCMBRG44DONBUGAZKLW5VOBXYFVCRLSYSX2KKXO7R2U256AGAY3K2XJN73WKD ls...@imip.me.com END:VEVENT
“SPDX Legal call” has been updated.
“SPDX Legal call” has been updated. when: Thursday, January 7, 2016, 11:00 AM MST - 12:00 PM MST Repeating event. View details – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGALB2B7MSIDNFQLRKLMDIRG6TLE36KUWHLCTKHAVUTKEWRIS5HCVQ=p07 invitees: You note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 updated by: Jilayne Lovejoy reply: Accepted View Event - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGALB2B7MSIDNFQLRKLMDIRG6TLE36KUWHLCTKHAVUTKEWRIS5HCVQ=p07 --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=ACCEPTED:mailto:spdx-legal@lists.spdx.org DTEND;TZID=America/Denver:20160107T12 TRANSP:OPAQUE UID:FC1A0588-FFD1-4BA6-99D1-81D1A0018C34 EXDATE;TZID=America/Denver:20160331T11 DESCRIPTION:Join the call: https: //www.uberconference.com/spdxteam\nOptional dial in number: 857-216-2871\nPIN: 38633 SEQUENCE:0 SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20160107T11 CREATED:20160106T180341Z RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TH;WKST=SU DTSTAMP:20160317T181849Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: 2_GE3TQNZUGQYDCMBRG44DONBUGALB2B7MSIDNFQLRKLMDIRG6TLE36KUWHLCTKHAVUTKEWRIS 5h...@imip.me.com END:VEVENT BEGIN:VEVENT TRANSP:OPAQUE DTEND;TZID=America/Denver:20160204T12 ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: lovejoyl...@gmail.com
“SPDX Legal call” has been updated.
“SPDX Legal call” has been updated. when: Thursday, January 7, 2016, 11:00 AM MST - 12:00 PM MST Repeating event. View details – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAWI3SXXU3C7C3XV5MSICEXIRK4NTACKN35WL2EOI34QV6OCKOSB4=p44 invitees: You note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 updated by: Jilayne Lovejoy reply: Accepted View Event - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAWI3SXXU3C7C3XV5MSICEXIRK4NTACKN35WL2EOI34QV6OCKOSB4=p44 --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2016 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=ACCEPTED:mailto:spdx-legal@lists.spdx.org DTEND;TZID=America/Denver:20160107T12 TRANSP:OPAQUE UID:FC1A0588-FFD1-4BA6-99D1-81D1A0018C34 EXDATE;TZID=America/Denver:20160331T11 DESCRIPTION:Join the call: https: //www.uberconference.com/spdxteam\nOptional dial in number: 857-216-2871\nPIN: 38633 SEQUENCE:0 SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20160107T11 CREATED:20160106T180341Z RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=TH;WKST=SU DTSTAMP:20160512T165601Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: 2_GE3TQNZUGQYDCMBRG44DONBUGAWI3SXXU3C7C3XV5MSICEXIRK4NTACKN35WL2EOI34QV6OC ko...@imip.me.com END:VEVENT BEGIN:VEVENT TRANSP:OPAQUE DTEND;TZID=America/Denver:20160512T12 ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: lovejoyl...@gmail.com
Jilayne Lovejoy invited you to “SPDX Tech/Legal teams joint call”.
Jilayne Lovejoy invited you to “SPDX Tech/Legal teams joint call”. when: Tuesday, August 8, 2017, 11:00 AM MDT - 12:00 PM MDT location: https://www.uberconference.com/katestewart invitees: spdx-t...@lists.spdx.org and you. See replies - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCPJEKREFYLQE23LOOIEANYYESFQGR5MNWHP7V63N6B5ZQSDVOBYK==US note: 17:00 UTC ( 10:00AM PDT, 11:00 MDT, 12:00PM CDT, 1:00PM EDT, 18:00 WAT, 19:00 CEST) https://www.uberconference.com/katestewart Optional dial in number: 877-297-7470 Alternate number: 512-910-4433 No PIN needed After some discussion on the last legal call about how to better represent GPL-2.0 only (and all the other GNU licenses), as well as a bit of clean up around other licenses with varying “or later” clauses such that we are being consistent across the board - we decided a joint call would be the next best step to join-up all the best SPDX minds to come up with a sensible approach. There is a summary of the background and issue here: https://wiki.spdx.org/view/Legal_Team/or-later-vs-unclear-disambiguation reply: Accept - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCPJEKREFYLQE23LOOIEANYYESFQGR5MNWHP7V63N6B5ZQSDVOBYK==US#reply=accept Decline - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCPJEKREFYLQE23LOOIEANYYESFQGR5MNWHP7V63N6B5ZQSDVOBYK==US#reply=decline Maybe - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCPJEKREFYLQE23LOOIEANYYESFQGR5MNWHP7V63N6B5ZQSDVOBYK==US#reply=tentative iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww https://www.apple.com/legal/internet-services/icloud/ww/ https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2017 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE
Jilayne Lovejoy invited you to “SPDX tech/legal call”.
Jilayne Lovejoy invited you to “SPDX tech/legal call”. when: Tuesday, November 21, 2017, 11:00 AM MST - 12:00 PM MST invitees: You note: Web conference: http://uberconference.com/SPDXTeam Optional dial in number: 415-881-1586 No PIN needed reply: Accept - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCK337XLPAWGZF2MWJMG322QH5B57H4MK6Q6DJNY4WQOID26W2K5A==US#reply=accept Decline - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCK337XLPAWGZF2MWJMG322QH5B57H4MK6Q6DJNY4WQOID26W2K5A==US#reply=decline Maybe - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCK337XLPAWGZF2MWJMG322QH5B57H4MK6Q6DJNY4WQOID26W2K5A==US#reply=tentative iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww https://www.apple.com/legal/internet-services/icloud/ww/ https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2017 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT TRANSP:OPAQUE DTEND;TZID=America/Denver:20171121T12 UID:F31FBFD4-9300-4B60-BEC6-81CB9A3EFDCD DESCRIPTION:Web conference: http://uberconference.com/SPDXTeam\n Optional dial in number: 415-881-1586\n No PIN needed SEQUENCE:0 SUMMARY:SPDX tech/legal call DTSTART;TZID=America/Denver:20171121T11 CREATED:20171115T145524Z ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:spdx-legal@lists.spdx.org DTSTAMP:20171115T145556Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: 2_GE3TQNZUGQYDCMBRG44DONBUGCK337XLPAWGZF2MWJMG322QH5B57H4MK6Q6DJNY4WQOID26 w2...@imip.me.com END:VEVENT END:VCALENDAR ___ Spdx
Jilayne Lovejoy invited you to “SPDX Legal call”.
Jilayne Lovejoy invited you to “SPDX Legal call”. when: Thursday, November 10, 2016, 11:00 AM MST - 12:00 PM MST Repeating event. invitees: Kris Reeves and you. See replies - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCOTLCDBI6LFVSDCOLUWAOJW5WUPI47PQQTCIOX5QPBW5TXYVYARY==US note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 reply: Accept - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCOTLCDBI6LFVSDCOLUWAOJW5WUPI47PQQTCIOX5QPBW5TXYVYARY==US#reply=accept Decline - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCOTLCDBI6LFVSDCOLUWAOJW5WUPI47PQQTCIOX5QPBW5TXYVYARY==US#reply=decline Maybe - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGCOTLCDBI6LFVSDCOLUWAOJW5WUPI47PQQTCIOX5QPBW5TXYVYARY==US#reply=tentative iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww https://www.apple.com/legal/internet-services/icloud/ww/ https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2017 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=Kris Reeves;CUTYPE=INDIVIDUAL;EMAIL=k...@pressbuttonllc.com; RSVP=TRUE:mailto:k...@pressbuttonllc.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=ACCEPTED:mailto:spdx-legal@lists.spdx.org DTEND;TZID=America/Denver:20161110T12 TRANSP:OPAQUE UID:1D0EA440-F382-4C2F-86D4-D276458702AA EXDATE;TZID=America/Denver:20171123T11 LAST-MODIFIED:20160707T160001Z DESCRIPTION:Join the call: https: //www.uberconference.com/spdxteam\nOptional dial in number: 857-216-2871\nPIN: 38633 SEQUENCE:0 SUMMARY:SPDX
“SPDX Legal call” has been updated.
“SPDX Legal call” has been updated. time changed: Thursday, December 7, 2017, 11:00 AM MST - 12:00 PM MST Repeating event. View details – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDPEZGXE6YERYBGY7RP66EWVMHWZ4IDFZBQFTH7RH2T5AGIKDVHDQ=p44=US invitees: k...@pressbuttonllc.com and you. See replies – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDPEZGXE6YERYBGY7RP66EWVMHWZ4IDFZBQFTH7RH2T5AGIKDVHDQ=p44=US note changed: New dial in number: 415-881-1586 No PIN needed The weblink for screenshare will stay the same at: http://uberconference.com/SPDXTeam updated by: Jilayne Lovejoy reply: Accept – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDPEZGXE6YERYBGY7RP66EWVMHWZ4IDFZBQFTH7RH2T5AGIKDVHDQ=p44=US#reply=accept Decline – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDPEZGXE6YERYBGY7RP66EWVMHWZ4IDFZBQFTH7RH2T5AGIKDVHDQ=p44=US#reply=decline Maybe – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGDPEZGXE6YERYBGY7RP66EWVMHWZ4IDFZBQFTH7RH2T5AGIKDVHDQ=p44=US#reply=tentative --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2017 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=j...@jilayne.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=Kris Reeves;CUTYPE=INDIVIDUAL;EMAIL=k...@pressbuttonllc.com; RSVP=TRUE:mailto:k...@pressbuttonllc.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:spdx-legal@lists.spdx.org DTEND;TZID=America/Denver:20171207T12 TRANSP:OPAQUE UID:43163941-8A88-49D0-BB05-4FF72F29AD6F
“SPDX Legal call” has been canceled.
“SPDX Legal call” has been canceled. when: Thursday, November 23, 2017, 11:00 AM MST - 12:00 PM MST note: Join the call: https://www.uberconference.com/spdxteam Optional dial in number: 857-216-2871 PIN: 38633 deleted by: Jilayne Lovejoy --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2017 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:CANCEL BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTAMP:20171115T143929Z UID:43163941-8A88-49D0-BB05-4FF72F29AD6F SEQUENCE:1 ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: lovejoyl...@gmail.com RECURRENCE-ID:20171123T18Z SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20171123T11 DTEND;TZID=America/Denver:20171123T12 ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=ACCEPTED:mailto:spdx-legal@lists.spdx.org END:VEVENT END:VCALENDAR ___ Spdx-legal mailing list Spdx-legal@lists.spdx.org https://lists.spdx.org/mailman/listinfo/spdx-legal
“SPDX Legal call” has been updated.
“SPDX Legal call” has been updated. when: Thursday, January 11, 2018, 10:00 AM MST - 11:00 AM MST Repeating event. View details – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAE3JJVDOW4JFRFTRU7ZKMA3XGDLLR2C7XKPLSZOXQQZQOOSS2QRE=p44=US location: http://uberconference.com/SPDXTeam invitees: You note: Web conference: http://uberconference.com/SPDXTeam Optional dial in number: 415-881-1586 No PIN needed updated by: Jilayne Lovejoy reply: Accept – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAE3JJVDOW4JFRFTRU7ZKMA3XGDLLR2C7XKPLSZOXQQZQOOSS2QRE=p44=US#reply=accept Decline – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAE3JJVDOW4JFRFTRU7ZKMA3XGDLLR2C7XKPLSZOXQQZQOOSS2QRE=p44=US#reply=decline Maybe – https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGAE3JJVDOW4JFRFTRU7ZKMA3XGDLLR2C7XKPLSZOXQQZQOOSS2QRE=p44=US#reply=tentative --- iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww Terms and Conditions: https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2018 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=lovejoyl...@gmail.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:spdx-legal@lists.spdx.org DTEND;TZID=America/Denver:20180111T11 TRANSP:OPAQUE UID:FE22C68D-F564-483D-B499-DC3759D2A41F LOCATION:http://uberconference.com/SPDXTeam DESCRIPTION:Web conference: http://uberconference.com/SPDXTeam\n Optional dial in number: 415-881-1586\n No PIN needed SEQUENCE:0 SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20180111T10 CREATED:20180109T145448Z RRULE:FREQ=WEEKLY
Jilayne Lovejoy invited you to “SPDX Legal call”.
Jilayne Lovejoy invited you to “SPDX Legal call”. when: Thursday, January 11, 2018, 10:00 AM MST - 11:00 AM MST location: http://uberconference.com/SPDXTeam invitees: You note: Web conference: http://uberconference.com/SPDXTeam Optional dial in number: 415-881-1586 No PIN needed reply: Accept - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGBYP4SKSOJVI2UFYFQ2N4ZOUM2WQM4ZVCRORMV65RNJKNOCRJECJO==US#reply=accept Decline - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGBYP4SKSOJVI2UFYFQ2N4ZOUM2WQM4ZVCRORMV65RNJKNOCRJECJO==US#reply=decline Maybe - https://www.icloud.com/calendar/eventreply/?t=2_GE3TQNZUGQYDCMBRG44DONBUGBYP4SKSOJVI2UFYFQ2N4ZOUM2WQM4ZVCRORMV65RNJKNOCRJECJO==US#reply=tentative iCloud is a service provided by Apple. Apple ID: https://appleid.apple.com/choose-your-country/ Support: https://www.apple.com/support/icloud/ww https://www.apple.com/legal/internet-services/icloud/ww/ https://www.apple.com/legal/internet-services/icloud/ww/ Privacy Policy: https://www.apple.com/legal/internet-services/privacy/ Copyright 2018 Apple Inc. 1 Infinite Loop, Cupertino, CA 95014, United States. All rights reserved. BEGIN:VCALENDAR VERSION:2.0 CALSCALE:GREGORIAN PRODID:-//CALENDARSERVER.ORG//NONSGML Version 1//EN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Denver X-LIC-LOCATION:America/Denver BEGIN:STANDARD DTSTART:18831118T120004 RDATE;VALUE=DATE-TIME:18831118T120004 TZNAME:MST TZOFFSETFROM:-0659 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19180331T02 RRULE:FREQ=YEARLY;UNTIL=19190330T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19181027T02 RRULE:FREQ=YEARLY;UNTIL=19191026T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:STANDARD DTSTART:19200101T00 RDATE;VALUE=DATE-TIME:19200101T00 RDATE;VALUE=DATE-TIME:19420101T00 RDATE;VALUE=DATE-TIME:19460101T00 RDATE;VALUE=DATE-TIME:19670101T00 TZNAME:MST TZOFFSETFROM:-0700 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19200328T02 RRULE:FREQ=YEARLY;UNTIL=19210327T09Z;BYDAY=-1SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19201031T02 RDATE;VALUE=DATE-TIME:19201031T02 RDATE;VALUE=DATE-TIME:19210522T02 RDATE;VALUE=DATE-TIME:19450930T02 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19420209T02 RDATE;VALUE=DATE-TIME:19420209T02 TZNAME:MWT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19450814T17 RDATE;VALUE=DATE-TIME:19450814T17 TZNAME:MPT TZOFFSETFROM:-0600 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19650425T02 RRULE:FREQ=YEARLY;UNTIL=19660424T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19651031T02 RRULE:FREQ=YEARLY;UNTIL=19661030T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19670430T02 RRULE:FREQ=YEARLY;UNTIL=19730429T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:19671029T02 RRULE:FREQ=YEARLY;UNTIL=20061029T08Z;BYDAY=-1SU;BYMONTH=10 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD BEGIN:DAYLIGHT DTSTART:19740106T02 RDATE;VALUE=DATE-TIME:19740106T02 RDATE;VALUE=DATE-TIME:19750223T02 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19760425T02 RRULE:FREQ=YEARLY;UNTIL=19860427T09Z;BYDAY=-1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:19870405T02 RRULE:FREQ=YEARLY;UNTIL=20060402T09Z;BYDAY=1SU;BYMONTH=4 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:DAYLIGHT DTSTART:20070311T02 RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3 TZNAME:MDT TZOFFSETFROM:-0700 TZOFFSETTO:-0600 END:DAYLIGHT BEGIN:STANDARD DTSTART:20071104T02 RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11 TZNAME:MST TZOFFSETFROM:-0600 TZOFFSETTO:-0700 END:STANDARD END:VTIMEZONE BEGIN:VEVENT TRANSP:OPAQUE DTEND;TZID=America/Denver:20180111T11 UID:FE22C68D-F564-483D-B499-DC3759D2A41F LOCATION:http://uberconference.com/SPDXTeam DESCRIPTION:Web conference: http://uberconference.com/SPDXTeam\n Optional dial in number: 415-881-1586\n No PIN needed SEQUENCE:0 SUMMARY:SPDX Legal call DTSTART;TZID=America/Denver:20180111T10 CREATED:20180109T145448Z ATTENDEE;CUTYPE=INDIVIDUAL;EMAIL=lovejoyl...@gmail.com;PARTSTAT=ACCEPTED; ROLE=CHAIR;CN=Jilayne Lovejoy:mailto:lovejoyl...@gmail.com ATTENDEE;CN=SPDX-legal;CUTYPE=INDIVIDUAL;EMAIL=spdx-legal@lists.spdx.org; PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:spdx-legal@lists.spdx.org DTSTAMP:20180109T145543Z ORGANIZER;CN=Jilayne Lovejoy;EMAIL=lovejoyl...@gmail.com:mailto: 2_GE3TQNZUGQYDCMBRG44DONBUGBYP4SKSOJVI2UFYFQ2N4ZOUM2WQM4ZVCRORMV65RNJKNOCR je