1 |
Joshua Saddler <nightmorph@g.o> said: |
2 |
> On Tue, 8 Dec 2009 10:20:36 +0100 |
3 |
> |
4 |
> Thilo Bangert <bangert@g.o> wrote: |
5 |
> > Hi all, |
6 |
> > |
7 |
> > similarly to the metadata.xml check, the following is a list of small |
8 |
> > problems related to the project metadata as found in the gentoo CVS |
9 |
> > repository. |
10 |
> > |
11 |
> > Documentation: Only 1 developers signed up for project! |
12 |
> |
13 |
> Only one GDP member, eh? Your script is rather unreliable. Take, for |
14 |
> example, our GDP page: |
15 |
> |
16 |
> http://www.gentoo.org/proj/en/gdp/index.xml |
17 |
> |
18 |
|
19 |
hhm, crazy. |
20 |
|
21 |
> It lists all our developers, as does: |
22 |
> |
23 |
> http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/metadoc.x |
24 |
> ml?view=markup |
25 |
> |
26 |
> Yet your script only seems to be looking at devrel's |
27 |
> roll-call/userinfo.xml file, |
28 |
|
29 |
no - the script crossreferences userinfo.xml with the projects index.xml. |
30 |
removing the comments between the devs makes the script work correctly for |
31 |
the gdp page... which leaves me a little mystified. |
32 |
in any case: thanks for the pointer |
33 |
|
34 |
|
35 |
> which is autogenerated from the LDAP |
36 |
> attributes each developer has. The problem with checking LDAP for |
37 |
> roles is that there doesn't seem to be a standard way to label |
38 |
> projects. For docs, you'll find the following roles: |
39 |
> |
40 |
> French Documentation Lead |
41 |
> Documentation |
42 |
> Documentation, Developer Relations, Infrastructure |
43 |
> ---> this one doesn't seem to be counted as Documentation, since it |
44 |
> lists other roles. Documentation, Czech Translation |
45 |
> Translator Follow-Up |
46 |
> . . . etc. |
47 |
> |
48 |
> There are LOTS more different references to working with documentation |
49 |
> or translation, some of them not even for the GDP. Normally |
50 |
> "Documentation" refers to the GDP, but I see some devs in there who |
51 |
> are not on the GDP team who list Documentation as a primary role. No |
52 |
> standardization there whatsoever. |
53 |
> |
54 |
> Another problem with checking LDAP attributes is that they tend to be |
55 |
> very out-of-date, even more so than project pages. People get their |
56 |
> LDAP stuff set ONCE, when they first join, then tend to forget about |
57 |
> them for the rest of their stay in Gentoo. Examples: all the Xfce (or |
58 |
> XFCE) guys who are no longer there, or anyone who's added six |
59 |
> different teams and package herds since their original |
60 |
> responsibilities. |
61 |
> |
62 |
> I wish there was a standard way of labelling existing duties, and I |
63 |
> wish there was an easier way to update the LDAP attributes. I think no |
64 |
> one cares enough to login to dev.g.o to change their stuff, as the |
65 |
> process is tedious. |
66 |
> |
67 |
|
68 |
ideally we would populate LDAP from the projects index.xml files. |
69 |
|
70 |
> You may want to point your script at all our (sub)project index pages |
71 |
> and check for the <dev role> tag to see who does what, though that may |
72 |
> generate some false hits because not all of 'em will actually be |
73 |
> Gentoo developers, as in the case of arch testers. |
74 |
> |
75 |
|
76 |
this is what i intended to do. i'll report back the results once this has |
77 |
turned into something a little more reliable. |
78 |
|
79 |
kind regards |
80 |
Thilo |