3391
Comment:
|
4315
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
#pragma page-filename DEV/versions/244 | #pragma page-filename DEV/versions/163932 == Mailman version resources == |
Line 7: | Line 8: |
== Initiatives and proposals == | |
Line 8: | Line 10: |
Google's doing a [[http://code.google.com/soc/|2006 Summer of Code]] program again this year. Mailman is not yet a sponsor, but I'd be willing to mentor if anybody is interested in doing some work under the program. See my [[../Summer of Code|Summer of Code]] page and [[../Mailman 2.2|Mailman 2.2]] page for ideas. | * [[../DKIM|DKIM]] * [[../OpenID|OpenID]] * [[../MemberAdaptor Semantics|MemberAdaptor Semantics]] * [[../Improved Logging|Improved Logging]] * [[../TemplatingNotes|Web U/I]] == Other developer information == Google's doing a [[http://code.google.com/soc/|2006 Summer of Code]]program again this year. Mailman is not yet a sponsor, but I'd be willing to mentor if anybody is interested in doing some work under the program. See my [[../Summer of Code|Summer of Code]] page and [[../Mailman 2.2|Mailman 2.2]] page for ideas. |
Line 10: | Line 18: |
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. == Relevant RFCs, references, and standards == Here are some useful references: * [[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)]] RFCs and drafts: * [[http://www.faqs.org/rfcs/rfc2033.html|RFC 2033 - Local Mail Transfer Protocol]] * [[http://www.dkim.org|DomainKey Identified Mail (DKIM) draft specs]] * [[http://www.openid.org|OpenID]] |
Mailman version resources
Here are the collection of resources for people interested in the development of Mailman.
Initiatives and proposals
Other developer information
Google's doing a 2006 Summer of Codeprogram again this year. Mailman is not yet a sponsor, but I'd be willing to mentor if anybody is interested in doing some work under the program. See my Summer of Code page and Mailman 2.2 page for ideas.
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 references:
RFCs and drafts: