This is where I am collecting the feature list and other artifacts for Mailman 2.2, which should be a modest, but well-deserved update for Mailman 2.1. It won't be as ambitious as Mailman 3.0, which is both good and bad, but I hope that it will help us get Mailman 2.2 out in a reasonable amount of time.
So far, none of these should be taken as commitments (unless marked with a Done ); manyare resurrected from the old zope.org wiki page), but currently this is the best place to collect the wish list. If you have specific requests, add them as comments to this page and I'll move them up into the main page as they get accepted for Mailman 2.2.
Mailman 2.2 development is well under way. It is not yet ready for prime time, but if you want to help develop, debug, or test the current code base, please read Testing Mailman 2.2. Contributors are welcome and encouraged! Anyone can check out and use the current development source branches.
To Do List
Here are things we need to do before MM2.2 can be released.
- Defend against runaway .bak file restore loops in the Switchboard.
(Potential) feature set
Compatibility and code cleaning
- Python 2.4 or newer will be required.
- Remove all unnecessary _future_ statements
A primary focus of MM2.2 will be an updated web UI. A prototype was done as part of the 2005 Google Summer of Code project. We intend to modernize the UI to use current web best practices and allow for much easier customization and integration with existing sites.
- Switch to a new templating system that lets us share templates across languages, but extract messages for the catalog.
Note that what we can accomplish here will be based on the availability of an Archiving Champion.
- Reconsider using a 3rd-party archiver, or
- Update Pipermail's web UI to match the technology, look, and feel of the main UI update.
These are things we're not going to do in Mailman 2.2
- Unified user database.