Am 30.06.2011 13:45 schrieb Mengu:
it would be awesome if we knew how mark and his team made sourceforge scale.
Mark explained it a bit in his EuroPython talk: http://ep2011.europython.eu/conference/talks/a-python-takeover
how can we make people use turbogears? 1) code side - making it perform way much better.
Agreed, and one of the first things we need to do is write a benchmark suite to monitoring the performance as we continue to develop TG. But anyway, I do not think performance is really such a big issue for the majority of us, and Chris Perkins has already worked on the performance in 2.1. Where actually do you perceive performance issues?
- much more nice and clean docs and api docs. - docs should be clear as hell, not complicated, not too long.
Right. If we make the docs too exhaustive, this may also slow down the development because we must always adapt the docs. I already see this happening with Pyramid which has really extensive docs. Crisp, concise docs are what we need for TurboGears. And we don't need to document parts which are already document very well, like SQLAlchemy. Just some introductory words, links to the original docs, and short explanation of the TG integration and usage.
i'm making a commitment to make a screencast series for turbogears like mark and kevin did. i still enjoy kevin's wiki 20 screencast on showmedo. i will build up an application and record it. i'll bother you guys on both irc and the list with my questions. i also would like to get my feet wet with the code however i am not virile enough for that, yet. though i would like to close some tickets.
Great, thanks for jumping in! -- 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.
