Minutes from May 2 Meeting
Philip Odence
The survey is still open. If you haven't responded, please do: www.spdx.org/survey
|
|
SPDX General Meeting Reminder and Collab Summit Summary
Philip Odence
Announcements
Summary of very successful Collaboration Summit (also appended at the bottom)
HELP WITH THE SURVEY (please please please)
Meeting Time: Thursday, May 2, 8am PST / 10 am CST / 11am EST / 15: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 Administrative Agenda
Attendance
Approve Minutes-
Technical Team Report - Kate
Next steps
Legal Team Report - Jilayne
Next steps
Business Team Report – Jack/Scott
Next steps
Cross Functional Issues –
Phil
Website Update – Jack
COLLABORATION SUMMIT SUMMARY
For those of you who didn’t make it to the Collaboration Summit, below is a summary of the different components of the event. It was pretty inspiring in a number of ways…for me, it felt like the
rubber is finally meeting the road seeing real tools—our own, from academia, and commercial—putting out real live SPDX docs. The every positive KarenC summed it up as “The discussions have much more of a feeling that this has to happen – the only questions
are around how.” And I agree.
All the team leads did an outstanding job organizing our ever expanding involvement in Linux event. (Now we even get our own track.) Gary, MarkG and Adam were also key in pulling this off.
Tech Team Working Session
In this session we went through the current model proposal for 2.0, and discussed options that would simplify the model, and still meet the use cases we're targeting. We were also able to start
off the relationship and element usage enumerations. Full details can be found at: http://wiki.spdx.org/view/Technical_Team/Minutes/2013-04-16.
Legal Team Working Session
The SPDX Legal Team met at the LF Collab Summit to hash out the remaining bits of the License Matching guidelines. Namely whether SPDX should provide "guidelines only" in regards to what is to be
considered substantive text of a license for matching purposes or whether SPDX should go further and provide some kind of actual markup or examples in regards to text than can be ignored or considered "replaceable" for matching purposes. And, if the latter,
to what extent and in what format to provide such markup or examples. The legal team, with good representation from various tool makers and tech team members, decided that markup was needed to avoid potential differences in interpretation by tool makers.
It was decided to use simple markup that could be illustrated within a .txt file, as that is the (mostly) preferred download format for the licenses. The exact details of the markup are being worked out and the Legal Team (with help from anyone else in the
SPDX Workgroup) will manage getting the markup created for the entire current SPDX License List.
Open SPDX Discussion
Mark Gisi from Windriver and Adam Cohn from Cisco held this session on Tuesday afternoon. It was held under Chatham House Rules which means “When a meeting, or part thereof, is held under the Chatham
House Rule, participants are free to use the information received, but neither the identity nor the affiliation of the speaker(s), nor that of any other participant, may be revealed.”. Now before you say hey you just said you weren’t supposed to mention names,
these two were the chairs as listed on the SPDX schedule.There was a lot of good discussion. One individual talked about how they are fully integrating SPDX into what they their company delivers and how they are shipping, and I believe the number was, over
500 SPDX documents with each release. They also had a website for generating SPDX documents. Others talked about how they have started to integrate SPDX into their compliance process using it for reviews but not yet quite shipping. The reasons seemed to vary
for that but they appeared to be more procedural than SPDX related. One individual did raise a concern on the amount of time that it might take to generate SPDX documents adding that it increased the cost of their compliance it was not something they could
do. A few individuals talked about the adoption of SPDX among open source projects. There was some discussion on how this could be done now as there are a few open source tools that have appeared to generate SPDX documents. One individual talked about how
they would like to see SPDX become more fully integrated into the community meaning that practices normally associated with an open source project such as peer review and so forth were used and considered part of the process of generating, reviewing and editing
SPDX documents.
SPDX Morning Sessions
Mark Gisi (the man that Scott calls “the spiritual leader of SPDX adoption”) kicked off the morning with License to Kill…You Code, a very cogent treatise on why it’s important for copyright holders
to get it right if they want their projects to thrive.
Then Gary “the Toolman” O’Neall lead a panel on Tooling up for SPDX. He gave an over view of group, community and commercial tools that are now compatible with SPDX. Gary was joined by Matt Germonprez
of the University of Nebraska Omaha and Sameer Ahmed from Wind River Systems who both talked in some detail about work their groups have done to “tool up.”
Conclusion: This stuff is real! And to prove it…
SPDX Bakeoff
The SPDX Bakeoff was held Wednesday afternoon. Our main objective was to compare SPDX output from different tools in order to identify bugs and resolve different interpretations of the specification.
We had great representation from the various tool providers, members of the SPDX working group, and a number of other interested parties. Gary O’Neall’s excellent spreadsheet comparison tool was used as the basis for comparison of the various SPDX files. Per
the agenda, we first stepped through the complete Time package on a file by file basis. Following that we dove into Busybox but only at the package level. There was a lot good discussion and yes we did find some bugs in the tools and areas where the specification
needs to be improved. All in all it was a very productive session and should serve to advance the adoption of SPDX. The spreadsheet along with notes from the session are captured on in this Google doc folder: https://drive.google.com/?tab=mo&authuser=0#folders/0BxKdX878M2HCTlZIbkZSMXN6SGc
|
|
SPDX Website and Survey
Philip Odence
Here's some great news about the website and a request for your help with the SPDX survey.
WEBSITE
I am pleased to tell you that http://spdx.org/ has been upgraded with a new, superior underlying platform as well as new architecture/look & feel. It should take you about 2 seconds to notice the improvement. The biggest
conceptual change is the we have separated the main site from the wiki and upgraded the wiki as well. Now the main site is mainly for purposes of learning and consumption and the wiki is our working area.
Jack Manbeck deserves a ton of credit for driving this change and herding the cats needed to make it happen before the Collaboration Summit. (He's accepting beers in SF next week.) Other worthy beer recipients are Brian Warner from the Linux Foundation
and Martin Michlmayr who seamlessly migrated the wiki. Jilayne, Scott, Kate and Gary also participated in the heavy lifting, and credit goes to Ibrahim Haddad for originally convincing us to accept the Foundation's generous offer to help with the site.
SURVEY
A key part of the business team's agenda is to make sure we systematically collect and utilize industry feedback on an ongoing basis. The first step in that is a survey to help better understand current awareness and adoption of SPDX and to get some insight
future plans and what we can do to shape that future. http://www.spdx.org/survey
We will be promoting the survey at the Collaboration Summit. Here is how you can help drive further participation:
Thanks,
Phil
L. Philip Odence
Vice President of Business Development
Black Duck Software, Inc.
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence
|
|
Re: Wiki migration: feedback required
Lamons, Scott (Open Source Program Office) <scott.lamons@...>
New wiki looks great.
Scott: ++1 The LF hasn't installed a WYSIWYG editor yet but we can request it ifthere's a need. Jack: I'm thinking we should request one. Media wiki syntax while not difficult may seem bizarre to some people? Scott: yes! |
|
Re: Wiki migrated to MediaWiki
Martin Michlmayr
* Marc-Etienne Vargenau <Marc-Etienne.Vargenau@...> [2013-04-11 15:48]:
The e-mail address wiki@... given in pageYeah, I know. I also sent a request to the LF. You can email me directly in the meantime. -- Martin Michlmayr Open Source Program Office, Hewlett-Packard |
|
Re: Wiki migrated to MediaWiki
Marc-Etienne Vargenau
Le 11/04/2013 12:58, Martin Michlmayr a écrit :
The wiki has been migrated to a proper wiki using MediaWiki. AllHello, The e-mail address wiki@... given in page http://wiki.spdx.org/view/Getting_started to request an account does not seem to work. Best regards, Marc-Etienne -- Marc-Etienne Vargenau Marc-Etienne.Vargenau@... Alcatel-Lucent France, Route de Villejust, 91620 NOZAY, FRANCE +33 1 30 77 28 33 OnNet 2103 2833 |
|
Re: Wiki migrated to MediaWiki
Manbeck, Jack
I glossed over the Getting Started link. Would it make sense to display it as "Getting Started Using this Wiki"?
toggle quoted message
Show quoted text
Jack -----Original Message-----
From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Martin Michlmayr Sent: Thursday, April 11, 2013 6:59 AM To: spdx@... Subject: Wiki migrated to MediaWiki The wiki has been migrated to a proper wiki using MediaWiki. All content (including past revisions) has been migrated. You can find the new wiki at http://wiki.spdx.org/view/ Here's a "Getting started" guide: http://wiki.spdx.org/view/Getting_started And a set of proposed wiki conventions, although they will have to be refined as we gain more experience with the new wiki: http://wiki.spdx.org/view/Wiki_Conventions If you have any questions, please let me know. -- Martin Michlmayr Open Source Program Office, Hewlett-Packard _______________________________________________ Spdx mailing list Spdx@... https://lists.spdx.org/mailman/listinfo/spdx |
|
Re: Wiki migration: feedback required
Manbeck, Jack
New wiki looks great.
The LF hasn't installed a WYSIWYG editor yet but we can request it ifthere's a need. Jack: I'm thinking we should request one. Media wiki syntax while not difficult may seem bizarre to some people? Attachments can only be downloaded when logged inJack: Attachments seem necessary so I wouldn't want to remove that ability if that is what you are suggesting. Let's talk about the issues first. I like the wiki conventions page. We should probably call it out on the main page to read before you make changes to the site? I would also suggest adding a few basics, such as How do I create a New Page on there (it's not obvious if you haven't done it) and how to upload and insert an image on a page? You could also link to here as well: http://www.mediawiki.org/wiki/Help:Formatting . If you'd like I could add it. Jack -----Original Message----- From: spdx-bounces@... [mailto:spdx-bounces@...] On Behalf Of Martin Michlmayr Sent: Thursday, April 11, 2013 7:00 AM To: spdx@... Subject: Re: Wiki migration: feedback required * Martin Michlmayr <tbm@...> [2013-03-11 16:28]: ## Known IssuesStill a problem. In fact, the attachment extension is quite buggy, so I'd like to remove it. * Comments have not been migratedComments have been migrated in the meantime. * I need to write a guide on how to use the new wikiDone. * There's no WYSIWYG editor on this wiki but there will be one once we migrateThe LF hasn't installed a WYSIWYG editor yet but we can request it if there's a need. * Category links are not workingFixed. -- Martin Michlmayr Open Source Program Office, Hewlett-Packard _______________________________________________ Spdx mailing list Spdx@... https://lists.spdx.org/mailman/listinfo/spdx |
|
Re: Wiki migration: feedback required
Martin Michlmayr
* Martin Michlmayr <tbm@...> [2013-03-11 16:28]:
## Known IssuesStill a problem. In fact, the attachment extension is quite buggy, so I'd like to remove it. * Comments have not been migratedComments have been migrated in the meantime. * I need to write a guide on how to use the new wikiDone. * There's no WYSIWYG editor on this wiki but there will be one once we migrateThe LF hasn't installed a WYSIWYG editor yet but we can request it if there's a need. * Category links are not workingFixed. -- Martin Michlmayr Open Source Program Office, Hewlett-Packard |
|
Wiki migrated to MediaWiki
Martin Michlmayr
The wiki has been migrated to a proper wiki using MediaWiki. All
content (including past revisions) has been migrated. You can find the new wiki at http://wiki.spdx.org/view/ Here's a "Getting started" guide: http://wiki.spdx.org/view/Getting_started And a set of proposed wiki conventions, although they will have to be refined as we gain more experience with the new wiki: http://wiki.spdx.org/view/Wiki_Conventions If you have any questions, please let me know. -- Martin Michlmayr Open Source Program Office, Hewlett-Packard |
|
Hello
Edo Shor
Hi all, Um, my name is Edo Shor and I'm from the White Source R&D team. Thank you for all the efforts in putting together the SPDX spec. We believe it is a certain step towards a better, open sourced, world. We are currently working to support the spec in our service. Enjoy the upcoming conference (^_^) |
|
SPDX Bakeoff sign-up!
Lamons, Scott (Open Source Program Office) <scott.lamons@...>
Hi folks,
Please let us know if you plan to participate in the upcoming SPDX Bakeoff workgroup session by filling out the sign-up form.
Regards, Scott Lamons Kate Stewart |
|
SPDX General Meeting Minutes and Important Highlights
Philip Odence
Minutes of April 4 meeting: http://spdx.org/wiki/201344-minutes
HIGHLIGHTS:
UNO Presentation
License list Inclusion Guidelines (NEED FEEDBACK):
The Survey says…
Collab Summit- Hope to see everyone there.
|
|
Reminder Thursday SPDX General Meeting with Special Guest Star
Philip Odence
We will have a presentation from Matt Germonprez
from the University of Nebraska to discuss their work with SPDX and FOSSology.
We'll move thru the normal agenda quickly and then turn it over to Matt for about 30 mins. Matt will be using slides, so please plan on being on line. Here's the link.
Note, use the dial in below a per usual.
Linux Collaboration Summit
Meeting Time: Thursday, April 4, 8am PST / 10 am CST / 11am EST / 15: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 Administrative Agenda
Attendance
Approve Minutes-
Technical Team Report - Kate
Legal Team Report - Jilayne
Business Team Report – Jack/Scott
Cross Functional Issues –
Phil
Website Update – Jack
|
|
SPDX License List overview page
Jilayne Lovejoy <jilayne.lovejoy@...>
Hello all,
The SPDX Legal Team has been working on updating and improving the SPDX License List overview page, with the inclusion of some newly drafted guidelines on what criteria is considered for new licenses to be added to the License List. We have gone over
the text amongst the Legal Team, but felt it was important enough to get final approval from the general list. Discussions concerning this have occurred during the Legal Team conference calls over the last couple months, so please refer to the minutes if
you missed that or are interested in the evolution, in particular the notes from 10/31 and 11/13 found here: http://spdx.org/wiki/spdx/legal/minutes and 2/14 and 2/28 found here: http://spdx.org/wiki/meeting-minutes-and-decisions-legal-team
The draft is posted here: http://spdx.org/wiki/spdx-ll-overview-and-license-inclusion-guidelines-draft-review
Please review and if you have any substantive feedback, send it via email or bring up on the next general call on April 4th. We will finalize the draft on the next legal call on Thursday, April 11th, so any feedback needs to be received before then.
Cheers,
Jilayne Lovejoy
SPDX | Legal Team lead
OpenLogic, Inc. | Corporate Counsel
jlovejoy@... | 720
240 4545
|
|
Collab Summit SPDX Track
Lamons, Scott (Open Source Program Office) <scott.lamons@...>
SPDX Community,
Good news! We have secured a track for SPDX at the upcoming Linux Foundation Collaboration Summit. The schedule for both the Tuesday and Wednesday tracks is now posted and we hope you can join us. There are some really good presentations and working group sessions planed for both producers and consumers of SPDX. And if you are working on tools that support SPDX be sure to join us for the Wednesday afternoon SPDX Bakeoff.
Regards, Scott Lamons & Jack Manbeck SPDX Business Team
Kate Stewart SPDX Technical Team
Jilayne Lovejoy SPDX Legal Team
|
|
SPDX General Meeting Minutes, Collab Summit and Special News about next meeting
Philip Odence
Here are the minutes from the 3/7 http://spdx.org/wiki/201337-minutes
Linux Collaboration Summit
SPECIAL next General Meeting
Phil
L. Philip Odence
Vice President of Business Development
Black Duck Software, Inc.
8 New England Executive Park, Suite 211, Burlington MA 01803
Phone: 781.810.1819, Mobile: 781.258.9502
Skype: philip.odence
|
|
SPDX Technical team invites your participation!
Bill Schineller
Hello SPDX'ers:
Just a quick blast to the larger SPDX mailing list to update you on the goings-on of the Technical team and invite your participation.
For a while now SPDX 1.1 has been out in the field, and over the past 6 months or more the Tech team has been studying the areas of improvement to target for an SPDX 2.0 specification.
There have also been contributions to the set of tools around SPDX, which will be presented at the Linux Collaboration Summit next month.
Regarding SPDX 2.0 we received tremendous industry and open source community input in the form of Use Cases and conceptual model proposals. A big thanks to all who contributed their time and ideas to that exercise!
Those Use Cases have given us a valuable point of reference for the areas where the SPDX 1.1 model could be expanded to support greater adoption.
More recently we are transitioning from conceptual modeling discussions / proposals into concrete proposals and we would welcome your involvement.
An example of some proposals under consideration for 2.0:
- exactly how a 'later' SPDX document references earlier SPDX documents to reuse/add/subtract/amend data
- how to indicate Usage of individual files (as this may relate to obligations...)
- how to indicate that a binary was derived from sources (and therefore license discoveries/assertions about the source may apply to the binary)
- how to indicate that a snippet within a file is derived from another file and what licensing info applies to the snippet
If you would like to help steer the technical proposals and decisions, please feel free to chime in on the
spdx-tech@... mailing list and join our weekly concalls Tuesdays 2pm Eastern time.
See http://spdx.org/content/participation-guidelines-sign-0 for details
Thanks!
- Bill
Bill Schineller
Senior Director, KnowledgeBase
Black Duck Software, Inc.
8 New England Executive Park
Burlington, MA 01803
T: 781/425-4405
|
|
Re: Reminder: SPDX Tools Survey
Lamons, Scott (Open Source Program Office) <scott.lamons@...>
Just to add a little more incentive, this is a really good opportunity to get exposure for your SPDX tools as Gary is planning to highlight these tools as part of the Tooling up for SPDX session at the upcoming Linux Foundation Collaboration Summit. Kate and I would also like to extend an invite to join us for the Wednesday afternoon SPDX Bakeoff working session. The complete SPDX track is available here and we look forward to hopefully meeting and collaborating with many of you at the Summit.
Regards, Scott Lamons SPDX Business Team
From: spdx-bounces@... [mailto:spdx-bounces@...]
On Behalf Of Gary O'Neall
Sent: Sunday, March 10, 2013 12:04 PM To: spdx@... Subject: Reminder: SPDX Tools Survey
Just a reminder that the responses to the SPDX tools survey are due this Tuesday March 12. If you are aware of any tools which support SPDX, please fill out the following survey: https://docs.google.com/forms/d/1sdHIc0We0TTJD-r4O259cO40Tehd95rZcd6xdzvfUgM/viewform Thanks, Gary
------------------------------------------------- Gary O'Neall Principal Consultant Source Auditor Inc. Mobile: 408.805.0586 Email: gary@...
|
|
Wiki migration: feedback required
Martin Michlmayr
As part of our migration of the web site to the Linux Foundation, we
decided a few months ago to move the SPDX development area to a proper wiki (MediaWiki). This will make collaboration easier and offer some features that have been requested in the past. I've been working on migrating our existing content over to MediaWiki. I've finished this work and I'd like to invite feedback on the new wiki: http://sandbox.spdx.org/index.php/Main_Page It would be great if each team leader (with the help of volunteers) could look through their areas on the new wiki to check if all content has been migrated properly. I tested everything thoroughly but with around 380 pages I'm sure I made some mistakes (on the other hand, I also fixed some formatting issues I found on the current wiki). If you find any issues, please email me. Do *not* makes fixes on the wiki as this is just a temporary wiki. Since this wiki is just a temporary site, feel free to make changes in order to get familiar with MediaWiki. Here's a page explaining the MediaWiki syntax: <http://www.mediawiki.org/wiki/Help:Formatting> I will prepare a guide on how to use the new wiki before we migrate. If you make changes to the test wiki, make sure to inform other people who have volunteered to check the wiki, so your changes won't be reported as problems with the conversion. Until we migrate to the new wiki, you can still makes changes to the current wiki (i.e. nothing changes for now). I'll incorporate any changes into the new wiki before we migrate officially. Below are more details for those interest. Let me know if there are any questions. Martin ## What has been migrated * All wiki pages (about 380) including their history (past revisions) * All attachments from wiki pages * All users who made changes to the wiki (see below for a list) * No comments (I'll try to look into this later but this is low priority) ## Notes on the conversion * URLs: I changed all URLs to make them more wiki-like. I tried to use a scheme that makes sense but you can obviously disagree with my choice. The URL scheme uses sub pages to add a hierarchy (like we have on the current site). If the URL scheme doesn't make sense, let me know. * Past revisions: I performed the conversion in 2 steps: 1) for all historical revisions of a page, I imported the HTML as an exact copy -- this works fairly well but not 100% as MediaWiki doesn't accept all HTML tags (specifically, links). 2) The latest revision of each page has been converted to MediaWiki markup; as a result, the pages are cleaner, easier to edit and look more unified. * User names: I migrated existing user names (if the user made a wiki edit); if you'd like a more "wiki-style" user name (FirstLast is popular), let me know * File names: some files had _ in their file name; MediaWiki doesn't like this so I changed _ to - * HTML attachments: MediaWiki doesn't accept HTML attachments. I put the existing attachments in manually but you won't be able to upload HTML attachments in the future. This may impact the technical team. ## Known Issues * Attachments can only be downloaded when logged in * Comments have not been migrated * I need to write a guide on how to use the new wiki * There's no WYSIWYG editor on this wiki but there will be one once we migrate * Category links are not working ## Users that have been migrated Let me know if you're not listed here but think you should be. * Adam Cohn * Bruno Cornec * bschineller@... -> Bschineller [no @ allowed in MediaWiki user names] * Eaw * Fmunoz * Goneall * Grouss * Ibrahimhaddad * JNW * JackM * Jason Buttura * Jlovejoy * Jnweiger * K.stewart * Knewcomer * Kweins * Mclow * Mgisi * Mjherzog * Pezra * Phil * Phil_koltun * Pierre * Podence * Pombredanne * Rockett * Slamons * Stcroppe * tbm -> MartinMichlmayr -- Martin Michlmayr Open Source Program Office, Hewlett-Packard |
|