All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@openembedded.org
Subject: Core team (was: Switching SCM to git and commit/review policy)
Date: Tue, 15 Jul 2008 01:24:13 +0200	[thread overview]
Message-ID: <g5gn73$es4$1@ger.gmane.org> (raw)
In-Reply-To: <g5g7io$mu3$1@ger.gmane.org>

Dear OE core, dear fellow OE members,

Koen Kooi wrote:
> The core-team will set the policy, so there's no need to vote.

Well, after this dragged on for well over half a year now and things got
stalled several times this was not the kind of response I was expecting.
 But I'll gladly pick up the ball you passed here to ask a more general
question or raise a more general concern I've been having lately.

Quite frankly, as of late, when it comes to OE governance, I've been
uneasy a lot.  For one, there's this ominous group of OE core that does
a lot of things behind closed doors.  It is not completely clear when
and why it was established, why the communication is not open, who is a
member and how it relates to ordinary members of the community.  Is OE
still an open project?  Is anybody outside core just a little-valued
monkey from which we gladly take code but leave out of any kind of
steering decision?

I am sure everything is alright, but I think some clarifications are in
order.  Looking forward to it.

Regards

Rolf




  reply	other threads:[~2008-07-14 23:25 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-13  8:20 Switching SCM to git and commit/review policy Richard Purdie
2008-06-13 10:06 ` pHilipp Zabel
2008-06-13 12:43   ` Cliff Brake
2008-06-13 14:16     ` Koen Kooi
2008-06-16 16:35       ` Rolf Leggewie
2008-06-13 17:17     ` Otavio Salvador
2008-06-13 17:49     ` Tom Rini
2008-06-13 14:09   ` Koen Kooi
2008-06-13 16:25     ` pHilipp Zabel
2008-06-13 17:38       ` Koen Kooi
2008-06-13 18:38         ` Otavio Salvador
2008-06-13 19:37           ` Holger Freyther
2008-06-13 21:00             ` Otavio Salvador
2008-06-16 11:10               ` Rolf Leggewie
2008-06-16 13:16                 ` Otavio Salvador
2008-06-16 14:30                   ` Rolf Leggewie
2008-06-16 15:48                     ` Otavio Salvador
2008-06-16 16:27                       ` Rolf Leggewie
2008-06-16 17:03                         ` Otavio Salvador
2008-06-16 14:17               ` Rolf Leggewie
2008-06-16 22:42                 ` Florian Boor
2008-06-16 23:21                 ` Michael 'Mickey' Lauer
2008-06-16 13:09           ` Mark Brown
2008-06-17  9:51             ` Jan Lübbe
2008-06-24  9:57 ` Graeme Gregory
2008-06-24 14:01   ` Alain M.
2008-06-24 18:48     ` Leon Woestenberg
2008-06-24 20:13       ` Philip Balister
2008-06-24 18:33   ` Koen Kooi
2008-06-24 19:06     ` Tom Rini
2008-06-24 20:51       ` Florian Boor
2008-06-24 21:29         ` Tom Rini
2008-06-24 22:51           ` Leon Woestenberg
2008-06-25  1:22             ` Luís Vitório Cargnini
2008-07-14 12:22 ` Rolf Leggewie
2008-07-14 18:57   ` Koen Kooi
2008-07-14 23:24     ` Rolf Leggewie [this message]
2008-07-14 23:24     ` Core team (was: Switching SCM to git and commit/review policy) Rolf Leggewie
2008-07-15  9:45       ` Richard Purdie
2008-07-18 18:30         ` Shane Volpe

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='g5gn73$es4$1@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.