9 Introduction to the OpenVMS Freeware 9 ------------------------------------ H OpenVMS Engineering is again sponsoring an OpenVMS Freeware CD-ROM. TheI OpenVMS Freeware CD-ROM contains "public domain" and "freeware" software I which runs on OpenVMS VAX and OpenVMS Alpha, and selected tools specific J to the interoperation of other systems with OpenVMS systems. The purpose I of the OpenVMS Freeware CD-ROM is to provide OpenVMS customers with easy H access to public domain software and to "free" internal Compaq software
and tools. H The guidelines for the software to be contained on the OpenVMS Freeware CD-ROM are the following: I o The software must be unencumbered to the public. No license fees shall : be requested of or required by the customer for its use.G o If a product authorization key (PAK) is required, an unrestricted PAK ' must be provided with the submission. F o The software must run on OpenVMS VAX and/or OpenVMS Alpha, or be of H direct relevance ("Affinity") to OpenVMS VAX or OpenVMS Alpha systems.G o Compaq does not warranty this software in any way. It is provided as "as is" software. G o Compaq will not provide service for this software, fix the software, & or warranty that it works correctly.E o Customers are free to adapt and change the sources for their needs. < Acquiring a Copy of the Freeware CD-ROM kit< ------------------------------------------- H The OpenVMS Freeware CD-ROM will be distributed in conjunction with the G standard OpenVMS operating system software distribution kits. It will E also be made available for anonymous access from the OpenVMS Website: http://www.openvms.compaq.com/ C The Freeware CD-ROM kit is not expected to be separately orderable. = Creating a Kit for Inclusion on the Freeware = -------------------------------------------- F Please carefully follow the following simple steps to ease the job of > packaging the wealth of software onto the Freeware CD-ROM kit: I 1: Build the software into a saveset or ZIP kit. Each product must be H in a DIFFERENT directory, or in a separate saveset or ZIP kit. If J the sources are included, place them in a subdirectory called [.SRC]. E You must to supply one file (and optionally two others) in each top-level directory: - FREEWARE_README.TXT E This file must have the following format for the FIRST line: 8 PACKAGE_NAME, CATEGORY, ONE_LINE_DESCRIPTION for example: M INTOUCH 4GL, LANGUAGES, High-performance 4GL for VAX and Alpha... L The one-line descriptions will be truncated to 60 characters. ThisK will allow them to display nicely on the selection menus later on. 3 The list of categories to choose from are: K AFFINITY Interoperation with Microsoft Windows systems ) BUILD TOOLS Build tools 0 WEB TOOLS CGI and HTML tools9 GAMES Games (also see Motif Toys) , GRAPHICS Graphics toolsI LANGUAGES Compilers, assemblers, and language-related 7 MISCELLANEOUS Or ask for a new category < MOTIF TOYS X Windows, CDE, and Motif toysB NETWORKING Networking and network-related toolsN SYSTEM MANAGEMENT Tools related to system managemet, security, etcN UTILITIES Random Utilities not related to other categories H Compaq OpenVMS Engineering may choose to reset the category to E match one of the above categories, or to a more appropriate H category. Petitions for the creation of new categories gladly accepted. K Any additional lines of text in the FREEWARE_README.TXT file will L be displayed to the user from the MENU SYSTEM, if they choose this package from the menu. * - FREEWARE_DEMO.TXT file (optional) L The FREEWARE_DEMO.TXT file is text that can explain how to try thisG software...or explains what the FREEWARE_DEMO.COM file will be showing the user. % - FREEWARE_DEMO.COM (optional) @ If the user selects this package from the menu system, 5 the FREEWARE_DEMO.COM file will be executed. E 2: Each directory should contain the VAX and Alpha executables (if G possible), help text, documentation, sources (in [.SRC]) and then C anything else you want to put there. If the kit contains both H VAX and Alpha objects or executables, consider using subdirectories' [.VAX_IMAGES] and [.ALPHA_IMAGES]. H If the software is already kitted as a VMSINSTAL or PCSI kit, that I is quite acceptable. Just put the kits in the directory along with / the instructions and a basic introduction. H 3: PLEASE make sure that the .txt and .com files are easy to read and J understand. The more friendly your instructions and directions, the 1 more likely that others will want to try it. E 4: In order for the software to be considered for inclusion on the G freeware CD-ROM, the attached release form MUST be submitted with the software. A Electronic copies of the signed release form are acceptable. ? The release form will not be included in the distribution. 0 How to Submit a Kit) ------------------- G Once the software is packaged, you can submit it on a tape (TK50, TK70, or TLZ04 preferred) to: ) OpenVMS Engineering Freeware Submissions Compaq Computer Corporation MS: ZKO3-4/S23 110 Spitbrook Road Nashua, NH 03062 F If you have internet access, you can send a pointer to the location of the kit to: freeware@star.zko.dec.com F and we will copy the kit electronically. Kits can be submitted as zipG kits or as BACKUP savesets, and can be base64 or uuencoded, and can be C downloaded via FTP or via a link at a specified website. Other kit 0 formats may be acceptable by prior arraignement. G The OpenVMS Development group is looking forward to your submissions... - RELEASE FORM - ------------ OpenVMS Freeware CD -------------------- DEVELOPER RELEASE FORM: = As the owner/developer of this software, I release it to be C included on the OpenVMS Freeware CD-ROM. I expect no remuneration B or payments for the use of this software from Compaq or Compaq's customers. _______________________ Developer/Owner Name
