And there is chat (plus dial-in info) on this uberconference: https://www.uberconference.com/SPDXTeam
-- Brad Edmondson, *Esq.* 512-673-8782 | brad.edmond...@gmail.com On Thu, Aug 4, 2016 at 1:13 PM, Sam Ellis <sam.el...@arm.com> wrote: > I am dialed in using: 857-216-2871 / pin 38633. > > > -----Original Message----- > > From: spdx-legal-boun...@lists.spdx.org [mailto:spdx-legal- > > boun...@lists.spdx.org] On Behalf Of Vidal, Thomas > > Sent: 04 August 2016 18:12 > > To: Jilayne Lovejoy > > Cc: SPDX-legal > > Subject: Re: call Thursday > > > > Do I have the wrong call-in information because nobody else is on the > line > > I'm on. > > > > > > On Aug 3, 2016, at 10:46 PM, J Lovejoy > > <opensou...@jilayne.com<mailto:opensou...@jilayne.com>> wrote: > > > > Hi all, > > > > Reminder we have a legal team call Thursday - same bat time, same bat > > channel. http://wiki.spdx.org/view/Legal_Team > > > > Agenda as follows: > > > > 1) any Business As Usual items - new license request, request for markup, > > etc. (see email threads, Dennis to lead :) > > > > 2) go over any flagged for review licenses in XML files > > > > NOTE - last meeting we came up with a timeline for completing the review > > and conversation to XML format for the SPDX License List. I've cut and > > pasted that from the meeting minutes below to make sure everyone > > remembers and we stay on track... :) > > > > Jilayne > > > > > > > > > > SPDX License List XML files - what needs to be done to get to release > stage: > > > > 1. finish main review of licenses so that all can merged and other > clean-up, > > which also includes: (finish by end of August) > > * opening and closing < SPDX > tag are not always same case - > should be > > all upper-case > > * discussion on what to do about some licenses that were flagged > as > > having self-referring numbering - will save this data even tho not > complete, > > just in case we want to go that route later; can be an attribute that is > not > > "seen" at this point; don't merge these yet --> Kris will add attribute > and > > merge. > > * for those that are tagged as "requires acknowledgement" - > reminder to > > not merge --> Kris to deal with those all at once > > * Kris to do another pass to do some clean-up, including body tag > to be > > removed > > 2. exceptions need to be added to XML - Kris will add to Github for > review, > > will have own pull requests (Note from Gary: tools don't care whether in > > same or different directory) > > 3. same situation for deprecated licenses - Gary's point that need > XML for > > tools (Gary and Kris were going back and forth on whether own XML files > > needed for this or not - to check on outcome of this) > > 4. review various webpages for updating --> Alan to do this (have > first pass > > for review by group by mid-August) > > * License matching guidelines page > > * License list overview page; add info/explanation about XML tags > (with > > input from Kris and Gary for tags) > > 5. define a new process for License List, i.e., how to request a new > license, > > what kind of pull requests we want, underlying process etc. --> Jilayne > to do > > this (end of August for review by group) > > * check with Kate re: moving license list to Github primary > (instead of LF > > Git and mirrored to Github) > > 6. Gary to update spdx-tools for new XML format (including website > > generation) - for 5 different formats (mid- to late- September) > > * Gary already has basic structure in place; time frame such that > he could > > do testing in mid- to end-September > > * end-of September would aim to have preview of website so we can > > check it, probably then one more pass at tools, etc. > > 7. need new tool to take text of new license and convert to XML file > (to do > > so by hand is a bit tedious). Will still need human review before > finalizing. > > (doesn't have to be done for release stage) > > > > > > SPDX Legal Team co-lead > > opensou...@jilayne.com<mailto:opensou...@jilayne.com> > > > > > > _______________________________________________ > > Spdx-legal mailing list > > Spdx-legal@lists.spdx.org<mailto:Spdx-legal@lists.spdx.org> > > https://lists.spdx.org/mailman/listinfo/spdx-legal > > > > > > ________________________________ > > > > ***CONFIDENTIALITY NOTICE*** > > This email contains confidential information which may also be legally > > privileged and which is intended only for the use of the recipient(s) > named > > above. If you are not the intended recipient, you are hereby notified > that > > forwarding or copying of this email, or the taking of any action in > reliance on > > its contents, may be strictly prohibited. If you have received this > email in > > error, please notify us immediately by reply email and delete this > message > > from your inbox. > > > > _______________________________________________ > > Spdx-legal mailing list > > Spdx-legal@lists.spdx.org > > https://lists.spdx.org/mailman/listinfo/spdx-legal > > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > _______________________________________________ > 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
