Hi, I agree with Dave that it's the project leader's task. In our project where the project culture forbids that decisions are made by one person, I'd suggest that the project leader coordinates the group decisions. This means:
- identify the need of a decision (e.g. about the next release, the processes, coding standards, money, and last but not least strategic topics) - coordinate/moderate a discussion on this list or elsewhere - collect the statements of every active team member, if necessary then in a one-on-one email exchange - decide about the result -> pre-decision made and communicated - communicate a time frame for comments/protests - declare and publish the finalized decision This might be a possible decision process without any tool dependency. Of course one could introduce a polling system or something like that, but it's up to the project leader. Thomas -------- Original-Nachricht -------- > Datum: Thu, 05 Feb 2009 22:53:32 +0000 > Von: Dave Thompson <[email protected]> > An: [email protected] > Betreff: Re: [argouml-dev] reminder for the need of planning > > 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!] -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01 ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=1111382 To unsubscribe from this discussion, e-mail: [[email protected]].
