Contributions to these pages will run in the "lead-in" position at the top of the page. They usually cover some topic from recent FOSS news (a release, mailing list discussion, plans made, etc.). Our general guideline is for articles to be around 1500 words in length, though somewhat longer or shorter can work too. The best articles cover a fairly narrow topic completely, without any big omissions or any extra padding. We are generally looking for authors who have their own ideas on topics they want to write about. Looking at past weekly editions in the Archives is a good way to get an idea of the kinds of topics we cover and how we cover them. First drafts of articles are typically due on Monday, with a (hopefully) one-day turnaround for a final draft sometime on Tuesday. Our deadline is early Wednesday morning, US/Mountain time (six or seven hours behind GMT, depending on the season), but it is best to not push up against that if possible. Articles that are less tightly tied to the news of the week can be delivered at most any time, the earlier, the better.
We are also always on the lookout for standalone feature articles. Feature articles can run independently, on the Weekly Edition front page, or both. Articles intended for a specific week's front page are subject to the same deadline constraints as other Weekly Edition material; others can be more flexible in their timing.
Please note that we are, as a general rule, not looking for "how to" articles; there are plenty of other outlets for such content on the net. We're more interested in the current news and in informing our readers of interesting developments in the community that they may not have previously heard of.
We are especially interested in authors who follow an area well enough to propose topics for articles and follow through quickly.
Please read our writing style information (below) so that you understand the kind of content we are looking for.
Before we can publish your work, we'll need full name and contact information from you. If you pay U.S. income taxes, we will need your tax ID number (and a completed withholding form) so that we can send you a 1099 form at the end of the year. If you are not subject to taxation in the U.S., we'll need a declaration from you to that effect.
Payments are sent out by the 15th of the month for all articles published in the previous month. At this time, we are able to make payments via U.S. check or PayPal.
Audience. LWN's readers tend to be highly educated and strongly technical in their outlook. Some of them are likely to be developers for the project you are writing about. Should you feel the urge to "dumb down" material, that urge should be resisted. LWN is not "Linux news for dummies;" our readers are most emphatically not "dummies." If you talk down to them, or tell only part of the story, they will call you on it.
Style. Here is an in-progress list of style guidelines for articles in LWN. They reflect the practice we have lived by since 1998, but never really documented before.
The overall voice of an article should be factual and authoritative. Do your research, and let it show. LWN has a long history of allowing the author's opinion to show through in its writing; in our opinion, it is better to let the audience know where the author is coming from than to try to adopt some pose of "objectivity." Opinions, however, should never get in the way of the facts; your reader should be able to separate the two.
Document your sources. If you are working from a press release, or a message on a mailing list, link to it. Always let your readers know where your information is coming from; many of them will follow the links for articles of interest and come to their own conclusions.
Special care is required when dealing with press releases. Much technical journalism seems to consist of rephrasing press releases and presenting the result as original work. LWN explicitly avoids any such practice. A press release can be a good source of information (once it is translated into English), but it is far from an objective source. If you are passing on information from a press release, make sure the readers know that. (Incidentally, our preferred places to link to press releases are, in order: (1) a local copy sent to us by the company or PR agency, or (2) a copy at the service which distributes the release (usually PRNewsWire or BusinessWire). Press releases on company sites tend to move or, if the company later regrets it, disappear. Services like Yahoo and NewsAlert age off releases quickly, breaking our links).
LWN is produced in the United States, and uses American English. The American variety is not in any way better than any other (though writing in Pidgin would present certain challenges to our readers), but lack of consistency can be distracting.
Be concise. Try to find a way to get your information across with a small number of well-chosen words.
Acronyms should be spelled out on their first use, except for the most common and obvious ones (i.e. GNU, GPL). Excessive use of acronyms can make articles harder to read and understand. Also, please avoid the use of informal terms when real terms can be used; thus, for example, "distribution" is always preferable to "distro".
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds