---
type: "article"
title: "The first OpenLint office hours"
summary: "On 24 September we held the first office hours under the OpenLint name. We’ve been meeting weekly since the summer, but those calls were mostly about what this project is and what to call it. This was the first one where we got to work.\nThe agenda is on GitHub, and the recording, summary and full transcript are here on the site.\nA name, and a foundation\nWe have a name, chosen by community vote. It’s literal, and a little boring, but after watching OpenAPI succeed, I think a name that explains itself is worth more than a clever one. The website, the GitHub org, a community repo and info@openlint.org are all in place. SmartBear may still decide to hand Spectral to the group. We’re not waiting on that.\nThe roadmap, in three areas\nWe walked through the starter roadmap: the specification, the toolbox, and the administration of the project. The list grew on the call:\nThe conformance suite and IDE integration each belong in both the specification and the toolbox.\nThe specification should be friendly to AI tools, with prompts and skills.\nMigration, keeping up with Spectral upstream, and the implementation landscape become one item about interoperability with Spectral, Vacuum, Speakeasy and other tools, rather than one-way migration.\nCoverage turns out to be two features: how much of a ruleset its tests exercise, and how much of an API document the rules actually reached.\nA code of conduct, a website item, and a process item went on the administration list.\nPhil Sturgeon walked through the first three discussions: aliases, cleaning up Stoplightisms, and rules testing.\nHow the work will happen\nWork starts as a discussion, becomes issues once we know who cares about it, and gets done in pull requests. My proposal for AI is to use it sparingly, agree on it pull request by pull request, and keep it out of our issues. That one is open for discussion too. The first discussions to open are the formal specification, the core libraries, the code of conduct and governance.\nIf any item on the roadmap matters to you, start a discussion on it, or join us at the next office hours."
newsletter: "OpenLint Blog"
newsletter_handle: "openlint"
newsletter_url: "https://usecommune.com/n/openlint"
author: "Kin Lane (@kinlane)"
published: "2026-09-24T00:00:00.000Z"
canonical_url: "https://usecommune.com/n/openlint/a/the-first-openlint-office-hours"
markdown_url: "https://usecommune.com/n/openlint/a/the-first-openlint-office-hours.md"
chat_url: "https://usecommune.com/n/openlint/a/the-first-openlint-office-hours/chat"
source_url: "https://openlint.org/blog/2026/09/24/first-openlint-office-hours/"
body_source: "imported"
likes: 0
replies: 0
body_words: 389
---

# The first OpenLint office hours

![Pill-shaped figures seated around a round table, with a mint-green squiggle resolving into a check mark at its center](https://openlint.org/assets/blog/2026-09-24-first-office-hours.jpg)

On 24 September we held the first office hours under the OpenLint name. We’ve been meeting weekly since the summer, but those calls were mostly about what this project is and what to call it. This was the first one where we got to work.

The [agenda is on GitHub](https://github.com/openlint/community/issues/1), and the [recording, summary and full transcript](https://openlint.org/meetings/office-hours/2026-09-24/) are here on the site.

## A name, and a foundation

We have a name, chosen by community vote. It’s literal, and a little boring, but after watching OpenAPI succeed, I think a name that explains itself is worth more than a clever one. The website, the GitHub org, a [community repo](https://github.com/openlint/community) and info@openlint.org are all in place. SmartBear may still decide to hand Spectral to the group. We’re not waiting on that.

## The roadmap, in three areas

We walked through the starter roadmap: the **specification**, the **toolbox**, and the **administration** of the project. The list grew on the call:

- The conformance suite and IDE integration each belong in both the specification and the toolbox.
- The specification should be friendly to AI tools, with prompts and skills.
- Migration, keeping up with Spectral upstream, and the implementation landscape become one item about interoperability with Spectral, Vacuum, Speakeasy and other tools, rather than one-way migration.
- Coverage turns out to be two features: how much of a ruleset its tests exercise, and how much of an API document the rules actually reached.
- A code of conduct, a website item, and a process item went on the administration list.

Phil Sturgeon walked through the first three discussions: [aliases](https://github.com/orgs/openlint/discussions/2), [cleaning up Stoplightisms](https://github.com/openlint/community/issues/3), and [rules testing](https://github.com/openlint/community/issues/4).

## How the work will happen

Work starts as a discussion, becomes issues once we know who cares about it, and gets done in pull requests. My proposal for AI is to use it sparingly, agree on it pull request by pull request, and keep it out of our issues. That one is open for discussion too. The first discussions to open are the formal specification, the core libraries, the code of conduct and governance.

If any item on the roadmap matters to you, start a discussion on it, or join us at the next office hours.

***

## Discussion

No replies yet.
