++WackoWiki is a non-commercial, all volunteer, Open Source project, and as such there is no formal list of feature requirments required for development. That said, there is an informal list of items that have been agreed upon by the WackoWiki developers as things that need to worked upon, known as the ((ToDoList TODO list)). Items on the list can be marked as completed in development, "claimed" by a developer and being activly worked on, or unmarked meaning that the item is likely not being activly worked on. Team members work on WackoWiki when they want to at their own speed.++
++So any future development depends on the contributions that will be made by its user community. Certainly working patches have a greater chance to become realized quickly than feature requests, but please don't hesitate to submit your suggestions to our ((/Org/Tools/BugTracker issue tracker)).++

The following features are planned to be implemented in a future version: |%%(wacko wrapper=box)**((Changelog))**

((https://wackowiki.org/bugs/roadmap_page.php Bug Tracker Log))
((https://bitbucket.org/wackowiki/wackowiki-stable/commits/all Change Log))


====((Release/R50 R5.0.x))==
  * This version is **!!not!! compatible with PHP 5.4 or greater**!
  * Fixing possible ((/Dev/Release/R50/Upgrade migration and upgrade)) issues from 4.x to 5.0, the 5.0.x development branch is reserved mainly for this purpose.

====((Release/R55 R5.5))==
-> ((Testing testing and debugging))
  * --migrate actions and handlers to use the new template engine-- DONE
  * fixing session related POST issues
  * ((Release/R55/ToDo Open Items)) for R5.5.
  * ((Release/R55/ReleaseNotes Release notes for R5.5.))

====((Release/R56 R5.6))==
  * rewrite and reimplementation of WackoFormatter
  * address GUI and usability issues
  * add template guide
  * improve and migrate themes

  * drop MyISAM support
  * **Unicode Support** -> PHP 7
    * The lack of Unicode support in PHP remains a serious problem, but at least we’re no longer nursing a dying animal (PHP 6) in the vain hopes of making it work when the entire surrounding situation has changed. This opens the door for new ideas on how to fix the issue.
      * http://www.slideshare.net/andreizm/the-good-the-bad-and-the-ugly-what-happened-to-unicode-and-php-6
    * unicode in database (utf8mb4)
    * UTF8 support for both SQL and HTML
    * ((/Dev/Guidelines/UnicodeCheatSheet Unicode (UTF-8) with PHP 5.3, MySQL 5.5 and HTML5))
    * http://kunststube.net/encoding/
  * treads in comments
  * page edit by sections / Section Editing
  * new edit handler
  * refactoring
    * we load too much code that we don't really need, the code needs restructuring to improve
      1. Move items not related to the core of the wiki out of wacko.class.php (ie. Forms, Users, DB, Referrers, Comments, etc.). The core should only be for loading actions, handlers, formatters, etc. All of these items should be offloaded into autoloading plugins. (?)
  * ...
  * Media Revisions

[Proposed / Postponed / Done]
  * ((/Dev/NewFeatures/PostgreSQL PostgreSQL support))
  * improve ((Projects/WikiEdit WikiEdit))
  * federation
  * private messages (privacy: no outbound messages)
  * Referential integrity
  * improve ((Projects/WackoFormatter WackoFormatter))
    * ((https://wackowiki.org/lab/News/2011/07/WackoWikiMarkupModule WackoWiki markup module))
  * Code Documentation
    * Add PHPDoc compatible documentation to all internal API's

  * here...
  * minimize loading of unused code
  * search - faceted search

====Long term goals ====

Note that the Roadmap is usually incomplete, for a complete list of features planned to be implemented in a future version, you can browse the ((https://wackowiki.org/bugs/roadmap_page.php Bug Tracker)).


original is located at: ((/Dev/Roadmap))