| 1 |
On Thu, 3 Jun 2010 17:44:10 +0300 |
| 2 |
Markos Chandras <hwoarang@g.o> wrote: |
| 3 |
|
| 4 |
> all the gnome-* herds look obsolete to me. It should be like kde and |
| 5 |
> use only one alias. Further more the comm-fax could be merged with a |
| 6 |
> net-* alias, and all the desktop-* could be merged in one herd. The |
| 7 |
> dev-embedded could be merged with embedded, kernel can merge with |
| 8 |
> kernel-misc. Plus I am sure that we can perform a clean up/merge on |
| 9 |
> net-* herds. Same rule for sci-*. |
| 10 |
|
| 11 |
Speaking for myself, the net-* and netmon herds are much too diverse to |
| 12 |
pile onto one big stack. As with the other suggested herd mergers, you'd |
| 13 |
merely end up piling more work onto unsuspecting developers' desktops, |
| 14 |
possibly discouraging some of them to dig through all the extra |
| 15 |
incoming mail. If any changes are made in this respect, it should have |
| 16 |
the approval of all members of all herds considered for a merger. |
| 17 |
|
| 18 |
> Having 150 herds for 300 *listed* devs doesn't seem optimal |
| 19 |
|
| 20 |
You could qualify that statement a lot better. I don't see a problem |
| 21 |
here. Many developers are members of more than one herd, which the |
| 22 |
simple 2:1 relation you exemplify does not carry out that important bit |
| 23 |
of information. |
| 24 |
|
| 25 |
There is a real problem with herds that have a single or no |
| 26 |
maintainer, the former mainly because that could very well lead to |
| 27 |
another case of the latter, and we should certainly address both |
| 28 |
problems, but we should create as little as possible new problems in |
| 29 |
the process. |
| 30 |
|
| 31 |
|
| 32 |
Regards, |
| 33 |
jer |
Archives