All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Schmidt <stefan@datenfreihafen.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] Koen Kooi : Revert "ecore: catch up with the	new SONAMEs; move to autosplitting"
Date: Tue, 28 Apr 2009 20:13:02 +0200	[thread overview]
Message-ID: <20090428181302.GA5449@excalibur.local> (raw)
In-Reply-To: <1240929710.30742.102.camel@mill.internal.reciva.com>

Hello.

On Tue, 2009-04-28 at 15:41, Phil Blundell wrote:
> On Sat, 2009-04-25 at 21:44 +0200, Michael 'Mickey' Lauer wrote:
> > Again the core team pretty much stood watching in apathy and let 
> > the most vocal decide on his own, letting him carry his own way again.
> 
> Also, I don't think that the external impression one gains of the core
> team is helped by the fact that its operations are somewhat opaque to
> non-members: there doesn't seem to be any public record of the decisions
> that the core team have made (if indeed it has made any) or the
> rationale for them.

I have to agree here. I even had to search the wiki for records who actually is
part of this team.

I seems that such discussions take place on the oe-private list. That is fine as
long as the issue needs to be addressed in a smaller circle until it came to a
conclusion. Still I miss a mail or similar once such a conclusion was done.

A trivial item was the new logo. An offer was posted to this very list that a
company was in favour of paying a designer for creating a logo. Great thing. The
next time I came in contact with this was as the new logo was used on the
website, wiki, etc. I was wondering what happened in between.

For such a trivial issue it was not even a needed to write a mail about it, but
it would have been nice to have a short report on what is/was going on. If a
coreteam of a project does not communicate what it is doing or plans to do it
leaves an aftertaste of missing transparency.

regards
Stefan Schmidt



  reply	other threads:[~2009-04-28 18:18 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090425075933.E6E18188456@amethyst.openembedded.net>
2009-04-25 11:04 ` [oe-commits] Koen Kooi : Revert "ecore: catch up with the new SONAMEs; move to autosplitting" Michael 'Mickey' Lauer
2009-04-25 13:32   ` Philip Balister
2009-04-25 13:40     ` Michael 'Mickey' Lauer
2009-04-25 18:17       ` Otavio Salvador
2009-04-25 18:27         ` Tom Rini
2009-04-25 18:51           ` Otavio Salvador
2009-04-25 19:00             ` Tom Rini
2009-04-25 19:03               ` Otavio Salvador
2009-04-25 18:34         ` Michael 'Mickey' Lauer
2009-04-25 18:44           ` Graeme Gregory
2009-04-25 19:44             ` Michael 'Mickey' Lauer
2009-04-25 20:01               ` Otavio Salvador
2009-04-25 20:13                 ` Michael 'Mickey' Lauer
2009-04-25 20:47               ` Marcin Juszkiewicz
2009-04-26  1:19                 ` Graeme Gregory
2009-04-26 12:09                   ` Philip Balister
2009-04-26  2:11                 ` Carsten Haitzler
2009-04-25 21:29               ` Marcin Juszkiewicz
2009-04-28 14:41               ` Phil Blundell
2009-04-28 18:13                 ` Stefan Schmidt [this message]
2009-04-29  8:12                   ` Marcin Juszkiewicz
2009-04-28 18:23                 ` Cliff Brake
2009-04-28 21:08                   ` Phil Blundell
2009-04-28 21:23                     ` Philip Balister
2009-04-28 21:26                     ` Philip Balister
2009-04-28 21:53                       ` Phil Blundell

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=20090428181302.GA5449@excalibur.local \
    --to=stefan@datenfreihafen.org \
    --cc=openembedded-devel@lists.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.