From: Adam B. <ad...@ad...> - 2004-10-10 23:08:16
|
Based on Chris' earlier suggestion, I threw up a few categories for us to use under the "Feature Request" tracker tool... Basically, if we can each take a minute or two and brainstorm a bit regarding (1) stuff the software *should* do, and (2) whether these things need to be in our "quick and dirty" version 0.01, or if they can wait: https://sourceforge.net/tracker/?func=add&group_id=116815&atid=676127 Just brainstorm a bit; don't worry if the ideas are way too long-term to worry about now (we'll classify them as such and then come back to them later). Just focus on putting together what you believe are the primary, most important things (from an end-user perspective) that the software needs to accomplish. (I already submitted an example -- "Issue certs." lol) The choices are basically (1) YES, this MUST be in the first version; (2) this SHOULD be in the first version if we can help it; (3) this can wait -- short term; (4) long term "strategic" stuff we *eventually* want, but don't need in v0.1; and finally (5) stuff that we really don't plan to ever worry about (non-priorities, stuff that is out-of-scope, etc.). Chris, can you help me keep an eye on the tracker and try to get some prelimnary categorizations selected for the stuff that comes in? Everyone else, could you please take a minute or two and type in a few of (what you think are) the most important things our software needs to do? If we can get a solid idea of the requirements/needs we have for a "quick and dirty version," it shouldn't be hard to manufacture a step-by-step plan for coding it. Thoughts? AB |