| 1 |
On 9/17/15 4:35 AM, Justin (jlec) wrote: |
| 2 |
> On 16/09/15 23:43, Matthew Thode wrote: |
| 3 |
>> On 09/16/2015 04:25 PM, Michał Górny wrote: |
| 4 |
>>> |
| 5 |
>>> So, what are your thoughts for unmessing this? |
| 6 |
>>> |
| 7 |
>> Herds are groups of developers that can then be mapped to a package. |
| 8 |
>> |
| 9 |
> Herds are a group of packages, which are maintained my one or more developers or |
| 10 |
> a project team consisting of one or more developers. |
| 11 |
> |
| 12 |
> |
| 13 |
> |
| 14 |
Let's begin by eliminating herds. We can do that by absorbing herds |
| 15 |
into projects where that makes sense (eg base-system), or expanding the |
| 16 |
herd into the respective maintainers where a clear association between |
| 17 |
herd and project does not make sense. An ebuild can then have a |
| 18 |
<project> tag in which case it is maintained by all members of a project |
| 19 |
or a maintainer list, or a combination of both. It can also have an |
| 20 |
observer tag for devs that want to track that pkg's maintenance while |
| 21 |
not being a maintainer. |
| 22 |
|
| 23 |
Aliases can be associated with projects in the same way that ebuilds |
| 24 |
are. An alias can either belong to a project, in which case it expands |
| 25 |
to all the project members plus other added emails, or just a free |
| 26 |
standing alias with just members. |
| 27 |
|
| 28 |
Eg1. I'm not on base system, so an pkg with |
| 29 |
|
| 30 |
<project> |
| 31 |
<name>base-system</name> |
| 32 |
<email>base-system@g.o</email> |
| 33 |
</project> |
| 34 |
<maintainer> |
| 35 |
<name>Anthony G. Basile</name> |
| 36 |
<email>blueness@g.o</email> |
| 37 |
</maintainer> |
| 38 |
<observer> |
| 39 |
<name>Devan Franchini</name> |
| 40 |
<email>twitch153@gentoo</email> |
| 41 |
<observer> |
| 42 |
|
| 43 |
would be maintained by all of base system with alias |
| 44 |
base-system@g.o and me. twitch153 is listed as just an observer |
| 45 |
of the pkg and would receive emails but not technically be allowed to |
| 46 |
maintain the package. The email alias for this pkg is automatically |
| 47 |
generated from the metadata.xml. |
| 48 |
|
| 49 |
|
| 50 |
Eg2. A "free standing" ebuild could have |
| 51 |
|
| 52 |
<maintainer> |
| 53 |
<name>Anthony G. Basile</name> |
| 54 |
<email>blueness@g.o</email> |
| 55 |
<proxy/> |
| 56 |
</maintainer> |
| 57 |
<maintainer> |
| 58 |
<email>bugs@××××××××××.nu</email> |
| 59 |
<name>Johan Bergström</name> |
| 60 |
</maintainer> |
| 61 |
|
| 62 |
Again the alias for this pkg is automatically generated from the |
| 63 |
metadata.xml |
| 64 |
|
| 65 |
Thoughs? |
| 66 |
|
| 67 |
-- |
| 68 |
Anthony G. Basile, Ph.D. |
| 69 |
Gentoo Linux Developer [Hardened] |
| 70 |
E-Mail : blueness@g.o |
| 71 |
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA |
| 72 |
GnuPG ID : F52D4BBA |
Archives