Re: [ICANN-EU] MEMO requesting discussion: Structuring a large ML

[Thomas Roessler <roessler@does-not-exist.org>]

On 2000-08-20 16:55:19 +0200, Vittorio Bertola wrote:
>  The announcements ML should not become the PR office for the
>  Director.

That's not really what I had in mind, as you'll have guessed.
Instead, I thought about the announcements ML as a place where an
ICANN director can post

- requests for comments (to be taken verbatim),
- reports about meetings and the like.

Ideally, I'd like to be able to only subscribe to the announce list,
to get a rough sense for the issues currently being discussed, and
to join the general mailing list only when it's necessary because
topics of particular interest are currently being discussed.

> In other words, I feel the need to restrict an announcements
> mailing list to *facts* (i.e. meeting agendas, resumes of the
> deliberations...) but to keep the discussion about opinions
> inside a more open environment.

Agreed.

> I have a slightly different idea on that. I think that the
> community should try to organize itself regardless to the
> opinions of the next Director. If the elected candidate does not
> want to discuss his ideas with his voters, his voters still have
> the right to try to get a voice on their own.

Certainly.  However, instruments needed may be different in this
case.

> It is fine by me, as long as opinions formed and supported
> locally are not disadvantaged in respect to opinions posted on
> the international list. The Director should take care to taste
> the feeling of the whole community, not only of its
> English-speaking subset. This is why I'm insisting on a regional
> At Large council (which could in fact just be a closed or
> moderated mailing list) to act as a connection between the
> Director and all the communities.

Those who either speak the director's mother tongue, or English,
will automatically be privileged by being able to express their
opinions and arguments directly, and by having timely access to
first hand materials.

-- 
Thomas Roessler                         <roessler@does-not-exist.org>