From: Richard Purdie <rpurdie@rpsys.net>
To: angstrom-distro-devel <angstrom-distro-devel@linuxtogo.org>
Cc: openembedded-devel <openembedded-devel@openembedded.org>
Subject: Angstrom Core Team
Date: Mon, 23 Jul 2007 22:38:30 +0100 [thread overview]
Message-ID: <1185226710.6148.133.camel@localhost.localdomain> (raw)
Hi Guys,
As people will note, Laibsch (Rolf) has been frustrated by politics and
personalities getting in the way of development and this is *bad*. I
don't think anyone wants this.
With this in mind I'd like to propose creating a formal core of Angstrom
developers similar to that which exists in OE (and has seemed to work
well as far as I know).
The core team is basically a group of developers who can collectively
guide the project. At the moment the leadership for Angstrom is unclear
and this would clarify that and mean that a solid structure is
established.
Whilst I can't really call myself an Angstrom developer exactly, I do
have a vested interest in seeing it become a success. Why is Angstrom
important? Most of the other handheld distributions in OpenEmbedded were
lining themselves up to work under the Angstrom banner. Familiar and
OpenZaurus are dead projects and all hopes for handhelds support from OE
now rest on Angstrom's shoulders. OE therefore has a vested interest in
Angstrom and this is one reason I want to see it succeed. I also think
it has massive potential if done correctly.
What I don't want is anyone feeling the need for yet-another-distro
which would be the next step is Angstrom's leadership cannot be made
clear. This leads to fragmentation which is bad.
So who should be on the core team? My thoughts are that Koen is an
obvious candidate. I'd propose Marcin/hrw (experience from OZ),
Graeme/XorA (developer/user) and Rod Whitby/rwhitby (to represent the
other non handhelds that Angstrom supports). I'd also propose inviting
Rolf/laibsch if he does consider coming back to the project.
Membership of the core team probably doesn't involve too much work, you
just need to care about the project, be involved with it in some way and
be prepared to make decisions now and again and make sure the project
agrees on a direction.
Thoughts, comments, suggestions and alternatives welcome.
I do think Angstrom needs some kind of formalised leadership though.
Cheers,
Richard
next reply other threads:[~2007-07-23 21:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 21:38 Richard Purdie [this message]
2007-07-24 8:20 ` [Angstrom-devel] Angstrom Core Team Graeme Gregory
2007-07-24 11:55 ` Dr. Michael Lauer
2007-07-24 12:23 ` Todd Blumer
2007-07-24 14:29 ` [Angstrom-devel] " Marcin Juszkiewicz
2007-07-24 17:37 ` Matthias Hentges
2007-07-24 19:25 ` Stelios Koroneos
2007-07-24 20:21 ` Koen Kooi
2007-07-25 14:51 ` Richard Purdie
2007-07-25 17:33 ` Cliff Brake
2007-07-25 10:32 ` Florian Boor
2007-07-24 21:00 ` Rod Whitby
2007-08-28 13:37 ` Todd Blumer
2007-08-28 13:48 ` [Angstrom-devel] " Koen Kooi
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=1185226710.6148.133.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=angstrom-distro-devel@linuxtogo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox