[ietf-nomcom] Fwd: Comments For I-D: draft-moonesamy-nomcom-eligibility-00
Abdussalam Baryun <abdussalambaryun@gmail.com> Sat, 29 June 2013 11:27 UTC
Return-Path: <abdussalambaryun@gmail.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 499BE21F9FE2 for <ietf-nomcom@ietfa.amsl.com>;
Sat, 29 Jun 2013 04:27:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No,
score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599,
NO_RELAYS=-0.001]
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 G+K6h7+u5FAK for
<ietf-nomcom@ietfa.amsl.com>; Sat, 29 Jun 2013 04:27:09 -0700 (PDT)
Received: from mail-pa0-x236.google.com (mail-pa0-x236.google.com
[IPv6:2607:f8b0:400e:c03::236]) by ietfa.amsl.com (Postfix) with ESMTP id
4664821F9FDF for <ietf-nomcom@ietf.org>; Sat, 29 Jun 2013 04:27:09 -0700 (PDT)
Received: by mail-pa0-f54.google.com with SMTP id kx10so3372117pab.13 for
<ietf-nomcom@ietf.org>; Sat, 29 Jun 2013 04:27:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:cc:content-type;
bh=6J4+8Y+t7ydlBwgi7ymYU+vIOdu5n9Qi9DtXCavk6cI=;
b=HuzejK5RvQPnEZ9mrDIaMAEtisXSj/yXAxZ/g8wtqQbHT/VbLevZqbr79qw2Krqf3L
9DShPYUFnVpeuTnw7c1g3LvWuluxLkrSS5El8774XU7rnIjUiOA3Ct1XdLxbGUBTxbnJ
CIcQhlqwThKNvQxRUfuA1EdvNy6Gbp/rYB09bzxNideDXH4bgSxBj0RKKPxexVxLwZz4
eB5nBMR45uejoMPNL875HlgTISZkQSdPjB2hPDE3k0PW7/BuqWiUakX+GaSgAivuNuVd
SLZm9haCxKbOF2G35olpnb6ToZlDL+wjeVvh7IGsREVSaVbqONSZcxsxLPdxYu6MqVyL V3cQ==
MIME-Version: 1.0
X-Received: by 10.66.221.101 with SMTP id qd5mr15371740pac.174.1372505228564;
Sat, 29 Jun 2013 04:27:08 -0700 (PDT)
Received: by 10.68.250.133 with HTTP; Sat, 29 Jun 2013 04:27:08 -0700 (PDT)
Date: Sat, 29 Jun 2013 13:27:08 +0200
Message-ID: <CADnDZ88mTwcmVJQP3mhTzTTkn3fYb7M_=T7g5YxEk2xuPBHSaw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: S Moonesamy <sm+ietf@elandsys.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Fri, 05 Jul 2013 07:28:22 -0700
Cc: ietf-nomcom@ietf.org
Subject: [ietf-nomcom] Fwd: Comments For I-D:
draft-moonesamy-nomcom-eligibility-00
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: Sat, 29 Jun 2013 11:27:10 -0000
Hi Moonesamy, (the Author of draft-moonesamy-nomcom-eligibility-00) I think the draft still needs more details, for example, the Abstract says to give remote contributors eligible to serve but how many remote, it is not-reasonable/not-practical to have most remote, and it is not fare/diverse to have all not remote. Furthermore, you did not mention diversity in the draft related to members selected. AB> I prefer if you refer me, or the discussion list chair can refer me to somewhere we can discuss this new draft. Please note that I was told not to post more discuss messages on this list, so the chair or you are required to respond on this issue related to discussing the draft, because this may be my last post regarding this I-D. AB> the update may need an informational draft (or better introduction) like what [1] is doing, so if we know the information on process challenges we will know the best practice. I like the [1] draft I think it needs to be renewed including remote members possibilities. [1] http://tools.ietf.org/id/draft-crocker-nomcom-process-00.txt AB> you need to define *remote contributor* in the draft. When the authors define it then I can amend or edit. You need to mention that most of meeting of IETF per year are in one region which makes some from other regions to contribute remotely. Section 2> The section is not reasonable because you changed with no strong reasons. Why you want to change totally, I recommend to add idea not change. As to give opportunity to additional memebrs that are remote. These additional memebrs will have a special condition. This way you don't change the conditions for the current procedure of selecting f2f memebrs, and you may limit the number of remote contributors maybe 10 % of the total memebrs. AB> suggest in Section 2> I suggest not to update the text of the RFC but to add new rule for selecting few remote participants. AB> you need to add what are the remote memebrs responsibilities, because they may be similar or different than the other memebrs. my answers to your questions below, On Fri, Jun 28, 2013 at 1:50 AM, S Moonesamy <sm+ietf@elandsys.com> wrote: > > Hi Abdussalam, > > > Thanks for explaining why you support the draft. I am going to list some questions. Please read them as points to consider. There isn't any obligation to provide comments. You mean the draft should consider, > > - What is your opinion about helping the "pie get larger"? No we don't want things to get larger for others to eat, we want things to get smarter for others to use, share, and develop equally. > > > - What would be an acceptable way of determining whether someone > has been contributing to the IETF over a period of five meetings? Where are the five meetings (is it a f2f meeting?)and what kind of contributing you are asking? > - Dave Cridland suggested that working groups provide a smallish set of > volunteers each for the selection process. Is it okay to leave it > to the working group chair to make the decision? <I will send you discusses/answers offline> I really want to focus questions related to the new draft not other issues. Therefore, I think the draft needs to involve what was discussed on the list (feedback). Updating this RFC procedure may need more reasons than what was presented in the draft, I think it is nice if you add more and change info to renew this draft for more further discusses. Thanks. AB
- [ietf-nomcom] Fwd: Comments For I-D: draft-moones… Abdussalam Baryun