Re: [OAUTH-WG] Implementation Support and Community

Dick Hardt <dick.hardt@gmail.com> Fri, 24 August 2012 03:33 UTC

Return-Path: <dick.hardt@gmail.com>
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 BB6BF21F84BF for <oauth@ietfa.amsl.com>; Thu, 23 Aug 2012 20:33:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.57
X-Spam-Level:
X-Spam-Status: No, score=-3.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 iGOkAYRZTNpp for <oauth@ietfa.amsl.com>; Thu, 23 Aug 2012 20:33:27 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 1F79B21F84B8 for <oauth@ietf.org>; Thu, 23 Aug 2012 20:33:27 -0700 (PDT)
Received: by pbbrr4 with SMTP id rr4so2541813pbb.31 for <oauth@ietf.org>; Thu, 23 Aug 2012 20:33:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=5yXox+19LvBciKAxcsxFq0olp3mBCAy3rGpueKfcm3U=; b=NR8l77hZiZNvrtDysWjHYd07IpId2kQVkWnfcsj2bs9K+8YvJti8U/38NHe+IpW/5S tbXq4lpMJhymoYcJHImJY/ANBI98rFpgdKK6iufcu+UEYcjgkzjDlTk2gCKqPFbpNtLE jqJfT278mOBhRmHT490UtKc9KzZ+04lASHIzKfb6SA00X2A/XLcrNFgqiQtTS4vPIid2 zaUAQDWyxCm577WSWDqvDtn+PmR3WUim4H74bceWB3z0Q72OdQ8WUUaORzoZpRvKQaL7 PVgDeJqD/GOJ/SEKPiHAvdxjyt34daP0ANzWbWo7zzFgFlSz2fV3GpX4/DaIotb67YNX HPIQ==
Received: by 10.68.228.132 with SMTP id si4mr2325252pbc.57.1345779206855; Thu, 23 Aug 2012 20:33:26 -0700 (PDT)
Received: from [10.0.0.91] (c-24-5-69-173.hsd1.ca.comcast.net. [24.5.69.173]) by mx.google.com with ESMTPS id hc10sm426605pbc.21.2012.08.23.20.33.25 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Aug 2012 20:33:25 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\))
From: Dick Hardt <dick.hardt@gmail.com>
In-Reply-To: <50364056.4000400@mitre.org>
Date: Thu, 23 Aug 2012 20:33:23 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <BA909498-90B2-4EDE-B28D-2F4F0D417AFA@gmail.com>
References: <50364056.4000400@mitre.org>
To: Justin Richer <jricher@mitre.org>
X-Mailer: Apple Mail (2.1485)
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [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: Fri, 24 Aug 2012 03:33:27 -0000

+1 to StackOverflow -- that has become the goto source for programming FAQs


On Aug 23, 2012, at 7:38 AM, Justin Richer <jricher@mitre.org> wrote:

> 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 mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth