Hi,

Brad and Barry: thanks for your reply!

On Thu, Jan 05, 2006 at 09:03:39PM -0500, Barry Warsaw wrote:
> On Wed, 2006-01-04 at 16:57 +0100, Joost van Baal wrote:
> 
> > I'd like to document my patch for making Mailman OpenPGP and S/MIME
> > aware ( http://non-gnu.uvt.nl/pub/mailman/ ).  I'd like this
> > documentation to integrate nicely with the official Mailman
> > documenation.  What is the preferred format for creating documentation?
> > 
> > I believe it's LaTeX.  However, the sources for
> > mailman-{admin,install,member}.{ps,pdf,txt} are neither in
> > cvs/sf/mailman/mailman/admin/www nor in mailman-2.1.7.tgz .  It'd help
> > me if these sources got published somewhere.
> 
> LaTeX is the preferred format for the documentation source.  We process
> our .tex files with the mkhowto program from the Python distribution.
> These rules apply for Mailman too:
> 
> http://www.python.org/doc/current/doc/doc.html
> 
> The source files are available in CVS, here:
> 
> http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/doc/?only_with_tag=Release_2_1-maint

Oops, of course.  Apparently I got confused by the rsync calls in the
Makefile in admin/www, and stopped searching too early.

I'll start documenting my Secure List Server patch using this
framework (it's patch #1167696, BTW).

Bye,

Joost

-- 
Joost van Baal                            http://abramowitz.uvt.nl/
                                                 Tilburg University
[EMAIL PROTECTED]                                  The Netherlands

Attachment: signature.asc
Description: Digital signature

_______________________________________________
Mailman-Developers mailing list
[email protected]
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-developers/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Reply via email to