Publish Your Technical Article on OTN

(Click here for Oracle Magazine Submission Guidelines)

Do you have a burning desire to share your insight and technical expertise with other Oracle users? If so, submit your article to OTN or publication. We are looking for DBAs, application developers, architects, and experienced freelance writers to write articles that provide specific and useful information that will help members become more successful in their use of Oracle products (including former BEA products) in conjunction with industry-standard technologies such as Java and Linux.

Before submitting an article, please familiarize yourself with our audience and editorial approach by reviewing previously published technical articles in our tech article archive.

Audience

The typical reader of OTN articles is: already using Oracle products; a power user, or becoming a power user; intelligent, and often largely self-taught in his or her areas of expertise; looking for ways to become even more successful using Oracle products; and looking for straightforward, compelling, step-by-step material relevant to his or her technology needs.

OTN has standing requirements for the following types of articles:

• Case studies that describe fast paths and pitfalls of actual projects and implementations
• Tips, tricks, and techniques for using a particular product, technology, product feature, or process
• Performance planning and tuning strategies
• Articles about applications, servlets, or components that have been built using technologies such as Java, JDBC, SQLJ, JSP, XML, SOAP, UDDI, WSDL, BPEL, and LDAP
• Step-by-step articles about using tools such as Oracle JDeveloper to create applications that run against the Oracle Database
• Articles that explain the use of open-source tools or languages alongside Oracle products (such as Oracle + PHP).

We are particularly interested in the following technology areas:

• Java/JEE
• Web Services/SOA
• Linux
• Open source scripting languages (PHP, Perl, Python)
• Security
• Data Warehousing/Business Intelligence
• SQL and PL/SQL

Ideally, technical articles are between 2,000 and 3,000 words (exclusive of code listings).

When writing a technical article, focus on adding value for the reader. Help readers make their use of Oracle products and technology more successful. Consider the following questions:

• Who is the intended audience for your article?
• How will readers benefit from reading your article?
• Will they learn a new technique?
• Will they work more effectively if they implement the list of tips you provide?
• Will they get started with a new product more successfully based on the implementation plan you describe?

In your article, be specific about the details of your project. For example, rather than say "data migration can take a long time," quantify what you know, even if it's anecdotal: "Data migration can take two to four months, depending on the size of the database."

• Provide rules-of-thumb and guidelines, and including point out obstacles they might encounter and offering workarounds for obstacles.
• If talking about a specific project, what do you know now that you wish you knew before you started?
• Offer sample code and detailed examples wherever possible.

Submission and Editorial Process

Authorization to Publish an Article

When you submit an article, you are stating the following:

• The article was created solely by you,
• The article is an original work and has not been published in any other form,
• You authorize Oracle's use, modification, reproduction, and distribution of the article.

Please do not submit articles that you've also submitted to another publication.

Response to Your Article Submission

If you've submitted a completed technical article to OTN, please note that it can take anywhere from 6 to 12 weeks for us to evaluate your article, and you may not be contacted immediately.

Editorial Process

If we decide to prepare your article for publication, you must be available for and respond to editorial queries on the content of your article. Articles may be edited for length and language, and will be published online only.

By the end of the editorial query process, we will determine when the article is scheduled for publication. (Note that our needs change very quickly so all schedules are subject to change.)

Compensation

We offer an author stipend upon publication. Be prepared to submit extensive documentation to become an Oracle approved vendor.