Thanks Tracy--I think we need a bit of a kick in the pants at this point. ;-) I was going to spend part of today figuring out how to kick this thing off as well so your post is well received.
In addition to what you outline below, I haven't received any design responses other than the logo (thanks again Ron!), I'm going to peruse some of the designs on oswd.org that might work. We can always change it but since the app needs to be easily skinnable anyway, it will at least be a starting point. With a design idea (good or bad) in place plus the basic structure you outline we should be able to start working on some things. I had an English teacher in college that always said "writing papers is easy--just write *something* every day, even if it's just your name or something you know is out of place or isn't going to work." While I don't think we want to get coded into a corner or anything, I think similar logic applies here, and Mach-II is flexible enough that it's relatively easy to back ourselves out of things if we get off on the wrong track. Thanks again, Matt On 1/29/06, Tracy Logan <[EMAIL PROTECTED]> wrote: > 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 > > > -- Matt Woodward [EMAIL PROTECTED] http://www.mattwoodward.com ~~~~~~~~~~~~ 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
