![]() |
Sponsored Link •
|
Ruby Code & Style is a peer-reviewed, online journal for the Ruby community. We are looking for authors, and invite you to submit a query or draft.
Timeliness and relevance to the current state of Ruby's evolution is the currency by which we'll measure the value of material submitted for publication in our magazine. We will do our best to keep the articles valuable in terms of this currency by carefully choosing topics which are attracting the attention of the software developers, architects, integrators, managers covering all aspects of Information Technology. Although the zine is slanted towards intermediate to advanced Ruby programmers, we will welcome tutorials which help Rubyists to get started in a specific domain of software development. Our emphasis will be on code supplemented, in-depth articles revealing various facets of Ruby. But we will not be limited by that. We also likely publish interviews, philosophical essays, quizzes, and translations (especially from our Japanese counterparts). We may also publish book-reviews, so long as they are related to Ruby and are relevant to our target audience: the informed Rubyist.
Keep in mind that Ruby Code & Style is peer-reviewed, so you may wish to show your article to a few of your closest Ruby friends before submitting it to our review process. In addition, remember you needn't limit yourself by what is typically presented on the printed page, as these articles will be published online on the World Wide Web.
To propose an article for publication in Ruby Code & Style, please submit a query that includes the information shown below to fsommers AT artima DOT com. Alternatively, you may submit an already completed article. If you submit a completed article, please include, along with your article, the Mission/Scope, Previous Publication, and Biographical Information items from the table below.
Query Information | |
---|---|
Title | A proposed title. |
Word Count | We prefer articles 1500 to 3000 words in length, not counting source code. |
Mission/Scope | Why would Ruby developers care about your article? |
Delivery Date | When could you deliver the finished manuscript to us for editing? |
Supportive Materials | Describe any code samples, scripts, graphics, etc., that you might include with your article. |
Summary | An overview of the article's content. |
Previous Publication | URLs or examples of articles or papers you've published previously, if any. |
Biographical Information | Why are you qualified to write this article? |
Sponsored Links
|