From: Patrick McLean <chutzpah@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: converting copyright/license information in OpenRC
Date: Fri, 11 Dec 2015 14:16:30 -0800 [thread overview]
Message-ID: <20151211141630.618f4678@gentoo.org> (raw)
In-Reply-To: <20151211213748.GA31218@whubbs1.gaikai.biz>
On Fri, 11 Dec 2015 15:37:48 -0600
William Hubbs <williamh@gentoo.org> wrote:
> On Fri, Dec 11, 2015 at 09:04:47PM +0100, Ulrich Mueller wrote:
> > >>>>> On Fri, 11 Dec 2015, William Hubbs wrote:
> >
> Well, the OpenRC project is currently inconsistent about this, so the
> intention is to make it consistent.
>
> The .c/.h files have file-scope licenses, but that isn't true for
> everything in the project.
>
> I am willing to make the effort to do this, I was just wondering if
> there are any legal pitfalls I need to worry about.
>
> My theory is I can probably use git to find out who all of the authors
> are, and generate an Authors list from that information and from
> looking at copyright notices.
>
One concern about this is the possibility of copied code. If OpenRC
ever copied code from other BSD licensed projects, then dropping the
notice from the top of the file would be a violation of the upstream
license.
next prev parent reply other threads:[~2015-12-11 22:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 15:39 [gentoo-dev] converting copyright/license information in OpenRC William Hubbs
2015-12-11 20:04 ` [gentoo-dev] " Ulrich Mueller
2015-12-11 21:37 ` William Hubbs
2015-12-11 22:16 ` Patrick McLean [this message]
2015-12-12 17:43 ` William Hubbs
2015-12-15 5:05 ` Mike Frysinger
2015-12-15 15:31 ` William Hubbs
2015-12-15 19:24 ` Mike Frysinger
2015-12-15 19:37 ` William Hubbs
2015-12-15 19:48 ` Mike Frysinger
2015-12-16 11:43 ` Alexander Berntsen
2015-12-16 12:39 ` Rich Freeman
2015-12-16 13:54 ` Alexander Berntsen
2015-12-16 15:31 ` Rich Freeman
2015-12-16 16:48 ` William Hubbs
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=20151211141630.618f4678@gentoo.org \
--to=chutzpah@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