|
Re: SPDX face to face at LF CollabSummit
Michael J Herzog <mjherzog@...>
Martin,
toggle quoted message
Show quoted text
The meeting last year at the Collab Summit was very productive so I strongly recommend that we plan an F2F meeting. We can manage the agenda around areas where we may need participation from Kate and Rockett. regards, Michael Michael J. Herzog +1 650 380 0680 | mjherzog_at_nexB.com nexB [Open by Design] 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 12/8/2010 6:29 AM, Martin Michlmayr wrote:
I'm wondering if we should make any plans for the LF Collaboration |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: SPDX face to face at LF CollabSummit
Philip Koltun
Great minds think alike!
I have been asked to organize a compliance track for the Collaboration Summit and would like to include SPDX briefings and updates as a significant part of the track. (FOSSBazaar as well.) I was planning to talk initially to Kate and Phil O about SPDX presentations. All ideas are welcome.
Phil Koltun
Director, Open Compliance Program
The Linux Foundation
On Wed, Dec 8, 2010 at 8:29 AM, Martin Michlmayr <tbm@...> wrote: I'm wondering if we should make any plans for the LF Collaboration |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
SPDX face to face at LF CollabSummit
Martin Michlmayr
I'm wondering if we should make any plans for the LF Collaboration
Summit in 2011. The CollabSummit will take place April 6-8 in San Francisco. Traditionally, FOSSBazaar had a room there and we could request a room and use it for SPDX. However, I noticed that at least Kate and Rockett will be presenting SPDX at the European Legal Network Conference, which unfortunately conflicts with the CollabSummit since it takes place on April 7-8 in Amsterdam. Any thoughts? -- Martin Michlmayr Open Source Program Office, Hewlett-Packard |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Python History and License
Tom Incorvia
Some additional information has been added to the Python license graphic (attached).
Based on the new information, it appears that the stand alone CNRI license on opensource.org is ONLY for the licensing of the beta version of python 1.6.1. Kate Stewart and I will confirm this with Python Legal.
Tom
Mobile: (408) 499 6850 From: Tom Incorvia
Sent: Friday, December 03, 2010 8:14 AM To: spdx@... Cc: Jilayne Lovejoy; kate.stewart@...; Esteban Rockett; Kim Weins Subject: RE: Python History and License
New Proposal for SPDX license tracking related to the Python project and Python “License”:
1. Track "Python License" separate from "Python License Stack". a. The Python Programming Language, regardless of version, would be attributed to the stack b. However, other projects can be licensed specifically under the Python License (which is ONLY the first license in the stack).
That’s it.
An update to the graphic from two weeks ago is attached. The highlighted portions are new.
Tom
This message has been scanned for viruses by MailController. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
License Meeting Minutes from today are available
Kim Weins
Hi Everyone
Minutes on license meeting are now available on the wiki at the link below. We have a few remaining followups that are being chased down (per the minutes) and after that we will temporarily CLOSE adding of new licenses. We need to focus on getting the license repo in place and getting license data loaded and reviewed. Once that is done, we will define and document the process for adding new licenses to the list and re-open the list. If you see any egregious items missing from the license list, please let us know ASAP. Everything else will need to wait for the license repo to get in place — we’re estimating that will be about 8 weeks away. License List on wiki http://www.spdx.org/wiki/license-list Minutes http://www.spdx.org/wiki/license-subteam-minutes-20101203 Kim Kim Weins | Senior Vice President, Marketing kim.weins@... Follow me on Twitter @KimAtOpenLogic 650 279 0410 | cell www.openlogic.com Follow OpenLogic on Twitter @OpenLogic OpenLogic, Inc. Headquarters, Broomfield, Colorado |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Updated Invitation: SPDX Legal Workstream (Rollout) Call 11ET/10CT/8PT @ Wed Dec 15 8am - 9am (spdx@fossbazaar.org)
Esteban Rockett <mgia3940@...>
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Invitation: SPDX SPDX Legal Workstream (Rollout) Call 11ET/10CT/8PT @ Wed Dec 15 8am - 9am (spdx@fossbazaar.org)
Esteban Rockett <mgia3940@...>
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: Python History and License
Tom Incorvia
New Proposal for SPDX license tracking related to the Python project and Python “License”:
1. Track "Python License" separate from "Python License Stack". a. The Python Programming Language, regardless of version, would be attributed to the stack b. However, other projects can be licensed specifically under the Python License (which is ONLY the first license in the stack).
That’s it.
An update to the graphic from two weeks ago is attached. The highlighted portions are new.
Tom
This message has been scanned for viruses by MailController. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Minutes from 2 Dec SPDX General Meeting and IMPORTANT notice
Philip Odence
IMPORTANT: We need interested folks to sign up for the respective mailing lists for the three teams (Technical, Business, Legal). In the next month or so, invitations to those teams' meetings will go only to the team lists. This general list will continue to be used to announce and circulate minutes for the General Meeting. If you need help see the memo from Martin I copied below. Or let me know if you have questions. Here are the minutes: Thanks, Phil FROM MARTIN M:
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
SPDX License Review: Part 3 10ET/7PT
Kim Weins
8:00 AM - 9:00 AM December 3, 2010 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Agenda for SPDX meeting today
Philip Odence
As discussed last meeting, we are evolving this to the be the SPDX General Meeting, the main purpose being sharing and cross functional coordination between the Technical, Business and Legal Teams. This will be the first General Meeting per se and we will be trying a new agenda structure. Meeting Time: Dec 2, 8am PDT / 10 am CDT / 11am EDT / 16:00 UTC. http://www.timeanddate.com/worldclock/converter.html Conf call dial-in: Conference code: 7812589502 Toll-free dial-in number (U.S. and Canada): (877) 435-0230 International dial-in number: (253) 336-6732 For those dialing in from other regions, a list of toll free numbers can be found: https://www.intercallonline.com/portlets/scheduling/viewNumbers/viewNumber.do?ownerNumber=6053870&audioType=RP&viewGa=false&ga=OFF Web: Note, we will be using a different URL for each meeting for purposes of taking attendance. When you login PLEASE INCLUDE YOUR FULL NAME IN THIS FORM: Phil Odence, Black Duck Software so I can just copy/paste into minutes. THX. http://blackducksoftware.na6.acrobat.com/spdx2dec10 Administrative Agenda
Technical Team Report - Kate Business Team Report - Kim/JohnE
Legal Team Report - Rockett/Karen Cross Functional Issues - Phil
Action Items Most of the action items belong with the Teams. So, in addition to statusing, we will dispatch them to the respective teams and will not continue to track in this meeting. Action items for this meeting will be cross functional. • Dave/JeffL - Update zlib based on new specification DONE, BUT AWAITING FEEDBACK FROM GARY • PeterW- Implement issue tracking system. BLOCKED ON KATE • Kate - submit ids to Linux Foundation so infrastructure setup can proceed - PENDING • Kate- Draft example for LF Member Counsel; include XML and corresponding spreadsheet (or spreadsheet-like) format. PENDING • Rockett- Query status of trademark application DONE. APPLICATION IS IN AN WAITING FOR ASSIGNMENT OF A TM EXAMINER • All- Review 6 months mail and contrast against licensing group spreadsheet. FOR NEXT LICENSE GRP MEETING • Kate- Write up formal proposal on SHA field change and mail to list. IN PROCESS • All- Review SHA field change proposal for technical flaws; if so, discuss on list. FOR TECH AGENDA NXT MEETING • Kate- Add back to SPEC page in WIKI preferred syntax for adding comments. TO BE DONE • Michael H- Write up and share position on "reporting" vs. "interpreting." • PhilO- Get legal team input on Michael's position. L. Philip Odence Vice President of Business Development Black Duck Software, inc. 265 Winter Street, Waltham, MA 02451 Phone: 781.810.1819, Mobile: 781.258.9502
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
New SPDX mailing lists
Martin Michlmayr
As Phil mentioned during the last SPDX call, we added a number of
mailing lists to facilitate discussions of specific areas. This list (spdx@...) will continue to be used for general discussions but discussions about specific topics (technical development of the spec; rollout and other business aspects; and legal aspects) will take place on the other mailing lists. If you want to participate in the technical, business or legal team discussions, you therefore have to subscribe to their mailing lists. You can find a link to the mailing lists on each team wiki page: - Technical Team: http://spdx.org/wiki/spdx/spec-development - Business Team: http://spdx.org/wiki/spdx/biz - Legal Team: http://spdx.org/wiki/spdx/legal Follow the link to the mailing list and on the page for the mailing list search for "Subscribing to". Enter your email address, name (optional) and password and click on "Subscribe". You will then get an email with a link that you have to follow in order to confirm their subscription. Mailing list archives are also available so you can check if you missed any discussions. If you have any questions or problems, please let me know. -- Martin Michlmayr Open Source Program Office, Hewlett-Packard |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
SPDX Business (Rollout) Call 11ET/8PT
Kim Weins
9:00 AM - 10:00 AM December 9, 2010 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Python History and License
Tom Incorvia
Regarding the Python licensing,
Kim is correct. http://python.org/psf/summary/ clearly states that the PSF Python releases are licensed under the stack of licenses. So my statement regarding a particular PSF version being licensed under one and only one license is incorrect for the PSF-related licenses – it is the stack.
If we can get a statement from the PSF saying that the stack license applies regardless of version (even the old CWI versions), then we will only need the stack-license (although it has a “pick whatever applies to your release” nature that is a bit different than what we have been doing). This is a bit different than the Mozilla tri-license where the end user picks . . .
The alternative to listing the stack-license would be to have PSF say on a version by version basis when a stack / stack-subset / individual license applies. Messy – that is the route that I was taking.
Tom
Tom Incorvia Direct: (512) 340-1336 Mobile: (408) 499 6850
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Python License Graphic for Friday Teledonference
Tom Incorvia
Please find attached a jpeg that details Python licensing (for today’s Python agenda item in the SPDX Licensing teleconference). Tom
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
newly uploaded license list
Jilayne Lovejoy <Jlovejoy@...>
Hi All,
I have uploaded a new version of the License List (v1.3) in spreadsheet format to the Wiki page, as well as accompanying guidelines document (remaining outstanding questions highlighted in yellow there). As per last week’s license meeting, I made the following changes:
Exceptions added: - GPL v2 w/Autoconf exception – I could not find a link to this. The GNU website only has the v3 exception, but there was one for v2. I even tried downloading an old version of Autoconf and the COPYING.txt file (which is supposed to have the exception included in it…) did not have the exception. Please check to see the text I did find is correct - GPL v2 w/Bison exception - GPL v2 w/Classpath exception - GPL v2 w/GCC Runtime Library exception – I could not find a link to this. GNU website only have v3 exception. Please check if this text is correct…
- GPL v3 w/Autoconf exception - GPL v3 w/GCC Runtime Library Exception – the GNU website has a v3.0 and v3.1 of this exception – the most recent one is included here. I could not find
If there is another exception you want added, can you please email me the name of it and a url for where you found the text.
Thanks,
Jilayne Lovejoy | Corporate Counsel
720 240 4545 | phone 720 240 4556 | fax 1 888 OpenLogic | toll free
OpenLogic, Inc. Headquarters, Broomfield, Colorado 80021
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Re: artifactof proposal ratified... but couldn't post comment (Martin?)
Martin Michlmayr
I'm not sure why the system would flag this comment as spam but the
toggle quoted message
Show quoted text
logs confirm that it did. I changed a setting so that comments marked as spam are no longer discarded; instead they require manual approval. Please post the comment again and I'll approve it. * Bill Schineller <bschineller@...> [2010-11-18 17:01]: Per our call, I attempted to comment on the ratification of the artifactof proposal by commenting on the wiki page --
Martin Michlmayr Open Source Program Office, Hewlett-Packard |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
SPDX License Review Meeting: Part 2
Kim Weins
8:00 AM - 9:00 AM November 19, 2010 |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
artifactof proposal ratified... but couldn't post comment (Martin?)
Bill Schineller
Per our call, I attempted to comment on the ratification of the artifactof proposal by commenting on the wiki page
http://www.spdx.org/wiki/proposal-2010-10-21-3-artifactof Unfortunately, the wiki told me my comment triggered the spam filter and wouldn’t save it. Here is the comment (Martin?) “2010-11-18 general call feedback “By choosing to reference DOAP model, we are tacitly approving that an SPDX document may include with it additional information which is in the DOAP vocabulary. We are requiring that an SPDX 1.0 compliant parser be able to understand only the 2 fields from DOAP (name and homepage). If additional information from DOAP is included within the SPDX document, an SPDX 1.0 compliant parser may silently ignore the additional information. Folks on the 2010-11-18 general call accepted the ArtifactOf proposal, and rejected the 'File origin' proposal.” On 11/17/10 5:23 PM, "Philip Odence" <podence@...> wrote: Meeting Time: Nov18, 8am PDT / 10 am CDT / 11am EDT / 16:00 UTC. http://www.timeanddate.com/worldclock/converter.html Bill Schineller Knowledge Base Manager Black Duck Software Inc. T: +1.781.810.1829 F: +1.781.891.5145 E: bschineller@... http://www.blackducksoftware.com |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
new release of Ninka
dmg
Hi everybody,
We are releasing a minor update to our license identification tool. The major difference with version 1.0-pre1 is packaging. We no longer require the user to download and patch the sentence splitter. It should be easier to use. We also thank Armijn Hemel for his help with the documentation. http://turingmachine.org/~dmg/temp/ninka-1.0-pre2.tar.bz2 Enjoy! --dmg -- -- Daniel M. German http://turingmachine.org/ http://silvernegative.com/ dmg (at) uvic (dot) ca replace (at) with @ and (dot) with . |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|