|
Size: 6787
Comment: Some initial install instructions
|
← Revision 61 as of 2018-04-20 06:57:02 ⇥
Size: 1896
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 3: | Line 3: |
| Mailman 3.0 was [[https://mail.python.org/pipermail/mailman-announce/2015-April/000210.html|released]] on April 28, 2015. See also the [[Mailman3|release notes]]. | |
| Line 4: | Line 5: |
| We aim to release Mailman 3.0 on Thursday, April 16, 2015. This page is where we are collecting the feature list and other artifacts for Mailman 3.0, which will be a major upgrade for the project. Many things that people have been wanting for years will be addressed, most notably a unified user database, true virtual domain support, and backing the Mailman data in a real database layer. From a development perspective, we will be adopting a very strict test-driven development model, utilizing modern Python technology and coding styles. The focus will be on providing core Mailman functionality through a REST API, architecturally separate components loosing communicating for better system administration and development lifecycles, while continuing the tradition of providing a turnkey solution with all the necessary parts, making it even easier to download, install, and go. Contributors are welcome and encouraged! Discussions will happen on the [[mailto:mailman-developers@python.org|mailman-developers mailing list]]. Anyone can check out and use the [[../MailmanBranches|current development source branches]]. The TODO list below is not a commitment of features (unless marked with a '''Done''' ). |
Contributors are welcome and encouraged! Discussions will happen on the [[mailto:mailman-developers@python.org|mailman-developers mailing list]]. Anyone can check out and use the [[DEV/MailmanBranches|current development source branches]]. |
| Line 11: | Line 8: |
| Mailman 3 is essentially four main projects: | |
| Line 12: | Line 10: |
| Mailman 3 is essentially five projects: * [[https://launchpad.net/~mailman-coders/mailman/3.0/ | Mailman Core]] * [[DEV/Postorius Web Interface|Postorius - The Web UI for Mailman]] ([[https://launchpad.net/postorius|code]]) * [[https://launchpad.net/mailman.client | Mailman Client - The REST API Client]] * [[HyperKitty|HyperKitty - The Archiver for Mailman]] ([[https://github.com/hyperkitty|code]]) * [[https://launchpad.net/mailman-bundler | Mailman Bundler - Installer for Mailman Suite including all above projects]] The suite as a whole is currently [[https://mail.python.org/pipermail/mailman-announce/2014-December/000197.html|at 3.0b5]]. [[https://mail.python.org/pipermail/mailman-developers/2015-January/024147.html|We aim]] to get a 3.0 release of the suite out by the end of the [[DEV/PyCon 2015 Sprint|PyCon sprints, April 13-16 2015]]. |
* [[https://gitlab.com/mailman/mailman |Mailman Core]] * [[DEV/Postorius Web Interface|Postorius - The Web UI for Mailman]] ([[https://gitlab.com/mailman/postorius |code]]) * [[https://gitlab.com/mailman/mailmanclient | Mailman Client - The REST API Client]] * [[HyperKitty|HyperKitty - The Archiver for Mailman]] ([[https://gitlab.com/mailman/hyperkitty |code]]) |
| Line 26: | Line 19: |
| * [[http://aosabook.org/en/mailman.html|Architectural overview]] * [[https://launchpad.net/mailman/3.0|Mailman 3 code "series" in Launchpad]] * [[https://bugs.launchpad.net/mailman/+bugs?field.tag=mailman3|bugs affecting the Mailman 3.x series]] * [[https://bugs.launchpad.net/postorius/+bugs?field.tag=mailman3-suite-blocker|bugs blocking the release of Mailman 3]] * [[DEV/A 5 minute guide to get the Mailman web UI running|a 5-minute guide to get Mailman core + Postorius running]] * [[https://mail.python.org/pipermail/mailman-announce/2014-April/000191.html|announcement of beta 1 preview (April 2014)]] * [[https://mail.python.org/pipermail/mailman-announce/2008-April/000104.html|announcement of alpha 1 (April 2008)]] <<Anchor(todo)>> = To Do List = == 3.0 == Here are things we need to do before Mailman 3.0 Suite final can be released. We started this list with the leftovers from [[../PyCon Sprint 2013|PyCon Sprint 2013]] and updated it at the [[../PyCon 2015 Sprint|PyCon Sprint 2015]]. * '''Mailman Suite''' * Update installation HOWTO(s) * Write release notes and announcement * Test new installs of 3.0 suite * '''Core''' * [[https://code.launchpad.net/~barry/mailman/subpolicy|Subscription management workflow/policy - WIP branch]] (see [[https://bugs.launchpad.net/postorius/+bug/1095552|bug 1095552]]) * '''Postorius''' * subscription moderation (see [[https://bugs.launchpad.net/postorius/+bug/1058449|bug 1058449]]) * '''Websites''' * Post HOWTO, release notes & announcement == 3.1 == TODOs for the next point release of 3.x: * Mailman Suite: * Internationalization - there must be a way for the community to contribute translations and for us to integrate them into releases ([[https://bugs.launchpad.net/mailman/+bug/1414154|bug 1414154]]) * Migration scripts for current Mailman 2 installations ([[https://bugs.launchpad.net/mailman/+bug/965532|bug 965532]]) * Test migration from 2 to 3 * Mailman 2 & 3 co-existing * Make it easier to install with Docker * Core * Subscription policy: dealing with permission to unsubscribe * Postorius * Implementation of django-browserid + custom audience checking * Add user settings page (Likely to be completed as part of stylistica's summer of code work; may need temporary fix sooner) * Add ability to remove moderators/owners from a list (see [[https://bugs.launchpad.net/postorius/+bug/1062889|bug 1062889]]) * non-member disposition [Put list of non-members in list settings with allow/deny, etc] (see [[https://bugs.launchpad.net/mailman/+bug/1414149|bug 1414149]]) * Pull list of supported languages for a domain from Mailman core via API (see [[https://bugs.launchpad.net/mailman/+bug/1414298|bug 1414298]]) * Hyperkitty * if a nonmember replies via the web interface, subscribe them as nondelivery member * Websites * Update visual style and information architecture of list.org and the wiki to feel more unified, be more navigable, and present a modern appearance * Convert www site generation from ancient ht2html scripts to something more modern like [[http://getnikola.com/|Nikola]] or [[http://blog.getpelican.com/|Pelican]] (no CMS required!) |
* [[http://aosabook.org/en/mailman.html|Architectural overview]] * [[https://gitlab.com/mailman |Mailman 3 projects on GitLab]] * [[https://gitlab.com/mailman/mailman/issues | bugs affecting the Mailman 3.x series]] * [[http://docs.mailman3.org/en/latest/devsetup.html| Development Setup Guide]] |
| Line 77: | Line 25: |
| Line 81: | Line 28: |
Currently the best path for installing the entire Mailman 3 suite at once is Mailman Bundler: [[http://mailman-bundler.readthedocs.org/en/latest/|Mailman Bundler setup instructions on ReadTheDocs]] If you're installing on Ubuntu, you might also want to look at [[DEV/Mailman 3.0/Mailman 3.0 Suite Install on Ubuntu]], which gives you some commands to install the prerequisites. We do eventually hope to have appropriate packages for some popular distros, so if you prefer packages only, please be patient! If you want to try Mailman 3 suite out in Docker, you might want to see [[DEV/Mailman 3.0/Mailman 3.0 Suite Dockerfile]]. I am still looking for someone to help provide nice instructions on how to use this, including connecting port 8000 inside the container to a port on the outside so that the tutorial can end with "and now go to http://localhost:8000/mailman3 to check out the web interface!" |
See http://docs.mailman3.org/en/latest/index.html for installation information. There exists debian packages and Container Images for Mailman 3. The above mentioned link has more details about requirements, installation howto and such. |
Mailman 3.0
Mailman 3.0 was released on April 28, 2015. See also the release notes.
Contributors are welcome and encouraged! Discussions will happen on the mailman-developers mailing list. Anyone can check out and use the current development source branches.
Development and status
Mailman 3 is essentially four main projects:
Mailman 3.0 is most suitable to new installations of Mailman. We do not guarantee that it will work well for migrations and upgrades of Mailman 2.x; we believe that will work, but encourage you to make backups and test your migrations first. It is not yet at full feature parity with Mailman 2.x, but we're working on that for 3.1.
Developer resources:
Installation HowTo
See http://docs.mailman3.org/en/latest/index.html for installation information. There exists debian packages and Container Images for Mailman 3. The above mentioned link has more details about requirements, installation howto and such.