From: hasufell <hasufell@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting 2015-01-13: call for agenda items
Date: Tue, 30 Dec 2014 14:25:46 +0000 [thread overview]
Message-ID: <54A2B5EA.1010403@gentoo.org> (raw)
In-Reply-To: <54A23154.8010007@gentoo.org>
Dean Stephens:
> On 12/29/14 15:06, Rich Freeman wrote:
>> I'll certainly agree that not everything needs a formal project.
>> However, if a project wants to have authority/autonomy beyond
>> anything-goes, then it should welcome members and elect a lead
>> regularly.
>>
> There is at least a defensible argument to be made that being able to
> reject applicants is more important to being able to maintain a coherent
> project than the often indicated duty to accept anyone who shows interest.
>
What about projects that don't even reject, but rather ignore
devs/contributors?
We tell them to elect a new lead, so we don't have to deal with the
people who screwed up, but can say "here, they formally are a functional
project according to a random glep... problem solved".
next prev parent reply other threads:[~2014-12-30 14:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-27 12:34 [gentoo-project] Council meeting 2015-01-13: call for agenda items Andreas K. Huettel
2014-12-28 11:43 ` Anthony G. Basile
2014-12-28 11:57 ` Michał Górny
2014-12-28 16:45 ` Andreas K. Huettel
2014-12-28 16:54 ` Michał Górny
2014-12-29 0:02 ` Patrick Lauer
2014-12-29 20:57 ` Matthew Thode
2014-12-29 21:44 ` Andreas K. Huettel
2014-12-30 0:18 ` Alex Legler
2014-12-30 14:20 ` Anthony G. Basile
2014-12-30 15:05 ` Rich Freeman
2014-12-30 16:18 ` Anthony G. Basile
2014-12-30 4:59 ` Dean Stephens
2014-12-29 19:34 ` hasufell
2014-12-29 20:06 ` Rich Freeman
2014-12-29 21:02 ` Matthew Thode
2014-12-30 2:22 ` hasufell
2014-12-30 2:47 ` Rich Freeman
2014-12-30 5:00 ` Dean Stephens
2014-12-30 8:28 ` Ciaran McCreesh
2014-12-30 11:31 ` Rich Freeman
2014-12-30 14:25 ` hasufell [this message]
2014-12-30 15:12 ` Rich Freeman
2014-12-30 20:51 ` hasufell
2014-12-31 4:19 ` Dean Stephens
2015-01-04 23:27 ` hasufell
2015-01-05 4:38 ` Dean Stephens
2015-01-05 14:06 ` hasufell
2015-01-06 4:25 ` Dean Stephens
2015-01-07 13:03 ` Rich Freeman
2015-01-07 16:30 ` William Hubbs
2015-01-07 17:45 ` Rich Freeman
2015-01-07 19:35 ` William Hubbs
2015-01-07 21:21 ` Andrew Savchenko
2015-01-08 15:05 ` William Hubbs
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=54A2B5EA.1010403@gentoo.org \
--to=hasufell@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