|author||Göktürk Yüksek <firstname.lastname@example.org>||2016-02-13 22:50:07 -0500|
|committer||Göktürk Yüksek <email@example.com>||2016-05-18 00:39:49 -0400|
|parent||devbook.xsl: Make UTF-8 usage and output more explicit (diff)|
general-concepts/herds-and-projects: update per GLEP 67 #572144 #549490
The changes are: - Rename the title to "Projects and Herds" to put the emphasis on projects - Explain projects and subprojects in a new "Projects" section - Add a subsection for starting new projects - Add a subsection for joining/leaving a project - Put a warning label at the beginning of the "Herds" section, declare it obsolete, and preserve it for historical reasons Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=572144 Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=549490 Signed-off-by: Göktürk Yüksek <firstname.lastname@example.org>
Diffstat (limited to 'general-concepts')
1 files changed, 100 insertions, 1 deletions
diff --git a/general-concepts/herds-and-projects/text.xml b/general-concepts/herds-and-projects/text.xml
index e030150..81b1885 100644
@@ -1,10 +1,106 @@
-<title>Herds and Projects</title>
+<title>Projects and Herds</title>
+The management structure of Gentoo, called the "metastructure", is
+GLEP 39</uri>. In Gentoo, a project is a group of developers working
+towards a common goal in various different areas. For example, the
+Devmanual</uri> project focuses on maintaining this document. Many
+others are responsible for maintaining packages. Projects spanning a
+large area of topics can have multiple subprojects specializing in
+particular fields within the domain of the parent project and thus
+form a project hierarchy.
+A package maintained by a project needs to have the
+project explicitly listed as a maintainer in its
+The full listing of all the projects can be found on
+api.gentoo.org</uri> or on the
+<title>Starting New Projects</title>
+According to the metastructure any developer may create a new
+project. There are two procedures involved in starting a new project:
+ Create a new project page <uri
+ through the wiki</uri>.
+ Post a Request For Comments (RFC) email to the gentoo-dev
+ mailing list.
+There is no approval required for the RFC and negative comments do not
+block a developer from creating a project. Competing projects are
+allowed to co-exist in Gentoo; existence of another project with
+similar goals do not block another developer from starting a new
+project with the same goals.
+<title>Joining and Leaving a Project</title>
+Members of a project are managed through the project's page on the
+Gentoo Wiki. Each page has a "Project" template in its source which
+lists the members of the project. Simply modifying the list is
+sufficient for adding or removing a developer. Note that different
+projects have different requirements and procedures for recruiting
+developers, which may require prior arrangements to be made before
+modifying the member list.
+Developers should remember to add themselves to the alias by editing
+<c><path>/var/mail/alias/misc/<alias name></path></c> on
+dev.gentoo.org. For example, the alias for the Devmanual project is
+located at <c>/var/mail/alias/misc/devmanual</c>, which corresponds to
+the project's email address <c>email@example.com</c>.
+Herds have been declared obsolete as per the Gentoo Council's <uri
+decision on January 10, 2016</uri>. The following section is preserved
+for historical purposes.
A <e>herd</e> is a collection of packages with an associated set of maintainers.
It can happen for example because of retirement that a herd has no developers
@@ -27,6 +123,9 @@ as the <c>silo</c> bootloader). This is <e>not</e> always the case.