Editorial Guidelines

Superuser is an online publication providing the global Open Infrastructure community a place to share open source use cases, tutorials and best practices to help people build and operate open infrastructure. The publication is managed and curated under the direction of the OpenStack Foundation staff.

Audience

Superuser serves the global community building and operating open infrastructure and addresses the community’s interests, which include AI/machine learning, bare metal, container infrastructure, CI/CD, edge computing, telecom + NFV, public cloud, private & hybrid cloud, security and more. Of particular relevance are the interests and activities of members of open source communities like Airship, Ansible, Ceph, Docker, Kata Containers, Kubernetes, ONAP, OpenStack, Open vSwitch, OPNFV, StarlingX, Zuul and more.

Superuser encourages a variety of submissions styles:

  • Tutorials;
  • Case studies;
  • Event recaps;
  • Thought leadership articles;
  • Product updates and announcements; and
  • Project news and release information

If you have ideas that are not covered in the above suggestions, please email [email protected]. Before submitting, please review the Superuser Style Guide to make sure your articles are consistent with other contributed content.

The editorial committee will reject submissions that, in the opinion of its editors, do not meet these standards. Where practical, we’ll offer tips on how to edit the submission to make it acceptable. Examples of unacceptable submissions include, but are not limited to:

  • Advertisements and sales solicitations;
  • Fundraising appeals;
  • Topics of a political, religious or general social nature; and
  • Campaign solicitations for OpenStack Foundation elections

Examples of submissions that fit the editorial mission of Superuser include:

  • The latest Kata Containers release features;
  • A personal take on the latest Open Infrastructure Summit;
  • How Verizon Media is using OpenStack at scale;
  • How to run a packaged function with OpenStack Qinling;
  • Running StarlingX at the edge for telcos
  • How to run project gating with Zuul

Some general things to keep in mind:

  • Take your turn. This is a community publication, and the editorial committee reserves the right to limit postings to two per month for any given project or corporate sponsor. During heavy news periods (such as the Summit months, for example) this might be relaxed a bit.
  • Plan ahead. Editors need 48-72 hours to review submissions for appropriateness and content. The system allows you to schedule for later, so posting in advance of your actual announcement date is fine. You can always contact the editorial committee if you have questions.
  • Share your plans. We publish content under a Creative Commons license. Please let us know if you plan to syndicate the content on another platform.
  • Republish with us. We are happy to publish syndicated content. When submitting articles that are published elsewhere, please share all original links so we can review along with the content.

If you have questions, contact the editorial committee at [email protected].