Difference between revisions of "How to contribute"
(→Repository structure) |
(→Repository structure) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 29: | Line 29: | ||
* '''master:''' ''last stable release + critical fixes''. It could generate new '''releases'''. | * '''master:''' ''last stable release + critical fixes''. It could generate new '''releases'''. | ||
* '''develop:''' ''last stable release + critical fixes (merged from master) + new (almost stable) features''. It cannot generate new '''releases'''. | * '''develop:''' ''last stable release + critical fixes (merged from master) + new (almost stable) features''. It cannot generate new '''releases'''. | ||
| + | |||
| + | === Release policy === | ||
When the '''codebase''' is considered stable on ''develop branch'', it is merged back to ''master brach'' and a new '''release''' is generated. | When the '''codebase''' is considered stable on ''develop branch'', it is merged back to ''master brach'' and a new '''release''' is generated. | ||
| Line 36: | Line 38: | ||
You are not allowed to upload copyright protected files. You should commit only tested things and should not upload code that does not compile on your own development platform. If you are not sure if things you've developed are running on other platforms please specify in your '''pull request''', so other people get informed and can test it on their platforms. | You are not allowed to upload copyright protected files. You should commit only tested things and should not upload code that does not compile on your own development platform. If you are not sure if things you've developed are running on other platforms please specify in your '''pull request''', so other people get informed and can test it on their platforms. | ||
| − | We can only accept code that is distributed under the | + | We can only accept code that is distributed under the EPL license or a compatible license and assume that your submission is under that (EPL) license if not specified otherwise. |
Latest revision as of 16:52, 6 March 2014
Contents
How to contribute
There are three main channels to contribute to the Horde3D project:
- Forum: contribute to create a friendly community.
- Wiki: help us documenting the project.
- GitHub: use your coding skills to improve the technology.
Report an issue
To report an issue, please use the official Issue Tracker at:
https://github.com/horde3d/horde3d/issues
Become a contributor
To contribute with code, please follow this workflow:
- Fork the project.
- Clone it on your machine.
- Code it!
- Commit & push back to your fork.
- Prepare a pull request.
Repository structure
According to the project vision of to be simple, the official GitHub repository contains two branches:
- master: last stable release + critical fixes. It could generate new releases.
- develop: last stable release + critical fixes (merged from master) + new (almost stable) features. It cannot generate new releases.
Release policy
When the codebase is considered stable on develop branch, it is merged back to master brach and a new release is generated.
Restrictions
You are not allowed to upload copyright protected files. You should commit only tested things and should not upload code that does not compile on your own development platform. If you are not sure if things you've developed are running on other platforms please specify in your pull request, so other people get informed and can test it on their platforms.
We can only accept code that is distributed under the EPL license or a compatible license and assume that your submission is under that (EPL) license if not specified otherwise.
