mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox <barebox@lists.infradead.org>,
	Frederik Van Slycken <frederik.van.slycken@gmail.com>,
	Robert Schwebel <robert@schwebel.de>
Subject: Re: picoTCP, barebox, and licenses
Date: Tue, 10 Jun 2014 04:33:05 +0800	[thread overview]
Message-ID: <8D47C8AE-9C6D-4A95-8062-1563942B3984@jcrosoft.com> (raw)
In-Reply-To: <20140606113723.88fac667196d249d600a49d4@gmail.com>


On Jun 6, 2014, at 3:37 PM, Antony Pavlov <antonynpavlov@gmail.com> wrote:

> 
> On Thu, 5 Jun 2014 21:48:10 +0200
> Frederik Van Slycken <frederik.van.slycken@gmail.com> wrote:
> 
>> 2014-06-05 21:36 GMT+02:00 Frederik Van Slycken
>> <frederik.van.slycken@gmail.com>:
>>> 2014-06-05 21:30 GMT+02:00 Robert Schwebel <robert@schwebel.de>:
>>>> Where is that in the wiki? IMHO it isn't correct, the toplevel COPYING
>>>> file says v2, which is also our intention.
>>> 
>>> http://wiki.barebox.org/doku.php#license
>>> 
>>> """
>>> This program is free software; you can redistribute it and/or
>>> modify it under the terms of the GNU General Public License as
>>> published by the Free Software Foundation; either version 2 of
>>> the License, or (at your option) any later version.
>>> """
>> 
>> A couple of other locations - I'm not sure if they're all up to date,
>> but these are results 3 and 4 when I do a google search for "barebox
>> license" :
>> http://www.barebox.org/documentation/barebox-2011.05.0/
>> http://www.barebox.org/documentation/barebox-2009.12.0/main.html
>> 
>> Number 2 was the wiki, already mentioned, and number 1 is wikipedia,
>> which does mention only gplv2 :)
> 
> I think Sascha can clarify this question.
> 
> AFAIR barebox itself is gplv2-only software, but we can add gplv2-or-later components into it.

For a legal point of view we do not care

Barebox is GPLv2 ONLY as it does contain quite a lot of file GPLv2 ONLY

and yes we DO can add GPLv2+ file into it

IIRC we already had this conversation on the ML before with Sascha & I over it and state that Barebox will be GPLv2 Only

It’s a statement for company that invest in Barebox that tomorrow the licence will not evolve
So they can have longterm plan with it (legal point of view)

Best Regards,
J.

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

  reply	other threads:[~2014-06-09 20:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-05 19:24 Frederik Van Slycken
2014-06-05 19:30 ` Robert Schwebel
2014-06-05 19:36   ` Frederik Van Slycken
2014-06-05 19:48     ` Frederik Van Slycken
2014-06-06  7:37       ` Antony Pavlov
2014-06-09 20:33         ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2014-06-07  3:18       ` Antony Pavlov

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=8D47C8AE-9C6D-4A95-8062-1563942B3984@jcrosoft.com \
    --to=plagnioj@jcrosoft.com \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.org \
    --cc=frederik.van.slycken@gmail.com \
    --cc=robert@schwebel.de \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox