summaryrefslogtreecommitdiff
path: root/doc (follow)
Commit message (Collapse)AuthorAgeFilesLines
* reorganize READMEs and other documentation. more still to do.bwarsaw2007-01-1419-7703/+0
|
* Reorganize the doc directory by creating a howtos directory for holding thebwarsaw2007-01-084-0/+0
| | | | LaTeX guides.
* backport mailman-install.tex from 2.1.6tkikuchi2005-08-281-0/+1803
|
* Addition to the thanks in the mailman-member document.spot2004-10-0211-408/+633
| | | | More man pages and some fixes to previously submitted pages.
* More man pages for Mailman 2.1: find_member, list_members, remove_members andspot2004-09-135-4/+282
| | | | sync_members.
* This is a man page for add_members. Hopefully, this will be the first ofspot2004-09-121-0/+58
| | | | a set of such pages for the command line utilities in mailman.
* Latest version of the documentation.spot2004-09-121-1/+9
|
* Pablo Chamorro C.'s Spanish translation of the member's manual.spot2004-04-161-0/+1635
|
* Bugfixes/small edits stemming mostly from Barry's commentsspot2003-10-011-123/+156
| | | | | Some more major revisions will be coming through shortly, mostly new sections (page oriented description, additional explanation of email commands, etc.).
* Member (subscriber/user) documentation for 2.1 (initial checkin)spot2003-05-051-0/+1505
|
* Another updatebwarsaw2003-02-081-0/+50
|
* Checkpointingbwarsaw2002-12-281-1/+229
|
* Checkpointingbwarsaw2002-12-271-51/+284
|
* Updatesbwarsaw2002-10-291-0/+158
|
* An updatebwarsaw2002-10-271-1/+250
|
* The start of a manual for list administrators. Written in Pythonbwarsaw2002-10-231-0/+484
| | | | | | | | | mkhowto format, you'll need the Python documentation tool chain to produce the pdf or html (but that's easy if you have Python's source distro). Contributions are welcome! I'll keep working on this during ball games, though. :)
* These are unreadable, so I'm removing them. Closes SF # 604704.bwarsaw2002-09-052-0/+0
|
* Diagrams (in dia native, PostScript, and crappy-scaled PNG) of the newbwarsaw2001-10-153-0/+735
| | | | sender-centric moderation flowchart.
* As with the IPC7 directory, let's go ahead and release the publishedbwarsaw1998-12-313-66034/+1
| | | | versions of these files (compressed though).
* Since these papers have been published, we might as well release thembwarsaw1998-12-317-730/+8
| | | | | | | now. By gzip'ing them we can get them down to reasonable sizes. Check in the compressed versions, remove the uncompressed versions, add a README, and remove the old intermediate files.
* (Nearly) the PostScript of the paper as published in Usenix LISA 98.bwarsaw1998-12-212-0/+66046
| | | | See README for one minor difference.
* Removed last slide, which seemed bogusbwarsaw1998-12-211-0/+0
|
* Removing extraneous pictures - the ones being used are in IPC7.doc.klm1998-11-174-0/+0
|
* This is it.klm1998-11-071-0/+0
|
* More developed version of IPC7 presentation slides.klm1998-11-061-0/+0
|
* Update to ipc7.doc word version of the IPC7 paper - this one went toklm1998-11-052-0/+0
| | | | | | | printers. Addition of ipc7.ppt slides for presentation at the conference - unfortunately, preliminary, i will be finishing them on friday...
* Another version because the screen shots were too fuzzy. Fixed, andklm1998-10-221-0/+0
| | | | | | | | too the opportunity to polish some things i was hoping to polish. (Wish i had more time to flesh out exactly what the versatility brings us - ease of implementing new things like mail/news gateway, cascading lists, spam protection, accommodating emerging maillist standards, ........)
* Small polishings, etc, including proper formatting according toklm1998-10-121-0/+0
| | | | conference requirements, as well as grammatical improvements.
* Final copy of IPC7 paper, in MS Word. I incorporated barry'sklm1998-09-281-0/+0
| | | | | | | | block-structure diagram from the Usenix paper - since it's such a nice diagram, particularly giving a decent sense of the context for the MailList object - but i only included a few sentences giving a very rough overview of the structure, covering only the MailList instance in the rest.
* Incorporated good suggestions from a reviewer, and did a bit ofklm1998-09-231-48/+51
| | | | tweaking, am about to work on the word rendering of this.
* The version sent. Lots of iterations as i bumbled through a miserableklm1998-07-291-6/+10
| | | | | | | haze, barely recognizing right from write from wrong and done with all productive endeavors, until tomorrow. Maybe. :-)
* Well, a bit more tweaking.klm1998-07-291-25/+33
|
* Too late, i'm going to submit this.klm1998-07-291-33/+46
|
* Several changes, many quite minor (web -> Web, and otherbwarsaw1998-07-291-71/+77
| | | | | | | | | | | | | | | capitalizations). Some minor typos and other language rewrites, again mostly minor. Two major questions, both marked with XXX's. The first sentence in "A Selective Tour" was completely unparseable to me. Ken could you please rewrite? Also I rewrote the last paragraph before the conclusion (static typing). I don't know if its any better, please proof read. Also note there's a slight problem with the driver excerpt, see my recent checkin. HOwever I don't think the draft needs to change since it's "just an excerpt".
* Began to address some issues john raised, but need help with these.klm1998-07-291-90/+147
| | | | | | | | | | | | | | | | | | | | | | | | | | 1) Fill in and/or fix the static typing discussion. I need your views and your verbage - i'm in bad shape today, myself, and i didn't have a good handle on this discussion in the first place. 2) John protested that i introduced some new ideas in the conclusion, suggesting it's not a good idea to do that. I agree, and totally toned down the stuff about Python's readability. (Gad, i'm so drawn to spew about that.) My question is, is there other stuff that needs attention? Added a section about what mailman *is*, at the top of the introduction. I almost overlooked this - i'm assuming it makes sense (but i'm in bad shape today - guys, whatever sanity checking and rectification you can provide today would be appreciated, we need to get this done in a few hours, and i've run out of steam.) Assembled some references - if one of you has time and knowledge about formatting them, i'd appreciate help with that. Incorporated two of the diagrams - user-ui.jpg and admin-ui.jpg. Where should the structure diagram go, if it's going to go in? Did a spell check.
* Some pictures you might want to use for the IPC7 paper.viega1998-07-294-0/+0
|
* Ok, i've filled in the architecture (now "structure") using stuff fromklm1998-07-281-157/+285
| | | | | | | | | | | | | | | | | barry's arch.txt. I've also taken my first complete pass through the document, refining the stuff i already had there (and adding, for example, a fragment from the driver script, exhibiting the handy dandy logging setup). I've addressed some of barry's written comments and suggestions, including applying some of the traditional capaitalization i tend to ignore, and changing "maillist" to "mailing list" when referring to the social entity - "MailList" refers to the programming class and instance entities. As for your "conventional protocols" question, barry - my understanding is that conventions *are* agreements - explicit or not. I think this is a good term, but lets scrutinize further.
* Almost a complete draft - i just have to incorporate barry'sklm1998-07-281-57/+179
| | | | | architecture sketch. And we need to consider the title of the thing - suggestions?
* Slightly rearranged, added section detailing core classes. Added XXXbwarsaw1998-07-281-0/+178
| | | | notes based on Ken's email and conversations.
* Another checkpoint - please read!klm1998-07-281-94/+69
|
* Checkpoint.klm1998-07-281-199/+172
|
* Draft of mailman paper for Internation Python Conference VII.klm1998-07-261-0/+263
generated by cgit v1.2.3-70-g09d2 (git 2.52.0) at 2026-02-08 17:56:27 +0000