August 2026 TSC Meeting

The technical steering committee met on August 6, the first meeting since the restructuring shipped.

The working group debate

Most of the meeting was about two connected things: how working groups form and how the TSC approves new lexicons. The short version is we landed on a lightweight framework. New lexicons need at least two people in a working group and a one-week comment period minimum. The TSC can move faster when there's prior art and established support, or slower when concerns come up. There is no auto-approval, and decisions go through affirmative gates, not silence. We'll revisit in four months to see if it holds.

The real debate was about friction. How much do you want? Rudy argued speed matters: two weeks is a ceiling before people just don't bother. Ms Boba pushed for enough time for real community input, especially on the big, common lexicons that affect a lot of people. The compromise lands on a week as default, with TSC judgment filling the gaps. It's not a perfect solution. It is one everyone could live with, which for governance is usually as good as it gets.

The changes that shipped

Nick ran through everything that's gone live since July's consent decision. The collaborator role is gone. TSC members are the only PR approvers now. At our scale, designated NSID owners were more process than they were worth. The website is the source of truth for governance docs, the schema directory, and contributing guides. It got a reconciliation pass: missing lexicons added, DNS cleaned up, running on Tangled.

@lexicons.lexicon.community is live as the dedicated publishing identity, separated from the main account so a credential leak on one doesn't compromise the other. The Offprint blog is running, with posts planned for each TSC meeting going forward.

Nick was candid about two things he thinks he got wrong: the website design wasn't very helpful and posting on social was too infrequent. Both are getting fixed.

Posting more, gatekeeping less

The TSC agreed to be more active on social. Nick has an automated agent scraping Discourse, PRs, and mentions to draft Bluesky posts. It's been running about two weeks. The plan: a blog post after each TSC meeting, automated Bluesky posting from @lexicon.community for lexicon changes and meeting announcements, and Discourse as the discussion hub. The vestigial email approach is getting retired.

We also agreed on a lightweight async decision model for non-governance stuff. Someone posts a proposal or PR, pings the TSC, if no objections surface in a reasonable window, it moves. Anyone can bump something to the next meeting. Governance changes still need a call and enthusiastic consent.

Next meeting

The September 3 agenda already has two items: how to change a published lexicon (Ms Boba's request, covering what happens when a schema is live and needs updates) and TSC role and identity (clarifying what this group is and how transparent it should be).

September 3, Thursday, 1 PM ET / 17:00 UTC. Calendar, forum thread. Show up if you want something discussed.