There are a lot of ways that you can contribute to this project depending on your interests and talents.
- You can register with this site to help us guage interest in mojoPortal. I promise we won't share your email address and we won't spam you.
- You can provide constructive feedback and suggestions for improvements
- You can provide a translation into a new language or help maintain resources for a language as new features are added
- You can design nice skin(s) and contribute them to the project
- You can provide bug reports and/or fixes if you find any
- You can implement features and contribute them to the project
- You can implement improvements to existing features
- You can help with creating documentation and tutorials
- You can help spread the word and promote the project
- You can contribute financial help or sponsor a feature
If you have questions about contributing, please post in the
forum (you must login)
Licensing and Contribution Guidelines
If you contribute features or bug fixes to the code of mojoPortal you must agree that your contribution will be licensed under the same license as mojoPortal, currently the
Common Public License. If you make use of any code not written directly by you please make sure it is under a compatible license and indicate its source of origin. If you have questions about license compatibility please post in the forums and we will try and help. If you implement a feature as an external module it doesn't have to be under the same license as mojoPortal core but must be under at least a compatible open source license for us to include it in the downloads. Of course you are perfectly free to implement external modules under any license even non-open source licenses but we can't include those with mojoPortal. In most cases I would probably be willing to link to your site where you can sell proprietary features under any license you choose.
Development Team Plan
Currently there are only a few people who have commit access to the Subversion repository. Many developers will not need commit access to contribute to the project because they can easily send files or svn patches to be reviewed and commited by the core developers. Those who consistently contribute code that requires little or no modification will be considered for commit access. Often contributors just contribute one feature or a few bug fixes or skins or translations and this can easily be done without commit access. No long term commitment is needed, if you have a feature you would like to implement and contribute your help is most welcome. If you do show continued interest and involvement that is even better but certainly not required. Even small contributions are welcome.
I think the development team will grow organically over time. As we get a few more trusted core developers on the team that I can delegate to help with coordinating contributions from others the process will get more efficient.