From: Andrew Savchenko <bircoph@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2018-10-14
Date: Fri, 12 Oct 2018 03:24:26 +0300 [thread overview]
Message-ID: <20181012032426.6570ebaeac0b96f6a19c5cee@gentoo.org> (raw)
In-Reply-To: <CAAr7Pr-S0wHgKRq0QWvHvKFkgAEkvdi86v0GgfwBWr+vP+edRw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1188 bytes --]
On Thu, 11 Oct 2018 20:09:39 -0400 Alec Warner wrote:
> On Thu, Oct 11, 2018 at 5:24 PM Andrew Savchenko <bircoph@gentoo.org> wrote:
>
> > On Thu, 11 Oct 2018 19:35:13 +0200 Ulrich Mueller wrote:
> > > >>>>> On Thu, 11 Oct 2018, Alec Warner wrote:
> > >
> > > > My reading of ulm's proposal is that it is allowed.
> > >
> > > > Ebuilds "shall" use the simple attribution, not that they "must" use
> > it.
> > >
> > > > To me that implies the simple attribution should be the default, but
> > the
> > > > complex attribution is acceptable in the ::gentoo repo.
> > >
> > > > Maybe I'm misunderstanding the proposal?
> > >
> > > No, you've understood it exactly how it was meant.
> >
> > Then please write this explicitly in the proposed change. Right now
> > it is only "shall" vs "must" difference which may confuse people
> > and create misunderstanding in future.
> >
>
> If we update the wording, are you happy with the proposal now that we have
> a shared understanding of its intent?
Yes, I'll be happy as long as alternate form (explicit authors list
with optional "and others") will be allowed with clear wording.
Best regards,
Andrew Savchenko
[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-10-12 0:24 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 [this message]
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=20181012032426.6570ebaeac0b96f6a19c5cee@gentoo.org \
--to=bircoph@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