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

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

Giovanni Biscuolo <g@xelera.eu> skribis:

> Hello Sharlatan,
>
> thank you very much for your patch, Weir and generative algorithms for
> art graphic production are very interesting
>
> We should check the overall license status of weir, see below
>
> [...]
>
> The license file
> https://github.com/inconvergent/weir/blob/master/LICENSE
>
> contains this:
>
> --8<---------------cut here---------------start------------->8---
>
> This code is released under the MIT license(see below). Unless otherwise noted.
>
> Most prominent exceptions are:
>
> 1. Some utilities from On Lisp by Paul Graham (in src/various.lisp). They are
>    bound by this notice:
>
> ---
> This code is copyright 1993 by Paul Graham, but anyone who wants
> to use the code in any nonprofit activity, or distribute free
> verbatim copies (including this notice), is encouraged to do so.
> ---
>
> 2. Some modified code by Victor Anyakin in (in src/auxiliary/dat.lisp):
>
> ---
> Copyright (c) 2013-2018 Victor Anyakin <anyakinvictor@yahoo.com>
> All rights reserved.
>
> Redistribution and use in source and binary forms, with or without
> modification, are permitted provided that the following conditions are met:
>     * Redistributions of source code must retain the above copyright
>       notice, this list of conditions and the following disclaimer.
>     * Redistributions in binary form must reproduce the above copyright
>       notice, this list of conditions and the following disclaimer in the
>       documentation and/or other materials provided with the distribution.
>     * Neither the name of the organization nor the
>       names of its contributors may be used to endorse or promote products
>       derived from this software without specific prior written permission.
>
> THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND
> ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO EVENT SHALL COPYRIGHT HOLDER BE LIABLE FOR ANY
> DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
> (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
> LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
> ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
> (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> ---
>
> 3. Some code suggested by @lispm (in src/auxiliary/dat.lisp, src/various.lisp). There
> are links to the original suggestions
>
> --8<---------------cut here---------------end--------------->8---
>
> 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.
>
> Thanks! Giovanni.

Hi Giovanni,

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

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.

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

  reply	other threads:[~2021-04-22  9:07 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 [this message]
2021-04-22  9:22     ` Giovanni Biscuolo
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=87tunyofo0.fsf@yamatai \
    --to=glv@posteo.net \
    --cc=47943@debbugs.gnu.org \
    --cc=g@xelera.eu \
    --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).