Pending resolving the open mod_perl issues. TWiki 4.0.1 does not work satisfactory with mod_perl. Users continuously run into issues when saving a topic ( Bugs:Item1576 ) and the login/logout issue ( Bugs:Item 1575 ) is also a problem that needs to be resolved. Making a doc that says how to run with mod_perl is more misleading than anything else. I have tried to get more debug info for a week but I cannot get to the bottom of this. The randomness in the failure makes it even more difficult for me. I have given up mod_perl for now. -- KennethLavrsen - 12 Feb 2006
Release focus of Edinburgh Release
Desired outcome: Agree on process and timeline to decide on EdinburghRelease focus
OSS projects roadmaps are mainly driven by who want to work on something and not what money can we get from it
"A guideline for developers" - not too stone ish - more or less just an organized and prioritized enhancement request list
A great roadmap can help attract developers, short term / long term
We could propell twiki way more if we tune the marketing message
"To succeed" means "providing something valuable"
It is important that a product knows its segment and what is wants to focus on - so that there is a difference between TWiki and the other Wikis. A good difference.
Suggestion for 4.1 roadmap: mod_perl
Suggestion for 4.1 roadmap: Incremental speed improvements and better WYSIWYG. And 5.0 redesign topic storage to something indexed that than scale much better then today where Twiki clearly has an "upper limit" defined by speed of searches.
Two different scopes. 1. Which features when. That is roadmap. 2. HOW. That is deciding on development model, branching, documentation model.
We each probably have personal roadmaps. Making them explicit and looking for commonalities might facilitate discussion.
Personal roadmaps are good to know where the interests are, but they distract from focus unless coordinated