ICANN/DNSO
DNSO Mailling lists archives

[council]


<<< Chronological Index >>>    <<< Thread Index >>>

Re: [council] List administration


Elizabeth:

Perhaps, as stated in previous messages to the GA, the organization is the
problem you have.

On Tue, 15 May 2001, Elisabeth Porteneuve wrote:

> Setting up lists on the DNSO is not only a short technical
> exercise.
For you, yes, it should be.

> The majority of time on new GA lists was spent in clarifying
> with new and old GA Chairs and List Monitors the lists
> requirements, the rules applied to each list and the rules
> applied accross lists. The procedures for posting rights
> handling, the synchronization between Lists Monitors decision
For now to the future, do it more simple:  Let the GA Chairs and monitors,
etc, arrange themselves on what they want, they send you rules ready to
post, the characteristics they want.  But, of course, those people have to
know what characteristics can be implemented with majordomo.  For this,
the only thing needed is to post in a webpage (a one time job) all the
features of majordomo, and then GA-Chairs and monitors has just to select
which features they want and sent it to you.

> and Secretariat, the timely technical implementation.
Also another issue of organization.  Set a procedure to be post in the
webpage (a one time job) that stablish simply that if today a request of
mailing list (with all pertaining texts) is sent to you, such a list will
be ready, next day...next hour, whatever...If there is a request of
several mailing list at the same time, then setup the time be ready.
Period...no discussion of this procedure and believe me, you will feel
with less load than before and will take for less less time to create a
mailing list.

The idea, is that you just have to make the technical setup which, again
is just five minutes.  But, what I want to know is who makes directly the
setup: you in person, or an AFNIC technical staff?  If it is the AFNIC
technical staff, then they are very well payed with DNSO funds, so they
shouldn't complain!!!

> There is more than 1300 subscribers to all active DNSO lists
> (more than 900 different e-mail addresses), and more than 300
> subscribers to the DNSO Voting Registry.
> The DNSO lists maintenance duties includes watching technical
> problem
not everyday work for mailing list server

> s as well as bounces handling
not so frecuent.

> and providing answers to those
> who get lost and ask for help in unsubscribing or modifying
> addresses.
five minutes to send an e-mail or an URL.  By the way, in the Welcome
Message can be included instructions to unsuscribe and modifiying address.
This would decrease the amount of people that writes you.

> Depending on traffic (either induced by e-mail addresses
> belonging to lists, and which may have temporary or permanent
> problems, or par cross posting, or par spaming, par chain-mails,
> par some automated answers, etc.), the usual load at listadmin
> is more than two hundred delivery-reports two times a day.
and who perfom this task...you directly?  And do you read all of them?

> As for my opinion for ga and ga-full lists, they are both
> associated and in equilibrum, adopted by the GA members
> after several months of work by former Chairs, Roberto Gaetano
> and Harald Alvestrand.
> Closing the ga-full list is not an independent decision, and may
> destabilize the compromise achieved one year ago.
I am agree with you.   I vote for GA-FULL not be closed, and I request to
you make your life easier in your voluntary job that I know you do it very
kindly, but this not means that if more mailing lists are needed, then now
you have to complicated your life.  Lets setup simply procedures
pre-technical job, and believe me that you will have more peace of mind
and time.

> I am asking the NC Colleagues to reconsider this.
Excellent!!!

Best Regards
Vany

-- 
Nilda Vany Martinez Grajales
IT Specialist
Sustainable Development Networking Programme/Panama
Tel: (507) 230-4011 ext 213
Fax: (507) 230-3455
e-mail: vany@sdnp.org.pa
http://www.sdnp.org.pa



<<< Chronological Index >>>    <<< Thread Index >>>