[Mailman3-dev] Suggested Features
Mark A. Mandel
mamandel at ldc.upenn.edu
Mon Mar 15 18:52:20 EST 2004
On Mon, 15 Mar 2004, Barry Warsaw wrote:
#On Mon, 2004-03-15 at 09:59, Mark A. Mandel wrote:
#> Ability to modify the HTML template for more than the couple of pages
#> that I can change now. It is currently difficult approaching
#> impracticable to go from reading, say, the Jan. 31 archive mail to the
#> Feb. 1 mail (assuming monthly archiving).
#
#Let me say right now that while I deeply sympathize with people who want
#a better archiver, it's not on my plate for Mailman 3.0 I think the
#best we can hope for is adapting the current Pipermail software to fit
#into the MM3 architecture, unless someone steps forward to champion the
#archiver effort.
Maybe I don't belong on THIS list, because I'm not a developer.
Pipermail is not part of Mailman? Ah.
I'm not asking for a better archiver, as I understand it; just a change
in the HTML template in which the archive levels are presented. Even if
the monthly archive pages and the individual posts (such as
.../pipermail/LISTNAME/2004-March/date.html and
...//pipermail/cyp-list/2004-March/000123.html) had links BACK TO THE
MAIN ARCHIVE PAGE (.../pipermail/LISTNAME/) -- a single static link in
the HTML templates -- it would be a real improvement.
The posts and the monthly archive pages now have links saying
"More information about the LISTNAME mailing list"
"More info on this list... "
which both point to
...mailman/listinfo.cgi/cyp-list
If that can be generated, so can a link to .../pipermail/LISTNAME/ .
So... where do I ask, if not here?
-- Mark A. Mandel
Linguistic Data Consortium, University of Pennsylvania
More information about the Mailman3-Dev
mailing list