From: Alex Griffin <a@ajgrf.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: License auditing
Date: Thu, 04 Aug 2016 09:40:51 -0500 [thread overview]
Message-ID: <1470321651.2999447.685989545.7F3461C9@webmail.messagingengine.com> (raw)
In-Reply-To: <87eg64vcjb.fsf@gnu.org>
On Thu, Aug 4, 2016, at 09:23 AM, Ludovic Courtès wrote:
> Strictly speaking it’s wrong, but I think it better reflects the intent
> of the authors (I think authors who throw a GPLv3 ‘COPYING’ file without
> bothering to add file headers probably think that GPLv3 and maybe later
> versions apply, but not previous versions.)
Ah, I guess that seems more reasonable when the whole situation is laid
out.
> I suppose many package violations could be detected using Guix, but
> you’re right that subtle cases like this one can go undetected.
>
> In the end, we’re talking about legal documents whose interpretation
> isn’t as formal as we would like. So I suspect that no single tool can
> provide what you want—there is no “license calculus”. Tools like
> Fossology go a long way, but AFAIK they are no substitute for proper
> manual auditing.
I know it can't and shouldn't be fully automated, but we can still build
useful tools to help us.
--
Alex Griffin
next prev parent reply other threads:[~2016-08-04 14:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 16:28 License auditing David Craven
2016-08-03 17:55 ` Danny Milosavljevic
2016-08-03 18:00 ` Jelle Licht
2016-08-03 18:05 ` Leo Famulari
2016-08-03 18:05 ` David Craven
2016-08-03 18:15 ` David Craven
2016-08-03 18:03 ` Leo Famulari
2016-08-03 20:42 ` Ludovic Courtès
2016-08-03 21:11 ` Alex Griffin
2016-08-03 22:59 ` David Craven
2016-08-04 14:23 ` Ludovic Courtès
2016-08-04 14:40 ` Alex Griffin [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-08-04 17:41 Philippe Ombredanne
2016-08-04 18:34 Philippe Ombredanne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1470321651.2999447.685989545.7F3461C9@webmail.messagingengine.com \
--to=a@ajgrf.com \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).