Dan Jacob wrote:
The question is: how can we guarantee a stable TurboGears platform even
post 1.0 (or for that matter, 2.0) if we cannot guarantee the stability
of the underlying components ? Should we enforce a "comply or die"
attitude to other projects (if you don't fix your issues, we'll go to
Quixote/Cheetah/whatever) ? I don't think that's very workable, and TG
is having a positive "rising tide lifts all boats" effect on other
projects, but still we are often hamstrung by what happens outside of
TG, something Rails and Django don't have to worry about.
Any ideas ?
Why don't *we* fix the issues? And I don't mean some TG specific hacks
as it is often done now. This approach still embodies the TG philosophy,
one may even say it enriches it as we are actively contributing in code
not just exposure. Even from a purely pragmatical stand-point this is
surely better than to write everything ourselves.
Should maintainers of a given third-party component not accept our
patches or enchantments, than it would be time to consider other options.
Simon
