I am sure everyone, including me is eager to see this module come to fruition.  However in the haste of pushing something tangle out to folks we may later find that the module is severely limited.   I don't think it is a great idea to push this out so fast as to make it limited.  Any project consumes (or should, based on experience) at least 60% in the design phase where the analysis of features and functionality of the module are identified.

Scott, with your approval I would like to suggest a topic be made for specific aspects of the project in order to give everyone a better understanding and opportunity to suggest ideas. 

Granted this may become an overwhelming task with everyone tossing in their wish list.  A caveat would be that not all suggestions would be implemented.  Nonetheless, the suggestions would allow the developers to better understand the back-end database requirements, proposed workflow, and may save time in making a feature more open and user-defined than static and prescriptive.

Here are some topics I feel would play an important part in soliciting comments to flush out the various needs of the project.  If there are other topics that you feel would be important to include as an area please suggest it. 

We need to strike a balance between how consumed we get and getting the module out to market.   Once we identify leaders for the particular sections we will see significant gains in production time to market. 

I am willing to lead any section you assign me to.

Stakeholder Analysis
this topic would include the various needs from all the possible users of the module.  This could include user, administrator, publisher, editor, client, guest, RSS, etc…

 

Needs and Feature Analysis
this topic could be further divided to express the various features and needs of the stakeholders

 

Workflow Analysis
discuss the business rules and module workflow

Algorthim and Code
Identify and create various code fragments and algorithims to make more efficient and effective the functionality and operations of the module.  Taking care to consider the various possible enviornments and platform configurations stakholders of the module are most likely to encounter.

 

Presentation and Interface
this topic will take ideas from the stakeholder and needs analysis topics to construct mock-up screen samples

 

Beta Testers
this topic is for the those who wish to beta test the module in various user environments and offer feedback

 

Documentation
this topic is for those who wish to help provide documentation, helpfiles, training, videos, etc…

Marketing
This topic is intended for those to help promote the module and bring Ventrian new customers