Como se unir ao Time do ProcessMaker
|
|
Do you think ProcessMaker is a great product and you would like to contribute? We need you!
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:
Contents |
Development
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 contact Amos at amos@colosa.com.
Translation
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 for more information, or contact amos at amos@colosa.com. Be sure to download, fill out, and send us a Contribution License Agreement first.
Forum
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.
Documentation
Another area where you can help enrich ProcessMaker is documentation. Our wiki is open for editing by the public, and we encourage you to register and chip in with more documentation in areas where our documentation may be weaker. Please contact Amos amos@colosa.com for more information on contributing to our wiki.
Reporting bugs
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. For more information, visit Reporting issues.
