[OAUTH-WG] Implementation Support and Community
Justin Richer <jricher@mitre.org> Thu, 23 August 2012 14:39 UTC
Return-Path: <jricher@mitre.org>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DEEC321F8497 for <oauth@ietfa.amsl.com>; Thu, 23 Aug 2012 07:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.582
X-Spam-Level:
X-Spam-Status: No, score=-6.582 tagged_above=-999 required=5 tests=[AWL=0.017, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bysoi81uIgSK for <oauth@ietfa.amsl.com>; Thu, 23 Aug 2012 07:39:49 -0700 (PDT)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC3821F847A for <oauth@ietf.org>; Thu, 23 Aug 2012 07:39:49 -0700 (PDT)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 004EF21B06BE for <oauth@ietf.org>; Thu, 23 Aug 2012 10:39:48 -0400 (EDT)
Received: from IMCCAS04.MITRE.ORG (imccas04.mitre.org [129.83.29.81]) by smtpksrv1.mitre.org (Postfix) with ESMTP id DE8F721B06B8 for <oauth@ietf.org>; Thu, 23 Aug 2012 10:39:47 -0400 (EDT)
Received: from [10.146.15.29] (129.83.31.58) by IMCCAS04.MITRE.ORG (129.83.29.81) with Microsoft SMTP Server (TLS) id 14.2.309.2; Thu, 23 Aug 2012 10:39:47 -0400
Message-ID: <50364056.4000400@mitre.org>
Date: Thu, 23 Aug 2012 10:38:14 -0400
From: Justin Richer <jricher@mitre.org>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:14.0) Gecko/20120714 Thunderbird/14.0
MIME-Version: 1.0
To: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [129.83.31.58]
Subject: [OAUTH-WG] Implementation Support and Community
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Aug 2012 14:39:50 -0000
With the core specs basically out the door and seeing wider adoption and publicity, the OAuth community is going to start to get more questions about "how do I do X?", and many of these are questions that have been answered before or seem "obvious" to those of us who have been up to our ears in the spec for the past few years. Nevertheless, these are important questions to support for the wellbeing of the protocol community, but where should they be asked? When the OAuth community lived on a simple Google Group, these kinds of questions make sense. But I'd argue that the IETF list is not really the right place for them. This list, and the IETF in general, seems to be best suited for *building* the protocol, not for the *use* and *support* of said protocol once it's built. The problem is that, as of right now, we don't have anywhere to point people where they could get a "real" answer. This opens a larger question of who might "sponsor" or "host" such a community. Anything like that needs moderators, and more importantly, needs experts willing to answer the questions. Some options I can think of: - Revive the google groups list for these kinds of questions/discussions - Start a new list/forum, linked to oauth.net - Point everyone to StackOverflow with an "oauth" tag -- Justin (who is not volunteering himself to host or moderate the group)
- [OAUTH-WG] Implementation Support and Community Justin Richer
- Re: [OAUTH-WG] Implementation Support and Communi… John Bradley
- Re: [OAUTH-WG] Implementation Support and Communi… Eve Maler
- Re: [OAUTH-WG] Implementation Support and Communi… John Bradley
- Re: [OAUTH-WG] Implementation Support and Communi… Igor Faynberg
- Re: [OAUTH-WG] Implementation Support and Communi… Dick Hardt