Return to bbleader.me CVS log

Up to [CSRG BSD Unix] / 43BSDReno / share / doc / usd / 08.mh

Annotation of 43BSDReno/share/doc/usd/08.mh/bbleader.me, revision 1.1.1.1

1.1       root        1: .\"    This file is automatically generated.  Do not edit!
                      2: .SC BBLEADER 1
                      3: .NA
                      4: BBleader \- responsiblities of a BBoard\-leader
                      5: .SY
                      6: bbl
                      7: bboard
                      8: \%[+folder]
                      9: \%[\-shell\ shell]
                     10: \%[\-verbose]
                     11: \%[\-help]
                     12: .DE
                     13: What follows is a description of the responsibilities of a BBleader.  
                     14: This is a working collection of facts:
                     15: there are no simple or elegant rules.
                     16: In the discussion that follows, 
                     17: substitute in the name of your BBoard wherever you see the ficticious
                     18: name ``hacks''.
                     19: 
                     20: .in +.5i
                     21: .ti -.5i
                     22: \fBPreliminary Maintenance\fR
                     23: .br
                     24: When you are appointed a BBleader by the person who is acting as the
                     25: \fIPostMaster\fR you should first make sure that 
                     26: the four addresses associated with your BBoard are correct
                     27: (see \fIbboards\fR\0(1)).
                     28: To check this, try \*(lqbbc -topics -verbose hacks\*(rq.
                     29: You should be listed under local leader(s), and the BBoard addresses should
                     30: be correct.
                     31: 
                     32: .ti -.5i
                     33: \fBPeriodic Maintenance\fR
                     34: .br
                     35: There are three functions that you should perform periodically:
                     36: .in +.75i
                     37: .br
                     38: .ti -.5i
                     39: \fBRead the BBoard\fR\0:
                     40: If you're a BBoard leader you should be keeping up on what's going on.
                     41: .br
                     42: .ti -.5i
                     43: \fBRemove inappropriate material\fR\0:
                     44: If offsensive or otherwise non-sensical material shows up, 
                     45: or if a duplicate message appears,
                     46: use the \fIBBl\fR program, delete the offending messages from the folder.
                     47: .br
                     48: .ti -.5i
                     49: \fBArchive non-recent material\fR\0:
                     50: The archive facility has been upgraded to be almost fully automated.
                     51: BBoards with the Auto-Archive flag set will have old material automatically
                     52: placed in the archive area once a week.  You may also archive material
                     53: yourself if you like, or if your BBoard is not set to Auto-Archive.
                     54: Just file messages in the folder ``+bbl'' into the folder ``+bbl/arc''
                     55: You should archive material whenever it takes a long time to read in a
                     56: BBoard using \fIbbc\fR and \fImsh\fR.
                     57: The only exception to this is (possibly) the \fBap-news\fR and
                     58: \fBny-times\fR BBoards,
                     59: in which case non-recent material is usually deleted,
                     60: and an archive is not kept.
                     61: .in -.75i
                     62: 
                     63: .ti -.5i
                     64: \fBSporadic Maintenance\fR
                     65: .br
                     66: As a BBoard leader 
                     67: there are three groups of people that you will be required to deal with:
                     68: .in +.75i
                     69: .br
                     70: .ti -.5i
                     71: \fBBBoard users\fR\0:
                     72: Correspondence from BBoard users is usually addressed to
                     73: \fBlocal\-hacks\-request\fR.
                     74: Although the nature of such correspondence varies, 
                     75: the most usual topic is how to get access to archives for the BBoard.
                     76: In such cases, if the archives are on-line in the ~bboards/archive/ area, 
                     77: then you should refer the BBoard user to the appropriate files.
                     78: If not, then you should contact the \fIPostMaster\fR and ask
                     79: for archive retrieval.
                     80: Archives may be accessed through the normal
                     81: \fIbbc\fR and \fImsh\fR programs, using the `\-archive' switch to \fIbbc\fR.
                     82: .br
                     83: .ti -.5i
                     84: \fBBBoard leaders\fR\0:
                     85: You may have to correspond with the people who maintain the
                     86: \fBInternet\fR mailing list for the BBoard.
                     87: Their address is \fBhacks\-request\fR.
                     88: .br
                     89: .ti -.5i
                     90: \fBPostOffice personnel\fR\0:
                     91: You may need help or advice.  The address to turn to is \fIPostMaster\fR.
                     92: .in -.75i
                     93: .in -.5i
                     94: .Fi
                     95: ^$HOME/\&.mh\(ruprofile~^The user profile
                     96: .Pr
                     97: ^Path:~^To determine the user's MH directory
                     98: .Sa
                     99: bboards(1), bbc(1), bbl(1), msh(1)
                    100: .De
                    101: The default bboard is \*(lqsystem\*(rq
                    102: .Co
                    103: None
                    104: .En

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.