From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: RFC - Gentoo on the Lab
Date: Mon, 22 Aug 2005 04:31:09 -0700 [thread overview]
Message-ID: <pan.2005.08.22.11.31.08.492258@cox.net> (raw)
In-Reply-To: 430947E3.1000201@gentoo.org
Donnie Berkholz posted <430947E3.1000201@gentoo.org>, excerpted below, on
Sun, 21 Aug 2005 20:34:59 -0700:
> Ricardo Loureiro wrote:
>
> | The final result of the project will be released to the community
> | (GPL or BSD, still need to think), so I'd love to ear from users
> | dealing with this kind of scenario, question, comments, whatever you
> | think I should focus on. Oh, a name for the project would be welcome
> | =)
>
> I strongly encourage you to release it under the same license as Portage
> is (GPL-2), so parts (or all) of it could be incorporated into Gentoo.
If I'm not mistaken (and I admit I could be, IANAL), BSD licensed
material, because the BSD license is a more permissive license with
generally few conditions, can be co-mingled in a GPL (2) project without
issue, and with the whole thing continuing to be GPL (2) licensed. I'm
not sure whether BSD markers must remain attached or not. In fact, I
believe it's fairly common for the kernel, for instance, to borrow BSD
code, and that said borrowed code doesn't have to be treated specially at
all (save for the traditional ACK of original source, but that's only
responsible origin tracing, certainly within the context of the SCOs of
the world).
Of course, the other possibility, if the permissiveness of BSD is desired,
would be a dual-license BSD/GPL. That clears up any possible conflicts
directly and immediately. OTOH, with portage itself already GPL2
licensed, I'm not sure I see much point in BSD licensing any portage
dependent new code, in any case, since it's dependent on GPL2 code anyway.
Still, the dual license certainly can't harm, and would likely be my
choice if I wanted the BSD permissiveness to apply to my code, under the
circumstances. (FWIW, I prefer GPL, so there's no question that's how I'd
license it if it were me, but it's not, so that doesn't count.)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-22 11:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 1:58 [gentoo-dev] RFC - Gentoo on the Lab Ricardo Loureiro
2005-08-22 2:12 ` Andrew Gaffney
2005-08-22 3:34 ` Donnie Berkholz
2005-08-22 10:05 ` Ivan Yosifov
2005-08-22 11:31 ` Duncan [this message]
2005-08-22 13:26 ` [gentoo-dev] " Ricardo Loureiro
2005-08-22 23:57 ` [gentoo-dev] " Duncan
2005-08-22 14:38 ` [gentoo-dev] " Marius Mauch
2005-08-22 15:35 ` Ricardo Loureiro
2005-08-22 16:57 ` Grobian
2005-08-22 17:49 ` Kristian Benoit
2005-08-22 20:39 ` Brian Harring
2005-08-23 16:25 ` Kristian Benoit
2005-08-23 17:22 ` Brian Harring
2005-08-23 17:27 ` Brian Harring
2005-08-23 22:58 ` Kristian Benoit
2005-08-25 0:50 ` [gentoo-dev] portage rewrite snapshot (was RFC - Gentoo on the Lab) Brian Harring
2005-08-23 16:45 ` [gentoo-dev] RFC - Gentoo on the Lab Ricardo Loureiro
2005-08-22 20:41 ` Stephen Bennett
2005-08-23 16:28 ` Kristian Benoit
2005-08-23 17:19 ` Brian Harring
2005-08-23 16:34 ` Ricardo Loureiro
2005-08-23 17:28 ` Marius Mauch
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=pan.2005.08.22.11.31.08.492258@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox