home *** CD-ROM | disk | FTP | other *** search
- I noticed that OCAT was mentioned in one of the Opus 1.70 docs.
- Right now, I only have 4 entries in the data base. If there is
- a software author in your net, please pass this on to them and
- ask them to fill it out and send it to me. I'm going to start
- putting stuff in as best I can. I also plan to compile a list
- of authors and perform a bombing run to solicit a response.
- If you can help, you'll be doing everyone a favor.
-
- Keith Ford, 24-JUL-91
- ===============================================================
-
-
- ══════════════════════════════
- ┌─┐ ┌─┐ ┌─┐ ┌┬┐
- │ │ │ ├─┤ │
- └─┘ └─┘ ┴ ┴ ┴
- ══════════════════════════════
- Opus Catalog of Amazing Things
-
-
- Copyright 1991 by Keith Ford
- in accordance with the Opus philosophy
-
- Dedicated to everyone who has helped someone
-
-
-
- About 15 months ago, I became an Opus CBCS sysop. Along the path from
- then to now I have had help from many people and from many pieces of
- software. Now, as I gaze out over the Meadow, I notice others asking
- the questions I had once asked. So I have decided to do a little
- something to pass on those many favors I have received.
-
- OCAT, the Opus Catalog of Amazing Things, is a listing of available
- utilities and helpful files that an Opus sysop might find useful. The
- only files that would not be useful are those that are "very" specific
- to another bbs package. I quote the word very because some software
- can be used in unique ways. For example Waffle can be run as a door
- for Usenet access.
-
- OCAT will be a living database, much like the software list at the end
- of each FidoNews. The database itself will be available in a number of
- formats. You can file request the magic word OCAT from my board at
- 1:373/12 (HST/V32bis) which will give more information should you be
- interested.
-
- The purpose of this letter is to solicit response from authors that
- have items they wish to include in OCAT. Following is a simple form
- that you can complete and send to me. And remember, send updates as
- you make them available.
-
- Program Name : (1)
- Version : (2)
- Opus Version : (3)
- Release Date : (4)
- Release Filename : (5)
- Software Class : (6)
- Author : (7)
- Fidonet : (8)
- Other : (9)
- Keywords : (10)
- Description : (11)
-
- Description of items listed in the form above.
-
- 1. Name that the program is known as. If your program name is an
- acronym, you should use what is most common. For example, OBUL
- is Opus Bulletin Utilization Language, but it is most commonly
- called OBUL (oh bull :-).
- 2. Version number of program for this description.
- 3. Version of Opus this program supports. (e.g. 1.0x, 1.2x, any)
- 4. Date author released this version.
- 5. Filename, without extension, author used for released program.
- 6. Type of software:
- Commercial
- Public Domain (all rights released)
- Freeware (no fee, some rights reserved)
- Shareware (fee for continued usage)
- Crippleware (fee required to enable all features)
- Nagware (fee required to turn off annoying screens)
- 7. Author's name.
- 8. Author's fidonet address for correspondence.
- 9. Other addresses for author. (Usenet, US Mail, phone, etc.)
- 10. Words that categorize the program, useful for quick searches.
- 11. Paragraph description of programs function, usage, requirements,
- compatibility and such. Might also include where the program is
- available, if it has a freq magic word, if source is included,
- and anything else that might be useful to readers.
-
- Thanks for listening! -kef/MM-
-
- ======================================================================
-
- When the data base is ready for initial release, information will be
- provided here indicating what files should be requested. The notice
- will appear in a number of echoes that are Opus releated.
-
-