djbrow54 wrote:
> 1. Decide on a group consensus for the feature set.
I've been lurking on this group since I first became aware of it and the
PSIM delivery debacle. I think this point of Dave's is crucial to
moving forward. It would be interesting to restart the project,
treating it like any other development project:
1. get a feature list, let everyone propose what they'd like to see in
this project
2. prioritize the feature list in a democratic manner
3. get consensus on the features that are in and out. formalize into a
requirements doc
4. propose an implementation
5. get a projected bom cost.
6. if you get this far and people are willing to commit - divide up the
work appropriately.
If nothing else, it would be interesting to see all the features that
are proposed. For example, Gary Chang needed the ability to synchronize
multiple devices - a need that wasn't originally foreseen. What other
"must have" features are missing?
-Dave