The Superuser editorial team wants to encourage contributions from everyone, upholding its goals to serve as a publication for the community, by the community.


Superuser is an online publication for the community, by the community. We’re publishing our editorial process to actively solicit submissions from the open infrastructure community, and we want to hear from you!

When Superuser launched in 2014, the goal was to serve as a conduit for our community of developers and users to share their experiences building and operating open infrastructure around the world. Summits, PTGs, Open Infrastructure Days, and other community gatherings are great ways to connect offline, and Superuser is an online way to keep those connections going. Content has historically been developed by a team of writers working with the foundation, as well as a handful of community members, and we want to invite the entire community to share their lessons learned, use cases, tutorials, and overall open infrastructure thoughts here as well.

We want to hear your ideas for articles you’d like to contribute about open source infrastructure and open source projects. Share your ideas with the Superuser editorial team. You might want to read over the Superuser Editorial Guidelines first, before reaching out.

So, what topics are fair game? Most anything relating to building and operating open infrastructure is a candidate:

  • AI/machine learning
  • Bare metal
  • Container infrastructure
  • CI/CD
  • Edge computing
  • Telecom + NFV
  • Public cloud
  • Private & hybrid cloud
  • Security
  • General open infrastructure thoughts

We’ll be particularly interested in content that’s relevant to projects in the open infrastructure community, like Airship, Ansible, Ceph, Docker, Kata Containers, Kubernetes, ONAP, OpenStack, Open vSwitch, OPNFV, StarlingX, Zuul, and others.

User case studies are always a big hit, but so are how-to tutorials, best practices, lessons learned, event recaps, project roadmap updates, and new release information. We’ll even consider product version updates and thought leadership content, provided it’s vendor neutral and focused on the community rather than competitors. Superuser is not a trade publication: we’re here to amplify the values of openness, collaboration, and solving shared problems.

So, what are some examples of content we’ll decline? Anything that reads like an advertisement or sales solicitation won’t make the cut. Opinion submissions must be supported by verifiable facts and voiced in a collaborative tone that invites community participation in finding solutions everyone can use equally.

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

What ideas do you have? Share them with us using this short form to engage with our editorial team.

Allison Price