GNOME Journal

• http://gnomejournal.org/

GNOME Journal is currently on an unscheduled hiatus as its editors and the marketing team decide how to integrate it into the GnomeMarketing communications strategy.

Gnome Journal plans to be a central hub for GNOME focusing on creating new longform content to highlight various parts of the GNOME Desktop. GNOME Journal aims to give balanced coverage of both the best and the worst parts of GNOME.

Meeting: We have no current meetings scheduled. Meetings discuss the next edition of GNOME Journal including available content and infrastructure needs. Sign up and agenda here. Meetings are often at at 22:00 EDT / 2:00 a.m. GMT in the IRC chat room on irc.gimp.net #gnome-journal.

Contact: Please join our mailing list (Archive).

• Article wishlist

• Article submission queue

• Announcement guide - (Describes how to promote a new edition)

• Place for new ideas - (Place your new article ideas here whether you intend to write about your idea or not. Also articles about GJ itself)

• Behind the scenes

Release Schedule

2011

Become a Writer

• You'd like to get a job in the IT publishing industry after college?
• You'd like to present new GNOME technology to other developers?
• You'd like teach others about GNOME's cool new ways to solve common IT problems?

The GNOME Journal is a great way to write about your beloved desktop, start your portfolio, present your software, teach about new IT solutions, and help others having a good time. What are you waiting for?

We're looking for articles about:

Functionality

Review new ways of dealing with information. What are the great new GNOME or GTK+ applications? Which software is superior to others, and why? Which functionality is missing to make a certain application a great one? Can you showcase a complete workflow using only GNOME technology?

Persons

Write history, or at least a note about it. Who contributed to the advancement of GNOME? What motivated them? What do they think? How do they live? What can be learnt by their example?

Trends

Analyse what will be cool tomorrow. Which GNOME technology finds adoption in the FLOSS community, or in the IT industry? Any new trends in interface design, usability, IT standards, or GNOME technology everybody should know? How does history affect present and future GNOME development?

Events

Enable the worldwide GNOME audience to keep in touch with each other. What's happening all around the world about GNOME? Who decided to use or deploy GNOME, and why? Where do GNOME developers, contributors, and users meet?

Discussions

Present different views on problems the GNOME community faces. What arguments support a new idea, a decision, a given trend? What's the opposite view? Is there a potential compromise, and if so, which one?

Join the GNOME journal mailing list today, and say 'Hello' . If you already have an idea on what you'd like to write about, it would be cool if you can present a draft on the article. If you just like to write, let us know.

Writing guidelines

Length

Write more than 750 words (which is a little bit too short) and less than 2000 (a little bit too long). In between 1000 to 1750 words is fine.

Style

The usual rules apply. For a good overview, see The Elements of Style. In particular, don't use 'is' if you can replace it by 'does' ('acts', 'uses', 'handles' etc.).

Format

Submit simple ASCII texts; no OpenOffice.org documents, and no Word documents ('shudder'). Use 'Textile' as a mark-up language if possible. You can learn it by using Textism. Please DO NOT include line breaks in your documents except at paragraph breaks. The text needs to be able to wrap naturally in HTML.

Images

Don't embed images into the text. Sent them separately with a link in the text. Use PNG as a format. For images larger than 400x120, make a thumbnail - not a resized/resampled version but a cropped one of the most important details.

Submission

1. If you're unsure if your article idea will fit into the GNOME Journal, ask on our mailing list. You can sent messages to the list, even if you're not a member, but it may take a day until it appears in the archives. You can also email to the release coordinator or the editor-in-chief.

2. If your idea fits into the GNOME Journal, start writing! Please add an entry in the /ArticleSubmissionQueue .

3. After you've finished your article, check the spelling with gEdit (American English). Additionally, have it proof-read by somebody else if possible. Don't worry if English is not your primary language! Ask on the mailing list for a native speaker. If this fails, our editor will proof-read the article.

4. Submit your article to the release coordinator (currently SumanaHarihareswara) or the editor-in-chief (currently PaulCutler).

5. The release coordinator uploads the article to the CMS, and updates your article's status.
6. Editors check for correct spelling, grammar, and possible errors. If extended changes are necessary because content is difficult to understand, a corrected version of the article will be sent back to the author for approval.
7. When the release date is due, the edition/issue will be published.

Deprecated

/CurrentIssueArticles

/ArticlesBeingWritten