As far as I was concerned I didn't like the lack of organizational structure in the project, which would be provided by milestones and tickets. If there is even a lack of organization and - if there is - if it is a problem, is of course a point where we may disagree.
A fact is, that at the time I brought this up, tickets were hardly used and milestones were not used at all.
As the organization might not look as bad when you are working at Orxonox and regularly meet with everybody else, for somebody from outside of the project it is quite hard to find out more detailed information about Orxonox.
You may argue, that there are no people at the outside of the project, except the student, who again meet regularly each week to discuss and work on Orxonox. Therefore proper organization is useless, time wasting and too complicated.
On the other hand, there might be no outside people exactly because of this lack of transparency. But again, this is a point where we disagree.
Of course you can also argue, that regardless of organization Orxonox is still in a state (or already?) where it is impossible to get a detailed view of the project.
And in the end you may not want everybody to be able to mess up the code.
In a related discussion we came to the question if it makes sense to have a milestone each semester, as the students need to finish their projects anyway and also because the projects of the students often do not complete a state of the game, which should be called a milestone in the development.
Together with the question of sense-making milestoning the question of version numbering came up as well. As we increased the version number every semester since we started again from scratch, we should be at version 0.3. This can also be seen in the rather poorly maintained milestones. Now since we may use the milestones to describe a certain state of the game, the question is how we do the version numbering. And an even more important question: What is the current version? Greenman told me, he does not think that the current state of the game satisfy the version number 0.3. I on the other hand, am not satisfied to call the current state v0.0.
We may discuss this forever and we might never agree completely, but we need some kind of decision.
Maybe that whole thing may be summarized in following questions:
- Do we need a change in organization?
- If yes: How would you handle milestones and the version numbering?