From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] New Team Structure
Date: Sat Jul 21 12:20:03 2001 [thread overview]
Message-ID: <20010721121905.E16789@cvs.gentoo.org> (raw)
On Sat, Jul 21, 2001 at 03:39:33AM +0200, Hendrik Visage wrote:
> Hi Daniel,
>
> currently I'm tempted to ask for a team leader position, but at
> present I haven't yet decided if the USE system is/will be working
> for me as it currently (ie. rc5 build install with a couple of options
> removed) doesn't quite work as advertized for me...
The USE system *does* indeed work; I am planning to upgrade it and already have
the new design in my head (with categories, much easier configuration and 100%
backwards compatibility). But I have no time to add new features to Portage;
that's where the new team concept comes in. Once the new teams are up and
running, I'll finally have some time to focus on *my* area of expertise --
Portage. Until then, all Portage upgrades are on hold as I try to juggle all
things Gentoo Linux, live my "real" life and answer gentoo-dev emails to boot.
So if you'd like Portage development to speed up (in reality, resume), then the
best way to make this happen is to come alongside us, take a personal stake in
the success of Gentoo Linux, and put in some solid, consistent long-term work
to help us take this OS to the next level. We're in this for the long haul;
Gentoo Linux *will* get to the level of refinement that you (and I, and
everyone else) desire. But whether we get to that point sooner or later is
largely dependent on how much help we get from the Gentoo Linux user community.
It depends on all of you who are reading this email.
Now that our project is really starting to grow, we need to get more people
meaningfully involved in Gentoo Linux development so we can benefit from the
economies of scale inherent in free, open software development. Up until now,
97% of the work going into Gentoo Linux has come from just two individuals, me
and Achim. And for the last year, Achim alone has been doing most of the work
while I have been focusing on my IBM dW articles. So, the Gentoo Linux that
you use today is effectively the fruit of just two individuals' hard work. My
goal is to rally the troops and parallelize our development process. With the
committed help of the Gentoo Linux community, this will allow us to *quadruple*
(4x!) the rate of Gentoo Linux development in the next 16 weeks, and then
double this rate by the end of the year. Imagine what a dramatic positive
impact this will have, allowing us to begin PPC and IA64 ports early next year.
This dramatic improvement in productivity *is* possible -- if the right people
step forward.
Best Regards,
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
next reply other threads:[~2001-07-21 18:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-21 12:20 Daniel Robbins [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-20 18:31 [gentoo-dev] New Team Structure Daniel Robbins
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=20010721121905.E16789@cvs.gentoo.org \
--to=drobbins@gentoo.org \
--cc=gentoo-dev@cvs.gentoo.org \
--cc=gentoo-dev@gentoo.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