<<<
Chronological Index
>>> <<<
Thread Index
>>>
[ga] Organizing structure work.
I'm tending towards setting up kind of a WG for this topic, and
moving the substantial discussions to the ga-icann sublist. For the
time of the structure work (which is limited to about six weeks, if
I gathered this correctly), list monitoring for this sublist would
be extremely strict, with, in particular, off-topic offenders being
removed quickly, and radically. Concerning participants, we should
invite:
- the GA membership, of course
- the membership of the names council (which plans to do a lot of
work by itself)
- any interested parties from constituencies
- the general public, in particular including those from NAIS and
ALSC who care to participate.
- general public.
We'll also need a close time line, and well defined milestones. As
a very first suggestion, what do you folks think about the following?
- March 15: Have terms of reference, and rules of procedure for the
WG done. This discussion should happen on the main GA list (i.e.,
in this thread). Send out invitations to NC, constituencies,
NAIS, ALSC, ALSC Forum, icann.Blog, icannwatch, Slashdot. Alex or
Danny: Could one of you try to extract terms of reference from
your recollection of the NC meeting? I was listening in on a
horrible phone connection. Possibly re-send invitations on March
18 and 21.
- March 15-22: Brain storming phase. What could ICANN structure and
mission look like? It may be helpful to try going through the
various proposals from the Aspen Institute meeting, plus the Lynn
proposal, and to try to cough up something ourselves. Documents
published so far should be collected during this phase, and linked
from a task force web site.
- March 22-29: Identify most interesting approaches, and produce
short descriptions of these ones, including arguments given during
discussion. This would be the first kind of document production
phase. For document production, I'm _strongly_ suggesting that we
use a blog-like document repository with comments, like the thing
I've started doing for the whois task force. Document formats
should be kept simple (plain text, HTML, MS-Office or StarOffice
without anything fancy - we don't need to repeat the document
format conversion hell the whois task force is experiencing, due
to my choice of StarOffice and heavy use of OLE tables).
- March 29: Milestone 1, have a structure and skeleton of a report
done.
At that point of time, it should be _possible_ to have a rough idea
of what proposals we may come up with, and it should also be
possible to use the subsequent weeks to refine such proposals, and
add more substance to them.
Any comments?
Also, if you have any online reference material on ICANN structure
and mission which could be relevant, please send me links. I'll try
to set up a reference web page ASAP, where the relevant material is
linked from.
--
Thomas Roessler http://log.does-not-exist.org/
--
This message was passed to you via the ga@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga" in the body of the message).
Archives at http://www.dnso.org/archives.html
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|