|| ||Asa Dotzler <asa-AT-mozilla.com> |
|| ||dev-planning-AT-lists.mozilla.org |
|| ||Re: Improving Firefox should not cause regressions in other
|| ||Mon, 17 Oct 2011 11:36:05 -0700|
|| ||Article, Thread
Kai Engert wrote:
> Our core Mozilla platform code contains general purpose code that is
> used across multiple applications, for example the code around SSL.
> In my opinion, when trying to improve Firefox, it's not acceptable to
> modify code in a way that creates regressions for other major Mozilla
> applications such as Thunderbird.
> Instead, the developer seeking to improve Firefox shall find solutions
> that (at least) keeps the existing functionality used by other
> Do you agree with this general directive?
I don't agree with this directive.
I'm not advocating breaking other apps for "no good reason", but moving
faster and making bigger strides in Gecko and Firefox development is
"good reason". These are the big levers the Mozilla project has in
advancing the Mozilla Mission. They will become less effective over time
if we do not move faster and smarter with both of them.
And so, I'm very uncomfortable with a directive that puts key Mozilla
Gecko and Firefox contributors in the position of having to maintain
code or features which are not absolutely necessary to the successes of
the Gecko and Firefox products.
to post comments)