Editorial Policy

We encourage community members and industry experts to contribute to Linux.com in an effort to share information and help prepare open source professionals who are building the next generation of open technologies.

Linux.com is a publication of The Linux Foundation and helps to promote Linux and open source, collaborative development. We provide educational and useful material that supports the mission of The Linux Foundation, its members, and the open source community at large. We accept and publish guest blogs, community blogs, and freelance articles that meet our editorial guidelines and terms of use, and are original or reproduced with permission.

We follow journalistic standards for fair, accurate and transparent reporting in the articles we commission from freelance writers and unpaid guest contributors. We aim to publish articles that are friendly, helpful, professional, respectful, interesting, informative, and passionate/ enthusiastic.

As a vendor-neutral, third-party nonprofit foundation The Linux Foundation supports Linux and all of its collaborative projects as platforms for collaboration and doesn’t take sides on controversial topics or disputes between companies. We don’t avoid critical commentary on broad issues, but approach them with sensitivity, professionalism and tact in a way that is beneficial and positive for the community.

See our Terms of Use for the do’s and don’ts of publishing on Linux.com. Violation of the terms will result in the removal of the content and a warning from the site's administrators. A second violation will result in the removal of your user account.


  • Please use English.

  • Read our site to get a sense of what we publish and to avoid reproducing a topic that has already been covered. Subscribe to the weekly Briefing Book newsletter for regular updates.

  • Write for developers, system administrators, managers and other open source professionals.

  • Help and inform. Solve a problem for your readers or help them level-up their skills and careers.

  • Avoid self-promotion. (See the previous bullet.)

  • Focus on a single idea. Instead of "how to use containers," perhaps write "how to use open source tool X to manage containers"

  • Use a recipe format in tutorials. After a little preliminary info, use numbered steps. Make the first sentence of the step the action and the second sentence the result.

  • Use graphics. Screenshots are good. Make sure no artwork is more than 500 px wide.

  • If you have an idea, fill out the contributor form first. We'll let you know if anyone else is planning on writing about that topic already, and give you some ideas on what else you could write about.

With Linux.com, The Linux Foundation is providing a framework for discussion and a resource for open source professionals to learn about the latest in Linux and open source technology, careers, best practices, and industry trends. Please note that freelance and contributed articles, as well as any other user-generated content on Linux.com (such as community blogs, Q&A, forums, comments, etc.), do not reflect the views or endorsements of The Linux Foundation, its staff, or its members. We recognize there may be inaccurate information reflected in this site and that users should understand that something that appears on Linux.com does not mean The Linux Foundation has vetted or endorsed that content.

If you spot an error, or a violation of this policy, please contact our editor at lclark (at) linuxfoundation (dot) org so that we may act accordingly

Click Here!