At 11:43 PM 10/02/2006, you wrote:
Hi,
we talked in the last meeting about the language lists. This requires a
new layout (or rather _a_ layout because today we dont have guidelines
about it) of the lists. We thought about it and came up with the
following:
We need to distinguish between 3 different variables in the mailinglists
names:
1. project
2. topic
3. language
This leads to the the following layout. For instance if you want to
create mailinglists for the project <project>
<project>@domain.tld
--------------------
- General mailinglist about the project <project> in <default language>
<project>-<language>@domain.tld
-------------------------------
- General mailinglist about the project <project> in <language>
<project>[EMAIL PROTECTED]
-----------------------------
- Announce/News mailinglist for project <project> in <default language>
<project>-announce-<language>@domain.tld
----------------------------------------
- Announce/News mailinglist for project in <language>
<project>[EMAIL PROTECTED]
--------------------------
- Support mailinglist for the project <project> in <default language>
<project>-users-<language>@domain.tld
-------------------------------------
- Support mailinglist about the project <project> in <language>
<project>-<topic>@domain.tld
----------------------------
- Mailinglist about the topic <topic> in the project <project> in
<default language>
<project>-<topic>-<language>@domain.tld
---------------------------------------
- Mailinglist about the topic <topic> in the project <project> in <language>
This would for instance mean for the openSUSE project:
[email protected] - General in english
[EMAIL PROTECTED] - Generl in german
[email protected] - Announce in english
[email protected] - Announce in german
[EMAIL PROTECTED] - Support in english
[EMAIL PROTECTED] - Support in german
[email protected] - Factory in english
[EMAIL PROTECTED] - Factory in german
This layout scales pretty good. We need the <project> prefix because in
the long run we are going to migrate everything that is on
lists.suse.com to lists.opensuse.org. And we have other projects there,
for instance taskjuggler or packet-writing.
Mailinglists will get setup on request. Im not going to setup
mailinglists with one or less subscribers. I need to think of an request
mechanism but it will probably be a mail address.
There is no hard requirement for a default language list but its very
desirable. So for instance there shouldnt be a
[EMAIL PROTECTED]
without a list
[EMAIL PROTECTED]
But it might be that we cant avoid that in all cases.
Comments?
Henne
1-
there are 23 major written language groups currently used on the
planet, there are
additionally some 158 dialect variations.
even if you only support the major language groups you will need some
physical space
and people time to translate between, or is it the intention to only
cover topics within
their own language group?
2-
have you thought about the matrix neccesary as you expand?
3-
can it be from the start that everything is in text (no html or
closed format attachments)
for security, etc. (I for one have autodelete on for all attachments)
4-
how will the mailing format to people go, message by message to all
subscribed (such as
suse uses now, it is the easiest way for the supplier but user
timewasting where only a small
number of threads may be of interest, especially to those that pay
per minute for connect time)
or daily digest (like freshmeat uses and provides a summary only,
takes a little work to setup
and monitor, requires the user to go and read a particular message to
get full details).
5-
finally, do we need such a large breakup as project, or would this be
better set as the first word
of the topic (or am i taking the word the wrong meaning)
hope i've not offended anyone yet!
regards
scsijon
ps has anyone tried listing the existing forums out there and their
purposes? maybe what is
needed is a rehash / combine/resplit instead.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
