The World of Computer Software

home *** CD-ROM | disk | FTP | other *** search

/ The World of Computer Software / World_Of_Computer_Software-02-387-Vol-3of3.iso / s / sdn_pol7.zip / SDN_SITE.DOC < prev

Wrap

Text File | 1992-08-18 | 32KB | 713 lines

┌─────────────────────────┐ │┌────────────────────────┴┐ ││ SDN International (sm) ├────────────────────────────────────────── ││ Distribution Site └──────────────────────────────────────────── ││ ││ Simple Guidelines for Sysops participating in SDNet Distribution ││ ││ Published by The SDN Project, Easter, April, 1992 ││ │ This document is (c) Copyright The SDN Project 1991 and the property of Ray L. Kaliss as The SDN Project. This document may not be copied in whole or in part without the express permission of The SDN Project. This document is not public domain. It is intended as an informational document for BBS Sysops considering becoming SDN distribution sites. This document may be copied in whole for that intend only. Official SDN International policy is formulated by The SDN Project and published at The SDN Project BBS in Meriden Connecticut, U.S.A. 203-634-0370. Policy online at The SDN Project supersedes policy in circulating form or of earlier date. SDN, The SDN Project, the service mark of SDN International (sm) and SDNet and the file extensions of .SDN/.SDA as used by The SDN Project are (c)Copyright 1989 of Ray L. Kaliss and can not be used with out express written permission of Ray Kaliss. ╒══════════════════════╕ │ THANKS AND GRATITUDE └───────────────────────────────────────────────────── Special thanks are due to a variety of people and organizations who have given of time, talent and good will to make SDN work. Thanks are also due to those who have contributed in some way to making my own tasks a bit easier or wiser. Charlie Smith, Pete White, James Smith, Chuck Venter, Mike Martell, Mike Fuchs, Ernesto Hagmann, Robert Tolz, Todd Pattist, John Souvestre, Barry Geller, Kelly Drown and Ray Waldo. Thanks to the other members of IFDC, Peter Stern (DVNet), Tom Hendricks (SDS) and Arthur Geffen (LAN) and thanks to G.K. Pace. Thanks for past or present support goes to American Cybernetics, USRobotics, PC-Link and Quantiun Services, BIX on-line Service, Central Point Software Inc., and NoGate Consulting. For the list of others needing special thanks read the entire SDNetList! ╒══════════╕ │ CONTENTS └───────────────────────────────────────────────────────────────── 1. Registered and Unregistered Sites........ 2. System Requirements...................... 3. Star Territories and Regions............. 3.1. Community Coverage.................. 4. Hatching and Routing.................... 4.1. Polling Your Feed................... 4.2. Session Security.................... 5. Downloadable Files Areas................. 5.1. Toss Files Like Echo................ 5.2. File Requests....................... 5.3. Compression Security................ 5.4. Thirty Day Holding Rule............. 6. Echo Message Areas....................... 7. Monthly SDNet Registration............... 8. Legal And Friendly....................... Addendum Information ╒══════════════════════════════════════╕ │ 1. REGISTERED AND UNREGISTERED SITES └───────────────────────────────────── SDN recognizes the fact that SDN author direct shareware files are popular and are now on many BBS's world wide. And they should be, they are in the condition that the author wants them distributed in and the user wants to receive them in.. author direct. SDN activity is now spread further than official SDN distribution sites by hundreds of local sysops and informal connections forming an informal and unofficial network off of the official core SDNet. In order for the public to know and recognize SDN's core of official and registered sites, where the full SDN activity is available by direct and secure feeds, and to recognize these sysops as participating in the SDN effort and concept of author, sysop and user cooperation in the shareware concept.. the SDN Project publishes a listing of registered, and official SDN participant BBS sites, the SDNetList. Although many BBS' may be posting SDN files, official sites are directly linked, secured, timely and approved by SDN managers. Approved sites represent the core of SDN distribution, the source of the stream into FidoNet and other networks. We encourage bulletin board systems to read our policy, set up their SDN activity as advised and apply to register their systems with a local SDN Manager. Registration, of course, costs absolutely nothing except your efforts to give full service SDN activity to your users, cooperation with the SDN policy that makes SDN possible, and shows a personal dedication to the concept of software by the shareware method. For a BBS system to become a distribution site, express permission from The SDN Project through it's authorized managers is needed. A registered site can be any FTS (FidoNet Technical Standards) capable Bulletin Board System approved by an SDN Star, Regional or Net Manager. Approval is simply based upon having your SDN areas and echo setup correctly, your ability to pass them to the next site and your cooperation to help run SDN in an organized manner as representing the hundreds of shareware authors that use SDN. Any sysop may apply to an existing SDN Net Manager or Regional Manager to become a member of SDN but only systems approved by SDN Managers become official, registered and part of core SDN distribution sites. Becoming a registered node is not a right but a privilege. Once approved, you have the legal right to display the SDN service mark and be recognized by the authors and public as contributing to the shareware movement. ┌──────────────────────┐ │SDN International (sm)│ └──────────────────────┘ ╒════════════════════════╕ │ 2. SYSTEM REQUIREMENTS └─────────────────────────────────────────────────── SDN activity is automated file and echo passing among amateur and professional netmail capable bulletin board systems using FidoNet Technical Standards of communications. Requirements for SDN activity are: Receive your SDN activity from another direct link site, one already registered and approved as part of the SDN core. Permanently post SDN policy and SDN author information kit, and update these versions when revised by The SDN Project. They are the soul of the network. A file area or areas dedicated to SDN files, open for downloading. Uploading by users into SDN areas is prohibited. Received .SDN files must be held for thirty days with out re-compression or change. Carry SDN echo message areas. Register with your SDN manager on a once per month bases. Poll your registered SDN feed site no less than twice a week. A high speed modem is recommended. ╒═════════════════════════════════╕ │ 3. STAR TERRITORIES AND REGIONS └────────────────────────────────────────── SDN Regions are defined by geographical location. Large territories are designated and serviced by individual SDN-Star system Managers under the authority of The SDN Project. UNITED STATES ============= SDN International U.S. Eastern Star 100 Gordon Green 1:132/119@fidonet, 603-880-1658 Serving: Maine, New Hampshire, Vermont, Mass, Conn, RI, NY, NJ, Penn, Md, Delaware, Virginia, W. Virginia, N. Carolina, S. Carolina, Tenn, Georgia, Alabama, Mississippi, Florida, Puerto Rico, Caribbean area. SDN International U.S. MidWest Star 200 John Souvestre 1:396/1@fidonet, 405-885-5928 Serving: Wisconsin, Michigan, Illinois, Indiana, Ohio, Kentucky, North Dakota Minnesota, Nebraska, Iowa, Kansas, Missouri, Kansas, Arkansas, Louisiana, Texas and South Dakota. SDN International U.S. Western Star 300 David James, 1:209/209@fidonet 702-253-9954 Serving: Alaska, Wash, Oregon, Idaho, Montana, Hawaii, California, Nevada, Wyoming, Utah, Colorado, Arizona, New Mexico CANADA ====== SDN International Canadian Star 400 Chris Wiesner, 1:163/223@fidonet, 613-830-5391 Serving: Ontario, Quebec, New Brunswick, Nova Scotia, Newfoundland Prince Edward, Alberta, B. Columbia, Manitoba, Saskatchewan EUROPEAN AND OTHERS =================== SDN International European Star 500 Switzerland Ernesto Hagmann, 2:300/50@fidonet, 41-61-962-122 Serving: Netherlands, Switzerland, Germany, Sweden, Denmark, Italy, Austria, U. K. and other countries in the area. Each SDN Star Territory is further divided into Regions by the Star Manager. Regions are managed by a volunteer Regional Manager under the authority of the Star Manager. Regional Managers further appoint local Net Managers. By the authority of this hierarchical management system sites are registered as official distribution sites and members of SDNet. To find out who to contact for participation in SDN locate the SDNetList and netmail the SDN Manager for your for your area. If there is no local SDN manager for your area then netmail the Star Manager for your territory. When netmail inquiry is made, wait one week and then poll for a reply put on hold. ╒═════════════════════════╕ │ 3.1. COMMUNITY COVERAGE └────────────────────────────────────────────────── As a distribution service for users and other sysops, we don't need an SDN BBS on every block. Generally only a few registered distribution are really needed in any local area. If there is not an SDN registered site in your local calling area, and you meet the requirements, please apply to your areas SDN Managers. The number of SDN sites to be approved for any local area is determined by the SDN management that serves that area. ╒═════════════════════════╕ │ 4. HATCHING AND ROUTING └────────────────────────────────────────────────── SDN routing is done in an organized tier or Star pattern. The top of the tier is the SDN Project BBS, which in turn feeds the SDN Territorial Stars, which in turn feeds it's Regional Managers, which in turn feed their Net Managers, which in turn feed end sites. This follows our management hierarchy. Project Manager --------------- | --------- (one or more Stars) (one or more Stars) | | Region Mgr. Region Mgr. | | -----Net Mgr. Net Mgr.----- | | | | | | | | (Hub) (Hub) | | Site | | | | Site Site Site Site Site We appreciate that sometimes an out of state long distance call is cheaper that a long distance call in state, also phone companies may offer long distance plans you might want to take advantage of... if this is something that is necessary for you - please remain inside your SDN Star Territory, get your link only from another registered SDN direct site and while you are still under local SDN Regional Manager authority. Your update monthly registration must be processed through local SDN Managers. SDN links across country boarders is restricted to SDN Star Managers and Regional Managers. On occasion a particular country's copyright and/or customs laws do not allow a particular program or type of program to be distributed beyond county boarders. Do not put yourself in legal liability you may not be aware of by exporting or importing. No one is allowed to upload or Hatch files into the SDN areas. File come from The SDN Project _only_. ╒════════════════════════╕ ─────┘ 4.1. POLLING YOUR FEED └────────────────────────────────────────────── As a SDN participant you will be expected to poll your feed system directly to pick up files and echo at least twice per week minimum. Don't let your mail and files pile sky high. All SDN sysop poll their feed sites, we are a 'bottom up' network and poll on our own 'dime'. It is not allowed for SDN sysops to charge any fee to other SDN sysops to establish connections to receive SDN echo or files. Exceptions are made only when a local net has policy for sharing expenses that has been agreed upon and passed by a local net meeting or referendum, then local net policy may be applied to sysops of that net. SDN management may confirm if such policy exists in any particular net. ╒═══════════════════════╕ ─────┘ 4.2. SESSION SECURITY └────────────────────────────────────────────── In order to insure the integrity of the released files, simple security measures are used to assure you and your users that you have received SDN files directly from The Project and authors. Through registered network links and compression verification, program files should be uncorrupted and complete. Minimum security is as simple as session password protection on netmail links with your SDN feed and unique password protection in your TICK.CFG configuration file. Arrange and use private passwords with your feed and those other SDN sites you may in turn feed. ╒════════════════════════════╕ │ 5. DOWNLOADABLE FILE AREAS └─────────────────────────────────────────────── A registered site must install one file or more file areas dedicated to SDN files. The area(s) must have public downloadable access with NO upload capability. All newly received SDN supplied program files must be posted in that area unchanged in any way for at least 30 days. The purpose of this area is to assure users of one place to look for new SDN distributed files and the safety, integrity and completeness of .SDN files. The first files posted in this area should be SDN Policy files and our chosen standard compression utility. These files should remain at the top of your SDN area and should not be changed except when updates to them arrive via your SDN feed. Presently, SDN related files which should be posted at the beginning of your SDN File Area are: SDNxxx.EXE - SDN International information. SDN_KITx.EXE-Sharewareauthors'getstarted'kit. PAKxxx.EXE - latest version used to decompress .SDN files. Program files are designated by the file extension of .SDN. Programs may be accompanied by another file which is a pure ASCII text description file called an SDA (SDN Distribution Abstract) and will have the .SDA extension. SDA files can also be turned into Echo or Net messages to notify local sysops and users of arrivals. (filename).SDN = Program file (filename).SDA = ASCII text description ╒═══════════════════════════╕ ─────┘ 5.1. TOSS FILES LIKE ECHO └────────────────────────────────────────── The majority of SDN sysops use a utility that automates handling of .SDN/.SDA files, written by Barry Geller, it is called TICK. Just about any SDN site will be able to supply you with the latest version. The TICK utility treats files as if they were echo mail and automatically tosses them to the designated directory while updating the files listings with the new file name and a description. Be sure to read the documentation when setting up TICK. The file area "Tic-tags" for automatic utility file transfers are: ┌────────────────────────────────────────────────────┐ │ SDN_BUSI SDN_COMM SDN_DATA SDN_GRAP SDN_GAME │ │ SDN_MISC SDN_UTIL SDN_WORD SDN_OTHR SDN_TEXT │ └────────────────────────────────────────────────────┘ An area named SDN_SYST is reserved for utilities and information that can specifically help in SDN operations. These are all required areas for any registered SDN site although they can be tossed into one downloadable area or many, they represent SDN 'basic-cable'. At times SDN may offer optional areas as well. The optional areas are like 'premium' channels but free and are not required. You must ask participation system that carry optional areas to feed you these. In some Regions SDN sites may auto-Tic to non-SDN systems. Inquire of your Regional manager for your Star Territory policy on this. BBS systems are not official SDN sites just because they may get auto-Tic'ed SDN areas from you. Here is an example TIC.CFG setup for an SDN site. Note that you must set the Tick options to prevent acceptance of incoming files from those downline from you, and to prevent inadvertently hatching a file to your upline SDN source feed. ┌─────────────────────────────────────────────────────────────┐ │ AREA c:\misc\ SDN_MISC │ │ 1:123/23 PASSON *& (your SDN feed) 1:125/01 TIMON H (you feed) 1:245/00 PWORD H (you feed) ╒════════════════════╕ ─────┘ 5.2. FILE-REQUESTS └───────────────────────────────────────────────── If the BBS or netmail software you use has "File-Requesting" capability, you should enable that function so that area sysops may request .SDN files from your 30 day posting area at reasonable times. This is the very minimum requirement SDN asks you to do to fulfill your roll as a distribution site. Please share the hobby, the fun and the files. ╒═══════════════════════════╕ ─────┘ 5.3. COMPRESSION SECURITY └────────────────────────────────────────── Each program file is compressed with a utility our sysops chose by vote in 1989. All .SDN files the world over are in this standardized compression with a verifiable security feature applied. In this way, distributed files can be tested that they have not been changed or tampered with from the time that The SDN Project received and processed them. If they are changed or corrupted in any way, you will be notified upon testing or extraction. This is your protection and your users protection against Trojan, virus and nogoodniks. Be sure you post the latest copy of the decompression utility where users can readily download it. It is advisable to set up a SDN information screen informing your users what the program files are (.SDN) and what to use to decompress them. ╒══════════════════════════════╕ ─────┘ 5.4. THIRTY DAY HOLDING RULE └─────────────────────────────────────── You can not, for at least 30 day from receiving any SDN files, change them in any way. You can not recompress, rename, or in any other way change them for a period of thirty days. Because of SDN exclusive use of our Security Envelope and verifiable seal applied when files are processed at the Project, we prefer you leave .SDN files alone and keep the .SDN extension intact. This affords users safety even after the .SDN file has migrated off your system. Any re-compression will destroy this security device and void it's effectiveness in protecting program files and users. ╒═══════════════════════╕ │ 6. ECHO MESSAGE AREAS └──────────────────────────────────────────────────── Install two Echo (or conference) areas just for SDN news and communications called SDN_SYSOP and SDN_PUBLIC. Each echo area must be configured for REAL NAME use. Both are international echo's and required on any SDN system worldwide. They link all of SDN in communications. The Echo area SDN_SYSOP is what the name describes. This will be utilized by and for SDN Sysops to report changes of net topography, reports of available shareware and other subjects related to the operation of SDN. We like to keep the sysop informed and we appreciate feed back. This message area is for registered SDN sysops only, it is not open to the public and can not be exported to non-registered systems. SDN_PUBLIC is public access by your users and is distributed internationally to each SDN participating system. All your users should be allowed to use this Echo area. This message area should be named 'SDN International ECHO' and designated SDN_PUBLIC in your Echo control file. SDN_PUBLIC must be sent to any non-SDN boards you may elect to auto-Tic selected SDN areas to. Both Echoes are moderated by a volunteer sysop approved by The SDN Project Manager. The moderator policy must be respected. Disregard of the moderator guidelines can result in a warning being sent to the sysop and SDN feed links being disconnected if abuses continue. The SDN echo area tags are: ┌──────────────────────────┐ │ SDN_PUBLIC and SDN_SYSOP │ └──────────────────────────┘ Local SDN Star's, countries or Regions may have local SDN echo areas also in use. ╒═════════════════════════╕ │ 7. MONTHLY REGISTRATION └────────────────────────────────────────────────── Once you have setup for SDN activity, and you agree to the guidelines, you can apply to register your system and be known to the public and shareware authors as participating. Contact the SDN Net manager or Regional manager who's area you are in, and request to be registered. If approved, you will need to create a simple, pure ASCII text file of information that will appear in the monthly SDNetList. You will need to set up a monthly event, to take place before the 7th of each month (for end nodes), where this 'registration' file will be file attached to your manger to be included in the listings. You will need to re-send this file each month, renewing your registration. The format for your registration text file is simple. It consist of only four lines. 1. The FIRST line is a flag line and is needed by our software, it consists of the '@' sign and the initials SDN. 2. The SECOND line begins with your full 3D nodenumber, your name, your BBS name, your city/provident, your state and country and your BBS number. 3. The THIRD line may consist of any text you want. Usually it tells in short, of things users might be interested in on your BBS. 4. The FOURTH line is your routing line. It begins with the 3D node address of the registered SDN site from which you get your SDN files and echo. The rest of the fourth line should be any further registered SDN sites that you feed. If you routing information does not fit on this line alone you may use one more routing line for a total of two routing lines. --[Example Registration Text File----------------------------------------- @SDN 1:141/865 Andre Normandin, The Ultimate BBS, Meriden CT 203-345-5666 No subscription. OS/2 utilities. Running Maximus and Binkley OS/2 versions 1:141/840 1:109/119 1:141/820 1:141/375 1:219/22 -------------------------------------------------------------------------- Andre is fidonode 1:141/865 and his BBS name Ultimate BBS, his dataline is 203-345-5666, Andre is into OS/2. He gets SDN areas from a registered direct feed 1:141/840 and gives them directly to 1:109/119 and 1:141/820 etc.. ╒═══════════════════════╕ │ 8. LEGAL AND FRIENDLY └──────────────────────────────────────────────────── We believe shareware and BBS'ing go together. We recognize the contribution that user-supported authors have made to online communications. After all, it is proven that files are the biggest reason for users to start BBS'ing, files are the most popular activity. We recognize shareware and user-supported programs to be outstanding in quality. SDN would like to offer authors the recognition that they deserve by having our sites run their boards in a mature, friendly and legal manner and follow good dictates of conscience on shareware registration policy. What does this mean? well, not much more than the way you should be running your board now anyway. * Commercial Copyright software must not be posted. * Illegal information should not be allowed in the SDN message areas and take care that "spicy" language in the message areas does not turn into objectionable obscenity. * Be 'pro-registration' which consists of a simple positive attitude and occasional gentle encouragement toward shareware user registration. Cooperate with SDN occasional shareware education activities. Register the shareware you yourself continually use. * Respect and compliance with your own network affiliation policy and officials. By complying with these above guidelines, you are complying with existing laws and common sense BBS'ing anyway. BBS'ing and using BBS's is an amateur hobby for most involved. Even professional BBS boards know that the people who log on are doing so as a hobby. We request that you keep a hobby spirit and operate your board in a friendly manner. * SDN activity is not to be used as a reason for means of commercial income or profit. Any specific SDN publication that are copyright by The SDN Project can not be used outside of SDNet without written permission of the SDN Project Manager. ╒══════════════════════╕ ────────────────────────────────────────────────────┘ ADDENDUM INFORMATION │ - 30 DAY RULE EXCEPTION SDN - policy is for all registered sites to hold new distribution files unchanged in the special SDN file area for 30 days. While we will do the best we can to distribute only "G" rated files and filter out objectionable material... if mistakes are made and a file apparently offends morality, sysops should feel free to quarantine that file and contact us over the content. - NOT-FOR-PROFIT - The SDN Project and SDN is an amateur hobby venture and not a commercial enterprise. Registered site sysops should accept no money for SDN services nor charge any fee for SDN service. - NECESSARY ACTIONS TO STOP ABUSE - In the event of a site abusing policy or other actions deemed a nuisance to other members of the network, warning shall be issued. If the abuse continues, files and echoes to the offender shall be requested cut, license as a distribution site shall be void and removed from the SDNetList. - OFFICIAL SDN PUBLIC LIBRARIES - The Head Librarian may appoint Official SDN Libraries. The general guidelines for this are: (A) 9600 baud, (B) reasonable File-Request times, (C) hold all distributed .SDN/SDA files online in original SDN compression for 365 days and (C) non-subscription availability of the SDN library file area. Approved SDN Libraries should fly the banner: ┌───────────────────────────────────────┐ │ SDN International (sm) Library Site │ └───────────────────────────────────────┘ - NETMAIL TO THE SDN PROJECT - As the information and processing center for SDN the SDN Project BBS 1:141/840@fidonet sometimes receives alot of netmail questions and inquiry, I try to answer them all but I simple can not afford to netmail back every answer nor do I have the time.. it's a hobby for me and I have a monthly limit on how large my phone bills can be... it is better to send me echo in the SDN_PUBLIC echo area at any registered SDN system and at some non-SDN systems (this echo is released to the public). If you must send me netmail.. wait one week and then poll for you answer which will be put on hold for your poll. - USDN NODELIST UFLAGS - Continued explosive growth of FidoNet seems to regularly force the limits of the nodelist and compilers, sending FTS programmers back to the drawing Please be reasonable in your nodelist entry. SDN reccommends that the USDN and SDN UFlag NOT be used in the FidoNet Nodelist and that the ReGnode method be used (elsewhere in this document). The SDNetList is the only official listing of participating SDN nodes. * FidoNet (tm) is a trademark of Tom Jennings. * RegNode is Copyright The SDN Project /*End