---
tags: OpenJS, blog-post
---

# Introducing the Standards Working Group

The OpenJS Foundation helps critical open source projects succeed by leveraging skills from lots of people. In addition to code contributions, projects need to issue reports, provide quality assurance, write documentation, do developer outreach, project management, and planning.

To provide projects with even more support and resources, the OpenJS Foundation's Cross Project Council has chartered a new working group. The Standards Working Group will actively monitor evolving standards to support and educate OpenJS Foundation projects about developments that might affect them. The group will also help projects formulate standards strategies and advance them with the appropriate standards development organization.

## Standards are important to OpenJS Foundation Projects

Many OpenJS projects, like jQuery and Node.js, have a long history of participating in and influencing standards. But what are "standards" and why do they matter to projects?

Standards are agreements between multiple parties about how a specific technical implementation will work. For example, JavaScript API standards help browsers agree on how a web page should appear to the person sitting in front of the screen. Standards also balance interests. You, viewing this document in your browser, have an interest in being able to pick a browser that you like and having it work with many web pages. We, the authors, have an interest in being able to produce one document that works in many browsers. Users who need assistive technologies like screen readers have an interest in those being able to integrate with browsers. Researchers have an interest in being able to understand technical corner cases that might affect privacy and security.

Standards development organizations, or "standards bodies," are neutral forums for people to create and maintain these agreements. Done right, a standards body brings people with diverse interests together in a way that helps the group be better stewards of end users' interests.

### Standards processes are challenging

In some cases, a standards-making group is not able to come to an agreement and the process fails. Or worse, a group of stakeholders isn't a truly diverse and representive population of stakeholders.

<small>courtesy xkcd.com</small>

As a result, the produced standard isn't a true agreement. *"If only we'd been included in this work 5 years ago!"* and *"If only we'd known earlier - we wouldn't have spent so much time building our thing in a way that wasn't interoperable with your thing!"* are the unfortunate refrains of a standards making effort that may well fail - wasting a lot of time (and effort) because all the stakeholders weren't at the table.

For example, an earlier lack of consensus and adoption of health IT standards created a barrier to healthcare data interoperability. This made it very difficult for health care providers and researchers to share data, and locked research institutions and hospital systems into a specific vendor's solutions. Global stakeholders have now converged around the HL7 FHIR standard that promises to deliver better outcomes at lower costs, but it has taken years to start to see this progress.

## The Standards Working Group can help

