Re: [PDO] Unanswered questions (was Re: [PDO] Re: PDO 2: Request for Comments)

Hi David,

> In a previous post, someone said that in these situations only Wez had
> commit access (in addition to the ClA'ed folks) and he was too overloaded
> to make all the necessary fixes. Maybe we're talking about different
> situations?

That was me talking about PDO_ODBC, where for a very long time Wez was the 
_only_ person with CVS access because he was 'saving' it for IBM on the 
understanding that they were likely to take over that code. IBM eventually 
decided to go their own way and opened up PDO_IBM, which is CLA'd but not 
core. Wez then re-opened PDO_ODBC access to all - but after two years of it 
being 'marked territory', nobody noticed that move. That situation led to 
this exchange only a few weeks ago: 
http://marc.info/?t=119799235600001&r=1&w=2. You'll notice we had the SEP 
syndrome (Somebody Else's Problem) all of a sudden - and this for a core 
module.

We've also seen the entire PHP build broken by a CLA'd module because 
someone committed their changes and then signed off for the weekend, tho' 
I'm unable to find any record of that at present (probably someone mentioned 
namespaces on-list the same weekend or something). That just doesn't happen 
in OSS... PHP users don't stop at weekends, and nor does anybody else 
involved with PHP. However that was a situation where there were indeed 
'significantly more developers working on that code on a day-to-day basis', 
it's just that when you're talking about paid development 'day-to-day' 
generally means 'Monday-to-Friday'.

So yes, we've had different situations, and none of them have been positive 
when it comes to core modules.

- Steph