Scope, scope creep, requirements and software goodness
Folks,
I'm really getting excited with all the participation! Let me take a moment to start a new thread regarding the "meta-process" I'm engaging in and what my goals and objectives are:
- Get out a new version of Events - soon!
- Work in a community context
- model good software development behavior
- document the hell out of Events for future generations...
We all agree on the basics - but I think that some of the comments are out of scope for what I'm interested in. Here's what I'm interested in - I want to get functionality out that can be used for grassroots, community based organizing - in this case Houseparties. I would also like to see the system usable by political and other campaigns to do less-formal campaign based events. In my view (which is subject to change) this does not include "volunteering", "choosing a date for a meeting", "pre-event organizing" - you get the idea.
That being said I would be happy to help document all these other issues/scopes - but I would probably need to see a clearly defined statement of functionality/description.
So if you would like to see a broader scope - this is the place to have that discussion.
Read more