public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich@thefreemanclan.net>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Council meeting 2015-01-13: call for agenda items
Date: Mon, 29 Dec 2014 21:47:09 -0500	[thread overview]
Message-ID: <CAGfcS_m=9_z07wXWbU6e9uGKtAG=Je-a6xXWPU97DLHBG7pzow@mail.gmail.com> (raw)
In-Reply-To: <54A20C7E.80807@gentoo.org>

On Mon, Dec 29, 2014 at 9:22 PM, hasufell <hasufell@gentoo.org> wrote:
>
> No, you don't need a project lead. You can just say any member can speak
> for the whole project at any time. Whether that works or not, is a
> different thing, but it's a valid model.
> Decisions can be reached by whatever method you want, with or without a
> lead.
>
> What matters is that the project is _functional_ and _responsive_. How
> they do that should be up to the and should not be specified anywhere.
>

Well, as long as everybody agrees there is no need for rules.  The
rules come into play when people disagree.  Nobody is suggesting that
project members can't just speak for the project if that is how the
project wants to operate.  However, when there is disagreement then it
makes sense to allow an elected lead to step in, otherwise everybody
is just going to appeal to the council, which is after all intended to
be the escalation path for stuff projects can't handle on their own.
I'm sure the Council members don't want to be stepping into every
little debate, and I'm even more sure that everybody else doesn't want
that either.

I think some kind of standardization is useful just so that people
know how to engage projects.  However, if we want to have projects
specify their own engagement/escalation models I don't have a problem
with that.  Of course, if the project can't bother to elect a lead,
I'd be shocked if they actually reached a formal consensus on some
other governance model.

I don't think anybody wants to increase the level of formality.

--
Rich


  reply	other threads:[~2014-12-30  2:47 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 [this message]
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
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_m=9_z07wXWbU6e9uGKtAG=Je-a6xXWPU97DLHBG7pzow@mail.gmail.com' \
    --to=rich@thefreemanclan.net \
    --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