| 1 |
On 04/07/10 14:00, Ben de Groot wrote: |
| 2 |
> On 7 April 2010 13:20, Sebastian Pipping <sping@g.o> wrote: |
| 3 |
>> - herds.xml does not hold membership lists for |
| 4 |
>> all projects, not even herds. The load |
| 5 |
>> evaluator needs access to complete mappings |
| 6 |
>> to generate output close to reality. |
| 7 |
>> How can such a mapping be made without |
| 8 |
>> duplicating data? |
| 9 |
> |
| 10 |
> herds.xml should be the definitive resource for herds, so any herds |
| 11 |
> that are not on there should be added, and outdated information should |
| 12 |
> be brought up to date. |
| 13 |
|
| 14 |
they are in there but keep their member list elsewhere. |
| 15 |
an example is herd "bsd": |
| 16 |
|
| 17 |
<herd> |
| 18 |
<name>bsd</name> |
| 19 |
<email>bsd@nospam</email> |
| 20 |
<description>Support for *BSD system packages, |
| 21 |
and *BSD derived packages.</description> |
| 22 |
<maintainingproject> |
| 23 |
/proj/en/gentoo-alt/bsd/index.xml |
| 24 |
</maintainingproject> |
| 25 |
</herd> |
| 26 |
|
| 27 |
now that i have a closer look maybe the herds itself are manageable, |
| 28 |
besides the annoyance of being in another CVS tree: |
| 29 |
|
| 30 |
<subproject ref="/proj/en/gentoo-alt/bsd/obsd/index.xml" |
| 31 |
inheritmembers="yes" /> |
| 32 |
<subproject ref="/proj/en/gentoo-alt/bsd/fbsd/index.xml" |
| 33 |
inheritmembers="yes" /> |
| 34 |
<subproject ref="/proj/en/gentoo-alt/bsd/nbsd/index.xml" |
| 35 |
inheritmembers="yes" /> |
| 36 |
|
| 37 |
<dev role="lead">welp</dev> |
| 38 |
<dev role="lead" description="Deputy lead">drizzt</dev> |
| 39 |
<dev role="member">aballier</dev> |
| 40 |
<dev role="member">the_paya</dev> |
| 41 |
|
| 42 |
that looks usable. |
| 43 |
|
| 44 |
with the herd "embedded" it's difficult though: the page |
| 45 |
<http://www.gentoo.org/proj/en/base/embedded/index.xml> |
| 46 |
lists members for it but the page source does not |
| 47 |
hold it, explicitly. where does it come from? |
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
> Other projects should have membership listed on their project pages. |
| 52 |
> Again, where these are outdated, they should be brought up to date. |
| 53 |
|
| 54 |
seems like they use the same syntax, too. i start to like guidexml :-) |
| 55 |
|
| 56 |
some of the mail aliases i don't handle yet, could also be a problem |
| 57 |
(especially those i don't have permission to look at). |
| 58 |
|
| 59 |
|
| 60 |
|
| 61 |
sebastian |
Archives