A V I A T I O N n e t

An Aviation fido-based BBS Network

Written by Cory Robin, AviationNet

(C) Copywrite Robin Aviation 1995

I. About AVIATIONnet

The purpose of AVIATIONnet is multifaceted. First, it serves as a base, aviation network of BBS boards able to bring low cost networking to those who are interested in aviation. Second, it serves its National community, by the distribution of subs specifically targeted for aviation discussion. Hopefully, this will include news sections and so on from clubs, Businesses, Organizations schools and so on.

II. Joining AVIATIONnet

ALL NODES must be coordinated through the NC or Assistant NC. Anyone may join AviationNet, ANY business or organization can make special arrangements through Cory Robin <Network Coordinator>. To obtain a node number, mail the Net Coordinator, Cory Robin (40:311/27 AVIATIONnet) uploading the following form. If you have already arranged a connection with a server, indicate so where appropriate. To maintain mail flow in as expedient a manner as possible and at the same time keep toll calls to a minimum, the net coordinator may suggest an alternate server. The purpose of the following form is only to gather appropriate data to properly administer the net, not for exclusionary purposes.

IV. Joining/Hosting Echos in AVIATIONnet

1. ALL NEW ECHOS must be coordinated through the Net Coordinator.

2. Gating of echo's between AVIATIONnet and other nets is permissible as long as the gate	is approved by the echo hosts in each net.

3. The following are REQUIRED AVIATIONnet echo's, all sysops must subscribe and	SCAN. General conversation will be allowed on these subs in an effort to obtain a close-knit	organization.

TOPIC	AREATAG

AVIATIONnet SysOps	AV_SYSOP

AVIATIONnet Admin	AV_ADMIN

4. The complete listing of the AVIATIONnet echo conferences is located in AVIATION.NA.

VI. Network Rules and Conduct

E.1 Why we have Rules

The reason that AVIATIONnet is such a great network is that everyone is able to get along well and support each other in everything they do. No one is asking you to agree with everyone else. However, common courtesy and respect are essential in all computer networks. As much as we hate to impose rules and restrictions, we feel that following these rules will help AVIATIONnet become even better.

First and Foremost, it is a SysOp's unique responsibilty to limit Network access on his or her system to responsible users. SysOps are expected to handle any problem user which is accessing

the network from his or her board. In the event that a problem is persistant, a warning will be issued to that system. If the problem continues, the Network Coordinator will have no choice other than to

suspend the network connect to the originating node.

E.2 Policy Guidelines

1. Always remember that you are a guest in many homes, when you post on the net. Please keep the language clean.

2. FLAMING IS EXPRESSLY PROHIBITED IN ALL SUBS ON AVIATIONnet. AVIATIONnet administration has seen what happens on OTHER nets, and they don't like it. So far, AVIATIONnet has been free of ANY disputes. Any overly aggressive posting will be grounds for your removal. No questions asked. If the network coordinator feels you are out of line, it is very easy for him to remove your node number. This is not a democracy.

3. NEVER make something received in email public, unless you have the sender's permission. Making Email public is annoying behaviour and may be grounds for removal from the network.

4. Always try to be helpful toward the newer members. Remember, you were new at one time.

5. Avoid junk posts. Enough said?

6. Never "talk down" to anyone. AVIATIONnet members have equal respect for one another, even though their views may differ.

7. Please make an effort to remain on topic.

10. Realize that a message does not appear on all systems on the same day. A message that you reply to, and think settled, may continue to receive replies for several days.

11. Remember that everyone is entitled to their opinion. If you do not agree, a cool, reasonable post stating the reasons for your disagreement, is much better than lowering yourself to name calling. Realize that some people will argue, just for the sake of argument. If you find yourself involved with one of this type, swallow your pride and let the argument die. It takes two to sustain an argument.

12. Do not belittle anyone's computer, software, etc. Remember that you choose your equipment because it best suits your needs. The other person may not have the same needs as yourself.

13. All ADULT material must be kept to the adults and access is the sole responsibility of the sysop. Although AVIATIONnet has only ONE adult echo (AV_MILE_HIGH) this MUST be clarified.

14. The Network Coordinator may remove any system from the network, without prior notification, for any reason.

Remember, this is a computer network, not a democracy. If there is a problem with an individual system, it should be dealt by the NC. If the NC is unable to resolve it, the RC will be consulted, and finally the ZC. All decisions of the ZC are final. If you are having problems with your NC or RC, contact the next highest staff level. For example, if you can't agree with your NC about when you should be allowed to connect, ask your RC to intervene.

15. One of the AVIATIONnet traditions is for all SysOps in the net to send mail to a new node once it has joined. The ZC always lists newly joined nodes in the SysOp Sub, and new SysOps will feel much more welcome if they receive some personal mail when they first join the net. Also, it is a good way to get to know the other SysOps.

16. Any gateways into or out of AVIATIONnet must be pre-approved by Network Coordinator.

17. Use of high-ascii in To: & From: headers, and in AVLISTs is prohibited. Use of high-ascii and colors in gated subs is completely prohibited.

18. No test posts or "this is a test" type messages are permitted in ANY echos.

19. Please obsever tagline guidelines. If incorrect taglines are allowed to enter the network, they can cause problems if they move through gateways to other BBS systems.

20. MassMailing right for the entire network or any portion thereof are reserved exclusively for the NC/RC/DC/ZC structure. Any board originating MassMail that is not of the previously mentioned offices is expelled from AVIATIONnet, no questions asked.

E.4 Un-Perfectionism

Remember that no one is perfect. The AVIATIONnet staff knows this as well. Even the best of us make mistakes. Please tolerate others, and kindly inform them that they are out of accordance with the rules. The network staff monitors almost all aspects of the network, and is usually aware when problems occur.

VII. Network Administration

F.1 Server/Client Policy

AVIATIONnet is a free and open network. Because of this, no mandatory fees are required to join. However, ANY server reserves the right to charge a REASONABLE fee for his services. This would most likely be a few dollars a month, to help cover long distance costs. Servers are not allowed to profit from their collections. Servers may choose to charge all their clients at a flat rate or by the size of their feed.

Clients, by the same token, are not required to serve from any one particular system. If you are dissatisfied with your server, contact your RC about changing. If you do not want to pay a fee to connect, find a server that doesn't charge.

Basically, you can connect to any system which is a server and will allow you.

F.2 AVNETKit Distribution

All NCs and RCs in AVIATIONnet are required to have the latest version of AVNETKit and the AVIATIONnet NA and AVLISTs as a free download on their board. It is also suggested that you establish the account AVNETKIT password AVNETKIT on your system and allow for fast and easy download of AVNETKIT.

AVNETKit is also available by mail from Cory Robin @1:311/27 FIDOnet and 1@1801032 VirtualNET. It is available by Fido FREQ from his board, as AVNETKIT.

The AVNETKit should include:

AVNET.DOC	<This Document File>

AVNET.APP	<AVIATIONnet Application>

AVIATION.NA	<AVIATIONnet Echo Listing>

AVLIST.xxx	<Current AVIATIONnet Nodelist>

README.1ST	<Contains this listing>

FILE_ID.DIZ	<BBS Description File>