FeatureX wiki page
To create a ))FeatureX(( page, do the following:
FeatureXDoc wiki page (what featureX does NOW)
-Please see: OldTikiWikiDocumentationPlan
FeatureXDev wiki page (what featureX will do LATER)
Here is a proposal for a typical page of a complex feature. Some features may not warrant as much detail.
Where are we? Where do we want to be? Who is working on what? (Priorities/goals/majors issues/roles)
Has the list of team members (with hyperlinks to their userpage). Team members are expected to subscribe and monitor all three pages and the dev forum. Using the backlinks from a userpage will show you all the stuff he/she is working on
Hyperlinks to appropriate trackers on SF (Bugs, RFEs, tech support and patches). Let's add Dennis Daniels creative hyperlink to SF bugs and RFEs. Dave Sanders has done excellent work on categories on our SF trackers.
Competition and standards
List of other products with similar/interesting/related features. Here I would like to see some "editorial" content. How do our features compare to others? This will let Tiki Evaluators know if the features they need are good enough for them. The Beat PHPBB project comes to mind.
Also, linking to several competitors in a field has an interesting side effect. We can get some traffic from people looking to compare some well know competitors. Ex.: Someone is looking for a comparison of vbulletin, phpBB and Phorum.
This may lead also in the future to some partnerships and/or increased userbase. For example, if a smaller project is going to stop development, we could work with the authors on a data migration script. At least users of the old project will have somewhere to turn to.
CVS Doc section
This is where new features (only in CVS) are documented. When the CVS becomes RC/official release, the info in the CVS docs is transferred to update the official docs (FeatureXDoc).
A forum from this page brings users to a place where ideas can be exchanged, debated, etc. Interested people can subscribe to the wiki page and/or to these forums as they would a mailing list. Once a conclusion is reached, the roadmap is updated. Discussion (forum) -> RoadMap (Wiki)
We need the info well organized, well categorized and easily searchable. IMHO, Threaded forums where titles are updated are the best.
The dev team may opt to add a poll or survey to ask people what future sub-features they would prefer. Ex.: for the calendar, do you prefer iCal or SyncML support?