From: Ulrich Mueller <ulm@gentoo.org>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting 2021-07-11 - call for agenda items
Date: Sun, 25 Jul 2021 19:22:39 +0200 [thread overview]
Message-ID: <ulf5u9ulc@gentoo.org> (raw)
In-Reply-To: <robbat2-20210708T175104-189941136Z@orbis-terrarum.net> (Robin H. Johnson's message of "Thu, 8 Jul 2021 17:51:54 +0000")
[-- Attachment #1: Type: text/plain, Size: 1477 bytes --]
>>>>> On Thu, 08 Jul 2021, Robin H Johnson wrote:
> On Thu, Jul 08, 2021 at 07:43:08PM +0200, Ulrich Mueller wrote:
>> >>>>> On Thu, 08 Jul 2021, Robin H Johnson wrote:
>>
>> > key:
>> > name of contributor and/or their associated unique email address
>> > (emails should not be duplicated in the keys)
>> > value:
>> > a list of entities who may own the copyright to parts of commits
>> > the developer has made
>> Can value be empty, if the contributor themself holds the copyright?
>> IIUC, YAML syntax would allow it.
> Yes, I feel that would be a valid entry.
> We'd just have to add an explicit ":" on the end of the lines we have
> right now.
As discussed in the meeting:
<@ulm> my impression is that this is not ready for a vote yet, because
there was no feedback from the entity listed in the AUTHORS file
<@dilfridge> this proposal is somewhat pointless if we do not have any
feedback from $CORPORATION people first
<@ulm> yes :)
<@gyakovlev> I have a feeling not enough discussion happened yet.
<@sam_> agreed
<@gyakovlev> especially with copyright holders in that file
<@ulm> let's postpone then
<@mgorny> do we want to assign someone from the Council to work on it?
<@dilfridge> so I suggest we ask robbat2 to obtain that feedback in
detail first
@robbat2: Could you try to get feedback from the currently listed
entities whether they are fine with the proposed change?
Ulrich
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]
next prev parent reply other threads:[~2021-07-25 17:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 9:20 [gentoo-project] Council meeting 2021-07-11 - call for agenda items Ulrich Mueller
2021-07-05 10:17 ` Ulrich Mueller
2021-07-05 10:19 ` Ulrich Mueller
2021-07-05 21:19 ` Aaron Bauman
2021-07-05 21:42 ` Ulrich Mueller
2021-07-05 21:53 ` Aaron Bauman
2021-07-06 7:02 ` Ulrich Mueller
2021-07-06 13:59 ` Thomas Deutschmann
2021-07-06 15:40 ` Ulrich Mueller
2021-07-06 17:42 ` Aaron Bauman
2021-07-06 17:55 ` Ulrich Mueller
2021-07-06 19:32 ` Rich Freeman
2021-07-07 13:45 ` Michał Górny
2021-07-07 1:59 ` Rich Freeman
2021-07-07 6:55 ` Sam Jorna (wraeth)
2021-07-07 11:25 ` Rich Freeman
2021-07-07 13:00 ` Sam Jorna (wraeth)
2021-07-07 11:40 ` Joonas Niilola
2021-07-07 11:51 ` Rich Freeman
2021-07-07 11:57 ` Ben Kohler
2021-07-07 13:41 ` Michał Górny
2021-07-07 20:38 ` Robin H. Johnson
2021-07-07 5:08 ` Robin H. Johnson
2021-07-07 9:27 ` Ulrich Mueller
2021-07-07 11:31 ` Rich Freeman
2021-07-07 20:28 ` Robin H. Johnson
2021-07-07 21:24 ` Rich Freeman
2021-07-08 16:57 ` Robin H. Johnson
2021-07-08 17:43 ` Ulrich Mueller
2021-07-08 17:51 ` Robin H. Johnson
2021-07-25 17:22 ` Ulrich Mueller [this message]
2021-07-08 17:43 ` Rich Freeman
2021-07-07 20:23 ` Robin H. Johnson
2021-07-07 23:00 ` Ulrich Mueller
2021-07-08 16:58 ` Robin H. Johnson
2021-07-08 15:44 ` [gentoo-project] Council meeting 2021-07-11 - agenda Ulrich Mueller
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=ulf5u9ulc@gentoo.org \
--to=ulm@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
--cc=robbat2@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