1 |
> > d) Simple and stupid mapping for e-mail aliases: |
2 |
> > project shortname y -> e-mail alias is y-project@g.o |
3 |
> > Legacy (e.g. y@g.o) addresses will be forwarded. |
4 |
> |
5 |
> Sounds like more typing but I guess this is what makes people happy. |
6 |
> Why alter the few team names who have trouble when we can force |
7 |
> a change on everyone... |
8 |
|
9 |
I'm also happy with altering the few critical team shortnames, as long as we |
10 |
can have a 1:1 mapping here between project shortname and mail alias. |
11 |
|
12 |
> > e) Since per GLEP 39 only developers can be project members, let's |
13 |
> > introduce "contributors" which are listed on the wiki project page |
14 |
> > together with the members. |
15 |
> |
16 |
> This doesn't solve the problem with developers who don't want to use |
17 |
> SMW. |
18 |
|
19 |
I just plainly dont care beyond a certain level of obstructiveness. |
20 |
|
21 |
> > f) The project e-mail alias is automatically populated from the wiki page |
22 |
> > (members and contributors). |
23 |
> |
24 |
> Is anyone going to actually do it? Or is this a purely theoretical idea |
25 |
> with nobody willing to do the work? |
26 |
|
27 |
It's feasible according to Alex (though he doesnt particularly like the idea). |
28 |
|
29 |
> > * Obviously there are exceptions to this rigid structure for few special |
30 |
> > teams (sec, infra, ...) |
31 |
> |
32 |
> Doesn't this kill the whole idea? Or are we talking about projects |
33 |
> which are not allowed to maintain packages? |
34 |
|
35 |
What's maintaining packages got to do with the generation the mail aliases? |
36 |
|
37 |
-- |
38 |
Andreas K. Huettel |
39 |
Gentoo Linux developer (council, perl, libreoffice) |
40 |
dilfridge@g.o |
41 |
http://www.akhuettel.de/ |