public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: ulm@gentoo.org, rich0@gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2018-10-14
Date: Sun, 14 Oct 2018 12:08:51 -0500	[thread overview]
Message-ID: <20181014170851.GA26234@linux1.home> (raw)
In-Reply-To: <w6g36t8frts.fsf@kph.uni-mainz.de>

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

On Sun, Oct 14, 2018 at 05:53:03PM +0200, Ulrich Mueller wrote:
> >>>>> On Sun, 14 Oct 2018, Mart Raudsepp wrote:
> 
> > If this is something to vote on in the meeting, lets have something we
> > can actually vote on before the meeting, please.
> > Can you come up with a wording of all this then that we can confidently
> > vote on, worded suitable for such, with the intentions clear in regards
> > to MUST/SHALL/SHOULD/MAY and whatnot? Maybe without referencing an
> > outside RFC to define what English words mean (or worse - using its
> > definitions without referencing it).
> 
> How about this motion:
> 
> The simplified form of the copyright attribution according to
> GLEP 76 [1], i.e., "Copyright YEARS Gentoo Authors", should be used
> for ebuilds and profile files in the Gentoo repository.

s/should be used/is preferred, but not required/

> Exceptionally, files carrying the long form of the copyright attribution
> ("Copyright YEARS MAIN-CONTRIBUTOR [OTHER-CONTRIBUTOR]... [and others]")
> can also be accepted, if there are valid reasons why the simplified
> attribution cannot be used.
 
 Remove this entire paragraph.

As rich0 said, there is no legal reason to mandate anything about the
copyright header.

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2018-10-14 17:08 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 [this message]
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=20181014170851.GA26234@linux1.home \
    --to=williamh@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=rich0@gentoo.org \
    --cc=ulm@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