Project Management

[PhilipLB]

Hi,

I just read the Ogre 1.9/2.0 thread and it came into my mind, that some more/stricter project management would be nice. What is already there?
- Mantis
- The (outdated) roadmap stuff in the Wiki
- An internal forum (?)

What I propose here is to use some better tools. Mantis is actually not bad if used properly (with nicely maintained roadmap and changelog). But there is more. Jira [1] is basically almighty and offers a free open source license [2].

The other thing needed (beside Jira or still Mantis) would be someone who intensivly maintains the roadmap and the tickets.

[1] http://www.atlassian.com/software/jira/overview
[2] http://www.atlassian.com/software/views ... se-request

[CABAListic]

I had been thinking about replacing Mantis and the SourceForge tracker with a unified solution, as that would ease tracker maintenance and reduce some overhead, I think. I don't know Jira, but another free alternative might be TheBugGenie.

[PhilipLB]

Jira is widely used. Basically all companies I worked for are using it.

// Edit: Just found this nice list. http://www.atlassian.com/company/customers?tab=jira

[Wolfmanfx]

Jira is super with bamboo and other useful stuff - and the best thing that maybe steve could help to get something for free

[spacegaier]

I had been thinking about replacing Mantis and the SourceForge tracker with a unified solution, as that would ease tracker maintenance and reduce some overhead, I think. I don't know Jira, but another free alternative might be TheBugGenie.

Yes, we definitely should get a unified solution. Makes the job easier for everyone! Don't know Jira either, but with those references, we cannot go wrong .

[jacmoe]

I wrote Bugitor for Ogitor because none of the existing solutions fit the bill.

[iFire]

What do you think of https://www.jetbrains.com/youtrack/?

[Mind Calamity]

What do you think of https://www.jetbrains.com/youtrack/?

That buy thing... It really is a problem when it comes to opensource projects, since they tend to stay away from anything not opensource/free.

[Transporter]

There is no need for a new tracker tool, because the old one of sourceforge is not used. Have a look at the patch queue at the tracker! There are a few patches where nobody is working on. If you don't like a patch you can reject and close it.

I've put there two patches to add Softimage 2013 support and fix a LOD problem in the XSI exporter. Both patches are changing only 4 lines of code in 3 files, but nobody is interested in.

It looks like the main problem is missing man power. There are only a few people developing ogre without enough time to check everything.

[andrewfenn]

Bitbucket has a bug tracker already why give yourselves more work by having to admin yet another service when you can just tick the "enable issue tracker" option on sinbad's ogre branch..

[Wolfmanfx]

Manpower is always a problem but there is no clear responsibility or separation who is responsible for what.

Patch tracker processing is really a hard job you have to judge if your 3 lines will break a standard behavior - i mean steve did this stuff on sundays a few years ago and i can remember that he rewrote patches often (so he put brain power into patch processing).

So i do not know who will step up and take care of this stuff (patch processing) because its pure work (i mean this task has to be done at least once a week because people who contribute gets frustrated when nobody is taking care of their patches also they can get the wrong picture of ogre like its unmaintained )

[Klaim]

Bitbucket has a bug tracker already why give yourselves more work by having to admin yet another service when you can just tick the "enable issue tracker" option on sinbad's ogre branch..

I don't know for patches, that would be good I guess, but for issues maybe bitbucket tracker is a bit too simple. Depends on what the issue workflow of Ogre team is.

That said, as it's an open source software, Ogre team can get a free Jira licence in combination with bitbucket (that are both in the same company now) so it would put everything with power tools on the same system.

I think it would be the easiest solution to have everything in one place, but in the same time I think setting up a Redmine or Trac might be better to keep control of everything, if it was not so much work to setup...

Also they don't provide patch trackers I think. For patches, only bitbucket/github/google-code are better solution than having using the sourceforge thing I think.

[CABAListic]

We're currently planning to install a JIRA instance on our own server to test the system. This could take a couple of days (or weeks), but I'll keep you posted.

[PhilipLB]

Maybe it's an option to ask atlassian whether they could host an instance? At least they offer such a service. No clue if for OpenSource projects, too.

[CABAListic]

They do, but I generally like to keep things local and under our own control where feasible

[Klaim]

I agree with Cabalistic, it can be problematic to host such a thing in another company.

For repositories it's not the same as it's easy to have duplicates everywhere.