Promo/Dot/Rules

Content

The Dot Contribute a Story page provides guidance on what we do and do not accept.

This is of course subject ot review, but it seems to be well observed so far. If an article is submitted that does not seem to match the criteria, we discuss it on list and then, if necessary, politely reject it.

Reviewing

Every article is reviewed by two editors prior to publication. Preferably neither of those editors was the original author. Reviews are requested on list with a link to the article and a statement on whether the article can be published straight after review or at some future date.

Reviews for urgent articles are sometimes also requested on IRC (editors may be found in #kde-promo or other kde channels). Also sending a message to the list notifying of iminent publication avoids someone publishing another article at the same time.

Scheduling

We try and avoid publishing multiple articles in one day (until or unless we get to the point of publishing on average more than one article per day). However, we don't hold very time sensitive article just for this reason.

Style

Interviews

Our current convention is to name both the interviewer and interviewee in an introduction at the start of the article, making their names bold with <b>Name</b> (you can also misuse <strong> for this).

The questions and answers are then set out like:

<b>Interviewer's name:</b> Interviewers question

<b>Interviewee's name:</b> Interviewees answer

We obviously try and avoid heavy editing of the interviewees responses - imperfect English is fine, but should be corrected when it becomes hard to understand or ambiguous. We can also make changes to reflect the proper use of KDE brands (i.e. changing "KDE 4" to "KDE Platform 4" or "Plasma Desktop").

Language

We keep it kind of formal - so we tend to avoid using abbreviations: use "do not" rather than "don't" although that does not matter too much.

We can use jokes and a bit of jargon such as "hacker", but not emoticons.

We try and edit in to good quality English as much as possible (but see the notes on interviews, above).

Common English mistakes

These are some things that non-native (and native) English speakers often confuse and that you need to look out for when editing.

It's or Its

"it's" always means "it is". The posessive is "its".

So these are correct:

"KDE software is great, it's getting better all the time" (however, we would probably prefer "it is" here)

"KDE software is great, its biggest strength is consistency"

T or D endings in the past tense

A common error is "build" rather than "built" (and vice versa). The first in present or future: "he will build, I build, they build, he builds" while the latter is the past "he built it, I built it". I think there are some other ones that are similar, but I forget them at present.