Return-Path: Delivered-To: apmail-incubator-cxf-dev-archive@locus.apache.org Received: (qmail 77480 invoked from network); 5 Dec 2006 13:44:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 5 Dec 2006 13:44:35 -0000 Received: (qmail 3756 invoked by uid 500); 5 Dec 2006 13:44:43 -0000 Delivered-To: apmail-incubator-cxf-dev-archive@incubator.apache.org Received: (qmail 3732 invoked by uid 500); 5 Dec 2006 13:44:43 -0000 Mailing-List: contact cxf-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cxf-dev@incubator.apache.org Delivered-To: mailing list cxf-dev@incubator.apache.org Received: (qmail 3723 invoked by uid 99); 5 Dec 2006 13:44:43 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Dec 2006 05:44:43 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of Daniel.Kulp@iona.com designates 65.223.216.181 as permitted sender) Received: from [65.223.216.181] (HELO amereast-smg1.iona.com) (65.223.216.181) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Dec 2006 05:44:32 -0800 Received: from amer-ems1.IONAGLOBAL.COM ([10.65.6.25]) by amereast-smg1.iona.com (Switch-3.1.7/Switch-3.1.7) with ESMTP id kB5DhnKB008328 for ; Tue, 5 Dec 2006 08:43:49 -0500 (EST) Received: from [10.59.0.31] ([10.59.0.31]) by amer-ems1.IONAGLOBAL.COM with Microsoft SMTPSVC(6.0.3790.1830); Tue, 5 Dec 2006 08:44:02 -0500 From: Daniel Kulp Organization: IONA To: cxf-dev@incubator.apache.org Subject: Re: [Proposal] CXF weekly IRC chat Date: Tue, 5 Dec 2006 08:43:58 -0500 User-Agent: KMail/1.9.5 References: <9A4696F35B459043970EE4A85A3173900667F9@amer-ems1.IONAGLOBAL.COM> In-Reply-To: <9A4696F35B459043970EE4A85A3173900667F9@amer-ems1.IONAGLOBAL.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612050843.58695.daniel.kulp@iona.com> X-OriginalArrivalTime: 05 Dec 2006 13:44:04.0281 (UTC) FILETIME=[6D9F4A90:01C71873] X-Virus-Checked: Checked by ClamAV on apache.org Jervis, On Tuesday 05 December 2006 01:18, Liu, Jervis wrote: > As our CXF release is finally out of door (well, almost :-)), move forward > to the next milestone, I would like to suggest a CXF weekly IRC chat. A > weekly chat could help to grow the community and get more developers > involved. While several community members already hang out at the IRC it > always remains to be seen who is there at a given point in time. It will > make our community stay focused and being more efficient by making > decisions and discussing major issues when everybody is around. Also for > these new developers, a weekly chat would make it easier to understand the > status of CXF development and what tasks are most appropriate for them to > start with. I have no problem with an IRC chat as long as we're careful with how we use it. However, one sentence above is a concern: "It will make our community stay focused and being more efficient by making decisions..." We CANNOT make decisions on IRC. That is NOT allowed at apache. All decisions must be on the email list. We can have discussions and stuff on IRC, but we need to make sure we use the IRC discussions as just starting points for email discussions as well. For example: if we start discussing a particular topic on IRC, we would then start a thread in the email list with a summary of the discussion (include the log, but also make sure there is a nice summary of the major points). > It is very very hard to find a time good for all, as a compromise I suggest > we initially hold this weekly chat on Monday 10pm Beijing Time, 2pm GMT, > 9am EST, up to one hour. Does this sound good to everyone? I'm OK with that time. > > Any thoughts and comments? Personally, if we limit the chats to status type things, a time to ask questions from others (which we could then put on the wiki if they seem to be FAQ type things), etc..., then I'm OK with it. However, if we start finalizing designs and settling on features and such, then that would be bad as that stuff NEEDS to be on the email list. -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 daniel.kulp@iona.com