However he does not maintain the mobile ports.
This lead to the situation where some of my patches are hanging around for 7 months already - without any progress happening.
Furthermore there was talk about setting up a CI build which would improve the code stability/ merge ratio drastically - but unfortunately it went nowhere.
Part of the problem here was that there CI solutions for Bitbucket are rare. Furthermore IMO Bitbucket is generally falling behind as a code hosting platform.
To generate some drive I created a Ogre fork on github which brings the following advantages:
- github being more popular should lead to more drive-by contributions
- better integration of issue tracking and the Wiki
- continuous integration using Travis. Currently only a Ubuntu 12.04 build is done but Android should be easily possible
- continuous testing: Tests are being run for every pull request. (fixed tests so everything is passing)
- github/ git is more flexible in regard to history rewriting which leads to cleaner pull requests
My focus is the default branch right now - even though I also migrated v2-0 and v2-1 as a proof of concept.
To keep the spot on the above issues I plan on accepting pull requests for the fork and merging with Bitbucket.
However I would rather like the whole project being migrated to github. There could be a TorusKnot group consisting of the current maintainers which would serve as an umbrella for Ogre and Ogre related projects like Meshy and Ogitor.
The changes so far are:
- fixed all tests to pass on Linux
- switched documentation to markdown so we get a friendly landing page
- merged my non controversial PRs: #477, #520, #571, #573