Gentoo Archives: gentoo-project

From: Donnie Berkholz <dberkholz@g.o>
To: gentoo-project@l.g.o
Subject: [gentoo-project] [ Re: Fw: Some questions about Gentoo]
Date: Sat, 22 Sep 2007 19:12:08
Message-Id: 20070922190349.GU31094@supernova
1 Chris responded to this on the PR alias, but I thought it would be
2 useful to have it publicly archived.
4 Thanks,
5 Donnie
7 ----- Forwarded message from Chris Gianelloni <wolf31o2@g.o> -----
9 Subject: Re: Fw: Some questions about Gentoo
10 From: Chris Gianelloni <wolf31o2@g.o>
11 To: Lucas Nussbaum <lucas@××××××××××××××.net>
12 Cc: pr@g.o
13 Date: Fri, 21 Sep 2007 12:06:41 -0700
15 On Fri, 2007-09-21 at 11:17 +0200, Lucas Nussbaum wrote:
16 > Q1. Packages
17 > How many "pieces of software" do you have in your distribution? Do you
18 > distinguish between "source packages" and "binary packages"? (if yes,
19 > give numbers for both). Are there subdivisions in the set of packages (by
20 > kind of support, by "freeness")? Are all packages supported the same way,
21 > or are there different levels of support? (If different levels, how many
22 > packages are supported with each level?) Are some packages imported from
23 > another distribution, or are most of your packages done from scratch by
24 > your developers ?
26 Gentoo Linux has over 12,000 packages in the tree. We make no
27 distinction between source and binary packages other than adding -bin to
28 the end of the name of a binary package. We do not subdivide our
29 packages into any arbitrary structure of support or freeness, but we do
30 divide the repository into multiple categories, to ease browsing and
31 also to resolve name conflicts. Since Gentoo uses its own package
32 manager, all packages are done entirely in-house.
34 > Q2. Your developers
35 > What's a "developer" in your distribution? How many developers do you
36 > have? How many of these developers were active in 2007? Does a company
37 > (which one?) employ a large number of developers? Do you have different
38 > "classes" of developers, or does everybody have the same access right to
39 > all your packages? How do you integrate new developers? How do you
40 > handle contributors who don't have access rights to the archive? (is
41 > there some kind of mentoring/sponsoring system?)
43 A "developer" within Gentoo is anyone who has been granted an
44 email address. This includes staff, such as our
45 Infrastructure team or Developer Relations, and our Documentation team
46 and translators. We have approximately 325 developers, of which most
47 were active at least once since January 2007, as we have a retirement
48 process where we retire inactive developers. We do have different
49 classes of developers. We have "staff" and we have "ebuild developers".
50 The distinction is access to the package repository. All developers are
51 given the same access to the repository. New developers are recruited
52 from our user pool and go through a recruitment process. Gentoo's
53 Developer Relations team takes care of all of the "human resources"
54 stuff, such as verifying quizzes, enabling access, and processing
55 retirements. We have a recruitment program, which pairs would-be
56 developers with an established developer to act as mentor.
58 > Q3. Developers and packages ownership
59 > What's the relationship between developers and packages? Does each
60 > package have an assigned developer, or can everybody modify all packages
61 > without stepping on anyone's toes? Are packages mostly maintained by
62 > teams, or by developers working alone?
64 Packages in Gentoo are grouped into "herds" of packages. These herds
65 will be all similar packages. These herds are maintained by a team,
66 which are sometimes also referred to as "herds". Some packages have an
67 assigned developer/maintainer, with a team as a backup. All packages
68 should have a responsible team, but there are some orphan packages in
69 our repository. We routinely check the repository for orphaned packages
70 and either reassign them, recruit someone to maintain them, or possible
71 even remove the package from the repository. Developers are free to
72 touch any package in the tree, but we recommend that they try to speak
73 with the maintainers prior to doing anything to someone else's packages.
75 > Other questions:
76 > - Did I send that mail to the right mailing list?
78 PR is fine.
80 > - Which question should I have asked? What should I ask next?
82 I think the workflow for how a package gets into a distribution is much
83 more interesting than the number of developers. ;]
85 > - Do you think that this initiative is interesting?
87 I do, and I'm sure others in Gentoo would, also.
89 > - Do you think that this should move to a seperate mailing list? Would
90 > you participate in such a mailing list?
92 I'm not sure why a list would be needed unless you were trying to
93 solicit responses from the entire developer community, versus a single
94 answer per distribution.
96 > - Can you suggest a project that could host such a mailing list without
97 > annoying anyone? :)
98 > - Any other suggestions?
99 >
100 > Thank you for reading me so far -- and for answering my questions if you
101 > did. ;) If you want me to ping you when I'll publish the answers, just
102 > drop me a mail.
104 I'd love to see the answers once you're done.
106 --
107 Chris Gianelloni
108 Release Engineering Strategic Lead
109 Alpha/AMD64/x86 Architecture Teams
110 Games Developer/Foundation Trustee
111 Gentoo Foundation
115 ----- End forwarded message -----
116 --
117 gentoo-project@g.o mailing list