1 |
>>>>> On Wed, 30 Sep 2015, Michał Górny wrote: |
2 |
|
3 |
>> I'm pretty sure I've mentioned this before, but seems that you have |
4 |
>> missed it. IMHO matching projects via their e-mail address is not a |
5 |
>> good idea, because some projects have an address <project>-bugs@g.o |
6 |
>> or dev-<project>@g.o which makes guessing the project's name (and |
7 |
>> finding the project page) more difficult. Therefore, projects |
8 |
>> should be matched by their proper name. |
9 |
|
10 |
> And why would you need to guess that? Wiki project names are already |
11 |
> disjoint from herds.xml <name/>s, so I don't see a problem with |
12 |
> that. |
13 |
|
14 |
We would need a "shortname" or "id" field in the project page |
15 |
template, e.g. "Quality Assurance" -> "qa" (but I guess most would be |
16 |
trivial, like "Emacs" -> "emacs"). I've already discussed this with |
17 |
a3li some time ago, and there should be no technical problems. |
18 |
|
19 |
>> > 2a. If someone really cares about this, we add an extra attribute or |
20 |
>> > element which indicates the 'kind' of <maintainer/>. Otherwise, we just |
21 |
>> > match herds.xml by e-mail address. |
22 |
>> |
23 |
|
24 |
>> Why don't we follow the KISS principle and replace <herd> by <project> |
25 |
>> in metadata.xml? That is, create a project for every herd. |
26 |
|
27 |
> Because this: |
28 |
|
29 |
> 1. breaks backwards compatibility, |
30 |
|
31 |
It is already broken. For example, <maintainingproject> in herds.xml |
32 |
does no longer work. |
33 |
|
34 |
> 2. doesn't change anything but the name which is the most meaningless, |
35 |
> waste-of-time change you could have proposed. if you do this, please |
36 |
> count me out. |
37 |
|
38 |
Huh? You really think that getting rid of herds and having all |
39 |
information about project membership in one central place (namely, |
40 |
the project page in the wiki) doesn't change anything? |
41 |
|
42 |
Ulrich |