From: Alexis Ballier <aballier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Relicensing sys-freebsd/* under the BSD-2 license
Date: Fri, 30 Mar 2012 14:34:29 -0300 [thread overview]
Message-ID: <20120330143429.6e7a1856@gentoo.org> (raw)
In-Reply-To: <4F75E092.6020703@cs.stonybrook.edu>
On Fri, 30 Mar 2012 12:34:26 -0400
Richard Yao <ryao@cs.stonybrook.edu> wrote:
> I wrote sys-freebsd/virtio-kmod (bug 410199) while studying
> Gentoo/FreeBSD as part of an attempt to port gptzfsloader to Gentoo
> Linux. naota wrote an improvement that would be useful to send
> upstream. However, the GPL-2 license poses a problem according to
> conversations that I had in #gentoo-dev.
>
if he wrote the improvement, he can send it upstream under whatever
license he wants; generally, it is implicit that a patch follows the
same license as the code it applies to, esp. when the author himself
agrees to share it with upstream.
> While I have asked naota for permission to upstream the line he wrote,
> this poses a more general issue for collaboration, especially if I
> port more kernel modules from FreeBSD Ports.
>
> Would it be possible to relicense sys-freebsd/* under terms of the
> BSD-2 license?
>
what do you mean by 'relicense' ? for ebuilds, you'll have to ask
permission to all contributors to this area, and, afaik, the foundation
owns copyrights so it has a word to say too.
if you mean the 'LICENSE' field of ebuilds, then this is not the right
place to ask.
A.
next prev parent reply other threads:[~2012-03-30 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 16:34 [gentoo-dev] Relicensing sys-freebsd/* under the BSD-2 license Richard Yao
2012-03-30 17:34 ` Alexis Ballier [this message]
2012-03-30 17:52 ` Richard Yao
2012-03-30 18:00 ` Jon Portnoy
2012-03-30 18:15 ` Richard Yao
2012-03-30 18:05 ` Richard Yao
2012-03-30 18:47 ` Ulrich Mueller
2012-03-30 19:12 ` Rich Freeman
2012-03-30 19:38 ` Richard Yao
2012-03-30 19:36 ` Richard Yao
2012-03-30 20:19 ` Alec Warner
2012-03-30 21:47 ` Richard Yao
2012-03-30 21:10 ` Joshua Kinard
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=20120330143429.6e7a1856@gentoo.org \
--to=aballier@gentoo.org \
--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