Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1EC53200C24 for ; Thu, 23 Feb 2017 12:48:18 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 1D838160B62; Thu, 23 Feb 2017 11:48:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5F300160B50 for ; Thu, 23 Feb 2017 12:48:17 +0100 (CET) Received: (qmail 10748 invoked by uid 500); 23 Feb 2017 11:48:11 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 10729 invoked by uid 99); 23 Feb 2017 11:48:11 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Feb 2017 11:48:11 +0000 Received: from mail-qt0-f179.google.com (mail-qt0-f179.google.com [209.85.216.179]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id BAF131A096C for ; Thu, 23 Feb 2017 11:48:10 +0000 (UTC) Received: by mail-qt0-f179.google.com with SMTP id n21so26100030qta.1 for ; Thu, 23 Feb 2017 03:48:10 -0800 (PST) X-Gm-Message-State: AMke39ngZHy/ExNHuXpgqo4kbA7zZSruPqR6ttkYsybfkRhBGZNURkI9FsET5/A0mXsGNWwh7qorAfsKVl9qVA== X-Received: by 10.237.55.196 with SMTP id j62mr33426164qtb.36.1487850489803; Thu, 23 Feb 2017 03:48:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.55.107.193 with HTTP; Thu, 23 Feb 2017 03:48:09 -0800 (PST) X-Originating-IP: [169.0.102.83] In-Reply-To: References: From: Garren Smith Date: Thu, 23 Feb 2017 13:48:09 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: RFC CouchDB Slack channel To: user , "dev@couchdb.apache.org" Content-Type: multipart/alternative; boundary=001a1141ce0aecbf5e0549312f2f archived-at: Thu, 23 Feb 2017 11:48:18 -0000 --001a1141ce0aecbf5e0549312f2f Content-Type: text/plain; charset=UTF-8 At this stage I only really want to consider slack. If that is successful we can consider other ways of helping the CouchDB community. On Thu, Feb 23, 2017 at 1:06 PM, Martin Broerse wrote: > I am ok with this but would like http://www.discourse.org/ better. This > way > you can google old discussions and advice given will not be lost. See: > https://discuss.emberjs.com/ > > - Martin > > On Thu, Feb 23, 2017 at 8:22 AM, Garren Smith wrote: > > > Hi All, > > > > I would like create a slack channel for the CouchDB community. IRC is > often > > considered a barrier to entry for people wanting to ask questions and > learn > > about CouchDB. Slack is a lot easier and less intimidating to get started > > with. When we do this, we would setup a IRC <-> Slack bridge. So that > > people on slack can communicate to people on IRC. So if you prefer IRC > you > > can still use it. > > > > The best success story for this model is the PouchDB community, they > have a > > slack channel with a bridge that links the IRC channel. And the community > > has really grown significantly since this has been implemented. I know > the > > Hoodie team also has something like this and it has also worked well. > > > > I would like to do the same, with a slack channel with two rooms that > then > > have a bridge back to #couchdb and #couchdb-dev. > > > > Would everyone be ok with this? Could we trial it for 3 - 4 months and > see > > how it goes? > > > > Cheers > > Garren > > > > Apache CouchDB PMC > > > --001a1141ce0aecbf5e0549312f2f--