|
Question on two MIT-derivatives
Hi Christian: <christian.ehrhardt@...> wrote: I ran scancode-toolkit and the license in base64.c [1] is identified as an ISC alright. The only (IMHO not material) change is the sentence "mod
Hi Christian: <christian.ehrhardt@...> wrote: I ran scancode-toolkit and the license in base64.c [1] is identified as an ISC alright. The only (IMHO not material) change is the sentence "mod
|
By
Philippe Ombredanne
· #1420
·
|
|
SPDX June General Meeting Minutes
Dear Phil: Thank you for these minutes! I want to comment on the spec license topic. <phil.odence=synopsys.com@...> wrote: The governance updates make change, but I cannot fathom the benefi
Dear Phil: Thank you for these minutes! I want to comment on the spec license topic. <phil.odence=synopsys.com@...> wrote: The governance updates make change, but I cannot fathom the benefi
|
By
Philippe Ombredanne
· #1412
·
|
|
Using SPDX for Python packages license documentation
Dear Special People Doing eXceptional things: FYI, I have been working with the Python community to specify how Python package distributions can use SPDX license expressions for their Core metadata. T
Dear Special People Doing eXceptional things: FYI, I have been working with the Python community to specify how Python package distributions can use SPDX license expressions for their Core metadata. T
|
By
Philippe Ombredanne
· #1353
·
|
|
SPDX License List license inclusion guidelines
Hi Jilayne: On January 31st a compliance tooling meeting and hackathon took place in Brussels before FOSDEM [1]. One of the session topics was SPDX. Everyone there agreed that SPDX license inclusion c
Hi Jilayne: On January 31st a compliance tooling meeting and hackathon took place in Brussels before FOSDEM [1]. One of the session topics was SPDX. Everyone there agreed that SPDX license inclusion c
|
By
Philippe Ombredanne
· #1299
·
|
|
[ANNOUNCE] Open source license compliance tooling meeting and hackathon on January 31st 2020 pre-FOSDEM fringe event in Bruxelles, Belgium
If you care about open source compliance automation and if you are going to FOSDEM there is a one day hackathon and meeting taking place the day before FOSDEM on Friday January 31st as "fringe" event,
If you care about open source compliance automation and if you are going to FOSDEM there is a one day hackathon and meeting taking place the day before FOSDEM on Friday January 31st as "fringe" event,
|
By
Philippe Ombredanne
· #1284
·
|
|
Working with Python maintainers to adopt SPDX license expressions
All: I started working with the Python community to draft what we call a PEP (Python Enhancement Proposal) to adopt SPDX license expressions to document the license of Python packages. You can join th
All: I started working with the Python community to draft what we call a PEP (Python Enhancement Proposal) to adopt SPDX license expressions to document the license of Python packages. You can join th
|
By
Philippe Ombredanne
· #1257
·
|
|
Standalone license tools for scanning debian/ubuntu apps?
Hi Dan: You are asking a simple question for which is there is no simple answer: this is not yet a solved problem and there is no easy button to press. Hence the long answer. Since you are trying to f
Hi Dan: You are asking a simple question for which is there is no simple answer: this is not yet a solved problem and there is no easy button to press. Hence the long answer. Since you are trying to f
|
By
Philippe Ombredanne
· #1214
·
|
|
[PATCH] USB: add SPDX identifiers to all files in drivers/usb/
The MODULE_LICENSE macro used in the kernel is a clear license statement. And better than a terse "Copyright (c) John Doe, GPL" that is seen in the kernel since there is a clear documentation of its m
The MODULE_LICENSE macro used in the kernel is a clear license statement. And better than a terse "Copyright (c) John Doe, GPL" that is seen in the kernel since there is a clear documentation of its m
|
By
Philippe Ombredanne
· #1134
·
|
|
[PATCH] USB: add SPDX identifiers to all files in drivers/usb/
FYI: In case you missed it: SPDX identifiers have landed in kernel land... Read the whole thread at https://patchwork.kernel.org/patch/10016189/ And as a side effect, some new patches elsewhere are co
FYI: In case you missed it: SPDX identifiers have landed in kernel land... Read the whole thread at https://patchwork.kernel.org/patch/10016189/ And as a side effect, some new patches elsewhere are co
|
By
Philippe Ombredanne
· #1132
·
|
|
Thursday SPDX General Meeting
<podence@...> wrote: All: I have attached a PDF if you are only calling in
<podence@...> wrote: All: I have attached a PDF if you are only calling in
|
By
Philippe Ombredanne
· #1100
·
|
|
Today's SPDX General Meeting
<podence@...> wrote: If that's of interest to the group, I would be happy to present our efforts to build a better SPDX license mousetrap with the FOSS ScanCode toolkit that I mainta
<podence@...> wrote: If that's of interest to the group, I would be happy to present our efforts to build a better SPDX license mousetrap with the FOSS ScanCode toolkit that I mainta
|
By
Philippe Ombredanne
· #1092
·
|
|
[ANNOUNCE] SPDX has been accepted as a mentoring organization for the Google Summer of Code 2017
A good news came in yesterday: SPDX has been accepted as a mentoring organization for the Google Summer of Code 2017 thanks to Gary's hard work. I look forward to contribute as an admin and mentor! Se
A good news came in yesterday: SPDX has been accepted as a mentoring organization for the Google Summer of Code 2017 thanks to Gary's hard work. I look forward to contribute as an admin and mentor! Se
|
By
Philippe Ombredanne
· #1088
·
|
|
SPDX License List v2.4 released
Thank you Gary. That was quick!
Thank you Gary. That was quick!
|
By
Philippe Ombredanne
· #1042
·
|
|
SPDX License List v2.4 released
Excellent! Note that none of the generated files are valid HTML. See http://spdx.org/licenses/Glide for instance With the .html extension, the browsers deal with the quirks somehow: http://spdx.org/li
Excellent! Note that none of the generated files are valid HTML. See http://spdx.org/licenses/Glide for instance With the .html extension, the browsers deal with the quirks somehow: http://spdx.org/li
|
By
Philippe Ombredanne
· #1038
·
|
|
Using SPDX for firmware
Very nice! About the dead link, I am not sure exceptions have been published yet, though it could be a bug too. IMHO using your own ID extensions is quite fine, there is nothing upsetting about it, es
Very nice! About the dead link, I am not sure exceptions have been published yet, though it could be a bug too. IMHO using your own ID extensions is quite fine, there is nothing upsetting about it, es
|
By
Philippe Ombredanne
· #996
·
|
|
Proposed spec for external packages
<ybronshteyn@...> wrote: Yev: I guess you meant External and not Eternal.... I provided a few comments to your proposed spec in the doc at https://docs.google.com/document/d/1WfArS8_
<ybronshteyn@...> wrote: Yev: I guess you meant External and not Eternal.... I provided a few comments to your proposed spec in the doc at https://docs.google.com/document/d/1WfArS8_
|
By
Philippe Ombredanne
· #976
·
|
|
License List v1.6 - uploaded
Thanks! imho we should have support for both GPL and LGPL there. Note that I think that the + there is misleading. its means "or later" elsewhere and here it means "any version". I would rather go wit
Thanks! imho we should have support for both GPL and LGPL there. Note that I think that the + there is misleading. its means "or later" elsewhere and here it means "any version". I would rather go wit
|
By
Philippe Ombredanne
· #312
·
|
|
License templates
Peter: my 2 cents: the idea is good, though we should not reinvent a license templates syntax when the OSI has alreday done something. They use angle brackets so I would suggest using the same, not sq
Peter: my 2 cents: the idea is good, though we should not reinvent a license templates syntax when the OSI has alreday done something. They use angle brackets so I would suggest using the same, not sq
|
By
Philippe Ombredanne
· #129
·
|
|
HTML Spec page weird look on spdx.org
All: this is most likely a known problem, but the draft web page for the spec at http://www.spdx.org/wiki/spdx/specification seems to be quite hard to read (many empty lines), the paragraph numbers ar
All: this is most likely a known problem, but the draft web page for the spec at http://www.spdx.org/wiki/spdx/specification seems to be quite hard to read (many empty lines), the paragraph numbers ar
|
By
Philippe Ombredanne
· #104
·
|
|
launchpad.net RDF
All: as discussed during today's call here are some pointers to Launchpad RDF: This is an example of a project page: https://launchpad.net/do and the matching RDF metadata: https://launchpad.net/do/+r
All: as discussed during today's call here are some pointers to Launchpad RDF: This is an example of a project page: https://launchpad.net/do and the matching RDF metadata: https://launchpad.net/do/+r
|
By
Philippe Ombredanne
· #100
·
|