Re: [ietf-nomcom] Nominating Committee Process: Eligibility - draft-moonesamy-nomcom-eligibility-01
S Moonesamy <sm+ietf@elandsys.com> Tue, 30 July 2013 16:24 UTC
Return-Path: <sm@elandsys.com>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix)
with ESMTP id 3CC1821F95DC for <ietf-nomcom@ietfa.amsl.com>;
Tue, 30 Jul 2013 09:24:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.554
X-Spam-Level:
X-Spam-Status: No, score=-102.554 tagged_above=-999 required=5 tests=[AWL=0.045,
BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com
[127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HLlzDQG9RSCh for
<ietf-nomcom@ietfa.amsl.com>; Tue, 30 Jul 2013 09:24:58 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com
[IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id
609A121F8BE6 for <ietf-nomcom@ietf.org>; Tue, 30 Jul 2013 09:24:57 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.132.63]) (authenticated bits=0)
by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r6UGOe0W019077
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
Tue, 30 Jul 2013 09:24:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010;
t=1375201494; bh=0cH/PiWbVzHjBwl5Aujd/PQfB0PgeyJBmInDRntYww0=;
h=Date:To:From:Subject:Cc:In-Reply-To:References;
b=NuFijv3tLVnuhLKSccJ5nArQ3M9njP0OMMZnQJZc7r0era8/Dixfl0jGGdlTkb00a
mHX5rnHqFpTwOhOjSsLS1+N3Fk4WLP1mUxusvoUfMfOxnw9v38sI6FwsD1O3L9hCIs
q89VQQgw4vagsmbxcpQq+udxR30r38xrmvjd4POw=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail;
t=1375201494; i=@elandsys.com; bh=0cH/PiWbVzHjBwl5Aujd/PQfB0PgeyJBmInDRntYww0=;
h=Date:To:From:Subject:Cc:In-Reply-To:References;
b=N+pnaTGR35cCDZIx2Ss8eR8n/AdLyy428X8tnobGxYTf+FS82pXYCX+9ad1mMuMFP
UJu+ojg3NgEps8O2FXegLkroPUiGWE+iQLtmBxCEH/bz7vvsJh2GpnIM/N+x+AWNiW
+6iuVq08OqeXICJ/M51a2utVPFdOyzJJnDz8YY5A=
Message-Id: <6.2.5.6.2.20130730085204.0d6ca950@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Tue, 30 Jul 2013 09:20:03 -0700
To: Michael Richardson <mcr+ietf@sandelman.ca>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <12009.1375197220@sandelman.ca>
References: <6.2.5.6.2.20130730022629.0b408308@elandnews.com>
<32379.1375179842@sandelman.ca>
<6.2.5.6.2.20130730034456.0d81a700@elandnews.com>
<21977.1375188403@sandelman.ca>
<6.2.5.6.2.20130730072017.0d2397d0@elandnews.com>
<12009.1375197220@sandelman.ca>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] Nominating Committee Process: Eligibility -
draft-moonesamy-nomcom-eligibility-01
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process
<ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>,
<mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>,
<mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jul 2013 16:25:01 -0000
At 08:13 30-07-2013, Michael Richardson wrote: >But, it doesn't even mention document authors, so it's a poor place to get a >list of active people. Either it could be improved, or another thing could >be used. I would like to avoid creating an incentive for more names in the author list. I'll try your suggestion (grep mailbox). > From 1996 until 2005, when my son was born, I was nomcom-eligible by the old >rules. Between 2004 and mid-2012 I was not nomcom eligible. >I certainly was at 15 meetings prior to 2005. >Did I attend 2 meetings in the last 5? >In 2006, I would have remained eligible. >Between 2007 and 2010 I would have remained in-eligible. >(I attended more than half of those remotely, and reviewed lots of IPsec WG >documents, and became involved in ROLL) >In 2011 I was not eligible according to current rules, but I would have been >eligible under your rule 1 meeting earlier. There will be cases, as mentioned above, where a person will not be NomCom-eligible. I do not think that it is not relevant. The previous questions were to try and get a sense of what people consider as making the difference. > > - Will it help people with experience be NomCom-eligible? > >it is better than before, but not significantly. I read "not significantly" as meaning that it does not make the difference between now and what is being proposed. At 08:52 30-07-2013, Spencer Dawkins wrote: >In the meantime, subscribing is never wrong ... I am subscribed. :-) My message triggered an anti-abuse rule. That is why it went to the moderation queue. Regards, S. Moonesamy
- Re: [ietf-nomcom] Nominating Committee Process: E… S Moonesamy
- Re: [ietf-nomcom] Nominating Committee Process: E… S Moonesamy
- Re: [ietf-nomcom] Nominating Committee Process: E… S Moonesamy
- Re: [ietf-nomcom] Nominating Committee Process: E… Spencer Dawkins
- Re: [ietf-nomcom] Nominating Committee Process: E… S Moonesamy
- [ietf-nomcom] Nominating Committee Process: Eligi… S Moonesamy
- Re: [ietf-nomcom] Nominating Committee Process: E… Michael Richardson
- Re: [ietf-nomcom] Nominating Committee Process: E… Eggert, Lars
- Re: [ietf-nomcom] Nominating Committee Process: E… Michael Richardson
- Re: [ietf-nomcom] Nominating Committee Process: E… Michael Richardson
- Re: [ietf-nomcom] Nominating Committee Process: E… S Moonesamy
- Re: [ietf-nomcom] Nominating Committee Process: E… Michael Richardson
- Re: [ietf-nomcom] Nominating Committee Process: E… Michael Richardson