Wishlist
Being an approximate and fallible list of things that might, and might not, make it into the core Textpattern distribution, if someone were to build them.
For the 4.0.x branch:
- Things that will almost certainly be added to Textpattern if someone builds them:
- Bug fixes
- Performance enhancements
- Small, incremental improvements to txp tags that eliminate shortcomings without changing existing behaviour
- Small, incremental improvements to the Texpattern admin UI (such as usability improvements with simple Javascript)
- Low risk internal changes that improve plugin capabilities
- Things we’ll consider including if someone submits a patch:
- Low risk new features that include a test plan and examples
- Things that we will probably reject:
- Major features that change or add a large amount of code
- Anything that’s likely to change existing valid behaviour
- Things that can be done well in plugins
- Code that we don’t know how to test
For the Crockery (4.1) branch:
- Things that will almost certainly be added if someone builds them:
- As above, plus
- Refactoring the admin UI code to make use of the new controller and view classes (txplib_controller.php and txplib_view.php)
- Removing the crufty tag code and attributes we’ve had to keep in 4.0.x for backwards compatibility
- Centralizing the code used for fetching stuff from the database (e.g.
get_article_list()instead ofsafe_rows('*', 'textpattern', ...)) - Cleaning up the database
- Refactoring the comment code
- Rearranging and simplifying preferences and language updates
- Rearranging modules, in particular moving functions out of publish.php and into lib
- Things that we’ll consider adding if someone can build it in a way that’s clean, simple, and doesn’t break or bloat other code:
- Better importer code (particularly a mechanism for writing importers as plugins)
- Unlimited categories
- Nested sections
- Improvements to the plugin format and installation process
- Library improvements that help improve plugins
- Anything that really belongs in the core
- Things we will probably reject:
- Things that can be done well in plugins (particularly Trackbacks)
- Code that we don’t know how to test
If you’re considering submitting a patch, or beginning work on a new feature, and would like to discuss it with the development team first, please contact us or post on the development forum. We’ll do our best to provide an indication of whether or not we think it’s appropriate for the stable or development branch.