PersonalRoadmapForSvenDowideit

I obviously will need to find and pull in all the other content where i have stated the technical directions that I would like to see TWiki cover.

in Summary

• TWikiInstallers
  • re-examine an upgradeTWiki script / tool - It will become vital for all of the TWikiInstallers
• general UserMapping? work - OpenID, Joomla, Trac,
• advanced UI, Web, User oriented tools, focused on creation and development of content.
  • TopicObjectModel -
  • InlineEditPlugin, ComponentEditPlugin? , WikiwygContrib - advanced sectional mini-editors
• flexible scalable TWikiApplication engine, with deployment and configuration tools
  • these tools should be able to be written as TWikiApplications
• a real workflow system
• decent OO, with a minimalistic TWikiKernel
• a community driven process, with no requirement for Core teams or Roles, other than TWikiJanitor? (the poor bugger that needs to have final root access to the server)
  • DEVELOP is the vehicle that this was developed on for DakarRelease, and now we're renameing that to be more obvious

results I hope to enable

• finish the modularisation of the UserAuth? & UserInfo? module (UserDotPm), implementing a JoomlaUser? (done for limited release), OpenID, PAMUser and WindowsUser?
• continue the development of TWikiStore? modules - SvnStore? , DBIStore, DistributedStore?
• move these implementation classes into a ObjectOrientedTWikiPluginSystem
• add functions to BugsContrib?

More general ideas

1. reduce the distributed docco & create Web based configuration and setup
2. refactor the content on twiki.org
   • create seperate webs for each release (Athens, Bejing, Cairo, Dakar) and move topics for each functionality / discussions into the appropriate webs, freeing up the namespace for future use (eg, there might be a RegistrationChanges? topic for each version, detailing the changes / ideas specific to that version)
3. continue UpgradeTWiki
   • redo UpgradeTopics? using the Store API, allowing upgrading from SVN

DevelopBranch needs

• a fully automated build system, that spits out TWikiKernel, TWikiRelease, TWikiDistros? , TWikiPlugins
  • see DailyBuildAndSmokeTest - DONE
• a fully automated testing system that runs all the unit tests whenever there is a commit (or similar), and sends out rude emails to all people with commit access when there is a failure
  • DONE - once a night, to not load the svn server too much
  • http://develop.twiki.org/users/develop/pub/TestOutput/runtest.html
• DEVELOPer's to ensure that there are tests for any work they do (the only IronFist? for DEVELOP)

I want the TWikiCommunity to not be dependant on the TWikiCore group. I want to see what TWiki becomes without the strong controls we have now.

-- SvenDowideit - 22 Nov 2004