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
Greetings SPDX Community,
We are pleased to announce that the penultimate version of the SPDX 2.0 Specification and the new SPDX License List are ready for community review. With 2.0 there have been great strides forwards in the expressiveness of an SPDX document through relationships and the license expression syntax.
There will be a general question and answer session on these at the March 12th General Meeting. Any comments regarding the material below should be submitted no later than March 23rd as directed below. We are hoping to finalize the material and officially release it at the April 2nd General Meeting. This should allow you plenty of time to do a thorough review.
Background Information
---------------------------------
For an overview of the 2.0 requirements you may read this http://wiki.spdx.org/images/SPDX-TR-2014-3.v1.0.pdf
The Use Cases are documented on the Technical team wiki athttp://wiki.spdx.org/view/Technical_Team/Use_Cases/2.0
For a presentation given at LinuxCollab in February 2015 on changes to the specification go here. It’s a nice overview.
http://spdx.org/sites/spdx/files/publications/SPDX%202.0%20Collab%202015%20Presentation.pptx
Specification Review Material
------------------------------------
SPDX 2.0 Specification, dated 20150303 is attached to this email as a PDF for your convenience. The same file is also available athttp://wiki.spdx.org/view/Technical_Team/SPDX_Specification_Versions
as SPDX-2.0rc3.pdf
The technical team would prefer comments were made in the google doc located athttps://docs.google.com/a/linaro.org/document/d/1wE_zvLU4c291ACi9wIJmQoE4ltKRW4rzM1TYiIvEVOs/edit#heading=h.x7jjfaxtluz1.
Comments may also be directed to the technical team mailing list at mailto: spdx-tech@... . You will need to be a member of the list to send an email.
The schema for the RDF can be found athttp://spdx.org/rdf/ontology/spdx-2-0-rev-12/ .
The model diagram can be found at http://wiki.spdx.org/view/Technical_Team/Model_2_0. The model is a great way to see how all the old and new pieces fit together.
Tools
-------
The tools for the 2.0 Specification are located in the SPDX GIT repository.
To try them, you will need to download the source and build them. You can access the repository here:http://git.spdx.org/?p=spdx-tools.git;a=snapshot;h=refs/heads/develop;sf=tgz
Instructions on building the tools can be found in the README.md file in the root directory of the source tree here: http://git.spdx.org/?p=spdx-tools.git;a=blob_plain;f=README.md;hb=5efe1f1e4727d7d7be48488225b68c65e71b84b9and here: http://spdx.org/publications/tool-documentation/how-to-use-the-software-package-document-exchange-spdx-tools
SPDX License List
-------------------------
The SPDX License List v2.0-rc3 and can be reviewed at http://spdx.org/licenses/preview/ . Due to the adoption of the License Expression Syntax, license exceptions have their own sub-list and some licenses have been deprecated. Information for all of this can be linked to from this page.
The master files for the license list can be found here: http://git.spdx.org/?p=license-list.git;a=summary
General information about the SPDX License List can be found here: http://spdx.org/spdx-license-list/license-list-overview
The Matching Guidelines can be found here:http://spdx.org/spdx-license-list/matching-guidelines
Feedback is welcome and can be sent to: spdx-legal@... . You will need to be a member of the list to send an email.
Best regards,
SPDX Technical, Legal and Business Teams
General Meeting/Minutes/2015-02-05
- Attendance: 5
- Lead by Phil Odence
- Minutes of January meeting approved
Contents
[hide]Biz Team Report - Jack[edit]
- Collab Summit
- Agenda set
- Tech Team will meet on Wed
- Friday afternoon meeting
- Jack will post
- Looking like 2.0 spec won’t be finalized
- Likely to be the subject for Friday afternoon
- Starting to gear up for another Google Summer of Code
Tech Team Report - Jack[edit]
- Some delay in finalizing due to last minute issues arising
- Has gotten very good detailed review by Tech Team
- 2.0 will go out for community review prior to Collab
Legal Team Report - Jilayne[edit]
- Beta LL list posted, feedback welcome
Cross Functional Topics - Phil[edit]
- Future Presentations for General Meeting
- TI would be happy to after Collab
- Would love to get other companies to share
Attendees[edit]
- Phil Odence, Black Duck
- Jack Manbeck, TI
- Hassib Khanafer, Protecode
- Pierre LaPointe, nexB
- Kirsten Newcomer, Black Duck
General Meeting/Minutes/2015-01-08
- Attendance: 6
- Lead by Phil Odence
- Minutes of December meeting approved
Cross Functional Issues – Phil[edit]
- Great Presentation from Bruno Grasset
- He opened and closed with thanks to everyone involved with SPDX for providing something so useful to the industry
- Valeo
- Supplier to Automotive Industry- Autonomous Cars, Connected Car, Intuitive Control
- Middle of complex supply chain
- Why they think SPDX is important
- Industry is “likes” standards, procedures, rules
- Have an explicit program to ensure respecting licenses and meeting obligations in all products
- Bruno is in charge of OSS compliance
- How they use
- License List
- Internal policy started with the SPDX list
- They use the SPDX license IDs in all of their documents and databases (including promoting publicly)
- And they check any licenses anyone supplies against our standard text
- Document Spec
- Prototyped use internally
- Have been looking for hierarchy, so 2.0 is important; evaluating in 2015
- License List
- Future Intent
- Large OEMs (car companies) are starting to require
- Customer requirements are making this a priority in 2015
- Will need to require from their own suppliers
- Integration with Yocto is critical
- Aiming for chain of trust, based on SPDX
- Questions
- When you evaluated SPDX, any features beyond hierarchy that they require?
- Not yet mature enough to completely evaluate
- How did you hear of? How can we promote?
- LinuxCon Europe session- Bruno came then promoted internally.
- He expects that in his space that SPDX will catch on quickly because of car makers requirements
- SPDX and Yocto- Is there only interest in Yocto integration or more general integration?
- Broader interest in integrating into process
- When you evaluated SPDX, any features beyond hierarchy that they require?
- Valeo
General Status - Phil[edit]
- On track for 2.0 release at CollabSummit
- Jack has been working hard to get a good agenda together
- We will be sharing a room with OpenChain so that folks can participate in both
- Looking forward to seeing everyone
Attendees[edit]
- Phil Odence, Black Duck
- Kirsten Newcomer, Black Duck
- Matt Germonprez, UNO
- Scott Sterling, Palamida
- Gary O’Neill, SourceA
- Bruno Grasset, Valeo
General Meeting/Minutes/2014-12-04
- Attendance: 6
- Lead by Phil Odence
- Minutes of Nov meeting approved
Contents
[hide]Cross Functional Issues – Phil[edit]
- Postponed presentation from Valeo to January 8
Biz Team Report - Phil[edit]
- Mostly focused on Collab Summit agenda
- Need to have rough agenda before holidays
- Coordinating with Open Chain who will share our room for 1/2 day
- Plugfest will likely take different form
- Anticipating tooling will not be fully in place
- More manual testing
- Discussion: Ideas for sessions
- SPDX 101 and 102 (the latter being update on 2.0)
- Update on License List
- 2.0 Tooling
Legal Team Report - Paul[edit]
- Beta LL list (targeting Dec 18) to include
- Continuing to add new licenses
- Deprecated licenses
- Exceptions list & some FAQs
- Templates
Tech Team Report - Scott[edit]
- Heads down reviewing 2.0 spec
- Cleaning up
- Adding/improving examples
- In pretty good shape
Attendees[edit]
- Phil Odence, Black Duck
- Paul Maddick, HP
- Mike Dolan, Linux Foundation
- Pierre LaPointe, nexB
- Scott Sterling, Palamida
- Mark Gisi, Wind River
When: Thursday, January 08, 2015 11:00 AM-12:00 PM. (UTC-05:00) Eastern Time (US & Canada) Where: Bridge info enclosed *~*~*~*~*~*~*~*~*~*
International dial-in number: (253) 336-6732
General Meeting/Minutes/2014-12-04
- Attendance: 6
- Lead by Phil Odence
- Minutes of Nov meeting approved
Contents
[hide]Cross Functional Issues – Phil[edit]
- Postponed presentation from Valeo to January 8
Biz Team Report - Phil[edit]
- Mostly focused on Collab Summit agenda
- Need to have rough agenda before holidays
- Coordinating with Open Chain who will share our room for 1/2 day
- Plugfest will likely take different form
- Anticipating tooling will not be fully in place
- More manual testing
- Discussion: Ideas for sessions
- SPDX 101 and 102 (the latter being update on 2.0)
- Update on License List
- 2.0 Tooling
Legal Team Report - Paul[edit]
- Beta LL list (targeting Dec 18) to include
- Continuing to add new licenses
- Deprecated licenses
- Exceptions list & some FAQs
- Templates
Tech Team Report - Scott[edit]
- Heads down reviewing 2.0 spec
- Cleaning up
- Adding/improving examples
- In pretty good shape
Attendees[edit]
- Phil Odence, Black Duck
- Paul Maddick, HP
- Mike Dolan, Linux Foundation
- Pierre LaPointe, nexB
- Scott Sterling, Palamida
- Mark Gisi, Wind River
Date: Wednesday, November 26, 2014 at 9:51 AM
To: "spdx@..." <spdx@...>
Subject: Re: Next week's SPDX General Meeting & Nov Meeting Minutes
Date: Wednesday, November 26, 2014 at 9:37 AM
To: "spdx@..." <spdx@...>
Subject: Next week's SPDX General Meeting & Nov Meeting Minutes
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
General Meeting/Minutes/2014-11-06
- Attendance: 15+
- Lead by Phil Odence
- Minutes of October meeting approved
Contents
[hide]Cross Functional Issues, Special Presentation from Polarsys – Phil[edit]
- Presentation from Polarsys COTSAQ project http://polarsys.org/proposals/cotsaq
- OSS tool for managing software BoMs
- SPDX connections
- First will use SPDX License List
- Connecting with code scanners through SPDX
Biz Team Report - Jack[edit]
- Last call cancelled. Call in an hour.
- Current focus is revamping the website homepage to guide new users
Legal Team Report - Jilayne[edit]
- Working through 2.0 task list
- Syncing with tech team schedule for release
- Cross team topic- Standard Header field in list that applies to a subset of licenses (e.g. GPL, Apache)
- Proposal is to remove the field as it becomes problematic with 2.0
- Notice will go out to tech team/legal team
Tech Team Report - Kate[edit]
- Fleshed out external SPDX document reference syntax. (currently sec 3.5, but may spin off to own section) and working on self reference (2.4)
- Finishing off clarifying examples for relationship references (sec 8)
- Extended the recognized checksums to include SHA256, MD5 (sec. 4.9, 6.4)
- Decided to start off separate spec for inline references rather than include it in Appendix.
- What's up for this month...
- Gluing it all together and making available for other reviewers
- Near term schedule: Draft Nov 14, feedback by Dec 1.
Attendees[edit]
- Phil Odence, Black Duck
- Kirsten Newcomer, Black Duck
- Pierre LaPonte, nexB
- Gary O’Neill, SourceA
- Mark Gisi, Wind River
- Scott Sterling, Palamida
- Matt Germonprez, UNO
- Jilayne Lovejoy, ARM
- Jack Manbeck, TI
- Mike Dolan, Linux Foundation
- Paul Maddick, HP
- Michael Herzog, nexB
- Pierre G, AirBus
- Others from project COTSAQ
Date: Wednesday, November 26, 2014 at 9:37 AM
To: "spdx@..." <spdx@...>
Subject: Next week's SPDX General Meeting & Nov Meeting Minutes
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
General Meeting/Minutes/2014-11-06
- Attendance: 15+
- Lead by Phil Odence
- Minutes of October meeting approved
Contents
[hide]Cross Functional Issues, Special Presentation from Polarsys – Phil[edit]
- Presentation from Polarsys COTSAQ project http://polarsys.org/proposals/cotsaq
- OSS tool for managing software BoMs
- SPDX connections
- First will use SPDX License List
- Connecting with code scanners through SPDX
Biz Team Report - Jack[edit]
- Last call cancelled. Call in an hour.
- Current focus is revamping the website homepage to guide new users
Legal Team Report - Jilayne[edit]
- Working through 2.0 task list
- Syncing with tech team schedule for release
- Cross team topic- Standard Header field in list that applies to a subset of licenses (e.g. GPL, Apache)
- Proposal is to remove the field as it becomes problematic with 2.0
- Notice will go out to tech team/legal team
Tech Team Report - Kate[edit]
- Fleshed out external SPDX document reference syntax. (currently sec 3.5, but may spin off to own section) and working on self reference (2.4)
- Finishing off clarifying examples for relationship references (sec 8)
- Extended the recognized checksums to include SHA256, MD5 (sec. 4.9, 6.4)
- Decided to start off separate spec for inline references rather than include it in Appendix.
- What's up for this month...
- Gluing it all together and making available for other reviewers
- Near term schedule: Draft Nov 14, feedback by Dec 1.
Attendees[edit]
- Phil Odence, Black Duck
- Kirsten Newcomer, Black Duck
- Pierre LaPonte, nexB
- Gary O’Neill, SourceA
- Mark Gisi, Wind River
- Scott Sterling, Palamida
- Matt Germonprez, UNO
- Jilayne Lovejoy, ARM
- Jack Manbeck, TI
- Mike Dolan, Linux Foundation
- Paul Maddick, HP
- Michael Herzog, nexB
- Pierre G, AirBus
- Others from project COTSAQ
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
General Meeting/Minutes/2014-11-06
- Attendance: 15+
- Lead by Phil Odence
- Minutes of October meeting approved
Contents
[hide]Cross Functional Issues, Special Presentation from Polarsys – Phil[edit]
- Presentation from Polarsys COTSAQ project http://polarsys.org/proposals/cotsaq
- OSS tool for managing software BoMs
- SPDX connections
- First will use SPDX License List
- Connecting with code scanners through SPDX
Biz Team Report - Jack[edit]
- Last call cancelled. Call in an hour.
- Current focus is revamping the website homepage to guide new users
Legal Team Report - Jilayne[edit]
- Working through 2.0 task list
- Syncing with tech team schedule for release
- Cross team topic- Standard Header field in list that applies to a subset of licenses (e.g. GPL, Apache)
- Proposal is to remove the field as it becomes problematic with 2.0
- Notice will go out to tech team/legal team
Tech Team Report - Kate[edit]
- Fleshed out external SPDX document reference syntax. (currently sec 3.5, but may spin off to own section) and working on self reference (2.4)
- Finishing off clarifying examples for relationship references (sec 8)
- Extended the recognized checksums to include SHA256, MD5 (sec. 4.9, 6.4)
- Decided to start off separate spec for inline references rather than include it in Appendix.
- What's up for this month...
- Gluing it all together and making available for other reviewers
- Near term schedule: Draft Nov 14, feedback by Dec 1.
Attendees[edit]
- Phil Odence, Black Duck
- Kirsten Newcomer, Black Duck
- Pierre LaPonte, nexB
- Gary O’Neill, SourceA
- Mark Gisi, Wind River
- Scott Sterling, Palamida
- Matt Germonprez, UNO
- Jilayne Lovejoy, ARM
- Jack Manbeck, TI
- Mike Dolan, Linux Foundation
- Paul Maddick, HP
- Michael Herzog, nexB
- Pierre G, AirBus
- Others from project COTSAQ
Sharing a blog post about my look into the open source compliance practice of the .NET core.
http://nunobrito1981.blogspot.com/2014/11/looking-into-net-license-compliance.html
The result is made available in SPDX format and posted on github.
With kind regards,
Nuno Brito
--
http://triplecheck.net
phone: +49 615 146 03187
From: Google Analytics <analytics-noreply@...>
Date: Wed, Nov 12, 2014 at 6:15 AM
Subject: You had 940 site visitors in October - see more with Google Analytics
To: spl518@...

