summaryrefslogtreecommitdiff
path: root/Mailman/pythonlib
diff options
context:
space:
mode:
authorklm1998-07-28 23:37:57 +0000
committerklm1998-07-28 23:37:57 +0000
commit029a4486ebed54ff4386b91bfd5af58a59e0b961 (patch)
treea0c3d6a756dc8a638d1a17ec89e64d2dfe6e8652 /Mailman/pythonlib
parentffd20d971828f5f08572dc064c90b2a65f8124dd (diff)
downloadmailman-029a4486ebed54ff4386b91bfd5af58a59e0b961.tar.gz
mailman-029a4486ebed54ff4386b91bfd5af58a59e0b961.tar.zst
mailman-029a4486ebed54ff4386b91bfd5af58a59e0b961.zip
Ok, i've filled in the architecture (now "structure") using stuff from
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.
Diffstat (limited to 'Mailman/pythonlib')
0 files changed, 0 insertions, 0 deletions