[BusyBox] busybox development status?

[Erik Andersen]

On Thu Apr 14, 2005 at 09:05:21AM -0400, Paul Fox wrote:
>  
> erik -- can you comment on the current state-of-the-project for
> busybox?
> 
> even allowing for the implementation of the slick new bug system,
> and the slick new svn repository (both big, distracting jobs), it
> feels like forward progress on the tree isn't happening very
> quickly.

Yup, thats pretty much where things stand.

> i just diffed the 1.00 sources against the current svn tree, and
> there have been a smattering of fixes done, but very few,
> considering the overall passage of time.  (ironically, one of the
> changes that _is_ in there ("read -t" in ash) is something that
> doesn't appear in the bug system, was never discussed on the list
> that i can find, and was something i was just today planning on
> implementing.  i'm glad i checked.  :-)
> 
> anyway, it feels like the backlog of candidate changes is getting
> longer and longer, with less and less discussion going on, and
> with less observable forward progress.
> 
> in short:  what's up?

In short, I've been swamped with work.  I have a family to feed
and a number of other projects I maintain which of late have been
receiving much more of my limited time.  BusyBox basically works,
so despite obviously correct patches sitting in the bug tracker,
when things slip (as they inevitably do given how insanely busy I
have been) it currently tends to be BusyBox that ends up being
short changed.

Despite the number of folks with commit priviledges, there has
been basically nobody helping me review and commit patches.  The
kernel maintainers maintain a codebase that is 6 times larger
than BusyBox and uClibc, yet they also have a bunch a lieutenants
(many of whom are full time kernel folks) helping them to review
and merge patches.  I have basically just myself, working as time
permits, with essentially a full time job doing other things.

Ideally, I need to find some lieutenants to help me get patches
reviewed and merged...

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--