From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: angstrom-distro-devel@linuxtogo.org
Cc: openembedded-devel@openembedded.org
Subject: Re: [Angstrom-devel] Angstrom Core Team
Date: Tue, 24 Jul 2007 16:29:16 +0200 [thread overview]
Message-ID: <200707241629.21404.openembedded@hrw.one.pl> (raw)
In-Reply-To: <1185226710.6148.133.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 3613 bytes --]
Dnia poniedziałek, 23 lipca 2007, Richard Purdie napisał:
> 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.
Losing developers is always harm. Losing valueable ones is even more harm.
> 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).
+1 from me
> 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.
When we will create core team we will need to create documentation team
which need to consist atleast one core developer and users interested in
writing documentation. It was working in last OpenZaurus releases so I
did not had to spend time on docs. Which method to use is what I would
leave for doc team. It can be drupal or any wiki as long as it allow to
protect pages from editing of people without proper rights. Personally I
do not care about which tool is used as long as it works and does not mix
with other projects.
> 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.
And there is also commercial way. As Todd Blumer wrote his company plans
to use Ångström on their devices - there are other companies which looks
at Ångström during work on own ones. We have a possibility to create one
good distro for all our devices/toys.
> 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.
Right - currently we have 4 distros in OE which use Ångström
configurations (FooNAS, MokoSlug, Mamona, amsdelta-oe) - they are more or
less same as our but use other names due to marketing (FooNAS, Mamona I
think). I hope that we can merge them one day so only names and some
images, tweaks will left from them.
> 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.
I as thinking about few other persons more:
- Mickeyl as one of Ångström founders and representant of commercial
distro (which has plans to merge with us)
- CoreDump - but some people will not agree and I think that he prefers to
work on getting distro working his way (I expect Hengtes distro release
after we release)
- Paul Sokolovski came to my mind too - he maintain many of our target
devices and spent lot of time to get OPIE working in our distro
--
JID: hrw-jabber.org
OpenEmbedded developer/consultant
42? 7 and a half million years and all you can come up with is 42?!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 196 bytes --]
next prev parent reply other threads:[~2007-07-24 14:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 21:38 Angstrom Core Team Richard Purdie
2007-07-24 8:20 ` [Angstrom-devel] " Graeme Gregory
2007-07-24 11:55 ` Dr. Michael Lauer
2007-07-24 12:23 ` Todd Blumer
2007-07-24 14:29 ` Marcin Juszkiewicz [this message]
2007-07-24 17:37 ` [Angstrom-devel] " 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=200707241629.21404.openembedded@hrw.one.pl \
--to=openembedded@hrw.one.pl \
--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 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.