Collectively, the OpenJS Foundation Standards Working Group [members](https://github.com/openjs-foundation/standards#working-group-members) have 50+ years of experience with technology standards, with an emphasis on web standards including those that define the languages and networking protocols that make up the web (CSS, HTML, JavaScript, DNS). We also have members with expertise on topics that come up often in application development, including security, privacy, internationalization, localization, accessibility, user experience, and API (Application Programming Interface) design.

Project maintainers and contributors are experts in their projects' needs and goals (among many other things). The Standards Working Group actively monitors standards work items to help projects stay informed about issues or decisions that may affect them. The group also helps demystify the process. Standards organizations can be confusing and intimidating, but the Standards Working Group can answer questions, connect people, and help projects figure out how to get its needs considered.

If you're concerned that standards making is intimidating, you're not alone. Most of our members had the same impressions at first:

> *"I had imposter syndrome. It seems overwhelming at first, but the best way to learn and get comfortable is to get involved."*
>

But over time and with mentorship, they gained the confidence they needed to be successful in the standards arena:

> *"I thought, going in, that I'd have to present to people who all knew more than me. But most of them remember being in the same boat, so you can go, listen, and talk about what you know to whom you choose until you're comfortable doing more."*
>

The Standards Working Group can advise projects to help set them up for success. For example, sometimes rephrasing a proposal so that its non-essential features look more like previously accepted proposals makes it easier to digest. The group can also help projects set expectations correctly - getting a diverse group to agree can take time. Knowing how long a similar kind of proposal has taken in the past may help planning. For individuals who want to learn how to best participate in standards activities, the Working Group provides [time-tested guideance](https://medium.com/@jorydotcom/revised-patterns-for-participation-in-standards-committees-dae82d93954e).

## Get support or get involved

If you're interested in joining the Standards Working Group, or would like some assistance or mentorship for your project, say hello in the OpenJS Foundation's [#standards Slack channel](https://slack-invite.openjsf.org).

The group also holds bi-weekly meetings that are livestreamed on YouTube, or you can join the meetings yourself by following the [/standards repository](https://github.com/openjs-foundation/standards). OpenJS Foundation's [bi-weekly Office Hours](https://github.com/openjs-foundation/open-office-hours) are another way to connect with us start onboarding.

You are also welcome to reach out to any working group member for more insight or support - we hope you'll connect with us and let us know how we can support you or your open source project participate in the standards arena!

draft ends
---

#GRAVEYARD content: standards done wrong. Example of a project that suffered because it wasn't involved in a standards process. Example of a win.

OpenJS Foundation's Standards WG aims to help projects avoid those kinds of problems; to avoid regrets like

> If only we'd been at this table five years ago

or

> Why did we spend so much time building this and they building that; it'll be really hard to get these working together. If only we'd known earlier.

or as xkcd.com explains

> The Standards Working Group actively monitors evolving standards to educate projects about developments that might affect them, and helps projects formulate standards strategies and advance them before standards bodies.

That's the mission statement of OpenJS Foundation's newly chartered _Standards Working Group (WG)_. Wow! It uses the word "standards" a lot.


Thanks, word cloud! <small>(Also, jasondavies.com\/wordcloud)</small>

What are "standards" and why do they matter to projects?

But standards processes fail.

# TODO: standards done wrong. Example of a project that suffered because it wasn't involved in a standards process. Example of a win.

OpenJS Foundation's Standards WG aims to help projects avoid those kinds of problems; to avoid regrets like

> If only we'd been at this table five years ago

or

> Why did we spend so much time building this and they building that; it'll be really hard to get these working together. If only we'd known earlier.

or as xkcd.com explains


So who are we and how can we help?

We're a group of [people](https://github.com/openjs-foundation/standards#working-group-members) who collectively have 50+ years of experience with a diverse group of technology standards, but with an emphasis on web standards including those that define the languages and networking protocols that make up the web (CSS, HTML, JavaScript, DNS). We also have members with expertise on topics that often come up including security&privacy, internationalization&localization, user experience, API (Application Programming Interface) design.

We can help you stay informed. You probably know your projects needs far better than we do but since we "actively monitor" standards, once we know a bit about your project's needs we can keep you informed.

We can demystify. Standards organizations can be confusing and intimidating. We can answer questions, connect people, and help you figure out how to get your needs considered.
# TODO: pullquote about being intimidated initially. Banner image with lots of standards logos.

Know that most of our members had the same impressions at first.
# TODO: quotes about what people didn't know and how they gained confidence.

We can advise. Sometimes rephrasing a proposal so that its non-essential features looks more like previously accepted proposals makes it easier to digest.

We can set expectations. Standards are agreements and getting a diverse group to agree can take time. Knowing how long a similar kind of proposal has taken in the past may help planning.

# TODO: how to get involved

# TODO: further reading

## Outline

- OpenJS Foundation supports core projects over the long term
- Standards an important piece of that. TODO: example of how paying attention to standards helped a project
- Standards Working Group [Mission Statement](https://github.com/openjs-foundation/standards/issues/80)
- Who we are
- How many people? TODO(survey)
- From what backgrounds?
- How many years experience total?
- Working with which groups?
- We can help by
- We listen, you get more out of your time in front of plenary
- Training next generation of standards contributors.
- Make people aware of others' contributions, perspectives, shared/conflicting interests
- Explain processes
- How to get involved?
- Livestreams
- Office hours
- TODO: Where should people who want to get involved introduce themselves? [Slack #introductions](https://openjs-foundation.slack.com/archives/CKPCJQ6QH) or #standards?
- Further reading
- ["Revised Patterns for Participation in Standards Committees"](https://medium.com/@jorydotcom/revised-patterns-for-participation-in-standards-committees-dae82d93954e)