IBM OS/2 Developer Magazine - Submission Guidelines

 8/92                ____________________________________

IBM OS/2 DEVELOPER MAGAZINE SUBMISSION GUIDELINES ____________________________________

"The Magazine for Advanced Software Development"

The IBM OS/2 Developer magazine is a quarterly publication of IBM's  Developer Assistance Program. It is for programmers developing commercial (for sale) and corporate (in-house) OS/2 applications. Articles about OS/2 features, functions, projects, tools, tips and techniques are solicited from OS/2 experts, software vendors and customers. This document summarizes the requirements for submitting articles for the OS/2 Developer.

Who Are Our Readers?

- OS/2 Application Developers * Independent Software Vendors (10,000+) * IBM Corporate Customers (10,000+)

- IBM Internal Distribution (5,000+) * Field Marketing & System Engineering * OS/2 Classes, Seminars, Forums & Trade Shows * OS/2 Development Lab

We're Looking for a Few Good Articles that...

- Simplify the OS/2 application development process - Publicize OS/2 2.0 features and functions that promote usability and improve performance - Provide how-to advice on Graphical User Interface, Object Oriented, Client-Server, and other advanced programming techniques - Expedite conversion of DOS and Windows applications to OS/2 32-Bit Platform - Publicize useful OS/2 development tools - Share useful tips & techniques, questions & answers, programming examples, case studies

The OS/2 Developer Has Several Departments...

- OS/2 Presentation Manager         - Resources (seminars, books) - OS/2 2.0 (32-Bit)                 - Micro Channel Hardware - OS/2 Database Applications        - Graphics & Multimedia - OS/2 Communication Applications   - Multi-User Systems - OS/2 Local Area Networks          - International - Software Tools                    - Spotlight Feature - Application Enablers              - Performance - Systems Application Architecture  - Manufacturing - Client-Server Programming

Want to Write an Article? Drop Us a Note!

- Articles are first proposed to the editor in a one page outline, which is a prerequisite to assigning the article to a future issue. Estimate the length (in single-spaced pages) of the final article, including the number of drawings, screen shots, and lines of source code. What department (see below) does the article belong in?

- We will give you a tentative yes or no for inclusion in an upcoming issue. Upon receipt of final copy, we will confirm our intent to use your material. We reserve the right to make a final decision about inclusion at any time.

The Next Step...

- Submit your article on or before the deadline. Use a magazine format: text, charts, code listings, and screen shots.

- Content: 5 - 10 pages, single-spaced. Keep the article brief by  summarizing the main points, using illustrations and short examples, and by referencing other sources. Remember: you may not be able to tell your readers everything they'll need to know about a programming technique or software tool in one article. Cover the highlights and refer them to reference publications for more detail. Excessively long articles will be returned for rewriting. Priority should be given to OS/2 2.0 32-bit functions, examples, tools and applications. Make sure your article reflects the latest release of OS/2. And remember -- you are writing for developers, not end users.

- Security: unclassified at time of publication. If product hasn't  shipped, include a disclaimer saying that function may be added, deleted, or changed in the final product.

- Title: Keep title short and simple, e.g., "Using 32-Bit APIs to   Improve Performance". Vendors: include your product's name in the title, e.g., "QuickTool: Generating More Efficient Applications".

- File format: Article text is stored in a file by itself, separate from artwork. Use the DOS ASCII format, free of any special characters. Format: flush left, no hyphenation, width 70. Include references and captions for all artwork, e.g., . Show level of each heading; example: How We Improved Performance , Final Fine-Tuning . IBM authors -- send your file over VM. Other authors: send us your article on a 3.5-inch diskette.

- Artwork: Keep diagrams, tables, etc.  separate from the text file; fax or mail your sketches to us (we redraw most illustrations). Vendors: include your company logo if possible.

- Code listings: ASCII file format:  well-commented, width 70 (placed at the end of article text). Limit your code examples to  the minimum number of instructions needed to make a point (maximum   100 lines). Include captions in your text. Make sure you test your code!

- Screen shots: We have a screen capture program which creates .PCX format files. Please request a copy from the publisher. No screen photos. Limit to three or four screens per article. Include captions in your article text.

- Authors: An article should credit one or more authors. A short, one-paragraph biography (see previous issues for examples) with a  black and white mug shot must be provided of each author. IBM authors: your site communications department may have a local photograper for this purpose. Include your current job title, responsibilities, career milestones, college and degrees, company address and phone number.

- Trademarks: Include a list of trademarked product names (indicate   registered trademarks where appropriate) and company names. The first occurrence of a name (such as OS/2 or Windows) must be marked with  or .

