[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [atlarge-discuss] Re: What am I missing...
J-F C. (Jefsey) Morfin wrote:
(B> Dear Walter,
(B> Joop is one of the few doers among us.
(B> http://icann-at-large.org now includes a page for @large links.
(B> The first link is to the current official site in disarray.
(B> The second one is to the restored forum.
(B> The third one to one to Joop's current site.
(B> Joop could I directly give the forum he http://forum.atlarge.ws address?
(B> You need to support that 3LD in your DNS and Apache confirguation file,
(B> targeting to the icannatlarge.com/forum directory.
(B> As indicated yesterday, everyone with a link to a specific action please
(B> profide a link
(B> I would be glad to link:
(B> - Joanna news site
(B> - Jan's response to ICANN
(B> - a page where Sotiris can report on ALAC
(BI lack a website for which you could provide a link. Consider me as the
(Bclassic "user," for whom the Internet is primarily a source of information
(B(in contradistinction to those who view it primarily as a potential or actual
(Bsource of profit). If you want a link, you will have to provide it yourself.
(BThat said, let me offer a brief "progress report" so that you and others
(Bmight better judge the need for such a link. I became aware of Stuart Lynn's
(B "A Plan of Action Regarding New gTLDs" through a posting on this mailing
(Blist by Sotiris (originated elsewhere by Thomas Roessler). Later I mentioned
(Bmy intent to respond to Lynn via public comment (the public comment period
(Bexpires Dec. 8th and if I cannot meet that, I will not post a comment at
(Ball). Subsequently I read Lynn's "Plan of Action" through and quickly
(Brealized it treated much of its content overly summarily, depending crucially
(Bon the earlier "Final Report of the New TLD Evaluation Process Planning Task
(BForce [NTEPPTF]" published 31 July 2002. I had not been previously aware of
(Bthat earlier document, which had been through a draft, public comment, and
(Brevision process without my knowledge. Therefore, I diverged from addressing
(BLynn's "Plan of Action" and have since taken the time to download (from the
(BICANN website) and read the "Final Report." Although that document in turn
(Breferences much other material, which I have not taken the time to access, I
(Bbelieve that I now understand the issues well enough to respond to Lynn (from
(Ba user's perspective). My intent is to provide a comment via the ICANN web
(Bsite, and to cross-post it here as well. I will do so as an individual, not
(Bas a representative of icannatlarge.org (nor in my opinion can any one person
(Blay claim to that distinction, just yet!).
(BAt this point I can draw a few tentative conclusions. Even though the "Final
(BReport" mentioned above had been through many hands and a revision process,
(Bit contained several annoying typos and inconsistencies, which would have
(Bbeen caught had *any one* of the Task Force members committed him/herself to
(Breading it through *critically* from start to end. (Yes, I am aware that I
(Bam stepping on some toes here. But the guiding principle is, if a person is
(Bwilling to have his/her name on a document, that person should be responsible
(Bfor all it contains.)
(BMore importantly, I regret to say that my time would have been better spent
(Baddressing the "Final Report" rather than the derivative Lynn "Plan of
(BAction." The opportunity was lost through lack of timely knowledge. I
(Blacked perfect diligence, but was not solely to blame. Two persons who
(Bregularly post on this mailing list (one of them *copiously*) had made
(Bcomments to ICANN on drafts of the "Final Report" during the public comment
(Bperiod. But as best as I can recall without going back through our archives,
(Bneither of them had cross-posted their comments here, nor had even mentioned
(Bin a post that such a draft document had been promulgated by ICANN and that
(Bthey intended to respond. Both sets of commentaries were substantive - I'll
(Bcredit them that - but did not address every issue that I would have.
(BThe lesson learned for this organization is that some of ICANN's
(Btime-critical publications are too important to let our members discover for
(Bthemselves. Our website, when we can finally claim to have one that works,
(Bshould provide all necessary links. And until that day, this mailing list
(Bhas to be the medium that informs the membership.
(BTo unsubscribe, e-mail: email@example.com
(BFor additional commands, e-mail: firstname.lastname@example.org