The Holy Grail (of computing?)

[Mark Shelby]

I enjoyed reading the discussion regarding (in)activity with the
project. I have been watching the whole uClibc/buildroot project for
several years now. I have joined and exited the list a few times. I
recently got interested again in uClibc and figured I'd check out the
progress...

I am dismayed that it is still in a "pre 1.0" release stage!

So I thought I'd just throw out a few questions to anyone on the list
and see what kind of responses we get. Keep in mind, I am not a
developer, nor am I advocating drastic changes in uClibc. I just
wanted to throw out a few thought provoking questions.

I know that the *typical* answer is to go to www.uclibc.org and look
at the answers for myself, but I don't think I'ld get as complete an
answer as I will in discussing it here.

I'll first make a few assumptions. For purposes of discussion I am
going to consider a uClibc system as "Busybox / uClibc / buildroot" in
companionship or combined with one another. If you chose to single out
one aspect over another, please point out if you are addressing the
project as a whole, or one of the three aforementioned components.

1.) Who is the target audience for a uClibc system?

Seems to me that I read that the primary target is for the embedded
market. Does that still hold true? Or has the embedded market passed
on uClibc. Either way, I'm looking for some real in depth answers. not
just "Oh, anybody could use it," stuff.

2.) What other needs (niches) might the uClibc system meet? When
thinking of other applications for uClibc, why not rank them in order
of "coolness?" (Very subjective, I know!)

3.) How heavily is uClibc tied to GNU software?

4.) How does this project feel about the proposition of Mark
Shuttlesworth to engage in a predictable 6 month release cycle?

5.) What do mailing list participants for uClibc system feel is the
most crucial step(s) needing to be taken to maximize the usage or
stability of the uClibc System?

6.) What are the greatest 5 inherent strengths of the system? What are
it's 5 most glaring weaknesses?

7.) Is the system "developer friendly?" Why, or why not? If yes, what
can be done to encourage more participation? If no, what fundemental
things need to be changed?

8.) As far as "philosophies" go, would this project more closely align
itself with the Free Software Foundation group or the Linux Foundation
group? If you had to pick one or the other, that is...

9.) How do you use your uClibc system?

10.) How well does uClibc support your computing activities (scale of 1 to 10) ?