From: "Anthony G. Basile" <blueness@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Call for Agenda Items -- Council Meeting 2016-02-14
Date: Fri, 5 Feb 2016 07:22:34 -0500 [thread overview]
Message-ID: <56B4940A.8070607@gentoo.org> (raw)
In-Reply-To: <CAGfcS_nythqDc0eGkxraX_6icJtmig3oAH32kjVEfPmCyJ5FRw@mail.gmail.com>
On 2/5/16 7:13 AM, Rich Freeman wrote:
> On Fri, Feb 5, 2016 at 6:49 AM, Anthony G. Basile <blueness@gentoo.org> wrote:
>> 3a) if he says he is coming back, then do nothing
>> 3b) if he says he might come back or doesn't answer then maintainers can
>> adopt a package at will, making themselves first maintainer and hasufell
>> second. packages that are not adopted after some time can be moved to
>> maintainer needed
>> 3c) if he says he won't come back ever, period, full stop, then, as sad
>> as it is, its open season
>
> We can talk about a council email, but in general anybody can
> co-maintain anything in Gentoo without anybody's blessing.
I was thinking first maintainer so you get assigned the bug. But that's
a small point.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : blueness@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
next prev parent reply other threads:[~2016-02-05 12:22 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-25 20:58 [gentoo-project] Call for Agenda Items -- Council Meeting 2015-11-08 Kristian Fiskerstrand
2015-10-25 22:14 ` [gentoo-project] " Ulrich Mueller
2015-10-26 7:47 ` Kristian Fiskerstrand
2015-10-26 12:52 ` Rich Freeman
2015-10-26 13:32 ` Kristian Fiskerstrand
2015-10-27 19:11 ` hasufell
2015-10-27 19:22 ` Ciaran McCreesh
2015-10-27 19:29 ` hasufell
2015-11-29 15:36 ` [gentoo-project] Call for Agenda Items -- Council Meeting 2015-12-13 Kristian Fiskerstrand
2015-11-29 16:08 ` Ulrich Mueller
2015-11-29 16:16 ` Ulrich Mueller
2015-11-30 16:20 ` Michał Górny
2015-12-27 16:50 ` [gentoo-project] Call for Agenda Items -- Council Meeting 2016-01-10 Justin Lecher (jlec)
2015-12-27 18:03 ` Ulrich Mueller
2016-01-07 3:12 ` Daniel Campbell
2016-01-07 9:29 ` Ulrich Mueller
2015-12-29 19:45 ` Michał Górny
2016-02-01 19:25 ` [gentoo-project] Call for Agenda Items -- Council Meeting 2016-02-14 Justin Lecher (jlec)
2016-02-02 8:06 ` Dirkjan Ochtman
2016-02-02 14:18 ` Justin Lecher (jlec)
2016-02-03 20:46 ` Dirkjan Ochtman
2016-02-04 8:51 ` Justin Lecher (jlec)
2016-02-02 15:25 ` Michał Górny
2016-02-02 20:55 ` Robin H. Johnson
2016-02-02 21:11 ` Ulrich Mueller
2016-02-02 22:40 ` Robin H. Johnson
2016-02-03 0:53 ` Ulrich Mueller
2016-02-04 10:07 ` [gentoo-project] Re: [gentoo-dev-announce] " Anthony G. Basile
2016-02-05 7:49 ` Daniel Campbell
2016-02-05 8:01 ` Daniel Campbell
2016-02-05 11:49 ` Anthony G. Basile
2016-02-05 12:01 ` Alexander Berntsen
2016-02-05 12:13 ` Rich Freeman
2016-02-05 12:22 ` Anthony G. Basile [this message]
2016-02-05 19:00 ` Daniel Campbell (zlg)
2016-02-05 19:03 ` Daniel Campbell (zlg)
2016-02-05 19:24 ` Ciaran McCreesh
2016-02-05 20:45 ` Rich Freeman
2016-02-05 21:21 ` Andreas K. Huettel
2016-02-05 23:12 ` Alexander Berntsen
2016-02-07 9:04 ` Santiago Ferreira
2016-02-09 1:23 ` Ian Delaney
2016-02-07 11:15 ` [gentoo-project] " Andrew Savchenko
2016-02-12 22:22 ` Michał Górny
2016-02-12 22:34 ` Anthony G. Basile
2016-02-13 0:44 ` Andreas K. Huettel
2016-02-13 8:30 ` Michał Górny
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=56B4940A.8070607@gentoo.org \
--to=blueness@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