public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Patrick Lauer <bugs@dev.gentooexperimental.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project]  Re: Re: [gentoo-dev] Special meeting [WAS: Council meeting summary for 8 May 2008] (fwd)
Date: Mon, 19 May 2008 19:55:08 +0000	[thread overview]
Message-ID: <200805191955.08965.bugs@dev.gentooexperimental.org> (raw)
In-Reply-To: <20080519195024.3510ba2b@snowcone>

On Monday 19 May 2008 18:50:24 Ciaran McCreesh wrote:
> On Mon, 19 May 2008 19:25:14 +0100
>
> Steve Long <slong@rathaus.eclipse.co.uk> wrote:
> > No one here is arguing that we have a slacking Council, similar to
> > the "bad old days", are they?
>
> A Council that conveniently fails to turn up when discussing things
> that either don't interest them or that might make them look bad?
Looks like one person had an unexpectedly long travel, one person had 
connection issues and one person was never notified over a reliable channel.

So that looks to me like Mr. Murphy showing what he can do ... 
Shit happens, now let's make manure out of it so the plants can grow better 
next season.

I'd say that 
(1) the meeting was not agreed on nor announced on the regular channels
(2) a re-election would only confuse things and re-elect the same people
(3) the people involved have shown that they try their best to improve things. 
Trying to kick them at the first sign of human error would not send a good 
signal

My suggestion thus would be, if people insist, to have a vote of no 
confidence. If people really can't live with this small oops then so be it, 
otherwise it'll show that while there has been an oops it's not the end of 
the world. 

> A 
> Council holding secret meetings and conspiring with the devrel lead
> behind the rest of devrel's backs? A Council that simultaneously says
> "yes, we were behind musikc's actions" and "no, it was solely musikc's
> decision"? That's a lot like the old days.
A person not working on gentoo writing 35%+ of all emails on some 
mailinglists? Random insults and starting pointless flamewars?

Looks like the old day. I'm still waiting for the day when you leave 
University and don't have that much time to troll others.

Anyways, this is a debianistic discussion, only discussing things so that 
things will be discussed. I hope people don't waste too much time on politics 
and focus on improving things instead of dissing others and stroking their 
p... ego.
-- 
gentoo-project@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-05-20  7:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.0805191441040.31850@polylepis.inforead.com>
2008-05-19 17:08 ` [gentoo-project] Re: [gentoo-dev] Special meeting [WAS: Council meeting summary for 8 May 2008] (fwd) Ferris McCormick
2008-05-19 18:25   ` [gentoo-project] " Steve Long
2008-05-19 18:50     ` Ciaran McCreesh
2008-05-19 19:27       ` William L. Thomson Jr.
2008-05-19 19:37       ` Richard Freeman
2008-05-19 19:55       ` Patrick Lauer [this message]
2008-05-19 20:53       ` [gentoo-project] " Steve Long
2008-05-19 21:04         ` Ciaran McCreesh
2008-05-20 18:53           ` [gentoo-project] " Steve Long
2008-05-20 19:30             ` Ciaran McCreesh
2008-05-20 20:11               ` William L. Thomson Jr.

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=200805191955.08965.bugs@dev.gentooexperimental.org \
    --to=bugs@dev.gentooexperimental.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