all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Frederick Muriithi <fredmanglis@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 3/4] gnu: Add python-paramunittest
Date: Sun, 26 Mar 2017 16:32:11 -0700	[thread overview]
Message-ID: <8737dzty10.fsf@gmail.com> (raw)
In-Reply-To: <CALjrZwZO1LqbezQB73bkwPFG322m7XDCLQDu0-PJ_uL_DCv_Qg@mail.gmail.com> (Frederick Muriithi's message of "Sun, 26 Mar 2017 18:47:00 +0300")

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

Frederick Muriithi <fredmanglis@gmail.com> writes:

> On Sun, Mar 26, 2017 at 6:12 PM, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
>> This package does not actually have an OSI approved license that I can
>> tell. We should contact the authors.
>>
>
> From PyPi (https://pypi.python.org/pypi/ParamUnittest/0.2) the license
> is indicated as BSD. I have also cloned the repository and looked at
> setup.py, where the license field is defined as:
>
>     'License :: OSI Approved :: BSD License'
>
> If this is not enough, I could start an Issue requesting a 'LICENSE'
> file be added.

Since the term "BSD License" is ambiguous it would be good to ask.  If
they mean the original BSD license, then this is free software, so it is
OK to add it, but it would also mean that the license is incompatible
with the GNU GPL.  It would be useful to know which license they mean.
The best way for them to do that is to include the text of the license
in the source tree.

https://www.gnu.org/licenses/license-list.html
https://www.gnu.org/licenses/bsd.html

-- 
Chris

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

  reply	other threads:[~2017-03-26 23:32 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-26  9:23 [PATCH 1/4] gnu: Add python-pytest-3.0.7 Muriithi Frederick Muriuki
2017-03-26  9:23 ` [PATCH 2/4] gnu: Add python-sphinx-1.5.2, python-sphinx-1.5.3 Muriithi Frederick Muriuki
2017-03-26 15:10   ` Pjotr Prins
2017-03-26 15:32     ` Frederick Muriithi
2017-03-26 16:40       ` Pjotr Prins
2017-03-27 19:10         ` Ricardo Wurmus
2017-03-27 15:11       ` Leo Famulari
2017-03-27 15:12         ` Leo Famulari
2017-03-28 20:03           ` Leo Famulari
2017-03-26  9:23 ` [PATCH 3/4] gnu: Add python-paramunittest Muriithi Frederick Muriuki
2017-03-26 15:12   ` Pjotr Prins
2017-03-26 15:47     ` Frederick Muriithi
2017-03-26 23:32       ` Chris Marusich [this message]
2017-03-27  2:41         ` Frederick Muriithi
2017-03-28  5:16           ` Frederick Muriithi
2017-03-28 19:25             ` Ludovic Courtès
2017-03-28 20:03   ` Leo Famulari
2017-03-26  9:23 ` [PATCH 4/4] gnu: Add python-mando Muriithi Frederick Muriuki
2017-03-26 15:16   ` Pjotr Prins
2017-03-27 15:14   ` Leo Famulari
2017-03-28 19:28     ` Ludovic Courtès
2017-03-28 20:04   ` Leo Famulari
2017-03-26 15:10 ` [PATCH 1/4] gnu: Add python-pytest-3.0.7 Pjotr Prins
     [not found]   ` <CALjrZwaRUvrctcwwFQ_5isqwoaaEq=77P2qFHwk1FL2mJ5T-dg@mail.gmail.com>
     [not found]     ` <CALjrZwaah9_Vv+MVTm2aiA_-WHycYhn=KCnk5KjsXo=8z0+QDA@mail.gmail.com>
2017-03-26 15:29       ` Frederick Muriithi
2017-03-27 15:09         ` Leo Famulari
2017-03-28 20:05           ` Leo Famulari
2017-03-28 20:04 ` Leo Famulari

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737dzty10.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=fredmanglis@gmail.com \
    --cc=guix-devel@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.