Re: License checking tool available

2017-08-04 Thread J Lovejoy
> Given there are bodies such as OSI and SPDX present, with presence on the > GitHub community, would the need for such a tool be mitigated if something > like the GPL—itself being copy written and arguably difficult to use > —be mitigated if

Re: License checking tool available

2017-08-04 Thread Josh Habdas
Errata: W3C and WHATWG operate in *a somewhat similar manner* On Sat, Aug 5, 2017 at 3:51 AM Josh Habdas wrote: > Given there are bodies such as OSI and SPDX present, with presence on the > GitHub community, would the need for such a tool be mitigated if something > like the

Re: License checking tool available

2017-08-04 Thread Josh Habdas
Given there are bodies such as OSI and SPDX present, with presence on the GitHub community, would the need for such a tool be mitigated if something like the GPL—itself being copy written and arguably difficult to use —be mitigated if each license

Re: License checking tool available

2017-08-04 Thread W. Trevor King
On Fri, Aug 04, 2017 at 02:53:05PM -0400, Richard Fontana wrote: > On Fri, Aug 04, 2017 at 11:44:45AM -0700, W. Trevor King wrote: > > The only difference that turned up in the license text is: > > > > Copyright [-©-]{+(C)+} 2007 Free Software Foundation, Inc. > > > > Our guideline for

RE: License checking tool available

2017-08-04 Thread gary
M > To: g...@sourceauditor.com > Cc: 'Michael Dolan'; 'Philippe Ombredanne'; 'SPDX-legal' > Subject: Re: License checking tool available > > On Fri, Aug 04, 2017 at 11:12:54AM -0700, Gary wrote: > > I feel we need another tool to compare text to a specific SPDX license > &

Re: License checking tool available

2017-08-04 Thread Richard Fontana
On Fri, Aug 04, 2017 at 11:44:45AM -0700, W. Trevor King wrote: [...] > The only difference that turned up in the license text is: > > Copyright [-©-]{+(C)+} 2007 Free Software Foundation, Inc. > > Our guideline for equating copyright symbols includes (c) but not (C) > [2]. Maybe that's

Re: License checking tool available

2017-08-04 Thread W. Trevor King
On Fri, Aug 04, 2017 at 11:12:54AM -0700, Gary wrote: > I feel we need another tool to compare text to a specific SPDX > license and indicate exactly where the 2 licenses do not match. Having this be part of the online tool would be great. But a quick-and-dirty way to accomplish this is to use

Re: License checking tool available

2017-08-04 Thread Brad Edmondson
Still, as a first effort I really like this. -- Brad Edmondson, *Esq.* 512-673-8782 | brad.edmond...@gmail.com On Fri, Aug 4, 2017 at 2:30 PM, Michael Dolan wrote: > > On Fri, Aug 4, 2017 at 2:12 PM, wrote: > >> When I tested the

Re: License checking tool available

2017-08-04 Thread Michael Dolan
On Fri, Aug 4, 2017 at 2:12 PM, wrote: > When I tested the application, I used the text from the SPDX license list > pages themselves which match. > That makes sense then. I also tried a copy/paste from the OSI pages and those didn't work either.

RE: License checking tool available

2017-08-04 Thread gary
] Sent: Friday, August 4, 2017 10:46 AM To: Philippe Ombredanne Cc: Gary O'Neall; SPDX-legal Subject: Re: License checking tool available Gary: I tried to paste the verbatim text of https://www.gnu.org/licenses/agpl.txt and its is not matched Do you think this a code or a matching

RE: License checking tool available

2017-08-04 Thread gary
l > Subject: Re: License checking tool available > > On Fri, Aug 4, 2017 at 6:46 PM, <g...@sourceauditor.com> wrote: > > An online tool for checking license text against the SPDX license list > > is now available at https://spdx.org/spdxweb The URL redirects to a >

Re: License checking tool available

2017-08-04 Thread Philippe Ombredanne
On Fri, Aug 4, 2017 at 7:14 PM, Alan Tse wrote: > Will there be an option to use fuzzy matching showing the differences? > While it’d be nice if licenses exactly matched, the concern would be if we > had something that almost completely matched. You mentioned other tools > that

Re: License checking tool available

2017-08-04 Thread Philippe Ombredanne
On Fri, Aug 4, 2017 at 6:46 PM, wrote: > An online tool for checking license text against the SPDX license list is > now available at https://spdx.org/spdxweb The URL redirects to a server > generously provided by the Openchain project team. > > The tool basically

RE: License checking tool available

2017-08-04 Thread Alan Tse
Awesome to hear. Is the source also at the github for spdx/tools? I took a brief look but didn't see it but admittedly didn't dig through all the files. Will there be an option to use fuzzy matching showing the differences? While it'd be nice if licenses exactly matched, the concern would be