Differences between revisions 15 and 25 (spanning 10 versions)
Revision 15 as of 2009-05-06 19:48:04
Size: 3888
Editor: barry
Comment:
Revision 25 as of 2016-03-02 17:34:55
Size: 5238
Editor: SimonHanna
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
#pragma page-filename DEV/versions/8487028 #pragma page-filename DEV/versions/786436

{{{#!wiki warning
'''This page is obsolete! The information included is probably invalid and thus should be used with care'''
}}}
Line 3: Line 7:
As of June 22, 2007, Mailman's source code is 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.
Line 5: Line 8:
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 [[http://code.launchpad.net|Launchpad]], but if you're looking for a place to host your branches, that can be a convenient and easy-to-use site. As of June 22, 2007, Mailman's source code is hosted on Bazaar, which allows for a proliferation of branches, both official and unofficial. As of early 2014, we also have several other components, some of which are hosted on !GitHub. 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 for Mailman, including the [[DEV/Postorius Web
Interface|Postorius]], mailman.client, HyperKitty, and bundler components of the Mailman 3 suite.

I
f 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 [[http://code.launchpad.net|Launchpad]], but if you're looking for a place to host your branches, that can be a convenient and easy-to-use site.
Line 13: Line 19:
== Official branches == == Official branches of Mailman ==
Line 16: Line 23:
For convenience you can use the following URLs to access the official Mailman branches.  If you are a member of the appropriate team on Launchpad, these URLs will translate to read/write bzr+ssh branches.  If you aren't a member of the appropriate team, these URLs will translate into read-only http branches. For convenience you can use the following URLs to access the official Mailman branches. If you are a member of the appropriate team on Launchpad, these URLs will translate to read/write bzr+ssh branches. If you aren't a member of the appropriate team, these URLs will translate into read-only http branches.
Line 19: Line 26:
'''Branch purpose'''
|| '''Branch url'''
|| '''Notes'''
'''Branch purpose '''

|| '''Branch url '''

|| '''Notes '''
Line 23: Line 32:
Mailman 2.1 maintenance
|| lp:mailman/stable
|| 1
Mailman 2.1 maintenance  
|| lp:mailman/stable  
|| 1 
Line 27: Line 38:
Mailman 2.2 development
|| lp:mailman/2.2
|| 1
Mailman 2.2 development  
|| lp:mailman/2.2  
|| 1 
Line 31: Line 44:
Mailman 3.0 development
|| lp:mailman
|| 1
Mailman 3.0 development  
|| lp:mailman  
|| 1 
Line 35: Line 50:
Administrative support
|| lp:mailman-administrivia
|| 2
Administrative support  
|| lp:mailman-administrivia  
|| 2 
Line 39: Line 56:
Line 40: Line 58:
 1. You must first apply for membership to the [[https://launchpad.net/~mailman-coders/|Mailman Coders]] team on Launchpad.  Start by creating a user id on [[https://launchpad.net|Launchpad]] and then [[mailto:barry@list.org|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!
1. You must first apply for membership to the [[https://launchpad.net/~mailman-coders/|Mailman Coders]] team on Launchpad. Start by creating a user id on [[https://launchpad.net|Launchpad]] and then <<MailTo(barry NO AT HARVEST list DOT org,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!
Line 42: Line 61:

== Official repositories for the Mailman 3 suite ==
{{{#!table
'''Component name and purpose '''

|| '''URLs'''

|| '''Notes '''
==
Postorious (the administrative web UI)

|| lp:postorius or https://launchpad.net/postorius

||
==
HyperKitty (the Django-based web archiver of posts)

|| https://github.com/hyperkitty

|| Per [[https://fedorahosted.org/hyperkitty/|the HyperKitty homepage]] you'll need all of the repositories: kittystore, hyperkitty, and hyperkitty_standalone.

==
mailman.client (REST client for driving Mailman 3)

|| lp:mailman.client or https://launchpad.net/mailman.client

||

==
bundler (the installer for the whole Mailman 3 suite/package)

|| lp:mailman-bundler or https://launchpad.net/mailman-bundler

||

}}}
Line 43: Line 99:
Anyone may add branches to the bottom of this table.  Only core developers may reorder these branches.
Anyone may add branches to the bottom of this table. Only core developers may reorder these branches.
Line 46: Line 103:
'''Author'''
|| '''Branch purpose'''
|| '''Branch url'''
|| '''Status'''
|| '''Notes'''
'''Author '''

|| '''Branch purpose '''

|| '''Branch url '''

|| '''Status '''

|| '''Notes '''
Line 52: Line 113:
William Mead
|| Mailman 3.0 LMTP enhanced
|| [[https://code.launchpad.net/~wilunix/mailman/lmtp]]
|| Working enhancement to Mailman 3.0.0a1
|| 1
William Mead  
|| Mailman 3.0 LMTP enhanced  
|| [[https://code.launchpad.net/~wilunix/mailman/lmtp|https://code.launchpad.net/~wilunix/mailman/lmtp]]  
|| Working enhancement to Mailman 3.0.0a1  
|| 1 
Line 58: Line 123:
Joost van Baal e.a.
|| PGP and S/MIME aware Mailman 2.1
|| [[https://code.launchpad.net/~joostvb/mailman/2.1-pgp-smime]]
|| See [[http://non-gnu.uvt.nl/mailman-pgp-smime/]]
Joost van Baal e.a.  
|| PGP and S/MIME aware Mailman 2.1  
|| [[https://code.launchpad.net/~joostvb/mailman/2.1-pgp-smime|https://code.launchpad.net/~joostvb/mailman/2.1-pgp-smime]]

|| See [[http://non-gnu.uvt.nl/mailman-pgp-smime/|http://non-gnu.uvt.nl/mailman-pgp-smime/]]
Line 64: Line 133:
Andreas Schosser
|| New Webinterface to Mailman 3
|| [[https://code.launchpad.net/~a-state-of-mind/+junk/mmclient]]
|| test case

|| test to integrate pylons, genshi and rest
==
Barry Warsaw
|| REST admin server
|| [[https://code.edge.launchpad.net/~barry/mailman/rest]]
|| working development
|| MM3
Andreas Schosser  
|| New Webinterface to Mailman 3  
|| [[https://code.launchpad.net/~a-state-of-mind/+junk/mmclient|https://code.launchpad.net/~a-state-of-mind/+junk/mmclient]]   || test case

|| test to integrate pylons, genshi and rest 
Line 76: Line 143:
Line 79: Line 147:

This page is obsolete! The information included is probably invalid and thus should be used with care

Mailman source code branches

As of June 22, 2007, Mailman's source code is hosted on Bazaar, which allows for a proliferation of branches, both official and unofficial. As of early 2014, we also have several other components, some of which are hosted on GitHub. 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 for Mailman, including the Postorius, mailman.client, HyperKitty, and bundler components of the Mailman 3 suite.

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.

For example, if you wanted to grab a copy of the current Mailman 3 development branch, you would run the following command:

% bzr branch lp:mailman

Official branches of Mailman

Only core developers may edit this section!

For convenience you can use the following URLs to access the official Mailman branches. If you are a member of the appropriate team on Launchpad, these URLs will translate to read/write bzr+ssh branches. If you aren't a member of the appropriate team, these URLs will translate into read-only http branches.

Branch purpose Branch url Notes
Mailman 2.1 maintenance lp:mailman/stable 1
Mailman 2.2 development lp:mailman/2.2 1
Mailman 3.0 development lp:mailman 1
Administrative support lp:mailman-administrivia 2

Notes

  1. 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 <barry NO AT HARVEST list DOT org> 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!

  2. Note that you must be accepted into the Mailman Administrivia team in order to push changes to this branch.

Official repositories for the Mailman 3 suite

Component name and purpose URLs Notes
Postorious (the administrative web UI) lp:postorius or https://launchpad.net/postorius
HyperKitty (the Django-based web archiver of posts) https://github.com/hyperkitty Per the HyperKitty homepage you'll need all of the repositories: kittystore, hyperkitty, and hyperkitty_standalone.
mailman.client (REST client for driving Mailman 3) lp:mailman.client or https://launchpad.net/mailman.client
bundler (the installer for the whole Mailman 3 suite/package) lp:mailman-bundler or https://launchpad.net/mailman-bundler

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
Joost van Baal e.a. PGP and S/MIME aware Mailman 2.1 https://code.launchpad.net/~joostvb/mailman/2.1-pgp-smime See http://non-gnu.uvt.nl/mailman-pgp-smime/
Andreas Schosser New Webinterface to Mailman 3 https://code.launchpad.net/~a-state-of-mind/+junk/mmclient test case test to integrate pylons, genshi and rest

Launchpad also provides a listing of all related branches, even those that aren't described here.

Notes

  1. LMTP server will reject mail at RCTP TO if: (a) the list doesn't exist, or (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.

MailmanWiki: DEV/MailmanBranches (last edited 2016-03-02 17:34:55 by SimonHanna)