Martin Schlander schrieb:

> opensuse-users@ -> opensuse-help
> 
> opensuse@ -> opensuse-project
> 
> Who's gonna misunderstand that?

I second that. Except these two names, I also liked the layout of
Henne's proposal with regard to the topic and language specifics.

> And then kill [EMAIL PROTECTED] There shouldn't be a plain opensuse@ - too 
> confusing 
> for people to figure out which aspects of opensuse belong on there

If I think about Henne's complete proposal once again, for me the
problem seems to be, to have exactly one schema both for low- and
high-traffic lists.
- For low traffic ones, Henne's layout perfectly fits, as everything can
go to project@ as a catch-all and only if there is need, more specific
subtopics are arranged.
- For high traffic ones however, subtopics are a must-have and then the
question remains, what will be on topic in the unspecific project@ list.
It would be best to not have it at all, but this breaks the unique schema.

So my proposal for high traffic lists is to have project@, but just send
an automatic answer that lists the topics of this project and the
relevant mailing list names. project-help@ as the standard sink for all
I-don't-know-where-to-ask-mails seems to be o.k.

With regard to Martin's suggestion about killing opensuse: As the
existence of opensuse@ is already spread over many sites, it would not
be good to just kill it. So, introduce the new name schema, adapt the
"communication" page at opensuse.org and send an automatic answer with
the new layout and a pointer to the communication page as answer to
every mail for [EMAIL PROTECTED]
In this way nobody thinks, that the mailing lists are not working any
more and in the same time gets the pointers, which hopefully take away
some work off Houghi on this list, and -help and -project should also
satisfy Randalf's need for good English. ;-)

Henne, would this be o.k. for you?

Ciao
Siegbert

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to