unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Guillaume Le Vaillant <glv@posteo.net>
Cc: 47943@debbugs.gnu.org, Sharlatan Hellseher <sharlatanus@gmail.com>
Subject: [bug#47943] [PATCH]: Gnu: Add Weir
Date: Thu, 22 Apr 2021 11:22:07 +0200	[thread overview]
Message-ID: <87fszifzcw.fsf@biscuolo.net> (raw)
In-Reply-To: <87tunyofo0.fsf@yamatai>

[-- Attachment #1: Type: text/plain, Size: 1687 bytes --]

Hi Guillaume,

thank you for your follow up and for your contribution to Guix!

Guillaume Le Vaillant <glv@posteo.net> writes:

> Giovanni Biscuolo <g@xelera.eu> skribis:

[...]

>> AFAIU the license in 1. means that that piece of code is not free
>> software, since "verbatim copy" AFAIU is not free
>>
>> The license in 2. AFAIU is free software, license:expat or other? Can
>> you clarify please?
>>
>> The code referenced in 3. is suggested by lispm in
>> https://gist.github.com/inconvergent/8b6ccfbde4fca7844c1962082ef07a7e
>> and AFAIU is not a trivial patch with no clear license: I really don't
>> know how this kind of code is normally evaluated from a GNU FSDG point
>> of view
>>
>> I think we need some guidance from someone more experienced in license
>> issues.

> I pushed the patch just before receiving your email about the possible
> license issue. Bad timing...

I saw your push some minutes after my message :-)

> I'm not a lawyer and I'm not sure what the final license of Weir is, so
> it would be nice if some license expert could give us their opinion on
> this. And in case there's a problem, I'll revert the patch.

I am almost sure that the licenses for the points 1 (license clearly
stated by Paul Graham) and 3 (no license for that code means "classic"
full copyright) are non-free.

Please do not forget that a reasonable copyright and license audit is
one of the things to do before committing, so please do not skip this
important step just IANAL ;-)

Please can you yust revert this patch and give us some time to settle
this issue?

Thanks! Giovanni

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

  reply	other threads:[~2021-04-22  9:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-21 21:38 [bug#47943] [PATCH]: Gnu: Add Weir Sharlatan Hellseher
2021-04-22  8:40 ` Giovanni Biscuolo
2021-04-22  9:02   ` Guillaume Le Vaillant
2021-04-22  9:22     ` Giovanni Biscuolo [this message]
2021-04-22 11:43       ` Guillaume Le Vaillant
2021-04-22 12:12         ` Guillaume Le Vaillant
2021-04-22 13:24           ` Giovanni Biscuolo
2021-04-26 13:24   ` [bug#47943] Weir licensing issue (was [PATCH]: Gnu: Add Weir) Giovanni Biscuolo
2021-04-22  8:43 ` bug#47943: [PATCH]: Gnu: Add Weir Guillaume Le Vaillant

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=87fszifzcw.fsf@biscuolo.net \
    --to=g@xelera.eu \
    --cc=47943@debbugs.gnu.org \
    --cc=glv@posteo.net \
    --cc=sharlatanus@gmail.com \
    /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).