Justin Aside from the obvious benefit of plausible deniability I'm intrigued to know what the benefit of keeping a development model "oral only" is? I know you've said "flexibility" but in this context isn't a primary goal of a development process to limit flexibility in a sensible way? Something that is not written down is hearsay, and leaves us with a development methodology that is an emergent property of behavior over time; which leaves everyone free to interpret it as they will.
Best regards Alan ------------------- T.J. Watson Research Center, Hawthorne, NY 1-914-784-7286 [email protected] From: Justin Clark-Casey <[email protected]> To: [email protected] Date: 04/17/2009 01:56 PM Subject: Re: [Opensim-dev] Development models Mike Dickson wrote: > Well, I know what I've observed over the last year and a half or so. > But I agree that having something in writing that could be referred to > would be a help. > > Mike > > On Fri, 2009-04-17 at 17:49 +0000, Diva Canto wrote: >> Before you go into proposing a different development process for >> OpenSim, make sure that you know what the current process is. >> I don't see it on the Wiki, so maybe people don't know. I'm happy to help formalize this a bit further on the wiki, based on what has happened historically. This would be written in as minimalistic and neutral a way as possible. Believe it or not, I have no love of extraneous process (I did work for IBM, after all :) I think there is value in leaving this oral (since it allows more flexibility), but perhaps the time for that is passing. If anybody has good arguments for not doing this, please put them forward. -- justincc Justin Clark-Casey http://justincc.wordpress.com _______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
_______________________________________________ Opensim-dev mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-dev
