Howdy, everyone! I thought I'd suggest a couple of ideas and see what you think:
Something that seems to happen a lot on group projects like this is what some Seussian wag termed "analysis paralysis" -- and it feels like that has happened here: we have the start of some really great requirements docs, but not much progress past that. So I'd like to propose that without changing what we're already doing, we add something to it: Rather than waiting for the full design to be finalized, let's steal one more of the *good* ideas from the Extreme Programming folks (hey, we have a wiki already!) -- specifically, "Release Early, Release Often". We're not doing anything as complex as the Linux crew (for an opinion on how that worked for them: http://www.catb.org/~esr/writings/cathedral-bazaar/cathedral-bazaar/ar01s04.html), but this is still a great way to build some real momentum. What I'm proposing is that, right now, well prior to final design checkoff, we create at least the app skeleton and add it to Trac. Perhaps nothing more than config file and a folder structure (with, I presume, a placeholder for Mach-II, rather than redistributing it?), perhaps with a few basic events (even just a Home default event will help newbies follow what's happening). That lets everyone get comfortable with Trac, SVN, and so on, before we get into the heavy-duty design phase. Sound interesting? I'll be happy to check in that sort of basic skeleton (in the meantime, learning more about Trac myself!) Sound horrifying? Somebody please stop me before I post again . . . ! :*) =tracy ~~~~~~~~~~~~ Reply To: [email protected] List Archive: http://www.mail-archive.com/devteam%40list.dfwcfug.net/ To Subscribe: Send an email to [EMAIL PROTECTED] with "subscribe devteam" in the body - no quotes. To Unsubscribe: Reply to the list with unsubscribe in the subject line. Sponsors: www.HostMySite.com & www.cvsdude.org