- References: List all appropriate references at the end of each article. If an IBM publication, include its Mechanicsburg order number. If you reference a publication in the text, indicate the use of italics, like this: See the IBM OS/2 Programming Reference Manual, G123-4567. Also reference any online information shipped with OS/2 or your product.

- Miscellaneous: We like to include pull-quotes (selected quotes   from the article) and cartoon illustrations in the margins. Your suggestions are appreciated.

Reviews and Approvals

- IBM authors: Site review (Communications, Legal, Intellectual   Property Law) required; check to see if your site has an Author Recognition Program (ask your manager or site communications  department). Make all revier changes during the editing cycle. Include a copy of your approval form.

- Multiple authors: Designate one author as our prime contact.

- Articles should be submitted by the deadline. Late submissions are accepted on a first-come basis. We do overbook, so if your article is bumped from an issue, it will be a prime candidate for the next one.

- All authors: Please sign the following release and fax to us:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

COPYRIGHT LICENSE AGREEMENT

Author(s) warrant that they are the exclusive owners of the copyright in an article titled:

_____________________________________________________________________

submitted herewith to International Business Machines Corporation (IBM) for publication in "IBM OS/2 Developer" and that they have full power and authority to enter into this agreement.

Author(s) warrant that the article is completely their original work and is not based upon pre-existing materials of a third party.

Author(s) hereby grant IBM a non-exclusive, worldwide, fully paid-up license to reproduce, adapt, distribute, and display the article and adaptations thereof, and to authorize others to do any or all of the above.

____________________________________________________________________ Author signature(s)

____________________________________________________________________ Author name(s) -- printed                              Company Name

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Pre-Production Cycle

- The editor will review and edit your submission and forward it to  the publisher. The publisher will assign a copy editor to your article and it will be faxed to you with recommended changes. You will see the article once again in page-layout (camera ready) format for final approval. Only typo corrections and emergency changes should be made to this version. IMPORTANT: once you send us a softcopy of your article, don't continue to make changes to  your file or you'll get out of sync with the in-edit version. Instead, communicate your changes to the copy editor by fax or  telephone.

- Authors work directly with the publisher (Miller Freeman  Publications) while articles are copy edited, artwork is completed, and pages are laid out. Deadlines are critical to staying on  schedule and must be observed. Either the author or a  knowledgeable representative must be available during this period to ensure quick turnaround.

Reprints

- Article reprints must give credit to the IBM OS/2 Developer. The publisher will furnish quantity prices upon request.

Publishing Calendar

Issue         Outline         Final Text       Print

- Winter        July 15         September 1      December 1 - Spring        October 15      December 1       March 1 - Summer        January 15      March 1          June 1 - Fall          April 15        June 1           September 1

Advertising

- The OS/2 Developer is the best way to reach the OS/2 community with news of software tools, publications, products and services. Ad  rates and schedules can be obtained from the publisher (see below).

How to Subscribe to the OS/2 Developer...

- Through the Publisher: Miller Freeman Inc., (800) WANT-OS2 ($39.95 yearly for four issues)

- Through IBM: Systems Library Subscription Service (SLSS) order number G362-0001. Copies of current issue can be ordered through PUBORDER. (Note: SLSS is accessed on the HONE system; PUBORDER on   VM).

- Members of IBM's Developer Assistance Program receive free copies

Book Compilations

A 780-page book, "OS/2 Notebook: The Best of the IBM Personal   Systems Developer", contains articles from Developer issues between November '88 and Fall '90. This book is sold by Microsoft Press through bookstores, by calling them direct at (800) MS-PRESS, and through IBM Mechanicsburg (G362-0003). New articles submitted to  the Developer may appear in a future book compilation, named "OS/2   Update".

Editor

- Dick Conklin           Voice: (407) 982-1105  Tie-line: 982-1105 IBM - Zip 2230         Fax:   (407) 443-4233  Tie-line: 443-4233 1000 N.W. 51 Street    IBM VM: BCRVM1(CONKLIND)  IBMMAIL(USIB12H2) Boca Raton, FL 33429   MCI Mail: 274-8797  Prodigy: CGVD41A

Publisher

- Miller Freeman Publications, Inc. 600 Harrison St.  San Francisco CA 94107 Executive Editor: Nicole Freeman (415) 905-2387, Fax 905-2234 Copy Editor:      Lisa Gluskin,  (415) 905-2777, Fax 905-2234 Advertising:      Cathy Passage, (415) 905-2392, Fax 905-2234

New York office: (212) 683-9294, Fax 725-0915 370 Lexington Avenue, New York, NY 10017

