Size: 3468
Comment:
|
Size: 3949
Comment: add an unofficial branch.
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
#pragma page-filename DEV/versions/5177346 | #pragma page-filename DEV/versions/5177347 |
Line 69: | Line 69: |
|| '''''' | == William Mead || Mailman 3.0 LMTP enhanced || [[https://code.launchpad.net/~wilunix/mailman/lmtp]] || Working enhancement to Mailman 3.0.0a1 || 1 |
Line 71: | Line 76: |
=== Notes === 1. LMTP server will reject mail at RCTP TO if: (a) the list doesn't exist, (b) generic_nonmember_action is set to "reject", and the sender is not a list member. Emails to sub-addresses will pass this point, but that issue should be addressed further. We should also accept the email if "accept_these_nonmembers" matches. |
Mailman source code branches
Mailman's source code is now (as of June 22, 2007) hosted on Bazaar, which allows for a proliferation of branches, both official and unofficial. This is a good thing, but it may be difficult for developers to know where to go to find interesting branches. Here then is a list of official and unofficial interesting branches.
If you have a branch that you'd like to share with people, feel free to list them below in the unofficial section only. Please don't clutter this list up with temporary, highly experimental, or private branches. In other words, include only branches that you think are interesting enough that other people might want to grab, collaborate on, or deploy. Your branches do not have to be hosted on Launchpad, but if you're looking for a place to host your branches, that can be a convenient and easy-to-use site.
Official branches
Only core developers may edit this section!
Here are the anonymous, read-only branches. Anyone can check these branches out, and make their own branches from them. You cannot push changes back to these branches.
Branch purpose | Branch url | Notes |
Mailman 2.1 maintenance | https://code.launchpad.net/~mailman-coders/mailman/2.1 | |
Mailman 2.2 development | https://code.launchpad.net/~mailman-coders/mailman/2.2 | |
Mailman 3.0 development | https://code.launchpad.net/~mailman-coders/mailman/3.0 | |
Administrative support | https://code.launchpad.net/~mailman-administrivia/mailman-administrivia/admin |
For core developers with write privileges, you will want to use the following branches instead:
Branch purpose | Branch url | Notes |
Mailman 2.1 maintenance | sftp://<you>@bazaar.launchpad.net/~mailman-coders/mailman/2.1 | 1, 2 |
Mailman 2.2 maintenance | sftp://<you>@bazaar.launchpad.net/~mailman-coders/mailman/2.2 | 1, 2 |
Mailman 3.0 development | sftp://<you>@bazaar.launchpad.net/~mailman-coders/mailman/3.0 | 1, 2 |
Administrative support | sftp://<you>@bazaar.launchpad.net/~mailman-administrivia/mailman-administrivia/admin | 3 |
Notes
You must first apply for membership to the Mailman Coders team on Launchpad. Start by creating a user id on Launchpad and then send Barry an email with your Launchpad user id. Note that Barry will only join you to the team if you're a known contributor to the Mailman project. But remember, you don't need to have write privileges to the official branches in order to create and publish your own branches!
Substitute your Launchpad user id for the placeholder <you>. These urls will change and be simplified in a future Launchpad release, but it will be trivial to update at that time.
Note that you must be accepted into the Mailman Administrivia team in order to push changes to this branch.
Unofficial branches
Anyone may add branches to the bottom of this table. Only core developers may reorder these branches.
Author | Branch purpose | Branch url | Status | Notes |
William Mead | Mailman 3.0 LMTP enhanced | https://code.launchpad.net/~wilunix/mailman/lmtp | Working enhancement to Mailman 3.0.0a1 | 1 |
Notes
- LMTP server will reject mail at RCTP TO if: (a) the list doesn't exist, (b) generic_nonmember_action is set to "reject", and the sender is not a list member. Emails to sub-addresses will pass this point, but that issue should be addressed further. We should also accept the email if "accept_these_nonmembers" matches.