<kstewart@...> wrote: I'd like to point out that this recommendation is contingent on being able to automatically scan and generate it. No one is suggesting manual inventory of code to

Hi, Just thought some of you might be interested in some recent announcements with SPDX showing up in them. FSFE just launched a new site today recommending use of SPDX license identifiers in

Please join us for a special presentation by Krys Nuvadga an SPDX 2017 Google Summer of Code student participant. He is a student of the University of Buea, Cameroon. Krys is working on the

Just spotted a very nice reference to SPDX in Dirk Riehle's paper, and thought those on the list might find the paper interesting as well.

Here are the minutes https://wiki.spdx.org/view/General_Meeting/Minutes/2017-08-03 Phil BLACKDUCK L. Philip Odence VP/General Manager Black Duck On-Demand Black Duck Software, Inc. 800

Please join us for a special presentation by Rohit Lodha, another of our Google Summer of Code particpants. I’ll introduce Rohit and his project (on which he will upate us) in his own words: I a

Die 12. 07. 17 et hora 15.25.22 scripsis: […] That makes a lot of sense. And again, huge kudos for all the time you invested in this migration and above all with gathering more contributions in

This works. And for folks who want to pass references around and who do not need the GitBook additions, you can use GitHub's source browser and it's default Markdown rendering. For example,

Hi, Sorry did not find the time to reply to this thread earlier… @all: Got asked this a couple times – Why Gitbook and not an alternative like Pandoc? My choice in GitBook was driven since

+1 for continuous build (I think that's what gulp is), and it gives you linkable tags for free. Very nice. -- Brad Edmondson, Esq. 512-673-8782 | brad.edmondson@...

Once appoach to that would be having gulp build master and and all tags (that have Markdown content), instead of just building master. For example: https://spdx.github.io/spdx-spec/ would be the

All, I’m forwarding this on behalf of Robin from UNO. As you know, UNO has been highly supportive of SPDX. The research Robin is discussing is outside of the scope of SPDX, but may be of interest to

Thanks to Anna for sharing he GSOC work. General Meeting/Minutes/2017-07-06 < General Meeting‎ | Minutes Attendance: 12 Lead by Phil Odence Minutes of June meeting approved

Thomas, This is excellent work. I want to link to the HTML spec from the website. Is it possible to label the 2.1 version so only that shows up on a link? - Jack

Great work Thomas! Thank you very much for your efforts to get our current (and future) specifications into a more community friendly format! :-) Kate

Die 03. 07. 17 et hora 20.53.18 Steenbergen, Thomas scripsit: Brilliant! Thank you. ToC with sections or subchapters of whatever depth should be doable and not an issue with MarkDown itself, but

Hi all, Wanted to let you all know that after several months in the making I pushed my MarkDown conversion of the SPDX specification 2.1 to https://github.com/spdx/spdx-spec/ Benefits ·

Please join us for a special presentation from Ana Buhman, one of our Google Summer of student coders. Anna is in the CS master’s program and the University of Nebraska Omaha where she did her

General Meeting/Minutes/2017-06-01 < General Meeting‎ | Minutes Attendance: 9 Lead by Phil Odence Minutes of May meeting approved Contents [hide] 1 Tech Team Report - Kate/Gary 2 Legal Team

GENERAL MEETING Meeting Time: Thurs, May June 1, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html Conf call dial-in: Join the call: