From: Raymond Jennings <shentino@gmail.com>
To: gentoo-project@lists.gentoo.org, chutzpah@gentoo.org
Subject: Re: [gentoo-project] rfc: copyright attribution clarifications
Date: Mon, 26 Nov 2018 16:05:58 -0800 [thread overview]
Message-ID: <CAGDaZ_pbrp07eqrVqqJaqv5ct1TYdLK-iHkxpnVSA_0xKXM7+A@mail.gmail.com> (raw)
In-Reply-To: <20181126231210.GA15590@whubbs1.gaikai.biz>
[-- Attachment #1: Type: text/plain, Size: 1758 bytes --]
My personal opinion is that rsync should eventually be retired for the tree.
On Mon, Nov 26, 2018 at 3:12 PM William Hubbs <williamh@gentoo.org> wrote:
> On Mon, Nov 26, 2018 at 09:20:52AM -0600, William Hubbs wrote:
> > On Sat, Nov 24, 2018 at 06:04:00PM -0800, Matt Turner wrote:
> > > On Sat, Nov 24, 2018 at 9:48 AM William Hubbs <williamh@gentoo.org>
> wrote:
> > >
> > > The GLEP says about the "Simplified Attribution":
> > >
> > > > Projects using this scheme must track authorship in a VCS, unless
> they list all authors of copyrightable contributions in an AUTHORS file.
> > >
> > > Would it be acceptable on your side to be listed in the AUTHORS file
> > > (which as far as I know has not been created yet)?
> >
> > I will get this answer today once I get to the office.
> >
> > There was also talk about adding a tag to commits that listed the
> > copyright holder for that commit but it never went anywhere. I would
> > propose something like:
> >
> > Copyright: <copyright notice>
>
> Putting the copyright notice in the commits might be the way to do this.
> If that's what we want, I suggest something like my example above.
>
> > > I'd be perfectly happy to ship an AUTHORS file in the ebuild repo that
> > > contains the names and emails of everyone and every company that has
> > > contributed to the repo.
> >
> > We probably should do this anyway and ship the AUTHORS file as part of
> > the rsync repository. You don't need it for the git repo since the
> > information is available via VCS.
>
> The AUTHORS file will contain AUTHORS, not copyright holders. Usually
> they are the same, but not always.
>
> So, I guess the question becomes, what do we want to do for Copyright
> holders in the the rsync repository?
>
> William
>
>
[-- Attachment #2: Type: text/html, Size: 2320 bytes --]
next prev parent reply other threads:[~2018-11-27 0:06 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 18:32 [gentoo-project] rfc: copyright attribution clarifications William Hubbs
2018-11-13 18:47 ` M. J. Everitt
2018-11-14 2:17 ` Rich Freeman
2018-11-14 2:46 ` William Hubbs
2018-11-14 7:18 ` Sarah White
2018-11-14 15:58 ` Rich Freeman
2018-11-14 19:38 ` Patrick McLean
2018-11-14 23:23 ` Rich Freeman
2018-11-15 0:00 ` Patrick McLean
2018-11-15 15:03 ` Rich Freeman
2018-11-15 15:28 ` William Hubbs
2018-11-15 15:52 ` Ian Stakenvicius
2018-11-14 8:24 ` Ulrich Mueller
2018-11-14 8:28 ` Raymond Jennings
2018-11-14 19:47 ` Patrick McLean
2018-11-14 20:09 ` Patrick McLean
2018-11-15 13:38 ` Thomas Deutschmann
2018-11-15 22:25 ` Kristian Fiskerstrand
2018-11-15 6:49 ` Ulrich Mueller
2018-11-15 15:35 ` William Hubbs
2018-11-15 17:50 ` Ulrich Mueller
2018-11-15 18:50 ` William Hubbs
2018-11-15 21:31 ` M. J. Everitt
2018-11-15 21:56 ` Andrew Savchenko
2018-11-16 9:16 ` Ulrich Mueller
2018-11-14 15:50 ` Rich Freeman
2018-11-14 14:45 ` Andrew Savchenko
2018-11-14 15:24 ` Rich Freeman
2018-11-14 15:53 ` Andrew Savchenko
2018-11-23 19:21 ` Sarah White
2018-11-23 19:46 ` Rich Freeman
2018-11-23 20:23 ` Sarah White
2018-11-23 20:25 ` Ian Stakenvicius
2018-11-23 20:40 ` Sarah White
2018-11-24 17:47 ` William Hubbs
2018-11-24 18:15 ` Sarah White
2018-11-24 19:41 ` Alec Warner
2018-11-24 20:12 ` Rich Freeman
2018-11-24 20:32 ` Alec Warner
2018-11-24 21:21 ` Rich Freeman
2018-11-26 12:01 ` Ulrich Mueller
2018-11-26 13:36 ` Alec Warner
2018-11-25 20:36 ` Matt Turner
2018-11-25 20:52 ` William Hubbs
2018-11-25 22:58 ` Rich Freeman
2018-11-24 23:11 ` Ulrich Mueller
2018-11-25 1:09 ` Sarah White
2018-11-25 1:37 ` Rich Freeman
2018-11-25 2:04 ` Sarah White
2018-11-25 2:22 ` Rich Freeman
2018-11-25 3:21 ` Sarah White
2018-11-25 6:53 ` Joonas Niilola
2018-11-25 2:04 ` Matt Turner
2018-11-26 15:20 ` William Hubbs
2018-11-26 23:12 ` William Hubbs
2018-11-27 0:05 ` Raymond Jennings [this message]
2018-11-27 2:38 ` Matt Turner
2018-11-27 4:51 ` William Hubbs
2018-11-27 6:20 ` Matt Turner
2018-11-23 20:42 ` Rich Freeman
2018-11-23 20:51 ` Sarah White
2018-11-23 21:11 ` Rich Freeman
2018-11-24 17:49 ` Sarah White
2018-11-23 20:57 ` Rich Freeman
2018-11-14 14:36 ` Andrew Savchenko
2018-11-14 15:31 ` Rich Freeman
2018-11-14 16:19 ` Andrew Savchenko
2018-11-14 18:59 ` Ian Stakenvicius
2018-11-14 19:38 ` William Hubbs
2018-11-14 20:02 ` Patrick McLean
2018-11-14 20:11 ` M. J. Everitt
2018-11-15 13:16 ` Thomas Deutschmann
2018-11-15 15:51 ` Brian Dolbec
2018-11-15 16:25 ` Thomas Deutschmann
2018-11-15 16:47 ` 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=CAGDaZ_pbrp07eqrVqqJaqv5ct1TYdLK-iHkxpnVSA_0xKXM7+A@mail.gmail.com \
--to=shentino@gmail.com \
--cc=chutzpah@gentoo.org \
--cc=gentoo-project@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