OS2NET Guidelines 09/03/92 ------------------------------------------------------------------------ 1.0 Introduction OS2NET is a collection of BBS SysOps who believe in the value and capabilities of the OS/2 operating system. OS2NET is in no way affiliated with the IBM Corporation, which is the owner of the OS/2 operating system. However, IBM and other parties may cooperate with OS2NET from time to time in limited capacities where the interests of OS2NET and its users are served. There are no rights associated with membership within OS2NET. The benefits gained from OS2NET membership may be revoked at any time with no advanced notice and without cause by any level of administration within OS2NET. Membership in OS2NET should be considered a privilege and not a right. Member sysops having a problem with a Coordinator that has not been resolved in direct efforts with that Coordinator, may, if the situation warrants, contact the Coordinator at the next highest level for assistance. Any decision made by that Coordinator will be binding on all parties concerned. We observe two general guidelines: 1) Don't be a bother. 2) Don't let other's actions easily bother you. 2.0 Membership Requirements 2.1 All members of OS2NET must have software that is functionally capable of communicating with others in OS2NET. 2.2 No disparagement. OS2NET does not tolerate arguments to the effect of 'this OS is better than that OS'. OS2NET exists to advance the skills and productivity of the OS/2 user community. Other operating systems and operating environments have their place. We simply do not allow discussions as to where those places should be. 2.3 No illegal activities. This includes but is not limited to credit card numbers, phreaking, exchanging passwords, pirated software, and exchanging personal information gained illegally. 2.4 No threats. Including those to software, hardware, property, person or institutions. 2.5 No obscenity or profanity. While not wishing to be prudes, this is intended to be a professional network. A network for professionals does not need this type of activity. If you can not express yourself accordingly you will be expressed out of the network. 3.0 Applying for Membership 3.1 First, obtain a current copy of the nodelist known as OS2LIST. This should be available from any OS2NET BBS. Contact the SysOp if you are having trouble locating it. 3.2 Send a message to the coordinator nearest you. OS2NET assigns addresses on a geographic basis. If you have contacted the wrong coordinator, your application will be forwarded to the correct coordinator. All of the following information must be included with your application. System Name Sysop Name Location (City, State/Province) System Phone Number Maximum Baud rate Name and version of Mailer Hours that the system is available for mail Modem type 3.3 Application for membership implies acceptance of the terms for membership defined in these guidelines. 4.0 Positions within OS2NET 4.1 Node. This is a system fully capable of participating in the OS2NET. 4.2 Network Coordinator (NC). Listed as HOST in the OS2LIST. This is the coordinator in charge of a small geographic area. Usually the size of a state, province, or small country. Duties for the NC include: 1. Assigning node numbers to prospective sysops in the NCs area of responsibility. 2. Providing updated nodelist information to the RC 3. Distributing the weekly OS2LIST/DIFF to leaf nodes. 4. Providing echomail services to leaf nodes. 4.3 Regional Coordinator (RC). Listed as REGION in the OS2LIST. This is a geographic area made up of several nets, usually a portion of a larger country or a continent. Duties for the RC include: 1. Appointing Network Coordinators for areas within the RC's geographic area. 2. Providing updated nodelist information to the ZC. 3. Distributing the weekly OS2LIST/DIFF to NCs. 4. Providing echomail services to NCs. 5. Participation in OS2NET echomail backbone. 4.4 Zone Coordinator (ZC). Listed as ZONE in the OS2LIST. The ZONE Coordinator for OS2NET is the coordinator for the entire network. The OS2NET ZONE (number 81) covers the entire planet at this time. Duties for the ZC include: 1. Appointing Region Coordinators. 2. Distributing the weekly OS2LIST/DIFF to RCs. 3. Acting as primary OS2NET representative to the world. 4.5 Zone Echomail Coordinator. The Zone Echomail Coordinator is responsible for coordinating the orderly flow of echomail within OS2NET. Duties for the ZEC include: 1. Coordinating the operation of the OS2NET backbone. 2. Arranging and monitoring gateways to other networks. 3. Maintaining the OS2NET Echo List, the network's echomail directory. 4.6 Moderator. A moderator runs an echomail conference. The moderator should be considered the owner of the conference and maintains complete authority over the conference. All OS2NET nodes must acknowledge the rights of the moderator to take whatever measures necessary to control the integrity of the conference. This includes dictating guidelines for partici- pation in the conference and the authority to order that a feed for a particular conference be terminated. 5.0 Echomail in OS2NET 5.1 The OS2NET backbone is composed of Regional Coordinators. Each RC provides all OS2NET echoes to the Network Coordinators for distribution to member nodes. Each NC will make any backbone echo available to its member node(s) on request. 5.2 "Local" or "non-backbone" echoes may exist, coordinated at either the NC or RC level, as appropriate. Such echoes often serve the needs of the local community, and are not appropriate for net-wide distribution. 5.3 Each node is required to carry, and encouraged to read, the OS2-SYSOP conference. This is a general discussion area for OS2NET sysops ONLY. It is used for discussion and announcements regarding both technical and administrative issues affecting member nodes. 5.4 To submit a new echo to the OS2NET backbone, the host node (home system for the prospective moderator) should provide the name and a full description of the echo, along with the name of the moderator to the Regional Coordinator. The RC recieving such a request will forward the information to the other backbone nodes (RCs ) on the OS2-ADMIN echo. After a vote of acceptance by the RCs, the ZEC will announce the availability of the echo to OS2NET in the OS2-SYSOP conference. 6.0 Finding OS2NET If you have received this document and have no idea where to find an OS2NET node you may contact the current Zone Coordinator or current Zone Echo Coordinator. Both are members of FidoNet and may be reached there. Please attempt to contact your local coordinator first, as you will probably receive a quicker response. Zone Coordinator -- Ron Gines The Gateway/2 OS/2 BBS St. Louis, Missouri U.S.A (314)554-9313 (FidoNet-1:100/220) (TOADNET-86:8012:17) (OS2NET-81:200/1) Zone Echo Coordinator -- Thom McElveen NiteWing BBS Owego, New York U.S.A. (607)687-3470 (FidoNet-1:260/410) (FamilyNet-8:72/5) (OS2NET-81:100/1) (PRODIGY-BDKV87A) (CompuServe-76414,427)