On 7/16/05, Ian Collins <[EMAIL PROTECTED]> wrote: > Chaps, > > I've been giving this some thought over the past couple of days and > while I believe this is a worthy effort that should be done, I think it > will flounder unless we organise. > > I propose that this process be run in a similar way to any other > distributed software project I would manage. > > Firstly we have to identify a customer or customer group for the work. > Their role is to identify the requirements (stories) and work with the > rest of the group to prioritise and estimate each one. This will give > us some initial structure, what has to be done and in what order. We > must reach a common understanding before any coding starts. This > includes the environment, tools and overall objectives. > > I'm not sure of the best way to organise this group, by mail list? Form > some kind of desktop CAB? > > Once the stories have been identified, each one should have an owner > from the developer community. I believe it to be essential that this > happens, to ensure we don't duplicate effort. The owner may do all of > the work, or for larger stories, coordinate a group to work on specific > tasks within the story. > > I know this sounds a bit heavy, but I believe it is lightest > organisational framework that can succeed in this situation. In an > ideal world, the group should be able to meet, but with the geographical > spread we have this isn't possible. Are there any appropriate net > meeting tools out there we could use? > > We should establish a project Wiki to share information. > > Cheers, > > Ian
+1. --Stefan -- Stefan Teleman [EMAIL PROTECTED] _______________________________________________ opensolaris-discuss mailing list opensolaris-discuss@opensolaris.org
