Hey,

On 04/01/2011 03:51 PM, Chuck Payne wrote:

> I wish you luck, I couldn't get one for north america, I really think
> we need regional mailing list along with the regular one. They wanted
> to do it by language, which made no sense because North America,
> Australia, UK and most of the work speak english so if I want to send
> notice to the ambassadors of North America about things we need to do,
> I would have comments from other parts who don't understand what we
> are trying to do.

Your region[1] based plan works for a very low number of regions. For
North America its okay'ish because its two countries and most Canadians
speak English but nearly all the other regions have tons of languages in
them. I really think you need to think this through. You guys want as
far as I can understand 3 things

1. Reach _ONLY_ the people that might be affected geographically
2. Communicate in your native language
3. Keep the amount of messages to the opensuse-ambassador to a minimum

Is that so? Then the only reasonable way to achieve all 3 is to add
country specific[2] lists I think. So opensuse-ambassadors-us or
opensuse-ambassadors-nl. I do what you want. I don't really care :-)

I just can tell you that everybody else is trying to achieve the exact
opposite. Most of us try to unite the communication channels because the
isolation effectively kills all communication in the local groups
because they are often way to small and it also kills communication
between the local groups and synergies are wasted. Yes it is sometimes
tedious to communicate on a bigger list but there are also huge benefits
to it.

But like I've said, this is your decision. As ml-admin I do what the
team tells me. Just don't tell me 3 conflicting things ;)

Henne

[1]
http://upload.wikimedia.org/wikipedia/commons/0/08/United_Nations_geographical_subregions.png
[2] http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2

-- 
Henne Vogelsang, openSUSE.
Everybody has a plan, until they get hit.
        - Mike Tyson
-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to