ICANN ICANN Email List Archives

[At-Large Advisory Committee]


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

Re: [alac] RE: Archiving comments received? (Proposal.)

  • To: Denise Michel <denisemichel@xxxxxxxxxxxxx>
  • Subject: Re: [alac] RE: Archiving comments received? (Proposal.)
  • From: Thomas Roessler <roessler@xxxxxxxxxxxxxxxxxx>
  • Date: Thu, 24 Apr 2003 11:10:50 +0200

On 2003-04-22 11:46:05 -0700, Denise Michel wrote:

> The intention is for the ALAC to have a sorted, indexed public
> comment forum on its website -- the beginnings of which are
> already there. The idea is to build upon past public comment
> mechanisms to foster a productive, substantive public discourse
> for At-Large issues.  It is not yet fully operational due to the
> complexities of off-site access to the website's server (and
> security issues).  I'll let ICANN know of your embarrassment and
> I'll see if we can accelerate this process.  Meanwhile, when
> comments start arriving on the "forum" list, they will be
> posted/sorted and highlighted.

I'm not sure what sorts of complicated things you are trying to set
up, but for most purposes, a dedicated comment address and a simple
mhonarc archive would be just fine -- without much complexity,
off-site access and the like, i.e., it could be done *now*.  Right
now, we have a forum page which announces that the forum will be
operational by Rio; we are soliciting comments without archiving
them or making them available; people start copying comments to
mailing lists which never arrive with the committee (Karl Auerbach's
comment, see the GA list); we have a statement on WHOIS which isn't
linked from anywhere on our own web pages; and so on.

I'm not investing the amount of time I'm currently putting into this
just to then see the committee lose credibility over trivialities
like the availability of decent comment processes and publication
channels.


If the problem is in fact with overworked technical staff, I'm
hereby volunteering to set up the necessary archives elsewhere.

Regards,
-- 
Thomas Roessler                        <roessler@xxxxxxxxxxxxxxxxxx>



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

Privacy Policy | Terms of Service | Cookies Policy