From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: council@gentoo.org
Subject: Re: [gentoo-project] Call for agenda items - Council meeting 2019-10-13
Date: Sun, 29 Sep 2019 17:56:01 +0200 [thread overview]
Message-ID: <0a3d9d42d62fd2d9c126a97174d4582a110f213a.camel@gentoo.org> (raw)
In-Reply-To: <w6g7e5rl31d.fsf@kph.uni-mainz.de>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Sun, 2019-09-29 at 14:06 +0200, Ulrich Mueller wrote:
> In two weeks from now, the council will meet again. This is the time
> to raise and prepare items that the council should put on the agenda
> to discuss or vote on.
>
> Please respond to this message with agenda items. Do not hesitate to
> repeat your agenda item here with a pointer if you previously
> suggested one (since the last meeting).
>
I would like to request the Council to clarify/generalize their decision
from 2019-05-12 meeting regarding valid forms of activity for
a developer.
In this meeting, the Council confirmed that committing a proxy (without
direct commit access) is a suitable form of activity for an existing
developer not to be retired. I would like to ask whether the same form
of activity (i.e. high level of activity as a proxied maintainer) is
suitable for recruiting someone as non-commit access developer.
If yes, then I'd like to ask why Recruiters are rejecting such
a recruit, and requiring him to go through full procedure including
establishing commit access.
[1] https://projects.gentoo.org/council/meeting-logs/20190512-summary.txt
--
Best regards,
Michał Górny
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
prev parent reply other threads:[~2019-09-29 15:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-29 12:06 [gentoo-project] Call for agenda items - Council meeting 2019-10-13 Ulrich Mueller
2019-09-29 15:34 ` Michał Górny
2019-09-29 15:56 ` Michał Górny [this message]
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=0a3d9d42d62fd2d9c126a97174d4582a110f213a.camel@gentoo.org \
--to=mgorny@gentoo.org \
--cc=council@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