Documentation on how to contribute, what repositories to use, how to send patches or pull requests, etc.
I have a few patches for Jinja2 support on turbogears2, however I'm a bit confused about what repository should I use, how do I send the patch? (to tg-trunk? bug tracker? have my git repo online?). There should be branches for new stuff, for example my jinja patch could not be integrated on 2.1 and would be better for 2.2, without a clear explanation of what to do in the mean time, that just discourages development, should I keep my own branch then? It is a bit obvious that not everyone can just add code to the core turbogears, how do we go about reviewing patches? do we have enough core developers to guide or help newcomers on contributing to turbogears core? Finally turbogears is mostly a glue between many best of breed projects that make it useful, from pylons, toscawidgets, sqlalchemy, repoze, sprox, etc. Most of my delays when developing with turbogears where from "external" projects, the lack of clear documentation on how to use them on turbogears, I often end myself moving from turbogears docs to toscawidgets or sprox site or even looking at the source code of these projects, documentation is perhaps the most lacking aspect of turbogears, it is tiny compared to all the features on turbogears (as a whole), and it is poor. What we can do is encourage documentation development, how do we write more docs? at first is not obvious you have to checkout the docs from the repository and edit the sphix created docs, then we get to the same issue as with source, how do I get my changes merged back? I think there are many passionate users and developers willing to contribute if we had a clear and simple process to get the ball going, even if the code does not get added to mainline branch. My two cents: Documentation Maybe we can work something like the "django book", toss a wiki, add the general outline and let the people fill the sections, while others may review and update the sections for correctness, rinse and repeat until done. Development Provide some guideliness to contribute, the "Extending and Contributing" section of the docs actually says nothing about how to contribute. Open up the development a bit more, have public branches or fast track branches to test newcomers code early and integrate code faster to mainline. Regards, Carlos Daniel Ruvalcaba Valenzuela -- 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.
