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:49:28 +0200	[thread overview]
Message-ID: <w6g4ldsgyqf.fsf@kph.uni-mainz.de> (raw)
In-Reply-To: <20181011081208.00646646@professor-x> (Brian Dolbec's message of "Thu, 11 Oct 2018 08:12:08 -0700")

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

>>>>> On Thu, 11 Oct 2018, Brian Dolbec wrote:

> My employer sponsors a lot of Gentoo ebuild and project work.  We are
> currently waiting for approval from the legal department to be able to
> continue after the Glep 76 approval and subsequent enforcement.  It
> very well may include a requirement to include a company copyright
> notice for the work done on comapny time and equipment.

> I have prepared a patch to repoman which fully implements Glep 76. [1]
> It adds a COPYRIGHT_OWNER variable to make.conf which can be set.
> The COPYRIGHT_OWNER is only ever ensured (possibly added) to the
> existing copyright line if the --copyright option is given on the cli.
> It is also used to generate a new copyright line if one did not exist.

As I've already commented in the pull request [1], I think this isn't
something that should be automated in a QA tool like repoman.

IMHO, repoman should accept both forms of the copyright notice, as long
as they're syntactically well-formed. Otherwise, it should leave the
copyright holder alone (with the possible exception of updating Gentoo
Foundation to Gentoo Authors).

> This option should only ever be used for significant changes to an
> ebuild.

Right, but I think there is the danger that the feature will be abused,
e.g. that people will use it also for non-copyrightable changes.

Also see my reply to bircoph's posting. The copyright notice has a
very specific purpose. It should neither be mistaken as an authors'
attribution, not should it be abused as a "scent mark".

> I could extend it to include a --others option to append the "and
> others" to the copyright. But I don't know if that will be used enough
> to justify the extra code.

> This patch also makes repoman more friendly for downstream repositiries
> which could set the copyright apropriately without manual editing.

> [1] https://github.com/gentoo/portage/pull/376

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

  reply	other threads:[~2018-10-11 17:49 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 [this message]
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
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=w6g4ldsgyqf.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