|
Size: 2368
Comment:
|
Size: 6646
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| #pragma page-filename DEV/versions/78 | #pragma page-filename DEV/versions/3833865 = Mailman Developer Resources = == Source code revision control == Mailman's source code is published in a publicly available revision control system called [[http://www.bazaar-vcs.org|Bazaar]] available through the code hosting and open source development service called [[http://launchpad.net|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 [[../MailmanOnLaunchpad|develop Mailman code using Bazaar and Launchpad]]. Here are a list of [[../MailmanBranches|important official and unofficial branches]]. == Versions specific resources == |
| Line 7: | Line 16: |
| == Initiatives and proposals == | |
| Line 8: | Line 18: |
| * [[../DKIM|DKIM]] * [[../OpenID|OpenID]] * [[../MemberAdaptor Semantics|MemberAdaptor Semantics]] * [[../Improved Logging|Improved Logging]] * Web U/I: [[../StyledPages|Using CSS]], [[../TemplatingNotes|Adding templating]] * [[../ModernArchiving|Modern Archiving]] * [[../Stable URLs|Stable URLs]] * [[../REST Interface|REST Interface]] == Other developer information == 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. == Relevant RFCs, references, and standards == Here are some useful RFCs, references and drafts: * [[http://www.jetcafe.org/npc/doc/mail_arch.html|A Highly Scalable Electronic Mail Service Using Open Systems (Christenson, et al)]] * [[http://www.jetcafe.org/npc/book/sendmail/|Sendmail Performance Tuning (Christenson)]] * [[http://www.washington.edu/imap/documentation/formats.txt.html|Mailbox Format Characteristics (Crispen)]] * [[http://www.faqs.org/rfcs/rfc3834.html|RFC 3834 - Recommendations for Automatic Responses to Electronic Mail]] * [[http://tools.ietf.org/html/rfc5064|RFC 5064 - The Archived-At Message Header Field]] '''draft''' * [[http://www.faqs.org/rfcs/rfc2033.html|RFC 2033 - Local Mail Transfer Protocol]] * [[http://www.ietf.org/rfc/rfc4871.txt?number=4871|RFC 4871]][[http://www.dkim.org|DomainKey Identified Mail (DKIM)]] * [[http://www.openid.net|OpenID]] * [[http://www.faqs.org/rfcs/rfc1893.html|RFC 1893 - Enhanced Mail System Status Codes]] * [[http://www.faqs.org/rfcs/rfc2034.html|RFC 2034 - SMTP Service Extension for Returning Enhanced Error Codes]] Best practices: * Anti-spam and anti-backscatter * [[http://wiki.exim.org/EximAutoReply|How To Do Autoreplies Without The World Hating You]]. * UK Joint Academic Network (JANet) provides network connectivity and services for UK HE institutions has [[http://www.ja.net/services/csirt/advice/policies/collateral-spam.html|guidance to victims of backscatter]]. * <<Verbatim([)>>A talk given at a UK Unix User Group meeting. Look for the 5th abstract on [[http://www.ukuug.org/events/winter2005/programme.shtml|this page]]. * [[http://www.dontbouncespam.org/]] * [[http://spamlinks.net/prevent-secure-backscatter.htm]] * The inevitable [[http://mayfirst.org/?q=node/180|"...considered harmful" article]]. * ...and another, also from JANet [[http://www.ja.net/services/csirt/threats/bounce.html|Spam Bounces Considered Harmful]]. * [[http://mipassoc.org/batv/|Bounce Address Tag Validation (BATV)]] |
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.
Versions specific resources
Here are the collection of resources for people interested in the development of Mailman.
Initiatives and proposals
Web U/I: Using CSS, Adding templating
Other developer information
Google did a 2006 Summer of Codeprogram in 2006, and Mailman was a sponsor. See the Summer of Code page and Mailman 2.2 page for more 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 knowafter 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:
A Highly Scalable Electronic Mail Service Using Open Systems (Christenson, et al)
RFC 3834 - Recommendations for Automatic Responses to Electronic Mail
RFC 2034 - SMTP Service Extension for Returning Enhanced Error Codes
Best practices:
- Anti-spam and anti-backscatter
- UK Joint Academic Network (JANet) provides network connectivity and services for UK
HE institutions has guidance to victims of backscatter.
[A talk given at a UK Unix User Group meeting. Look for the 5th abstract on this page.
The inevitable "...considered harmful" article.
...and another, also from JANet Spam Bounces Considered Harmful.