From majordomo-docs-owner Sun Feb 22 08:53:39 1998 Received: (majordom@localhost) by honor.greatcircle.com (8.8.5/Honor-Lists-970926-1) id IAA20499; Sun, 22 Feb 1998 08:09:02 -0800 (PST) Received: from sina.hpc.uh.edu (Sina.HPC.UH.EDU [129.7.3.5]) by honor.greatcircle.com (8.8.5/Honor-980202-1) with ESMTP id XAA23705; Sat, 21 Feb 1998 23:21:08 -0800 (PST) Received: (from tibbs@localhost) by sina.hpc.uh.edu (8.7.3/8.7.3) id BAA27039; Sun, 22 Feb 1998 01:26:54 -0600 (CST) To: majordomo-users@greatcircle.com, majordomo-docs@greatcircle.com Subject: Majordomo2 documentation list Mime-Version: 1.0 (generated by tm-edit 7.100) Content-Type: text/plain; charset=US-ASCII From: Jason L Tibbitts III Date: 22 Feb 1998 01:26:53 -0600 Message-ID: Lines: 34 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: majordomo-docs-owner@GreatCircle.COM Precedence: bulk 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 . - J<