The Ogre code suppository -> https://bitbucket.org/ogreaddons
HipChat room: http://www.hipchat.com/gal7YYRu4
What is it?
It is a collection of useful Ogre projects that has fallen without a steady maintainer.
The old ogreaddons repository on Sourceforge uses SVN and it is cumbersome to contribute the odd patch. We need something a bit more distributed.
Instead of letting code rot or scatter all around the globe, it would be nice to group those projects together as separate repositories under the care of the Bitbucket team 'OgreAddons'.
OK. Ogitor will be moving their dependencies out of their main repository into separate repositories to keep the main repository clean and tidy, and instead use CMake External Projects to automatically pull down the code and build it out of source (see below).
We know that several of those dependencies seems to be the only actively maintained copies left, so instead of putting the dependencies up under Ogitor Team, we thought: why not put into a new OgreAddons collection so that it can become easier to contribute improvements back to them without having to grab Ogitor?
Fork, improve, issue pull requests or even ask to get developer access so that you can help yourself.
It should be easy to contribute the occasional fix, without taking full on responsibility.
The OgreAddons team is open, if you want developer access then shout.
OgreAddons is supposed to be maintained by the Ogre Community, that is you.
There are currently 39 projects under the OgreAddons 'umbrella'.
- TechnoFreak animation blend editor
- Ogre Debug Drawing Utility
Only projects which have been without maintainer is eligible for addition to the OgreAddons code suppository.
Border cases can be created as a fork of the original, making it possible to issue pull requests against the original repository.
Repository Donations Accepted
It is possible to transfer your repository to the OgreAddons user, or one of the OgreAddons team, if you happen to have no time to tend to it.
Note: This page will be updated as things develop.
original topic below
I just checked out ogreaddons from Sourceforge..
Man, there's just so much code in there!
It's very depressing to see that the code just sits there and rots away..
I've been thinking of creating an OgreAddons team at Bitbucket and add some of the projects to it, without repository history (because it's in the old Sourceforge repository) for simplicity.
If the OgreAddons team creates the repositories it would be one repository per project and still collected in the OgreAddons 'namespace'.
It would be much easier for people to fork and issue pull requests and even step up as maintainers.
What do you think?
We really don't have an active collection of OgreAddons projects atm.