public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@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 10:12:33 -0500	[thread overview]
Message-ID: <CAGfcS_nJVRFU2W+tY1_mK1DNP2KCPTaWEeRKYOidQO26GeWZdw@mail.gmail.com> (raw)
In-Reply-To: <54A2B5EA.1010403@gentoo.org>

On Tue, Dec 30, 2014 at 9:25 AM, hasufell <hasufell@gentoo.org> wrote:
> 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".
>

Keep in mind that rules don't exist to justify bad behavior, but to
promote good behavior.

I can guarantee that whatever rules come out of the council meeting
are going to have some loophole that somebody can point to in order to
justify their idiotic behavior.

We should be aiming for a GLEP that promotes a reasonable way for
projects to govern themselves without a lot of unnecessary
overhead/etc.  If somebody wants to contribute to a project and feels
that they can't, they should just ask for help.  I don't want to
burden every group in Gentoo that gets along just fine because some
projects aren't that way.

Really, though, it seems like the biggest complaint is AWOL project
leads or members.  I suggest that the simplest solution in such a case
is for somebody to step up and be bold.  Just send out an email to the
alias announcing that they added themselves to the alias (non-devs can
ask somebody to help out with that), call meetings to discuss things
that are important, and so on.  If not having an active person in
charge is detrimental then the team can just organize an election.
Leadership is more than titles.  FOSS tends to be do-acracy, so if
you're trying to do something you probably have more power than you
realize.

--
Rich


  reply	other threads:[~2014-12-30 15:12 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
2014-12-30 15:12           ` Rich Freeman [this message]
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=CAGfcS_nJVRFU2W+tY1_mK1DNP2KCPTaWEeRKYOidQO26GeWZdw@mail.gmail.com \
    --to=rich0@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