Batch File Distribution System file echo Network                        
Update: June 15, 1995
Dennis Powers BFDS Coordinator
1:141/1135
                                POLICY STATEMENT  
                               ==================

 Area Type   Area Name        Area Description
 =========   =========        ================
  FDN         BFDS            FDN Batch Files, Utilities, and Enhancement programs
  FDN         BFDS4DOS        File Echo for 4DOS code, scripts and utilities
  FDN         BFDS_ADM        File Echo Return to BFDS Headquarters (Pass thru)

  ECHO        BFDS_MAIL       BFDS Message echo for Admin of the BFDS Network
      
 1) "Files" are refered to as Libraries, scripts, Source code or
    Executables pertaining to BATCH file programming including utilities
    for enhancing DOS or it's equivilent.  I also ask that the author 
    (or authorized agent) please make sure that the file being entered
    into the BFDS be  documented, and functional.  "CrippleWare" 
    or "VaporWare" should not be  submitted.    
    
    ONLY PUBLIC DOMAIN AND SHAREWARE SHOULD BE SUBMITTED! 

 2) Demonstration software submitted will be allowed only if the software
    is able to be used in some fashion that will enable the end user to
    "Try before you buy".  Editors that are designed around programming
    are encouraged to be submitted as well, as long as they meet the above
    criteria.

 3) Any and all nodes will be able to directly hatch submissions into the
    BFDS_ADM for return to the BFDS Headquarters, As long as they are connected 
    to the BFDS_MAIL echo (see item 4).  Any Node that abuses this will be 
    removed from the BFDS.  Open Hatching is NOT allowed in the mail BFDS FDN.

 4) There is an Echo set up between all the the BFDS Nodes called
    BFDS_MAIL. This Echo is for the use of the BFDS in each Zone
    and is open to all sysops and Batch / DOS utility authors who wish
    information or help in the distribution of their files.

 5) It is recommended that all BFDS nodes will have session-level
    passwords with their up/downlinks.  This is simply to ensure the
    integrity of the BFDS.   ANY file that comes to your system via the
    BFDS should have the CRC checked  by TICK as it is processed.  No
    archive advertisments should be placed into the archive while the file
    is still being sent to another node.  The BFDS is not meant to
    advertise a BBS, but to move files.  This also corrupts the CRC info,
    and it will cause TICK to bomb out on the CRC check.  Nodes should not 
    re-archive the file until that node is sure ALL the downstream nodes
    have it.  Please pay attention to authors wishes when re-packing files.

 6) All Archived files Hatched from the BFDS Headquarters will be in the
    ZIP format (version 2.04g) and will contain an -AV code assigned to
    the BFDS File Distribution Network by PKware Inc.

 7) The BFDS is FREE, and open to everyone.  However, sometimes it costs
    money to move these files, so there is no problem with asking LOCAL
    downstream nodes to help pay for the phone call when picking up the
    BFDS.  The cost sharing  policy should be fair, well laid out, and with
    the consensus of all involved.  The BFDS should be allowed to travel as
    far and to as many nodes as possible.

 8) The files and programs distributed via the BFDS FDN may have distribution
    channels other than FIDONET.  However before any distribution channel is
    established it must be approved by the BFDS coordinator.

 9) All Files and programs Hatched (distributed) into the BFDS or the BFDS_ADM
    file echos must be free of distribution restrictions (Satellite, Internet..)
    If there are *any* distribution restrictions the file must be forwarded to
    the BFDS Coordinator directly for review and possible distribution.

10) Any changes/additions to this policy should be coordinated with:

    Dennis Powers
    BFDS Coordinator
    1:141/1135