How to join the ProcessMaker Team
Would you like to contribute to ProcessMaker and help make it an even better product? You do not have to necessarily write code! You also could be a tester, translator, supporter or all of the above. There are many ways to contribute to ProcessMaker.
Want to get involved? Here's how you can join the ProcessMaker team:
One of the great benefits of open source software is the ability to leverage the innovations of a community of developers. If you'd like to develop code for ProcessMaker, or you've developed something that you'd like to share with us and the community, we'd love to have your help. Be sure to download, fill out, and send us a Contribution License Agreement first. Check out our Developer Documentation for more information, or send an email to [liliana AT colosa.com].
We're always looking for Community members to translate ProcessMaker to their native languages. If you're interested in contributing to a ProcessMaker translation, visit the Translations page and the how to translate ProcessMaker page for more information, or send an email to [liliana AT colosa.com]. Be sure to download, fill out, and send us a Contribution License Agreement first. Any contributions will be published with the contributor name.
A valuable contribution you can make to the ProcessMaker project is participating in our Forum. All ProcessMaker-related support in the forum is provided by the Community, and your contribution there answering questions makes using ProcessMaker a richer experience for all. Visit http://forum.processmaker.com to chip in.
Another area where you can help enrich ProcessMaker is documentation. Please refer to [liliana AT colosa.com] email if you'd like to contribute ProcessMaker by sending documentation, now we close the public edition because of spam issues, but we will be pleased to receive any kind of documentation missing on our wiki. Any contributions will be published with the contributor name.
More resolved bugs means stronger software. If you'd like to report bugs and help us make ProcessMaker a better product, visit http://bugs.processmaker.com. We appreciate the watchful eye(s) of the community.