Jonqui Stack
📖 Tutorial

How to Secure Paid Standards Development Work as an Open Source Maintainer

Last updated: 2026-05-01 11:27:51 Intermediate
Complete guide
Follow along with this comprehensive guide

Introduction

If you're an open source maintainer who has ever wished you could help shape the technical standards your projects depend on, there's good news. The Sovereign Tech Agency has launched a pilot program called Sovereign Tech Standards that pays maintainers to participate in the standard-setting bodies of the internet. For a full year, selected participants receive a monthly stipend between €4,800 and €5,200, plus coverage for participation fees and travel, to contribute roughly ten hours per week to working groups at the Internet Engineering Task Force (IETF), the World Wide Web Consortium (W3C), or the International Organization for Standardization (ISO).

How to Secure Paid Standards Development Work as an Open Source Maintainer
Source: itsfoss.com

This guide walks you through everything you need to know to apply—from checking your eligibility to submitting a compelling application. The program is currently running a pilot in 2026, with applications due by May 19, 2026, at 11:59 PM CEST.

What You Need

  • Active maintainer role in an open source project that relates to standards at IETF, W3C, or ISO.
  • Project relevance – your work must touch upon specifications developed by one or more of these bodies.
  • Time availability – you must be able to commit approximately 10 hours per week to standards work from mid-June 2026 through June 2027.
  • No prior standards experience needed – the program is open to newcomers.
  • No geographic restrictions – applicants from anywhere in the world are welcome.
  • Internet access for remote meetings and document review (though in-person travel is also part of the support).
  • A clear idea of which working group you want to join and what specific contribution you plan to make.

Step-by-Step Guide to Applying

Step 1: Confirm Your Eligibility

Before you invest time in an application, make sure you meet the core requirement: you must be an active maintainer of an open source project. The project should have a clear connection to the work of IETF, W3C, or ISO. For example, if you maintain a library that implements a W3C web standard or a protocol that relies on an IETF RFC, you qualify. The program is specifically aimed at maintainers who currently lack the resources to participate in standards development—so if you already work for an organization that sends you to these meetings, you're probably not the target audience.

Step 2: Understand the Commitment

The pilot cohort will run from mid-June 2026 to June 2027. Participants are expected to dedicate roughly 10 hours per week to standards-related activities: attending working group meetings, reviewing drafts, contributing to discussions, and possibly authoring or editing specifications. The program covers participation fees for the standards development organizations (SDOs) and reimburses travel to in-person meetings. You must be comfortable with this time investment and be able to balance it with your maintainer duties.

Step 3: Choose Your Standards Body and Working Group

Identify which of the three organizations—IETF, W3C, or ISO—is most relevant to your open source project. Then explore their working groups to find a team whose focus aligns with your expertise. The selection committee will look for applicants who can fill missing perspectives in a group, so consider where your background as a maintainer brings unique insight. For example, if you maintain a widely used DNS tool, participating in the IETF's DNS operations working group could be valuable. If your project is a web browser engine, W3C groups on performance or accessibility might be a natural fit.

Step 4: Prepare Your Application Materials

The application process is competitive (only up to 10 maintainers will be selected), so prepare thoughtfully. The selection panel scores applications based on:

  • How foundational the relevant standard is – does it underpin a critical piece of internet infrastructure?
  • Your planned work – what exactly do you intend to contribute? Be specific about goals (e.g., "propose an extension to the SVG spec for better accessibility").
  • Your perspective's uniqueness – is your viewpoint currently missing from the working group? Highlight your independent maintainer angle.
  • Your background as a maintainer – show your track record of building and maintaining software used by others.

Write a concise statement addressing these points. No prior standards body experience is required, so don't worry if you've never attended an IETF meeting before. Emphasize your hands-on knowledge of where the specs break down in practice.

How to Secure Paid Standards Development Work as an Open Source Maintainer
Source: itsfoss.com

Step 5: Submit Your Application

Applications are open now and close on May 19, 2026, at 11:59 PM CEST. Submit through the Sovereign Tech Agency's official portal (available on the program's page). Double-check that you've included all required information and that your contact details are correct. After submission, review and selection will occur during May 2026, with notifications sent out in June 2026. The cohort starts at the end of June 2026.

Tips for a Strong Application

  • Be specific about your goals. Vague plans like "help improve web standards" are less compelling than concrete proposals (e.g., "contribute to the WebTransport specification to address latency issues experienced by real-time applications built with my library").
  • Show how your project depends on the standard. Explain the real-world impact—if the standard isn't maintained well, your users suffer. That urgency matters to the selection panel.
  • Don't underestimate the value of your practical experience. Maintainers often catch edge cases and implementation bugs that spec authors miss. Frame your application around this unique insight.
  • Start early. Standards working groups have their own jargon and rhythms. Even though prior experience isn't required, reading recent drafts and attending a few virtual meetings before applying can strengthen your proposal.
  • Consider the time commitment realistically. 10 hours per week sounds manageable, but when combined with your maintainer duties, it can be intense. Plan your schedule accordingly.
  • Reach out to the program coordinators if you have questions. The Sovereign Tech Agency has a support contact listed on the official page—use it to clarify any uncertainties.

This pilot is a rare opportunity for independent open source maintainers to shape the infrastructure that powers the internet—and get paid for it. If you meet the eligibility criteria, don't hesitate to apply. Your perspective matters, and this program wants to hear it.