Tryton vs. ERPnext

I may understand that our tools are not the usuall one but we use them because people that regualiry commit on the project prefer them. We are not gonna change it and we found that this is not really a problem for people that want to contribute.

Having said that I’m always happy to help somebody with the contribution process, so feel free to ask on our forum and we will provide as much as help as possible.

If you plan to contribute to our documentation and you do not want to deal with or tools I offer myself as bridge between them. In order to do so please create the files following our guideliness, delivery them to my PM box and I will upload to our review process.

Please note that reviewing all the patches that should be included takes time. We can not avoid reviewing patches without lowering our quality. IMHO lowering the quality is not something that will benefit the project.

Having said that, if you want to speed up the process please join the review process.

There is a Third Party Modules category in this module where everyone can share their extensions.

Also there is a Tryton Framework classifier on PyPI which contains oficial and “contributed” extensions.

Personally I prefer to discuss all the features with the tryton community and try to integrate them with the project. Altought this is harder on the short term it produces more benefits on the long.