Majordomo2 development is coming along nicely and one of the few things
holding off the "alpha" designation is the lack of a reasonably complete
set of user documentation. (Actually it doesn't yet have even a
rudimentary help file.) To remedy this I have created a list entitled
"mj2-docs" at my site to host relevant discussion and I invite members of
these lists who may be interested in writing or discussing documentation
but haven't wanted to follow the technical development details on
majordomo-workers to join. To add yourself to the list, send the
appropriate incantation to mj2-docs-request@hpc.uh.edu. Note that you
shouldn't send your request to majordomo@hpc.uh.edu, because mj2-docs is
actually being run by Majordomo2 itself while my normal lists still run on
my Majordomo1 server.
Your request will have to be confirmed; the method is different from
Majordomo1 but hopefully the instructions are sufficiently enlightening.
If not, that's what the list is for.
Some may be asking why we shouldn't just use majordomo-docs@greatcircle
instead of creating another list. Well, my main concern was to free the
list from having to escape administrivia. (Thanks to Majordomo2 features,
I can allow some folks to get away with more than others.) Plus this gives
me a set of users who will be reasonably understanding of the various
issues involved in testing and developing the software so that I can
actually use Majordomo2 to run it. Finally it gives the folks a chance to
actually use the software they'll be documenting. Hopefully no one will
find me too presumptuous.
Finally, remember that the list is being run with essentially alpha-quality
software that most definitely has bugs. It's been up, running and carrying
traffic for several ways now and hasn't been problematic but there's always
one more (pile of) bugs. Please be patient and if you notice any anomalies
be sure to report them at <URL:http://www.hpc.uh.edu/majordomo/#bugs>.
- J<
|
|
