How to Join and Participate in the JSON Schema Community

Updated

You can join the JSON Schema community by signing up for the official Slack workspace, attending the recurring Office Hours and Open Community Working Meetings, following the project blog, and contributing to the surrounding tooling ecosystem. These channels are open to anyone working with JSON data—from developers evaluating schema validation for the first time to maintainers of validators, generators, and linters. The project reports over 60 million weekly downloads and a Slack community of more than 5,000 practitioners and experts, so there is an active audience for most questions.

Join the Slack workspace

The Slack workspace is the main day-to-day channel for questions, project feedback, and connecting with other practitioners.

  1. Go to json-schema.org and use the Join Slack link (it appears in the site header and again in the community section).
  2. Complete the Slack invitation flow, then join the channels that match your interest—validation, tooling, specification discussion, or general help.
  3. Ask your question with the relevant schema snippet and the validator or language you are using; that context is what makes answers actionable.

Expected result: access to a workspace of 5,000+ members where you can ask questions and get feedback on your projects. The site does not state any membership fee or login restriction beyond the Slack invitation itself, so treat the invitation flow as the only documented gate.

Common snag: the site's own framing is that Slack is for questions and project feedback, not for filing formal specification changes. If your goal is to change the specification, use the working meetings and GitHub instead.

Attend meetings and Office Hours

The community runs two recurring meeting types, and both are listed on the site's community events section.

Meeting Schedule Best for
Office Hours Every first Tuesday of the month, plus by appointment Getting direct answers on your own schema or implementation
Open Community Working Meetings Monthly (see the events listing for the current date) Following specification work and community decisions

The site also notes that Office Hours now run weekly—check the events listing before planning, since the monthly and weekly descriptions appear in different places on the page.

Before you attend: prepare a minimal schema plus the data that fails or behaves unexpectedly. Office Hours time is most useful when the problem is already reduced.

Follow the blog and the specification work

The blog carries project news and deeper technical context. A current example is "JSON Schema and IETF" by Greg Dennis (2026-07-06, about 3 minutes), which is relevant if you care about how the specification is standardized. Reading the blog is the lowest-commitment way to stay current; it requires no account.

For the specification itself, start from Read the docs on the homepage, then move to the specification pages when you need exact keyword behavior rather than tutorials.

Contribute to tooling and discussion

The site describes JSON Schema as more than a specification—an ecosystem of validators, generators, linters, and other utilities across many programming languages. The JSON Schema Landscape page lists companies and projects using JSON Schema, and the Explore link under the ecosystem section is the entry point for finding tooling.

Practical ways to contribute:

  • Report and reproduce bugs in a validator or generator you use, with a minimal schema and input.
  • Publish or improve a tool in a language where coverage is thin; the landscape listing helps you see what already exists.
  • Answer questions in Slack once you have solved a problem—the community's value depends on practitioners sharing fixes.
  • Join a working meeting if you want to discuss a proposal rather than just report a bug.

Decide which channel fits your goal

  • "I have a schema that won't validate" → Slack, or Office Hours for a live walkthrough.
  • "I want to track specification changes" → blog plus Open Community Working Meetings.
  • "I want to find a validator for my language" → the ecosystem/landscape pages first, then Slack if nothing fits.
  • "I want to influence the specification" → working meetings and the GitHub repository, not Slack alone.

The site does not publish a formal membership tier, fee, or contribution requirement for any of these channels; participation is organized through the Slack invitation, the public meeting schedule, and the public repositories.