1) I would like to see Mj2 Archives follow more of a directory structure
like the list information does. By this I mean it would be nice to have:
.../archives/domain/list/rotation/mail
[ Note the Y2K compliance vs .../workers-archive/majordomo-workers.9809 ]
For example:
.../archives/majordomo.umd.edu/amd-workers/1998/amd-workers.1998
Or:
.../archives/majordomo.umd.edu/woman-studies/199801/woman-studies.199801
Or:
.../archives/majordomo.umd.edu/busy-list/19980801/busy-list.19980801
If the rotation is "null" then skip the extra directory;
For example:
.../archives/coursemail.umd.edu/hist410-0101/hist410-0101
The Archiver would need to create the new directories on the fly when
nessesary
2) It would very nice to have hooks to pipe a copy of the mail to a program
during the archive phase.
For example:
| mhonarc -add -outdir <current-archive-path> <other options>
Or:
| hypermail -i -u -d <current-archive-path> <other options>
In many cases there are enough variables set in mj2 to pass reasonable
options to one of these programs.
It would make a nice base for the HyperText side of Majordomo. We could then
have a "MHonArc" or "HyperMail" plugin pretty easily that could automate
much of the work (as well as delegate those parts to others...hint). I would
think this would be implementable with out haveing to add lots of knowledge
to Mj2.
The seperate directories would allow a place to maintain .htaccess files for
private lists, html archive files, search engine files, or homepages for
each list where "info.html" files coule be kept.
It opens the door to a number of options that are best left till after Mj2
goes out. However the two basic pieces would be nice sooner.
1) Archive to directories
2) Pipe to a program while mj_variables are set.
What whould all this give us?
a) Automatiic maintainance of the directory structure for the web side of
Majordomo.
b) A documentable filesystem layout to build other tools against.
I am thinking of a "MajorHype".
Where:
http://majordomo.umd.edu/amd-workers
Would take you to the "amd-workers" home page and archives.
Where:
http://majordomo.umd.edu/amd-workers/request
Would take you to "-request" options for the "amd-workers" list.
where:
http://majordomo.umd.edu/amd-workers/owner
Would take you to "-owner options for the "amd-workers" list.
Where:
http://majordomo.umd.edu/
Would take you to the "majordomo.umd.edu" home page and list pages.
Where:
http://majordomo.umd.edu/request
Would take you to "-request" options for the "majordomo.umd.edu" domain.
Where:
http://majordomo.umd.edu/owner
Would take you to "-owner options for the "majordomo.umd.edu" domain.
We would use the majordomo/bin commands like "mj_shell" to manage the
lists. These (for those who have not used them) are a powerful addition to
Majordomo.
We could offer SSL and https to get added security for majordomo.
We could provide an easy to understand web interface to the growing lists of
Mj2 features. (I really really like the features of Mj2, however my user
community is way too confused. I need to give them something with a "help"
button by every command, and hide syntax as much as possible.)
Randall
Follow-Ups:
|
|
