In a PyCon 2010 Talk, Tres Seaver pointed out some lessons learned when
developing repoze.bfg, which I think are also applicable to TurboGears:
* Reuse can be overvalued, because it comes with some cost
(we already experienced this)
* Test coverage necessary, but not sufficient
(functional/integration testing)
* Make measurements easy and obvious
("Speedometer" in page header - sounds like a good idea)
* Documentation hurts so good
(our own documentation, require docs for all dependencies)
You can watch the video here: http://pycon.blip.tv/file/3263959/
Quick forward to minutes 17-22 for this passage.
Concerning functional/integration testing, it would be good to have some
small demo/reference applications, using all available features
(particularly stuff like i18n that's often neglected), and it should be
possible to test all of these apps in one go.
-- Christoph
--
You received this message because you are subscribed to the Google Groups
"TurboGears" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/turbogears?hl=en.
