On Thu, 5 Feb 2009 21:20:16 +0100, "Linus Tolke" <[email protected]> said: > Hello Thomas! > > Your wishes of having decisions communicated looks very simple. There > is, > however, a method problem in that we don't have any structure for making > this kind of decisions. > > Do you have any ideas on how we should decide such things? Shall we > appoint > someone to do it?
Hi Linus, I think that this would have to be your role as project leader. I think that the project leader should: - listen to the suggestions from the different parties on the dev lists - listen to the needs and requests from the users - be aware of the skills available amongst the current developers - be aware of how long the given tasks might take - be aware of what benefit(s) the tasks might offer then make a decision on which general areas we should be working on, whether that's UML2 support, fixing existing bugs, changing the colour scheme or whatever. Clearly, moving in any direction depends on people being willing and able to do the work, which means that the decisions must be made carefully, and may not be easy. A consensus should be aimed for, but if not possible, (in my opinion) the decision lies with Linus (even if the decision is to defer the final decision to a later date!). I notice that http://argouml.tigris.org/members/project_members.html does not define the leader's role, so perhaps it needs updating. Regards, Dave P.S. [Sorry for limited work on the P2 issues lately - both of my computers are broken atm - currently reading my email while booted from SystemRescueCD!]
