Annotation of 43BSDReno/contrib/mh/conf/doc/bbleader.rf, revision 1.1.1.1

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

unix.superglobalmegacorp.com

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