Wildcat! File Network Policy Revision 1.02 - June 8, 1998 Gary Petersen Coordinator, Wildcat! File Network FidoNet 1:290/111 XpressNet 99:1/3 BBS 515-792-3702 E-mail garyp@pcpartner.net The Wildcat! File Network (WCF) includes the following file echo conferences: Conference Tag Conference Description ============== ====================== WCF_ADMN WDNet administration files WCF_4UTL Wildcat! v4.x utilities and files WCF_4DGM Wildcat! v4.x door games WCF_5UTL WIN Server utilities and files WCF_5DGM WIN Server 32-bit door games WCF_5RLS WCF: Santronics WIN Server public release files WCF_NAV WCF: Wildcat! Navigator utilities and files WCF_UPST File submissions to WCF Headquarters WCF Policy Statements 1. Any node will be able to directly hatch files into the Wildcat! File Network in the WCF_UPST file conference. Files will be received at 1:290/111 in this area and will be reviewed for distribution by the WCF Coordinator. In releasing files in this area, the author or agent understands the file may be released in any manner the WCF Coordinator sees fit. Under no circumstances may any node release a file in any other WCF file echo other than WCF_UPST. Authors or agents may file attach files for review to FidoNet node 1:290/111 or XpressNet node 99:1/3 at any time. Please note that any files submitted in this manner must be sent directly (NOT routed) and should include a netmail message with information about the file. Authors or agents may logon to Midwest Xpress BBS (515-792-3702) and upload files for review at any time. Use the following login information, or create your own user account. First Name: WCF Last Name: Upload Password: wcf 2. Only public domain, freeware, shareware, and authorized demonstration files may be submitted for distribution through the WCF. 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". 3. The WILDCAT!_SUPPORT echomail conference on the FidoNet North American and Zone 1 Backbones is available for Wildcat! and WIN Server support. That echo may be used to discuss files that have been distributed through the WCF. 4. All WCF nodes must have session-level passwords with their uplink and downlink systems. This is simply to ensure the integrity of the WCF. 5. Any file that comes to your system via the WCF should have the CRC checked by your TIC file processing software as it is processed. No archive advertisments may be placed into the archive while the file is still being sent to another node. The WCF is not meant to advertise any product, service, or BBS, but to move files. This also corrupts the CRC info, which can caus TIC processing software to reject the file. 6. The WCF is not an official distribution means for Santronics Software, Inc. and is not directly affiliated with Santronics in any way. 7. All files will be scanned for viruses before being hatched. If a file is archived with authenticity verification from the author, the archive will be modified only to add the IFDC standard archive comment. If a file is not archived with authenticity verification from the author, it will generally be rearchived using the WinZIP archiver. 8. All files must include a properly formatted FILE_ID.DIZ description file. The proper format is for no more than 10 lines of flat ASCII text characters no more than 45 characters per line. The FILE_ID.DIZ file cannot contain high-ASCII characters, special formatting with non-text characters made to look like borders, or spaces to position text side to side across a line. Many TIC file processors will improperly handle FILE_ID.DIZ files that contain such information or are too long. When an improperly formatted FILE_ID.DIZ file is provide by the author, it will be left in the archive, but renamed to FILE_ID.ORG and replaced with a properly formatted FILE_ID.DIZ file. A text file named README.WCF will also be added explaining that these changes were made by the Wildcat! File Network Coordinator when the file was hatched. Revision History ================ Rev Date Description ======================================================================= 1.00 12-04-1997 Initial Release. 1.01 07-01-1998 Added WCF_5MSI, WCF_NAV, and WCF_WEB file areas. Added Policy Statements 7 and 8. Added Revision History. 1.02 06-08-1999 Deleted the WCF_QMOD, WCF_5MSI, and WCF_WEB file areas. Changed email address from gary@mwx.paonline.com to garyp@pcpartner.net. Updated Policy Statements 3 (support echo and backbone listings), 6 (Mustang to Santronics), and 7 (RAR to WinZIP).