? Introduction to the OpenVMS Freeware Submissions? ------------------------------------------------BOpenVMS Engineering is again sponsoring an OpenVMS Freeware CD-ROMCcollection. The specific schedule for release is to be determined.CThe OpenVMS Freeware CD-ROM contains "public domain" and "freeware"Csoftware which runs on OpenVMS VAX, OpenVMS Alpha, OpenVMS I64, andCselected tools specific to the interoperation of other systems withOpenVMS systems. AThe purpose of the OpenVMS Freeware CD-ROM is to provide OpenVMS @customers with easy access to public domain software, to various@otherwise unreleased tools and software developed within HP, and8to provide a channel for HP to release retired products.HThe guidelines for the software to be contained on the OpenVMS Freeware CD-ROM are the following:Eo The software must be free and access unencumbered. No license feesF shall be requested of or required by the customer for its use. GNU,D OpenBSD or or similar open-source licenses may (or may not) apply.E If specific licenses apply and are not already widely available and= widely known, please include the license(s) within the kit.Co If a product authorization key (PAK) or similar key mechanism is D required, an unrestricted PAK or other key (with no termination!) F must be provided with the submission. If a PAK is not provided, HP F may (at its sole discretion) elect to provide a PAK or other similar. key to fully enable the Freeware submission.Jo The software must run on OpenVMS VAX and/or OpenVMS Alpha and/or OpenVMSF I64, or for other platforms with direct relevance (or "Affinity") to" operations with OpenVMS systems.Eo Neither HP nor the submittor(s) warranty this software in any way. < It is provided as "as is" software. Use At Your Own Risk.Co HP will not provide service for this software, test the software,G review the software or the source code, fix the software, or warrantyG that it works correctly or at all. Individuals and vendors that haveE submitted packages to the Freeware may explicitly elect to provide E additional services, testing, enhancements, updates and/or specificG warrantees for submissions -- beyond "none" -- but no such statements! should be expected nor assumed.Eo Customers are free to adapt and change the sources for their needs.Eo HP products on the Freeware may or may not provide source code, butF -- and at the discretion of HP -- all other submissions are expected to provide full source code.Go The OpenVMS Freeware is not intended for use as a commercial softwareB distribution channel, though its use for the release of retired % commercial products is appropriate.Co Submissions that are regulated under US export controls will not C be accepted. As binary submissions cannot be verified for exportE compliance, the submission of binary kits is generally discouraged.< Acquiring a Copy of the Freeware CD-ROM kit< -------------------------------------------HThe OpenVMS Freeware CD-ROM will be distributed in conjunction with the Gstandard OpenVMS operating system software distribution kits. It will Ealso be made available for anonymous access from the OpenVMS Website:( http://www.hp.com/go/openvms/freeware/?The Freeware CD-ROM kit may or may not be separately orderable.= Creating a Kit for Inclusion on the Freeware= --------------------------------------------FPlease carefully follow the following simple steps to ease the job of Jpackaging the wealth of software submissions 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].L If executable or shareable images are included, place them one or more N architecture-specific subdirectories, and preferably named [.VAX_IMAGES],+ [.ALPHA_IMAGES], and/or [IA64_IMAGES].F You must to supply two files (and optionally two others) in each top-level directory: - FREEWARE_RELEASE.TXT A This is a software distibution release. See below for details. - FREEWARE_README.TXT E This file must have the following format for the FIRST line:8 PACKAGE_NAME, CATEGORY, ONE_LINE_DESCRIPTION for example:I INTOUCH, 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.I Spaces are not allowed in the kit name or the category name, andE exactly two commas (delimiters) can exist within the entire string.I (If you have questions on the format, the current processing for@ this is listed over in [FREEWARE]CREATE_FREEWARE_PACKAGE.COM.)3 The list of categories to choose from are:= BUILD_TOOLS Source code build-related toolsH DECWINDOWS X Windows, CDE, and Motif tools (and toys)B FREEWARE Reserved for Freeware-specific files# GAMES Games: GRAPHICS Graphics tools and utilitiesI LANGUAGES Compilers, assemblers, and language-related7 MISCELLANEOUS Or ask for a new category< MULTIMEDIA Multimedia Tools and UtilitiesB NETWORKING Networking and network-related toolsF PROGRAMMING Tools of interest to OpenVMS ProgrammersH SOFTWARE Random Software Packages, Retired ProductsN SYSTEM_MGMT Tools related to system managment, security, etcM STORAGE_MGMT Tools related to Storage and Storage ManagementT UNKNOWN Reserved; assigned to submissions lacking ReadMe filesN UTILITIES Random Utilities not related to other categoriesK MS_TOOLS Interoperation with Microsoft Windows systemsB WEB_TOOLS CGI and HTML tools, web servers, etcI HP OpenVMS Engineering may choose to reset the category to matchI one of the above categories, or to modify the requested categoryK to a more appropriate category. Petitions for the creation of newG categories or for the retirements of old ones 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 file) 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.L Depending on the volume of software submitted, these demonstrations9 may require the end-user unzip the distribution.* - FREEWARE_DEMO.COM (optional file) @ If the user selects this package from the menu system, 5 the FREEWARE_DEMO.COM file will be executed.L Depending on the volume of software submitted, these demonstrations9 may require the end-user unzip the distribution.J 2: Each directory should contain VAX, Alpha and/or IA64 executables (if J possible), help text or help libraries, documentation, source file(s)K (preferably in a [.SRC] subdirectory) and then anything else you wishH to include. If the kit contains objects or executables or multipleL platforms, consider using subdirectories [.VAX_IMAGES], [.ALPHA_IMAGES]L and/or [.IA64_IMAGES]. Also consider providing object files, for thoseK potential users that might lack particular tools, compilers or certain OpenVMS versions.H If the software is already kitted as a VMSINSTAL or PCSI kit, that G is quite acceptable. Just put the kit(s) in the directory, along C with the installation instructions and a basic introduction. I Depending on the volume of software submitted to the Freeware, theseJ installation kits may be left available directly, as well as residingG within the zip archive. (Source code may or may not be compressedE into zip archives, as well, depending on the submission volume.)H 3: PLEASE make sure that the .txt and .com files are easy to read and G to understand -- introduce the tool to those that are not familiarG with it. The more friendly your instructions and directions, the > more likely that others will want to try to use the tool.E 4: In order for the software to be considered for inclusion on the D freeware CD-ROM, the attached FREEWARE_RELEASE.TXT release form) MUST be submitted with the software.A Electronic copies of the signed release form are acceptable.F The release form itself will not be included in the distribution.0 How to Submit a Kit) -------------------GOnce the software is packaged, you can submit it on a tape, floppy diskor other common media to:, HP OpenVMS Engineering Freeware Submissions Mailstop: ZKO3-4/S23 HP 110 Spitbrook Road Nashua, NH 03062, USAIIf you have Internet access, you can attach and mail the kit or can send Ea pointer to the location of the kit or can otherwise request an FTP transfer by sending mail to: openvms.freeware<--at-->hp.comGand HP will transfer the kit electronically. Kits can be submitted as Gzip kits or as BACKUP savesets, as mail attachments, and can be base64 Ior uuencoded, and can be downloaded via FTP or via a link at a specified Dwebsite. Other kit formats may be acceptable by prior arraignement.JThe HP OpenVMS Development group is looking forward to your submissions...5 - FREEWARE_RELEASE.TXT (required; not shipped)- RELEASE FORM- ------------OpenVMS Freeware CD--------------------DEVELOPER RELEASE FORM:E As the owner/developer of this software, I have read and understand N the submission documentation, and I release the package to be includedM on the next OpenVMS Freeware CD-ROM. I expect no remuneration and noN payments for the use of this software from HP nor from HP's customers. _______________________ Developer/Owner Name