Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-17 Thread Glen Daniels
On 9/17/2010 11:27 AM, Bertrand Delacretaz wrote: > On Fri, Sep 17, 2010 at 5:21 PM, Leif Hedstrom wrote: >> +1 indeed. If not, ATS is in big trouble :). We have a very active community >> in the IRC room, where we brainstorm and help each other out all the time > > I don't think anybody said

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-17 Thread Bertrand Delacretaz
On Fri, Sep 17, 2010 at 5:21 PM, Leif Hedstrom wrote: >  On 09/17/2010 08:20 AM, Benson Margulies wrote: >> >> +1. It's hypocrisy to tell podlings that chat is entirely intolerable >> when plenty of running projects have them. > > +1 indeed. If not, ATS is in big trouble :). We have a very active

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-17 Thread Leif Hedstrom
On 09/17/2010 08:20 AM, Benson Margulies wrote: +1. It's hypocrisy to tell podlings that chat is entirely intolerable when plenty of running projects have them. +1 indeed. If not, ATS is in big trouble :). We have a very active community in the IRC room, where we brainstorm and help each othe

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-17 Thread Urs Lerch
Hi Glen Thanks for your input and a different view. I took the chat channell off the proposal, because I don't want that the project to be assessed on this single point. If a chat is useful for the followers, why not, as long as it is transparent and decisions are not made that way. Best Urs Am

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-17 Thread Benson Margulies
+1. It's hypocrisy to tell podlings that chat is entirely intolerable when plenty of running projects have them. On Fri, Sep 17, 2010 at 9:58 AM, Glen Daniels wrote: > On 9/17/2010 9:41 AM, Urs Lerch wrote: >> To cut a long story short: ALOIS is _not_ about a chat channel, it's a >> tool for secu

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-17 Thread Glen Daniels
On 9/17/2010 9:41 AM, Urs Lerch wrote: > To cut a long story short: ALOIS is _not_ about a chat channel, it's a > tool for security incident and event management. Since the chat channell > in the required resources list was only a wish, I gladly dropped it off > the proposal. Hi Urs, While I cert

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-17 Thread Urs Lerch
Hi To cut a long story short: ALOIS is _not_ about a chat channel, it's a tool for security incident and event management. Since the chat channell in the required resources list was only a wish, I gladly dropped it off the proposal. Best Urs Am Freitag, den 17.09.2010, 07:32 -0400 schrieb Jim J

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-17 Thread Jim Jagielski
I still don't see how that gets around the perception, and the reality, that development is being done outside the list. So I don't see that proposal as helping out at all... On Sep 16, 2010, at 3:27 PM, Scott Deboy wrote: > I understand the concern raised by the use of real-time communication f

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-16 Thread Upayavira
On Thu, 2010-09-16 at 21:32 +0200, Bertrand Delacretaz wrote: > On Thu, Sep 16, 2010 at 9:27 PM, Scott Deboy wrote: > > ...I'm interested in what others think of their proposal for supporting > > real-time communication, and curious what others are doing, if anything, to > > support the growing i

Re: Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-16 Thread Bertrand Delacretaz
On Thu, Sep 16, 2010 at 9:27 PM, Scott Deboy wrote: > ...I'm interested in what others think of their proposal for supporting > real-time communication, and curious what others are doing, if anything, to > support the growing interest in real-time communication between project > participants

Real-time communication (was [VOTE] ALOIS to enter the incubator)

2010-09-16 Thread Scott Deboy
I understand the concern raised by the use of real-time communication for Apache projects - that decisions may be made off-list, and that folks who aren't a party to the real-time communication do not have the opportunity to benefit from or impact the decisions that result from the real-time commun