PDN POLICY REV 9.3
Revised 13 February 1996 by Janis Kracht

Janis Kracht
International Coordinator, Programmer's Distribution Network
1:2320/38 (V.Everything)
1:2320/100 (V.Everything)
Voice: (502)245-4353.
Internet: jkracht@thepoint.net
Web:      http://www.thepoint.net/~jkracht


The PDN is now comprised of the following File Echos:

  Area Name        Area Description
  =========        ================
  PDNHATCH         Files from Authors/All Nodes. Required Area for PDN
                   Membership.
  PDNAI            Files related to Artificial Intelligence
  PDNNEWS          Any and all Programming related Newsletters, Magazines
  PDNASM           80xxx Assembly files
  PDNBASIC         MSDOS Basic files
  PDNCEE           MSDOS C / C++ files
  PDNDJGPP         D.J. Delorie's C/C++ Compiler
  PDNJAVA          JAVA Development
  PDNOS2           OS/2 files
  PDNOTHER         Amiga, Macintosh, etc. files
  PDNGNU           GNU/Unix files
  PDNGNDOS         GNU/DOS files
  PDNLANG          Other files & languages(Modula-2, Cobol, fortran, etc.
                    and multiple language files.
  PDNUNIX          UNIX related files
  PDNTECH          Technical specifications, FAQ files.
  PDNWIN           Windows files
  PDNVBWIN         Files for VB Windows environment
  PDNVBDOS         Files for VB DOS programmers
  PDNWINNT         Development/programmers tools for WindowsNT
  PLSLACK          PDN Linux SlackWare v2.x



The PDN is now working with Marc Van Leeuwen, coordinator of PASCAL-Net in
Holland.  These areas replace PDNPASCL:

area PASADMIT    ADMIT files for Pascal-Net (PDN) area's in Zones other than 1.
area PASCLNET    Pascal-Net related files and programs
area PASCOMMS    Pascal-Net | Communication & Networks
area PASFILES    Pascal-Net | Ungrouped files and programs
area PASGRAPH    Pascal-Net | Graphical orientaded files
area PASNDIFF    Pascal-Net | DIFF-files
area PASNLIST    Pascal-Net | Nodelist
area PASOOP      Pascal-Net | Object Orientated Programming
area PASPATCH    Pascal-Net | Updates and patches for the compiler
area PASSWAG     Pascal-Net | SWAG (-related) programs/files
area PASTEXT     Pascal-Net | Pascal-related textfiles
area PASTOOLS    Pascal-Net | Tool(boxes) and utilities
area PASTVIS     Pascal-Net | Turbo Vision related files
area PASWIN      Pascal-Net | Windows related files


1.  Any and all nodes will be able to directly hatch submissions into the PDN
in the PDNHATCH file area. Files will be received at 1:2320/38 via this area
and will be reviewed for distribution by the International Coordinator. In
releasing files in this area, the author or agent understands the file may be
released via any method the International Coordinator sees fit.

As of  3 January, 1994, all nodes are required to add the PDNHATCH
file echo to their TICK (or compatible) config file whether they themselves
intend to release files or not. Under no circumstances shall any node release
a file in any other PDN File Echo Area other than PDNHATCH.

Authors or agents may file attach files for review to 1:2320/38 (VEverything)
or 1:2320/100 (HST/V32B) at any time.

Authors or agents may logon to <<PRISM BBS (502)245-8117 VEverything, or (502)
245-1146 HST/V32B and upload files for review at any time.

Submissions may also be mailed (snail mail) to me at this address:
     Janis Kracht
     1512 Grandin Woods Court,
     Louisville, Kentucky 40299 USA

2.  In the above text, "files" are refered to as Libraries, Object code,
Source code or Executables.  I would also ask that the author (or authorized
agent) please make sure that the file being entered into the PDNHATCH file
area be documented, and functional.  "CrippleWare" or "VaporWare" should not
be submitted.

             ONLY PUBLIC DOMAIN AND SHAREWARE SHOULD BE SUBMITTED.

    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".  An example in the 'C' language is a library that contains a
certain memory model that can be used at link time so the end user can see
first hand the power of the library.  Editors that are designed around
programming are encouraged to be submitted as well, as long as they meet the
above criteria.

3.  There is an Echo set up between all the the PDNRC's called PDNRCECHO.
This Echo is strictly for the use of the PDNRC's in each Zone, and for
nodes that are a gateway to another Zone.  Normal downstream nodes should
not have access to this echo, as it is for administrative uses only.

4.  There is an Echo set up for all the nodes called PDNECHO. This Echo is
for the users of individual BBS's so those users of files that are sent
through the PDN can have a medium that is appropriate to contact the author
about the file.  It will also be used by the PDNRC's to conduct business
pertaining to the PDN with downstream nodes.  This echo is also used to
allow for a general "chit-chat" area about programming in any and all
languages and platforms. This echo is available on the backbone with the tag
PDNECHO.

5.  ALL PDN nodes will have session-level passwords with their up/downlinks.
This is simply to ensure the integrity of the PDN.

6.  ANY file that comes to your system via the PDN 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 PDN 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.

7.  New areas:  If a node wishes to create a new area for the PDN, so the PDN
can be better defined, that node should make a formal "request for comments"
in the PDNECHO for all to discuss.  After a substantial amount of time (to be
determined by the PDNRC's and the PDNIC, but no longer then necessary), the
new area may be created.  If the new area is created, then the node
requesting the new area should either find someone willing to "moderate" the
area, or do it him/herself.

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

9.  Any changes/additions to this policy should be coordinated with
    Janis Kracht 1:2320/38, and discussed in the PDNRCECHO or the PDNECHO.
