Here you will learn how you may contribute to repoze.what, either extending it or fixing issues.
Please feel free to send patches to fix bugs or implement features, but keep in mind that it will take some time to get applied if it doesn’t follow our basic coding conventions. If you can, please include the respective tests too.
Patches should be sent to the Repoze mailing list.
There are no special guidelines to create unofficial plugins, but you are highly encouraged to create plugins under the repoze.what.plugins namespace and contact us once you have at least one usable release (so that we can mention it in the manual).
Official plugins must meet certain requirements:
If you want to turn your repoze.what unofficial plugin into an official one and you are willing to make it meet the requirements above, please propose it after you have at least one usable release (e.g., a beta, a release candidate; not only pre-alphas) – The rate of stillborn Free Software projects is very high, so we prefer to turn a unofficial plugin into an official one if it has ever seen the light.
The basic coding conventions for repoze.what are not special at all – they are basically the same you will find in other Python projects:
However, we have the following additional coding conventions which should be applied in the first beta release of a package at the latest (this is, they are not strictly necessary in alpha releases):