| 1 |
The changes are: |
| 2 |
- Rename the title to "Projects and Herds" to put the emphasis |
| 3 |
on projects |
| 4 |
- Explain projects and subprojects in a new "Projects" section |
| 5 |
- Add a subsection for starting new projects |
| 6 |
- Add a subsection for joining/leaving a project |
| 7 |
- Put a warning label at the beginning of the "Herds" section, |
| 8 |
declare it obsolete, and preserve it for historical reasons |
| 9 |
|
| 10 |
Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=572144 |
| 11 |
Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=549490 |
| 12 |
Signed-off-by: Göktürk Yüksek <gokturk@××××××××××.edu> |
| 13 |
--- |
| 14 |
general-concepts/herds-and-projects/text.xml | 101 ++++++++++++++++++++++++++- |
| 15 |
1 file changed, 100 insertions(+), 1 deletion(-) |
| 16 |
|
| 17 |
diff --git a/general-concepts/herds-and-projects/text.xml b/general-concepts/herds-and-projects/text.xml |
| 18 |
index e030150..e05cb81 100644 |
| 19 |
--- a/general-concepts/herds-and-projects/text.xml |
| 20 |
+++ b/general-concepts/herds-and-projects/text.xml |
| 21 |
@@ -1,10 +1,106 @@ |
| 22 |
<?xml version="1.0"?> |
| 23 |
<guide self="general-concepts/herds-and-projects/"> |
| 24 |
<chapter> |
| 25 |
-<title>Herds and Projects</title> |
| 26 |
+<title>Projects and Herds</title> |
| 27 |
|
| 28 |
<body> |
| 29 |
|
| 30 |
+<section> |
| 31 |
+<title>Projects</title> |
| 32 |
+<body> |
| 33 |
+ |
| 34 |
+<p> |
| 35 |
+The management structure of Gentoo, called the "metastructure", is |
| 36 |
+defined in |
| 37 |
+<uri link="https://wiki.gentoo.org/wiki/GLEP:39#Specification"> |
| 38 |
+GLEP 39</uri>. In Gentoo, a project is a group of developers working |
| 39 |
+towards a common goal in various different areas. For example, the |
| 40 |
+<uri link="https://wiki.gentoo.org/wiki/Project:Devmanual"> |
| 41 |
+Devmanual</uri> project focuses on maintaining this document. Many |
| 42 |
+others are responsible for maintaining packages. Projects spanning a |
| 43 |
+large area of topics can have multiple subprojects specializing in |
| 44 |
+particular fields within the domain of the parent project and thus |
| 45 |
+form a project hierarchy. |
| 46 |
+</p> |
| 47 |
+ |
| 48 |
+<p> |
| 49 |
+A package maintained by a project needs to have the |
| 50 |
+project explicitly listed as a maintainer in its |
| 51 |
+<uri link="::ebuild-writing/misc-files/metadata">metadata.xml</uri>. |
| 52 |
+The full listing of all the projects can be found on |
| 53 |
+<uri link="https://api.gentoo.org/metastructure/projects.xml"> |
| 54 |
+api.gentoo.org</uri> or on the |
| 55 |
+<uri link="https://wiki.gentoo.org/wiki/Project:Gentoo">wiki</uri>. |
| 56 |
+</p> |
| 57 |
+ |
| 58 |
+<subsection> |
| 59 |
+<title>Starting New Projects</title> |
| 60 |
+<body> |
| 61 |
+ |
| 62 |
+<p> |
| 63 |
+According to the metastructure any developer may create a new |
| 64 |
+project. There are two procedures involved in starting a new project: |
| 65 |
+ |
| 66 |
+<ol> |
| 67 |
+ <li> |
| 68 |
+ Create a new project page <uri |
| 69 |
+ link="https://wiki.gentoo.org/wiki/Gentoo_Wiki:Developer_Central/Project_pages"> |
| 70 |
+ through the wiki</uri>. |
| 71 |
+ </li> |
| 72 |
+ <li> |
| 73 |
+ Post a Request For Comments (RFC) email to the gentoo-dev |
| 74 |
+ mailing list. |
| 75 |
+ </li> |
| 76 |
+</ol> |
| 77 |
+ |
| 78 |
+There is no approval required for the RFC and negative comments do not |
| 79 |
+block a developer from creating a project. Competing projects are |
| 80 |
+allowed to co-exist in Gentoo; existence of another project with |
| 81 |
+similar goals do not block another developer from starting a new |
| 82 |
+project with the same goals. |
| 83 |
+</p> |
| 84 |
+ |
| 85 |
+</body> |
| 86 |
+</subsection> |
| 87 |
+<subsection> |
| 88 |
+<title>Joining and Leaving a Project</title> |
| 89 |
+<body> |
| 90 |
+ |
| 91 |
+<p> |
| 92 |
+Members of a project are managed through the project's page on the |
| 93 |
+Gentoo Wiki. Each page has a "Project" template in its source which |
| 94 |
+lists the members of the project. Simply modifying the list is |
| 95 |
+sufficient for adding or removing a developer. Note that different |
| 96 |
+projects have different requirements and procedures for recruiting |
| 97 |
+developers, which may require prior arrangements to be made before |
| 98 |
+modifying the member list. |
| 99 |
+</p> |
| 100 |
+ |
| 101 |
+<p> |
| 102 |
+Developers should remember to add themselves to the alias by editing |
| 103 |
+<c><path>/var/mail/alias/misc/<alias name></path></c> on |
| 104 |
+dev.gentoo.org. For example, the alias for the Devmanual project is |
| 105 |
+located at <c>/var/mail/alias/misc/devmanual</c>, which corresponds to |
| 106 |
+the project email address <c>devmanual@g.o</c>. |
| 107 |
+</p> |
| 108 |
+ |
| 109 |
+</body> |
| 110 |
+</subsection> |
| 111 |
+ |
| 112 |
+</body> |
| 113 |
+</section> |
| 114 |
+ |
| 115 |
+<section> |
| 116 |
+<title>Herds</title> |
| 117 |
+<body> |
| 118 |
+ |
| 119 |
+<warning> |
| 120 |
+Herds have been declared obsolete as per the Gentoo Council's <uri |
| 121 |
+link="https://projects.gentoo.org/council/meeting-logs/20160110-summary.txt"> |
| 122 |
+decision on January 10, 2016</uri>. The following section is preserved |
| 123 |
+for historical purposes. |
| 124 |
+</warning> |
| 125 |
+ |
| 126 |
<p> |
| 127 |
A <e>herd</e> is a collection of packages with an associated set of maintainers. |
| 128 |
It can happen for example because of retirement that a herd has no developers |
| 129 |
@@ -27,6 +123,9 @@ as the <c>silo</c> bootloader). This is <e>not</e> always the case. |
| 130 |
</p> |
| 131 |
|
| 132 |
</body> |
| 133 |
+</section> |
| 134 |
+ |
| 135 |
+</body> |
| 136 |
</chapter> |
| 137 |
</guide> |
| 138 |
|
| 139 |
-- |
| 140 |
2.7.3 |
Archives