So we've been thinking about the best way of doing this, and would like to share our plans to gather in feedback. Note that, at this stage, we're focusing on how best to expose the product, not on how it should be improved (that time will come!). We're trying to figure out how the open source community would like us to share our work in general; this will set a precedent for all future releases, not just RippleRap.
Our suggestion is that RippleRap.com will be the place where one goes for:
- A written "how to" for developers
- A written "how to" for conference organisers
- Links to new and modified components on the subversion repository (each component will be documented in due course)
- A link to the server side code (location to be confirmed, and implementation guidelines included in "how to" for developers)
- A link to a new 'ripplerap' component on the TiddlyWiki.org bug tracker, which will serve as a bug report / feature request mechanism
- A link to a complete copy of RippleRap, without any data (ready to populate with conference agenda, etc.)
One other question is whether future RippleRap discussions should take place on the TiddlyWiki Google group, or if we should create a new RippleRap Google group. My personal view is that we should stick with the TiddlyWiki group, because some of the current and future components may be of use to the wider TiddlyWiki community. We can always re-open the debate at a later stage if the noise becomes too loud. But please let me know if you have strong views to the contrary and we'll take them under advisement!