public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2018-10-14
Date: Thu, 11 Oct 2018 19:29:57 +0200	[thread overview]
Message-ID: <w6gin28gzmy.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <20181011153139.7700484dc6c452ed570df66a@gentoo.org> (Andrew Savchenko's message of "Thu, 11 Oct 2018 15:31:39 +0300")

[-- Attachment #1: Type: text/plain, Size: 3186 bytes --]

>>>>> On Thu, 11 Oct 2018, Andrew Savchenko wrote:

> On Wed, 10 Oct 2018 09:43:52 +0200 Ulrich Mueller wrote:
>> The new copyright policy (GLEP 76) leaves it to projects to decide
>> whether they use the long form or the simplified form of the copyright
>> attribution. I would like to ask the council to decide that the
>> simplified attribution [1] shall be used for ebuilds in the Gentoo
>> repository.

> I'd like to voice strongly against this motion.

> Rationale:

> - We have out of the Gentoo repository ebuilds which may be
> incorporated in the main repository and are licensed properly but
> an author requires his copyright in the first line to be preserved.

The author's copyright will be preserved, regardless if he is listed in
a copyright line or not. It would even be preserved if there wasn't any
copyright notice at all.

The sole purpose of having a copyright notice is to protect us against
an "innocent infringement" defense under U.S. law. It really doesn't
matter much who is listed there (so we can list "Gentoo Authors" which
isn't even a legal entity), as long as we have a notice at all.

> GPL-2 allows us to use such ebuilds, but our past copyright policy
> mandating "Gentoo Foundation" doesn't, as well as proposed motion
> which mandates "Gentoo Authors" instead of the list of authors
> including main author if they require so.

It is virtually impossible to account for all authors of an ebuild,
and listing "Gentoo Authors" is only done because of practical
considerations (as I had outlined in the rationale). Also, please don't
confuse the copyright notice with an attribution of authorship.
The latter is achieved by the Git (or another VCS) commit information.
Again, this is already outlined in GLEP 76: "Projects using this scheme
[namely, 'Gentoo Authors'] must track authorship in a VCS".

> - GLEP 76 already did significant harm to our community by
> outlawing current anonymous or pseudonymous contributions. Moreover
> we have people who want to join community, but keep their identity
> hidden. This is understandable, especially for security or privacy
> oriented software. The harm should go no further. We have a lot of
> talks how we need more developers, but what we are doing in many
> steps including GLEP 76 is exactly the opposite: we are creating
> additional barriers due to vague and bureaucratic reasons.

How is that relevant for the proposal at hand?

> Of course if authors wants to use "Gentoo Authors" this should be
> allowed, especially for automatic migration from the "Gentoo
> Foundation" line. But we must preserve the right to use explicit
> list of authors (including "and others" if necessary) if a
> maintainer wants so.

Exactly. The aim of the "simplified attribution" policy is to simplify
modification of ebuilds, because contributors (whether Gentoo developers
or users) shouldn't have to think about the copyright line.

The purpose of the proposal explicitly is *not* to stop anybody from
adding an ebuild with a preexisting copyright notice. However, we should
make it clear that we strongly prefer the simplified form for ebuilds in
the Gentoo repository, entirely for practical reasons.

Ulrich

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2018-10-11 17:30 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-30 13:05 [gentoo-project] Call for agenda items - Council meeting 2018-10-14 Sergei Trofimovich
2018-10-10  7:43 ` Ulrich Mueller
2018-10-11 12:31   ` Andrew Savchenko
2018-10-11 15:12     ` Brian Dolbec
2018-10-11 17:49       ` Ulrich Mueller
2018-10-11 18:05         ` Rich Freeman
2018-10-11 17:03     ` Alec Warner
2018-10-11 17:35       ` Ulrich Mueller
2018-10-11 21:24         ` Andrew Savchenko
2018-10-12  0:09           ` Alec Warner
2018-10-12  0:24             ` Andrew Savchenko
2018-10-12  1:30               ` Sarah White
2018-10-12  6:05           ` Ulrich Mueller
2018-10-12 12:52             ` William Hubbs
2018-10-12 17:27               ` Ulrich Mueller
2018-10-12 17:44                 ` Rich Freeman
2018-10-13  3:32         ` desultory
2018-10-13  9:15           ` Ulrich Mueller
2018-10-14  9:24             ` Mart Raudsepp
2018-10-14 15:53               ` Ulrich Mueller
2018-10-14 17:08                 ` William Hubbs
2018-10-14 17:21                   ` Ulrich Mueller
2018-10-11 17:29     ` Ulrich Mueller [this message]
2018-10-11 21:09       ` Andrew Savchenko
2018-10-11 21:28         ` Rich Freeman
2018-10-12  1:25           ` Sarah White
2018-10-12  1:59             ` Rich Freeman
2018-10-12 11:34               ` Sarah White
2018-10-12 12:40                 ` Rich Freeman

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=w6gin28gzmy.fsf@kph.uni-mainz.de \
    --to=ulm@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