Andreas Franke wrote:

> Gervase Markham wrote:
> 
> 
>>Architecture
>>------------
>>All the key APIs should be frozen. This definitely includes all APIs, like
>>Plugins and OJI, likely to be written to by third parties. [...]
>>
> 
> There are areas where third parties are unable to
> contribute because APIs don't even exist yet.
> There are even situations where module owners
> - with the support of [EMAIL PROTECTED] -
> are rejecting contributed code for very popular
> enhancements because they are too busy with
> other things that they can't spend their time on
> re-architecting the area in question to create the
> needed APIs, but at the same time refuse any
> non-generic "workaround" solution.
> 
> I think it is necessary to come up with a reasonable
> plan of attack for problems of this kind as soon as
> possible, but certainly before Mozilla 1.0.


A plan of attack? Sure, but lets not get into a situation where new 
things are being pulled in pre-1.0. The number of bugs assigned to 0.9.x 
and 1.0 keeps gradually increasing due to minor features and fixes that 
could be done post-1.0, and this is the time to start weeding those out.

The feature set is generally acceptable right now. There may be some 
unimplemented LDAP functional that corporate users need (I don't follow 
LDAP, sorry) and similar things here and there, but I'm not eager to see 
a lot of stuff added that isn't 4xp.

It's also hard to say no when presented with a real (non-feature) bug, 
but if it's not seriously affecting usability, let it wait. I'm thrilled 
with Mozilla right now, and a lot of people are avoiding it for no other 
reason than lack of a 1.0 version number.
-- 
http://www.classic-games.com/              http://www.indie-games.com/
I've often thought intelligence agencies should recruit idiots, as
idiots seem able to infiltrate any group in large numbers.


Reply via email to