Re: [PROPOSAL] Weekly dev@ meetings on IRC

2010-11-19 Thread Jim Jagielski
Hmmm... use of IRC as a development process is not recommended. Even if logged and posted, it still, by its very nature, excludes people due to timezone differences and the like. Occasional uses of IRC (and other more "real-time" events like f2f and hackathons) are OK but rare. Having an "official

IRC

2010-11-19 Thread Wyn Williams
Hello Still following this conversation with interest, IRC is in fact a very powerful tool in open source communities, log on to #plone for instance, a lot of people and developers hang out there every day and answer questions, collaborate with each other and otherwise interact with each other. #p

Re: [PROPOSAL] Weekly dev@ meetings on IRC

2010-11-19 Thread Nick Kew
On 19 Nov 2010, at 13:24, Jim Jagielski wrote: > Hmmm... use of IRC as a development process is not recommended. > Even if logged and posted, it still, by its very nature, excludes > people due to timezone differences and the like. Occasional > uses of IRC (and other more "real-time" events like

Documentation and text processing

2010-11-19 Thread Alan M. Carroll
In the dev meeting there was an agreement that we would use Doxygen for reference and some other text system for more general documents. A concern was the ability to link from the general documentation to the reference (e.g., if an API call is discussed, that should have a link directly to the r

Re: [PROPOSAL] Weekly dev@ meetings on IRC

2010-11-19 Thread Jim Jagielski
On Nov 19, 2010, at 9:38 AM, Nick Kew wrote: > > On 19 Nov 2010, at 13:24, Jim Jagielski wrote: > >> Hmmm... use of IRC as a development process is not recommended. >> Even if logged and posted, it still, by its very nature, excludes >> people due to timezone differences and the like. Occasiona

Re: Next dev meeting: Tuesday 11/30 at 9.30am PST

2010-11-19 Thread Leif Hedstrom
On 11/18/2010 04:19 PM, Leif Hedstrom wrote: Hi all, As per the discussion today, the dev meetings will be held on Tuesdays, at 9.30am PST. Meeting agendas will be set the Monday before (noon). The next such IRC meeting will be held on Tuesday 11/30. Please email me suggestions for topics t

Re: Next dev meeting: Tuesday 11/30 at 9.30am PST

2010-11-19 Thread Wyn Williams
Somewhere an IRC angel wept On Fri, 2010-11-19 at 10:24 -0700, Leif Hedstrom wrote: > On 11/18/2010 04:19 PM, Leif Hedstrom wrote: > > Hi all, > > > > As per the discussion today, the dev meetings will be held on > > Tuesdays, at 9.30am PST. Meeting agendas will be set the Monday before > > (no

Coverity Scan contact person for Apache TS

2010-11-19 Thread Leif Hedstrom
Hi all, I would like to submit a request that Apache Traffic Server gets added to the Coverity Scan system. The first step for their signup process is to agree on a contact person. To speed things up, I'd like to nominate myself as the contact person. Of course anyone else can be nominated

Re: Coverity Scan contact person for Apache TS

2010-11-19 Thread Leif Hedstrom
On 11/19/2010 11:47 AM, Leif Hedstrom wrote: Hi all, I would like to submit a request that Apache Traffic Server gets added to the Coverity Scan system. The first step for their signup process is to agree on a contact person. To speed things up, I'd like to nominate myself as the contact per

Re: Next dev meeting: Tuesday 11/30 at 9.30am PST

2010-11-19 Thread Jim Jagielski
As I said, occasional irc chats, or very *directed and focused* IRC chats are fine... it's the standing ones which are a concern. For example, someone my decide not to bring something up on dev@ because "well, I'll just bring it up at the irc meeting" and so the irc meetings would evolve into the p

Re: [PROPOSAL] Weekly dev@ meetings on IRC

2010-11-19 Thread Igor Galić
- "Jim Jagielski" wrote: > Hmmm... use of IRC as a development process is not recommended. > Even if logged and posted, it still, by its very nature, excludes I believe that rather than posting the logs alone it would make sense to give a summary of what was discussed and what conclusions -

ink_atomic.h to ts/atomic.h ?

2010-11-19 Thread Leif Hedstrom
Hi, what do you all think about moving libinktomi++/ink_atomic.h to ts/atomic.h, and make it part of the public APIs? We'd then also, of course, rename them accordingly, e.g. ink_atomic_swap() -> TSAtomiSwap() ink_atomic_cas() -> TSAtomicCAS() etc. This would be useful I think for

Re: ink_atomic.h to ts/atomic.h ?

2010-11-19 Thread Alan M. Carroll
One problem is that if you move something to public API, you force it to be C compatible, rather than C++ enabled, which impacts internal development. Friday, November 19, 2010, 5:18:26 PM, you wrote: > Hi, > what do you all think about moving libinktomi++/ink_atomic.h to > ts/atomic.h, an

Re: ink_atomic.h to ts/atomic.h ?

2010-11-19 Thread Leif Hedstrom
On 11/19/2010 05:42 PM, Alan M. Carroll wrote: One problem is that if you move something to public API, you force it to be C compatible, rather than C++ enabled, which impacts internal development. Hmmm, I only briefly looked at ink_atomic.h before posting, is there anything in there that is