|
Re: SPDX recommendations from other communities! :-D
Philip Odence
Sorry, all, didn’t mean to cc the list. But you might find my blog amusing as well.
From: <spdx-bounces@...> on behalf of Philip Odence <podence@...>
Wow, Kate, great stuff! Thanks for sharing. I’ll talk to Jack about putting reference on the website.
In the meantime, for your amusement: http://blog.blackducksoftware.com/open-source-licenses-interesting
From: <spdx-bounces@...> on behalf of Kate Stewart <kstewart@...>
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 the source files, and generating a manifest from an SPDX document. :-)
Also there are a similar set of recommendations by the Commons Conservancy which also recommend use of the tags, and generation of SPDX documents:
Best regards, Kate
|
|
|
|
Re: SPDX recommendations from other communities! :-D
Philip Odence
Wow, Kate, great stuff! Thanks for sharing. I’ll talk to Jack about putting reference on the website.
In the meantime, for your amusement: http://blog.blackducksoftware.com/open-source-licenses-interesting
From: <spdx-bounces@...> on behalf of Kate Stewart <kstewart@...>
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 the source files, and generating a manifest from an SPDX document. :-)
Also there are a similar set of recommendations by the Commons Conservancy which also recommend use of the tags, and generation of SPDX documents:
Best regards, Kate
|
|
|
|
Re: SPDX recommendations from other communities! :-D
On Wed, Sep 6, 2017 at 8:47 AM, Kate Stewart
<kstewart@...> wrote: Hi,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 generate SPDX document. -- 真実はいつも一つ！/ Always, there's only one truth!
|
|
|
|
SPDX recommendations from other communities! :-D
Kate Stewart
Hi, Just thought some of you might be interested in some recent announcements with SPDX showing up in them. use of SPDX license identifiers in the source files, and generating a manifest from an SPDX document. :-) Also there are a similar set of recommendations by the Commons Conservancy which also recommend use of the tags, and generation of SPDX documents: Best regards, Kate
|
|
|
|
Thursday SPDX General Meeting Reminder
Philip Odence
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 License Coverage Grader tool. This tool takes an SPDX document and pointer to the original source files, and determine a "grade" to quantify how complete the licensing information is at the file level for the code represented by the SPDX document.
GENERAL MEETING
Meeting Time: Thurs, Sept 7, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
Join the call: https://www.uberconference.com/katestewart Optional dial in number: 877-297-7470 Alternate number: 512-910-4433 No PIN needed
Administrative Agenda Attendance Minutes Approval: https://wiki.spdx.org/view/General_Meeting/Minutes/2017-08-03
Guest Presentation – Krys
Technical Team Report – Kate/Gary
Legal Team Report – Jilayne
Business Team Report – Jack
Cross Functional Issues –All
Phil
BLACKDUCK
|
|
|
|
"License Clearance in Software Product Governance"
Kate Stewart
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.
Kate
|
|
|
|
SPDX Aug General Meeting Minutes
Philip Odence
Here are the minutes
https://wiki.spdx.org/view/General_Meeting/Minutes/2017-08-03
Phil
BLACKDUCK
General Meeting/Minutes/2017-08-03 < General Meeting | Minutes
Contents [hide]
Guest Presentation - Rohit[edit]
Tech Team Report - Kate/Gary[edit]
Legal Team Report - Jilayne/Paul[edit]
Outreach Team Report - Jack[edit]
Attendees[edit]
|
|
|
|
Reminder about SPDX General Meeting on Thursday with guest presenter.
Philip Odence
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 third year student pursuing B.E Computer Science at Birla Institute of Technology and Science, Pilani, India (BITS Pilani). I love developing websites and have a huge interest in Python.
GENERAL MEETING
Meeting Time: Thurs, Aug 3, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
Join the call: https://www.uberconference.com/katestewart Optional dial in number: 877-297-7470 Alternate number: 512-910-4433 No PIN needed
Administrative Agenda Attendance Minutes Approval https://wiki.spdx.org/view/General_Meeting/Minutes/2017-07-06
Guest Presentation – Rohit
Technical Team Report – Kate/Gary
Legal Team Report – Jilayne
Business Team Report – Jack
Cross Functional Issues –All
Phil
BLACKDUCK
|
|
|
|
Re: MarkDown conversion of specification live on SPDX GitHub
Die 12. 07. 17 et hora 15.25.22 scripsis:
@all: Got asked this a couple times – Why Gitbook and not an alternative[…] @Matjia: I should have been clearer in the limitation wording. Should haveThat 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 mind. If none of the ToC plugins work, we could try to modify one, or as a last resort, simply make the chapters hierarchy flat. What do you think? cheers, Matija -- gsm: tel:+386.41.849.552 www: http://matija.suklje.name xmpp: matija.suklje@... sip: sip:matija_suklje@...
|
|
|
|
Re: MarkDown conversion of specification live on SPDX GitHub
W. Trevor King
On Wed, Jul 12, 2017 at 03:25:22PM +0000, Steenbergen, Thomas wrote:
@Jack @Trevor: Yes, it’s possible to build multiple versions on theThis 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, [1,2]. Cheers, Trevor [1]: https://github.com/spdx/spdx-spec/blob/231b27009182d92d6ec06582c71ad307d10dc0a6/chapters/appendix-IV-SPDX-license-expressions.md#3-exception-with-operator [2]: https://github.com/spdx/spdx-spec/blame/231b27009182d92d6ec06582c71ad307d10dc0a6/chapters/appendix-IV-SPDX-license-expressions.md#L90 -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
|
|
|
|
Re: MarkDown conversion of specification live on SPDX GitHub
Thomas Steenbergen
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 I wanted to reduce the threshold for contributions. GitBook offered a defined format + structure, nice HTML output and a nice all-in-one solution including a WYSIWYG editor with GitHub upload (limited Git knowledge required). Could build this with PanDoc as well, have done so before but would have been more work and harder for others to maintain.
@Matjia: I should have been clearer in the limitation wording. Should have change “Simplified lay-out as MarkDown” to “Simplified lay-out as MarkDown and GitBook“ ToC simplification is because GitBook by default does not allow anchors in its ToC. I have tested several of the ToC plugins you link to but ones I tried either only worked in HTML or had issues. Will complete testing ToC plugins and ten pick one.
As part of fixing broken links I also inserting HTML anchors in MarkDown, hope I find the time to finish this change with next few days and push it to GitHub. My plan is to submit some pull requests to GitBook 4.x to fix some of the limitations I found.
@Jack @Trevor: Yes, it’s possible to build multiple versions on the gh-pages branch but uncommon way of working and think this may confuse users. Topic was discussed in yesterday’s technical meeting current agreement was to have official releases on spdx.org. I am thinking to extend current Gulp build script with 2 new tasks 1) a task to automate deployment of an official release to spdx.org 2) a task to deploy any new release tag to GitHub Releases
Regards,
Thomas Steenbergen Principal Engineer Open Source Governance and Policy
HERE Deutschland GmbH, Place of Business: Invalidenstraße 116, 10115 Berlin, Germany – Commercial Register: Amtsgericht Charlottenburg, HRB 106443B - USt-IdNr.: DE 812 845 193 - Managing Directors: Michael Bültmann, Robertus A.J. Houben
From:
<spdx-bounces@...> on behalf of Brad Edmondson <brad.edmondson@...>
+1 for continuous build (I think that's what gulp is), and it gives you linkable tags for free. Very nice.
On Mon, Jul 10, 2017 at 1:41 PM, W. Trevor King <wking@...> wrote:
|
|
|
|
Re: MarkDown conversion of specification live on SPDX GitHub
Brad Edmondson
+1 for continuous build (I think that's what gulp is), and it gives you linkable tags for free. Very nice.
On Mon, Jul 10, 2017 at 1:41 PM, W. Trevor King <wking@...> wrote: On Thu, Jul 06, 2017 at 02:38:24PM +0000, Manbeck, Jack via Spdx wrote:
|
|
|
|
Re: MarkDown conversion of specification live on SPDX GitHub
W. Trevor King
On Thu, Jul 06, 2017 at 02:38:24PM +0000, Manbeck, Jack via Spdx wrote:
I want to link to the HTML spec from the website. Is it possible toOnce 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 master build, https://spdx.github.io/spdx-spec/2.1.1-rc1/ would be a build of the 2.1.1-rc1 tag if/when that tag is made, https://spdx.github.io/spdx-spec/2.1.1/ would be abuild of the 2.1.1 release if/when that tag is made, etc. I'm happy to help with tooling for this if it sounds useful. Cheers, Trevor -- This email may be signed or encrypted with GnuPG (http://www.gnupg.org). For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
|
|
|
|
FW: Modeling Legal Text: A Tool Demonstration
Robin Gandhi
All,
toggle quoted messageShow quoted text
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 some. Phil
On 7/6/17, 4:15 PM, "Robin Gandhi" <rgandhi@...> wrote:
Webinar: Join the call: https://www.uberconference.com/robinagandhi Optional dial in number: 585-632-5623 PIN: 86451 **Best to join using a computer as I will using screen share for the demonstration.** When: Meeting Time: Thurs, July 13, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html Note: Hello all, Please consider attending this conference call to provide feedback on a method to model legal text and its use for compliance analysis. The discussion will demonstrate associated tool support and discuss related model semantics. Here is an abstract from a recent paper that our team authored: Modular Norm Models: A Frame-Semantic Approach Abstract— Norms in contractual agreements include claim-rights and corresponding duties. Analysis of norms expressed in voluminous legal text can benefit from the automation and traceability of logic-based models. Such norm models help reason about available rights and required duties based on the satisfiability of situations, a state-of-affair, in a given scenario. But model extraction from natural language needs subject matter expertise. Compliance reasoning in complex scenarios using large norm model networks is also difficult. We outline a novel method for modular norm model extraction and reasoning. For extraction, using the theory of frame-semantics we construct two foundational norm templates that cover Hohfeld’s concepts of claim-right and its jural correlative, duty. Template instantiations from legal text result in a re- peatable method for extraction of modular norm models. For reasoning, we introduce the notion of a super-situation. Super- situations contain other norm models. Compliance results from a modular norm are propagated to its containing super-situation, which in turn participates in other modular norms. This modularity allows on-demand incremental modeling and reasoning using simpler model primitives than previous approaches. We show our method on a variety of contractual statements in privacy and open source software domains. Here is the Github repository with some demonstration links: https://github.com/robinagandhi/modularnorms
|
|
|
|
SPDX July General Meeting Minutes
Philip Odence
Thanks to Anna for sharing he GSOC work.
General Meeting/Minutes/2017-07-06 < General Meeting | Minutes
Contents [hide]
Guest Presentation - Anna Buhman[edit]
Tech Team Report - Kate/Gary[edit]
Legal Team Report - Jilayne/Paul[edit]
Outreach Team Report - Jack[edit]
Attendees[edit]
|
|
|
|
Re: MarkDown conversion of specification live on SPDX GitHub
Manbeck, Jack
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
From: spdx-bounces@... [mailto:spdx-bounces@...]
On Behalf Of Steenbergen, Thomas
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
· Working on GitHub and using MarkDown should make it easier for people to contribute either via Git, editing files online or by filling issue · Specification now be build as HTML, PDF, ePUB or Mobipocket · HTML version is now mobile friendly and PDF has a table of contents · Every change on master branch is automatically build and deployed as HTML to https://spdx.github.io/spdx-spec/ (using Travis CI)
Limitations · Simplified lay-out as MarkDown has some limitations compared to Google Docs. See for example table of contents – no section included due not being able to directly link to sections within different chapters
To Do · Write CONTRIBUTING.md - explain to contributors how they can participate in shaping future version of the specification. Propose we discuss best workflow in the next call. · Minor issues - broken links, lay-out issues or spelling mistakes in original specification · Introduce workaround for MarkDown shortcomings in HTML version · Automate publishing of PDF, ePUB, Mobipocket to GitHub Releases for a new version of specification · Upgrade to GitBook 4.x when it becomes available
All fixes will be made on the development/2.1.1 branch. If you find something feel free to send me an email or raise an issue.
Regards,
Thomas Steenbergen Principal Engineer Open Source Governance and Policy
HERE Deutschland GmbH, Place of Business: Invalidenstraße 116, 10115 Berlin, Germany – Commercial Register: Amtsgericht Charlottenburg, HRB 106443B - USt-IdNr.: DE 812 845 193 - Managing Directors: Michael Bültmann, Robertus A.J. Houben
|
|
|
|
Re: MarkDown conversion of specification live on SPDX GitHub
Kate Stewart
Great work Thomas! Thank you very much for your efforts to get our current (and future) specifications into a more community friendly format! :-) Kate
On Mon, Jul 3, 2017 at 3:53 PM, Steenbergen, Thomas <thomas.steenbergen@...> wrote:
|
|
|
|
Re: MarkDown conversion of specification live on SPDX GitHub
Die 03. 07. 17 et hora 20.53.18 Steenbergen, Thomas scripsit:
Wanted to let you all know that after several months in the making I pushedBrilliant! Thank you. LimitationsToC with sections or subchapters of whatever depth should be doable and not an issue with MarkDown itself, but with whatever software generates the HTML/PDF/ePub/… from MarkDown. There seems to be several ToC plugins for GitBook: https://plugins.gitbook.com/browse?q=toc e.g. this one: https://plugins.gitbook.com/plugin/simple-page-toc has a `maxDepth` option, with which you can select how deep it should go. The default seems to be 3 levels (i.e. subsubsection). For in-sentence references this would probably work: https://stackoverflow.com/questions/5319754/cross-reference-named-anchor-in-markdown Potentially useful for footnotes as well: https://plugins.gitbook.com/plugin/footnote-string-to-number · Introduce workaround for MarkDown shortcomings in HTML versionAFAIK simply using HTML tags is always a workaround in MarkDown. cheers, Matija -- gsm: tel:+386.41.849.552 www: http://matija.suklje.name xmpp: matija.suklje@... sip: sip:matija_suklje@...
|
|
|
|
MarkDown conversion of specification live on SPDX GitHub
Thomas Steenbergen
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
· Working on GitHub and using MarkDown should make it easier for people to contribute either via Git, editing files online or by filling issue · Specification now be build as HTML, PDF, ePUB or Mobipocket · HTML version is now mobile friendly and PDF has a table of contents · Every change on master branch is automatically build and deployed as HTML to https://spdx.github.io/spdx-spec/ (using Travis CI)
Limitations · Simplified lay-out as MarkDown has some limitations compared to Google Docs. See for example table of contents – no section included due not being able to directly link to sections within different chapters
To Do · Write CONTRIBUTING.md - explain to contributors how they can participate in shaping future version of the specification. Propose we discuss best workflow in the next call. · Minor issues - broken links, lay-out issues or spelling mistakes in original specification · Introduce workaround for MarkDown shortcomings in HTML version · Automate publishing of PDF, ePUB, Mobipocket to GitHub Releases for a new version of specification · Upgrade to GitBook 4.x when it becomes available
All fixes will be made on the development/2.1.1 branch. If you find something feel free to send me an email or raise an issue.
Regards,
Thomas Steenbergen Principal Engineer Open Source Governance and Policy
HERE Deutschland GmbH, Place of Business: Invalidenstraße 116, 10115 Berlin, Germany – Commercial Register: Amtsgericht Charlottenburg, HRB 106443B - USt-IdNr.: DE 812 845 193 - Managing Directors: Michael Bültmann, Robertus A.J. Houben
|
|
|
|
July SPDX General Meeting Reminder
Philip Odence
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 undergrad as well. She will talk about her work with GitHub and SPDX. She is creating a facility which will automatically create and maintain an SPDX document along with any evolving GitHub project. Very exciting stuff!
GENERAL MEETING
Meeting Time: Thurs, July 6, 8am PDT / 10 am CDT / 11am EDT / 15:00 UTC. http://www.timeanddate.com/worldclock/converter.html
Join the call: https://www.uberconference.com/katestewart Optional dial in number: 877-297-7470 Alternate number: 512-910-4433 No PIN needed
Administrative Agenda Attendance Minutes Approval https://wiki.spdx.org/view/General_Meeting/Minutes/2017-06-01
Guest Presentation – Anna Buhman
Technical Team Report – Kate/Gary
Legal Team Report – Jilayne
Business Team Report – Jack
Cross Functional Issues –All
Phil
BLACKDUCK
|
|
|