Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org Received: (qmail 27554 invoked from network); 10 Feb 2006 16:34:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 10 Feb 2006 16:34:28 -0000 Received: (qmail 39347 invoked by uid 500); 10 Feb 2006 16:34:25 -0000 Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org Received: (qmail 39323 invoked by uid 500); 10 Feb 2006 16:34:25 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 39307 invoked by uid 99); 10 Feb 2006 16:34:25 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2006 08:34:24 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of flamefew@gmail.com designates 64.233.162.207 as permitted sender) Received: from [64.233.162.207] (HELO zproxy.gmail.com) (64.233.162.207) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Feb 2006 08:34:23 -0800 Received: by zproxy.gmail.com with SMTP id 8so264952nzo for ; Fri, 10 Feb 2006 08:34:02 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=CmMNNwBbheme80gxJUPKQ+vmNJRIr5FpZwGnx/8UmUiOo0QAptdE658+Oal4X/lUM1l8TKO6MXCO8dKgdJjHDUi6ERQhlGgepvtXGDEGizmVZ0Z5qzOgoBuyfj3Frpb77KoBaxh2RW2GDrmi7HdVYT2tJxv2cbwAmjjhAQGX048= Received: by 10.36.79.1 with SMTP id c1mr2259575nzb; Fri, 10 Feb 2006 08:34:01 -0800 (PST) Received: by 10.36.140.3 with HTTP; Fri, 10 Feb 2006 08:34:01 -0800 (PST) Message-ID: <31cc37360602100834o5cb7c638r487cb85cd766ac68@mail.gmail.com> Date: Fri, 10 Feb 2006 11:34:01 -0500 From: Henri Yandell To: Jakarta Commons Developers List Subject: IRC: #commons ? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N I've been using IRC more recently for various apache channels. It's quite a fun thing to do. Any thoughts on connecting to a #commons at irc.freenode.net? The obvious negative to be listed is the worry that it'll pull important information off of the -dev list and bugs will get answered that won't go onto the -user list's history. The first is easy to fix; we just bear in mind that IRC is just a place to chat for us committers. The second is harder, but I think we can deal with it if it starts to feel like its happening. Another negative is that a minority may be strictly firewalled and unable to contribute. What are the pluses? * #apache is a very active irc channel where lots of httpd questions get answered. I doubt they're even being answered by committers; just knowledgable contributors. * It's superb for the general socialization. Really pulls people together as a community, improving individual and group ties - we can chat, joke, discuss without spamming the hell out of the -dev/-user list. * It brings us into more contact with the user community. This'll help with being aware that we want to offer people committership etc. * Gives the users somewhere else to ask questions. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-dev-help@jakarta.apache.org