[apps-discuss] How we decide (was: Re: Call for Adoption draft-ordogh-spam-reporting-using-imap)
John C Klensin <john-ietf@jck.com> Sat, 12 May 2012 14:44 UTC
Return-Path: <john-ietf@jck.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1987A21F86D5 for <apps-discuss@ietfa.amsl.com>; Sat, 12 May 2012 07:44:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.529
X-Spam-Level:
X-Spam-Status: No, score=-102.529 tagged_above=-999 required=5 tests=[AWL=0.070, 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 TbZt8vITbmlM for <apps-discuss@ietfa.amsl.com>; Sat, 12 May 2012 07:44:54 -0700 (PDT)
Received: from bsa2.jck.com (bsa2.jck.com [70.88.254.51]) by ietfa.amsl.com (Postfix) with ESMTP id 1540B21F86CF for <apps-discuss@ietf.org>; Sat, 12 May 2012 07:44:54 -0700 (PDT)
Received: from [198.252.137.7] (helo=PST.JCK.COM) by bsa2.jck.com with esmtp (Exim 4.71 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1STDTf-000293-Kq; Sat, 12 May 2012 10:39:23 -0400
Date: Sat, 12 May 2012 10:44:46 -0400
From: John C Klensin <john-ietf@jck.com>
To: Barry Leiba <barryleiba@computer.org>, apps-discuss@ietf.org
Message-ID: <5F7401D1EDD86FC7ECE491BC@PST.JCK.COM>
In-Reply-To: <CAC4RtVAphPhn4HpCkn6=bYcpjV7OPRmx3zMNLiTkffSWjhLgGQ@mail.gmail.com>
References: <9452079D1A51524AA5749AD23E00392811ECBB@exch-mbx901.corp.cloudmark.com> <6.2.5.6.2.20120511165259.09522610@resistor.net> <CAC4RtVAphPhn4HpCkn6=bYcpjV7OPRmx3zMNLiTkffSWjhLgGQ@mail.gmail.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Subject: [apps-discuss] How we decide (was: Re: Call for Adoption draft-ordogh-spam-reporting-using-imap)
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 12 May 2012 14:44:55 -0000
--On Saturday, May 12, 2012 09:25 -0400 Barry Leiba <barryleiba@computer.org> wrote: >... > I think AppsAWG is a good way to get attention paid to work > that the Apps community has thought about and decided is worth > doing. Thought and filtering are critical to that, and that's > what's happening in this thread. Barry, I agree, with one qualification. In managing "normal" WGs, we usually try to keep the number of individual "life" issues and documents limited in order to improve workflow management and raise the likelihood that each issue really gets adequately careful attention. Sometimes we do that by charter, sometimes by document and workflow management, but I suggest that, in most cases, WGs who are successful in developing consensus documents and being confident that consensus do so. Looking at this from a personal perspective, the number of active documents in AppsAWG, whether in discussion for adoption, adopted and presumably under development, or in WG or IETF Last Call, is getting hard for me to stay on top of, especially when my other IETF commitments (including to a few WGs I try to follow) and limited time are swamping my ability to keep up, even with documents for which I have direct responsibility. I hope I'm atypical and that others are doing much better, but I do hope that the question of "Given existing commitments, do we have the collective bandwidth among the active people in the applications area to do this well?" is considered along with whether the work is worthwhile, whether we have the expertise, etc. john
- Re: [apps-discuss] Call for Adoption: draft-ordog… Barry Leiba
- Re: [apps-discuss] Call for Adoption: draft-ordog… Cyrus Daboo
- [apps-discuss] Call for Adoption: draft-ordogh-sp… Murray S. Kucherawy
- Re: [apps-discuss] Call for Adoption: draft-ordog… Ned Freed
- Re: [apps-discuss] Call for Adoption: draft-ordog… SM
- Re: [apps-discuss] Call for Adoption: draft-ordog… Ned Freed
- Re: [apps-discuss] Call for Adoption: draft-ordog… John C Klensin
- Re: [apps-discuss] Call for Adoption: draft-ordog… John Levine
- Re: [apps-discuss] Call for Adoption: draft-ordog… Murray S. Kucherawy
- Re: [apps-discuss] Call for Adoption: draft-ordog… Patrik Fältström
- Re: [apps-discuss] Call for Adoption: draft-ordog… Ned Freed
- Re: [apps-discuss] Call for Adoption: draft-ordog… John C Klensin
- Re: [apps-discuss] Call for Adoption: draft-ordog… John R Levine
- [apps-discuss] How we decide (was: Re: Call for A… John C Klensin
- Re: [apps-discuss] Call for Adoption: draft-ordog… Dave Crocker
- Re: [apps-discuss] Call for Adoption: draft-ordog… Ned Freed
- Re: [apps-discuss] Call for Adoption: draft-ordog… Dave Crocker
- Re: [apps-discuss] Call for Adoption: draft-ordog… John R Levine
- Re: [apps-discuss] Call for Adoption: draft-ordog… Dave Crocker
- Re: [apps-discuss] Call for Adoption: draft-ordog… Ned Freed
- Re: [apps-discuss] Call for Adoption: draft-ordog… Ned Freed
- Re: [apps-discuss] Call for Adoption: draft-ordog… Ned Freed
- Re: [apps-discuss] How we decide (was: Re: Call f… SM
- Re: [apps-discuss] How we decide (was: Re: Call f… Murray S. Kucherawy
- Re: [apps-discuss] How we decide (was: Re: Call f… SM
- Re: [apps-discuss] Call for Adoption: draft-ordog… Alessandro Vesely
- Re: [apps-discuss] How we decide (was: Re: Call f… Murray S. Kucherawy
- Re: [apps-discuss] Call for Adoption: draft-ordog… Ned Freed