Hi John, > I would like to try and have two teams really - one to box off v8.1 and > another to continue work on v9.
I would not try to split into two actual teams, but there are essentially two virtual teams with hugely overlapping membership already. [email protected] handles the updates whilst [email protected] handles the development. To make SME 8.1 happen, get the commitment of someone to roll the needed ISOs. Currently this has been Shad, but the needed scripts are available to all. Once the commitment is there then the rest can follow. > However, as I mentioned above, knowing who is doing what is a tad > difficult and makes organising anything almost impossible. The development model is robust to an anonymous development community. The problematic points are the lack of Troubleshooters and the lack of verification - which are not specific to SME 8 / 9. > I appreciate that getting people to add their names on a mailing list is > not necessarily the best way of finding out who is doing what. It is quite easy to generate names of active committers, less easy but not impossible to generate a list of developers/Troubleshooters/Verification people. What is impossible is to know future commitment. > Somehow we MUST get a bit more organised. If not we will end up > duplicating effort and wasting our precious time and resources, or even > worse, nothing will get done at all. I would prefer the effort going towards finding and supporting new Troubleshooters including verification. I have not yet seen duplication/wasted effort, but where we have serious problems are lack of troubleshooting of incoming errors, and virtually no verification of fixes. Chris has done an amazing job in this area but more community people should be there helping. Ian _______________________________________________ Discussion about project organisation and overall direction To unsubscribe, e-mail [email protected] Searchable archive at http://lists.contribs.org/mailman/public/discussion/
