<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: NomCom nonsense continues</title>
	<atom:link href="http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/feed/" rel="self" type="application/rss+xml" />
	<link>http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/</link>
	<description>An infuriatingly infrequently updated reflection on the Internet, the US, and life in general</description>
	<lastBuildDate>Sat, 13 Feb 2010 07:16:55 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kieren</title>
		<link>http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/comment-page-1/#comment-10513</link>
		<dc:creator>Kieren</dc:creator>
		<pubDate>Thu, 07 Dec 2006 17:40:02 +0000</pubDate>
		<guid isPermaLink="false">http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/#comment-10513</guid>
		<description>Hi Vittorio

I&#039;m not claiming there is some grand conspiracy. I am despairing at everyone agreeing that the system has to change and then blindly continuing on with the exact same process.

I don&#039;t think people realise when they themselves are contributing to an aura of unnecessary secrecy and opaqueness by making decisions without wider review, without saying they are making the decision, when, how, why and then not making those selections public.

Now the NomCom goes out of its way to remain what it sees as uninfluenced but any reasonable observable outside the process sees as unduly secretive. 

But by making a decision about who will serve on the NomCom when it is completely unnecessary to decide at that moment; when the process is up for review; and when the last year&#039;s NomCom hasn&#039;t even reported, is either incredibly unthinking or highly suspicious.


Kieren</description>
		<content:encoded><![CDATA[<p>Hi Vittorio</p>
<p>I&#8217;m not claiming there is some grand conspiracy. I am despairing at everyone agreeing that the system has to change and then blindly continuing on with the exact same process.</p>
<p>I don&#8217;t think people realise when they themselves are contributing to an aura of unnecessary secrecy and opaqueness by making decisions without wider review, without saying they are making the decision, when, how, why and then not making those selections public.</p>
<p>Now the NomCom goes out of its way to remain what it sees as uninfluenced but any reasonable observable outside the process sees as unduly secretive. </p>
<p>But by making a decision about who will serve on the NomCom when it is completely unnecessary to decide at that moment; when the process is up for review; and when the last year&#8217;s NomCom hasn&#8217;t even reported, is either incredibly unthinking or highly suspicious.</p>
<p>Kieren</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vbertola</title>
		<link>http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/comment-page-1/#comment-10501</link>
		<dc:creator>vbertola</dc:creator>
		<pubDate>Thu, 07 Dec 2006 16:34:28 +0000</pubDate>
		<guid isPermaLink="false">http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/#comment-10501</guid>
		<description>Kieren, as much as I share some of your points about the NomCom process being too secretive and intransparent (I think you could find public documents of mine dated 2002, with points on that), who appoints the NomCom members is one of the most clear things in it - it is clearly defined by the ICANN Bylaws.
Specifically, Michael Froomkin was appointed by us (the ALAC) last year, and we confirmed him again for next year. We appoint five members, one per each ICANN Region (and Michael, obviously, is for North America).
Thanks,</description>
		<content:encoded><![CDATA[<p>Kieren, as much as I share some of your points about the NomCom process being too secretive and intransparent (I think you could find public documents of mine dated 2002, with points on that), who appoints the NomCom members is one of the most clear things in it &#8211; it is clearly defined by the ICANN Bylaws.<br />
Specifically, Michael Froomkin was appointed by us (the ALAC) last year, and we confirmed him again for next year. We appoint five members, one per each ICANN Region (and Michael, obviously, is for North America).<br />
Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kieren</title>
		<link>http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/comment-page-1/#comment-10442</link>
		<dc:creator>Kieren</dc:creator>
		<pubDate>Thu, 07 Dec 2006 09:01:55 +0000</pubDate>
		<guid isPermaLink="false">http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/#comment-10442</guid>
		<description>I think was a reasonable assumption from what you wrote Michael, but my point wasn&#039;t whether you were chosen yesterday or in November - and it most certainly wasn&#039;t that you personally had been chosen - it was that the members for next year&#039;s NomCom had already been decided.

Just another mysterious decision taken by someone, somehow, not relayed to anyone except those in the group, not posted anywhere publicly. When everyone knew the NomCom was due to be reviewed, this smacks of a fix rather than business as usual.

But, yes, of course I will correct my posts.


Kieren</description>
		<content:encoded><![CDATA[<p>I think was a reasonable assumption from what you wrote Michael, but my point wasn&#8217;t whether you were chosen yesterday or in November &#8211; and it most certainly wasn&#8217;t that you personally had been chosen &#8211; it was that the members for next year&#8217;s NomCom had already been decided.</p>
<p>Just another mysterious decision taken by someone, somehow, not relayed to anyone except those in the group, not posted anywhere publicly. When everyone knew the NomCom was due to be reviewed, this smacks of a fix rather than business as usual.</p>
<p>But, yes, of course I will correct my posts.</p>
<p>Kieren</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Discourse.net</title>
		<link>http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/comment-page-1/#comment-10408</link>
		<dc:creator>Discourse.net</dc:creator>
		<pubDate>Thu, 07 Dec 2006 02:55:55 +0000</pubDate>
		<guid isPermaLink="false">http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/#comment-10408</guid>
		<description>&lt;strong&gt;Off to Brazil...&lt;/strong&gt;

I don&#039;t usually blog about ICANN here -- I save that for ICANNWatch, but the next few days may be an exception, as I&#039;m going to Sao Paulo for the second half of the ICANN meeeting, which will be followed by a NomCom meeting. It&#039;s seems I&#039;ve been re...</description>
		<content:encoded><![CDATA[<p><strong>Off to Brazil&#8230;</strong></p>
<p>I don&#8217;t usually blog about ICANN here &#8212; I save that for ICANNWatch, but the next few days may be an exception, as I&#8217;m going to Sao Paulo for the second half of the ICANN meeeting, which will be followed by a NomCom meeting. It&#8217;s seems I&#8217;ve been re&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Froomkin</title>
		<link>http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/comment-page-1/#comment-10406</link>
		<dc:creator>Michael Froomkin</dc:creator>
		<pubDate>Thu, 07 Dec 2006 02:37:44 +0000</pubDate>
		<guid isPermaLink="false">http://kierenmccarthy.co.uk/2006/12/06/nomcom-nonsense-continues/#comment-10406</guid>
		<description>I did NOT blog that I was informed yesterday that I was selected.  This is  total distortion of what I wrote.  I blogged that I was leaving for Brazil yesterday, which I was, and explained that the reason I was going was that I was on the nomcom again.  

I was informed of my selection several weeks ago, which is how I had time to book the ticket, arrange for accommodations, etc.

Please correct your blog post here and elsewhere.</description>
		<content:encoded><![CDATA[<p>I did NOT blog that I was informed yesterday that I was selected.  This is  total distortion of what I wrote.  I blogged that I was leaving for Brazil yesterday, which I was, and explained that the reason I was going was that I was on the nomcom again.  </p>
<p>I was informed of my selection several weeks ago, which is how I had time to book the ticket, arrange for accommodations, etc.</p>
<p>Please correct your blog post here and elsewhere.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