|
I would like to announce an upcoming SPDX webinar on Tuesday November 11th @ 12pm PST - it will include a commercial case study on how SPDX data was used in the license compliance review process to deliver higher quality license data that also reduced the time and overall cost of the review.
Registration Link: http://www.omm.com/SnapshotFiles/54302027-c9b6-4403-968f-37baaeea7fd3/Subscriber.snapshot
- Mark
|
|
Portions of this communication may contain attorney advertising. Prior results do not guarantee a similar outcome. Please direct all inquiries regarding our conduct under New York's Code of Professional Responsibility to O’Melveny & Myers LLP, Times Square Tower, 7 Times Square, New York, NY, 10036, Phone:+1-212-326-2000. © 2014 O'Melveny & Myers LLP. All Rights Reserved. |
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
1. Go to https://airbusconferencing.webex.com/airbusconferencing/j.php?MTID=m3741610561a9bc8117624abe74f4b35e2. If requested, enter your name and email address.3. If a password is required, enter the meeting password: P0lar$ys4. Click "Join"
- Attendance: 7
- Lead by Phil Odence
- Minutes of Sept meeting approved
Contents
Cross Functional Issues – Phil
- 2.0 Schedule
- Proposed reset of phased release to be ratified by Tech Team - roughly:
- Release candidate targeted early Nov
- Presentations to and feedback for OpenChain group- Dec
- RC 2 January; tooling development in parallel
- Final Release at CollabSummit in Feb
- Proposed reset of phased release to be ratified by Tech Team - roughly:
Biz Team Report - Jack
- Website
- University Participation page is up
- Looking at Google Analytics
- Pointed to need to revamping front page to make it roll-based
- Continuing to look for improvements for website
- 2.0 Press Release on hold
Legal Team Report - Jilayne
- Call today agenda
- Focus is what’s needed for 2.0
- Need to work out license list release timing implications
- How do we have pre-release version of LL?
Tech Team Report - Kate
- No meeting this week
- Still cleaning up relationship types, license types
- Email discussion about new release schedule and approach.
Attendees
- Phil Odence, Black Duck
- Scott Sterling, Palamida
- Jack Manbeck, TI
- Pierre LaPonte, nexB
- Scott Lamons, HP
- Matt Germonprez, UNO
- Jilayne Lovejoy, ARM
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
Of course. Good thinking. (or, limited thinking on my part)Would be interested to hear if anyone has more details.
From: Kate Stewart <kate.stewart@...>
Reply-To: Kate Stewart <kate.stewart@...>
Date: Thu, 18 Sep 2014 06:44:14 -0700
To: Phil Odence <podence@...>, Nuno Brito <nuno.brito@...>, "spdx@..." <spdx@...>
Subject: Re: GitHub announces license selection in SPDX format
Hi Phil,I think that's just the drop down menu being shown (human readable), for selection.Key is what's being stored (which is probably the short form). But I'm just guessing here.
Hi Nuno,Thanks for flagging!
Kate
On Thursday, September 18, 2014 5:37 AM, Philip Odence <podence@...> wrote:
It¹s rewarding to see the keepers of such a popular platform tip their hat
to SPDX and to continue to encourage proactive license selection in
general. I/we pushed this hard with them several years ago and there
wasn¹t a lot of interest. I have to say, though, I¹m not sure what Mr.
Balter means by ³SPDX compliant.² They didn¹t go with the short names as
we had advocated, more like our long form names but abbreviated in some
cases (e.g. GNU GPL v2.0 vs. GNU General Public License v2.0). Still I
don¹t want to detract from the effort.
On 9/18/14, 5:26 AM, "Nuno Brito" <nuno.brito@...> wrote:
>Good morning,
>
>Some good news to start the day:
>https://twitter.com/BenBalter/status/512330244729344000/photo/1
>
>
>With kind regards,
>Nuno Brito
>
>--
>email: nuno.brito@...
>phone: +49 615 146 03187
>_______________________________________________
>Spdx mailing list
>Spdx@...
>https://lists.spdx.org/mailman/listinfo/spdx
_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx
_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx
Reply-To: Kate Stewart <kate.stewart@...>
Date: Thu, 18 Sep 2014 06:44:14 -0700
To: Phil Odence <podence@...>, Nuno Brito <nuno.brito@...>, "spdx@..." <spdx@...>
Subject: Re: GitHub announces license selection in SPDX format
to SPDX and to continue to encourage proactive license selection in
general. I/we pushed this hard with them several years ago and there
wasn¹t a lot of interest. I have to say, though, I¹m not sure what Mr.
Balter means by ³SPDX compliant.² They didn¹t go with the short names as
we had advocated, more like our long form names but abbreviated in some
cases (e.g. GNU GPL v2.0 vs. GNU General Public License v2.0). Still I
don¹t want to detract from the effort.
On 9/18/14, 5:26 AM, "Nuno Brito" <nuno.brito@...> wrote:
>Good morning,
>
>Some good news to start the day:
>https://twitter.com/BenBalter/status/512330244729344000/photo/1
>
>
>With kind regards,
>Nuno Brito
>
>--
>email: nuno.brito@...
>phone: +49 615 146 03187
>_______________________________________________
>Spdx mailing list
>Spdx@...
>https://lists.spdx.org/mailman/listinfo/spdx
_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx
to SPDX and to continue to encourage proactive license selection in
general. I/we pushed this hard with them several years ago and there
wasn¹t a lot of interest. I have to say, though, I¹m not sure what Mr.
Balter means by ³SPDX compliant.² They didn¹t go with the short names as
we had advocated, more like our long form names but abbreviated in some
cases (e.g. GNU GPL v2.0 vs. GNU General Public License v2.0). Still I
don¹t want to detract from the effort.
On 9/18/14, 5:26 AM, "Nuno Brito" <nuno.brito@...> wrote:
>Good morning,
>
>Some good news to start the day:
>https://twitter.com/BenBalter/status/512330244729344000/photo/1
>
>
>With kind regards,
>Nuno Brito
>
>--
>email: nuno.brito@...
>phone: +49 615 146 03187
>_______________________________________________
>Spdx mailing list
>Spdx@...
>https://lists.spdx.org/mailman/listinfo/spdx
_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx
to SPDX and to continue to encourage proactive license selection in
general. I/we pushed this hard with them several years ago and there
wasn¹t a lot of interest. I have to say, though, I¹m not sure what Mr.
Balter means by ³SPDX compliant.² They didn¹t go with the short names as
we had advocated, more like our long form names but abbreviated in some
cases (e.g. GNU GPL v2.0 vs. GNU General Public License v2.0). Still I
don¹t want to detract from the effort.
Good morning,
Some good news to start the day:
https://twitter.com/BenBalter/status/512330244729344000/photo/1
With kind regards,
Nuno Brito
--
email: nuno.brito@...
phone: +49 615 146 03187
_______________________________________________
Spdx mailing list
Spdx@...
https://lists.spdx.org/mailman/listinfo/spdx