Differences between revisions 37 and 45 (spanning 8 versions)

Mailman Developer Resources

Source code revision control

Mailman's source code is published in a publicly available revision control system called Bazaar available through the code hosting and open source development service called Launchpad. On June 22, 2007, we switched from using Subversion on SourceForge to the new repository, and while the old Subversion repository will still be available read-only, no new updates will be committed to it. Hosting the source code on Bazaar provides both the core developers and unofficial third party extensions much more freedom to hack on Mailman.

Here is more detail on how to develop Mailman code using Bazaar and Launchpad.

Here are a list of important official and unofficial branches.

Version-specific resources

Here are the collection of resources for people interested in the development of Mailman.

Sprints

Initiatives and proposals

Suggestions

People seem to have trouble figuring out where to make suggestions or feature requests. There is a suggestions page here, or you may wish to start a discussion on the mailman-developers list

Other developer information

Mailman is a GNU project with the majority of the copyrights being held by the Free Software Foundation. We therefore request that developers who contribute code, assign their copyrights in their Mailman contribution to the FSF. To do this, you first need to submit a GNU copyright assignment request form containing some basic information, and then fill out the form that the FSF sends you. Please let us know after you've sent the second form so that we can track your contribution. The FSF often doesn't tell us in a timely manner when such forms have been received.

Relevant RFCs, references, and standards

Here are some useful RFCs, references and drafts:

Best practices:

Anti-spam and anti-backscatter
- How To Do Autoreplies Without The World Hating You.
- [A talk given at a UK Unix User Group meeting. Look for the 5th abstract on this page.
- http://www.dontbouncespam.org/
- http://spamlinks.net/prevent-secure-backscatter.htm
- The inevitable "...considered harmful" article.
- UK Joint Academic Network (JANet) provides network connectivity and services for UK

HE institutions has guidance to victims of backscatter.

...and to system adminstrators Spam Bounces Considered Harmful.
Bounce Address Tag Validation (BATV)
Mailman's own recommendations for controlling spam

-  ⇤ ← Revision 37 as of 2008-04-22 04:52:31 → 
  Size: 6731
  Editor: ianeiloart
  Comment:
+   ← Revision 45 as of 2009-02-08 18:18:15 → ⇥
  Size: 6989
  Editor: barry
  Comment:
-Deletions are marked like this.
+Additions are marked like this.
 Line 1:
-#pragma page-filename DEV/versions/3833869
+#pragma page-filename DEV/versions/7602267
 Line 10:
-== Versions specific resources ==
+== Version-specific resources ==
 Line 16:
+== Sprints ==
 * [[../PyCon 2009 Sprint|PyCon 2009 Sprint]]
 * [[../Summer of Code|Google Summer of Code 2006]]
 * [[../Google Summer of Code 2008|Google Summer of Code 2008]]
-Line 17:
+Line 21:
+ * [[../GPLv3|GPLv3]]
-Line 22:
+Line 27:
- * Web U/I: [[../StyledPages|Using CSS]], [[../TemplatingNotes|Adding templating]]
+ * [[../Web Interface|Web Interface]]
-Line 26:
+Line 31:
+ * [[../Patches|Patches]]
== Suggestions ==
People seem to have trouble figuring out where to make suggestions or feature requests.  There is a [[../suggestions|suggestions]] page here, or you may wish to start a discussion on the [[http://mail.python.org/mailman/listinfo/mailman-developers|mailman-developers list]]
-Line 27:
+Line 36:
-Google did a [[http://code.google.com/soc/|2006 Summer of Code]]program in 2006, and Mailman was a sponsor. See the [[../Summer of Code|Summer of Code]] page and [[../Mailman 2.2|Mailman 2.2]] page for more information.

Mailman is a [[http://www.gnu.org|GNU]] project with the majority of the copyrights being held by the [[http://www.fsf.org|Free Software Foundation]]. We therefore request that developers who contribute code, assign their copyrights in their Mailman contribution to the FSF. To do this, you first need to submit a [[../GNU copyright assignment request form|GNU copyright assignment request form]] containing some basic information, and then fill out the form that the FSF sends you. Please [[mailto:mailman-cabal@python.org|let us know]]after you've sent the second form so that we can track your contribution. The FSF often doesn't tell us in a timely manner when such forms have been received.
+Mailman is a [[http://www.gnu.org|GNU]] project with the majority of the copyrights being held by the [[http://www.fsf.org|Free Software Foundation]]. We therefore request that developers who contribute code, assign their copyrights in their Mailman contribution to the FSF. To do this, you first need to submit a [[../GNU copyright assignment request form|GNU copyright assignment request form]] containing some basic information, and then fill out the form that the FSF sends you. Please [[mailto:mailman-cabal@python.org|let us know]] after you've sent the second form so that we can track your contribution. The FSF often doesn't tell us in a timely manner when such forms have been received.