From: Daniel Robbins <drobbins@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] New Team Structure
Date: Fri Jul 20 18:31:01 2001 [thread overview]
Message-ID: <20010720183009.A11108@cvs.gentoo.org> (raw)
Hi All,
The dev-wiki has been updated to reflect our new team structure (many thanks to
Thread!). I haven't really gotten much response about who wants to be on what
team; if you're a developer, you *need* to get this info to me or I'll pick a
team for you. Also, we have lots of team leader positions open. I hope my last
email didn't scare anyone from becoming a team leader; to compensate, here are
some of the good things about being a team leader:
- you'll have the ability to shape a complete section of the Gentoo Linux
distro.
- you'll have a team of developers at your command.
- you'll be interacting with me and Achim directly; if you're not a team
leader, you'll be reporting to the team leader rather than me and Achim, so
your contact with us will be limited.
- you will be playing a key role in making Gentoo Linux ready for prime-time,
and if you do a great job your efforts will not be forgotten after Gentoo
Linux 1.0. Any excellent team leaders will become a key part of our
development team. When we start generating income, that could potentially
translate into a full-time staff position.
- This is chance to prove yourself by helping Gentoo Linux. As you do, Achim
and I will gradually give you more authority. Our goal is to use the Team
Leader position to cultivate developers who want to rise to the "achim" and
"drobbins" level of Gentoo Linux expertise. This will allow us to
potentially put some of our Team Leaders in charge of, say, the entire x86
version of Gentoo Linux so that me and Achim can focus on the PowerPC and
other processors, as well as other Unix operating systems. Or,
alternatively, you may lead these new development efforts. Basically, by
becoming a Team Leader, you will be putting yourself in a position where you
can eventually manage the entire distro. We're going to spend more time
personally interacting with our Team Leaders and give you the resources you
need to gain this experience and expertise.
- Prestige. Since you will be getting involved in Gentoo Linux development in
a non-trivial way, you'll have something of significance to add to your
resume.
We have Team Leader positions open in the System, Tools, Infrastructure and and
Server teams. All developers please get back to me and let me know how you'd
like to be involved in the new team structure: You need to tell me a team name
you'd like to be part of and whether or not you'd like to be a team leader.
Best Regards,
--
Daniel Robbins <drobbins@gentoo.org>
President/CEO http://www.gentoo.org
Gentoo Technologies, Inc.
next reply other threads:[~2001-07-21 0:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-20 18:31 Daniel Robbins [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-07-21 12:20 [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=20010720183009.A11108@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