2024 New Year's Cleaning meta-issue

[handrews]

[EDIT: All issues listed here are now tracked via either the Contributor Guidance project or Automation & Infrastructure project]

Towards the end of 2023, a number of folks expressed frustration with the apparently-static state of affairs regarding this repository's issues and PRs. We've been taking action to fix that, starting with @baywet 's automation efforts and @lornajane 's issue-closing push. The weekly TDC calls this year have devoted a lot of time to figuring out what to clean up and how to best get it done.

I'm filing this issue to track that work and make it visible to folks who don't join the weekly calls or keep track of the meeting notes.

Governance:

• Add new members to the @OAI/tsc (this process has now been started)
• Added a CODEOWNERS file #3489 (allows @OAI/openapi-maintainers write access to all but the actual specification documents)
• Define triage role criteria and process #3523
• Define the maintainer role criteria and process #3524
• TOB info needs to be updated #3482
• Update development document #1346

Build, test, deploy, and automate:

• Define deployment process for link fixes to published specifications #3515 See also the list of fixes in question
• fix: GitHub changed markdown rendering for headings/anchors #3548
• Add automation to prevent PRs from changing specification files that need to be immutable. #3432
• npm package not published? #2400
• reinstate validation of schemas and examples, fixes #3557
• Host schema publicly #151 (comment) (specifically, add dates to non-dated schemas and define and document the deployment process)
• Investigate automation of closing issues that are labeled as "enhancement" but have not gained sufficient community interest #3430
• What is our authoritative spec URL and how do people find it? #3576

Managing more repos and projects:

• Where to put ancillary content #1246 (should we split any more non-spec content out of this repo?)
• Define the need for documentation beyond the current scope of the OAS #2872 (how to manage SIG-specific specifications)
• Use community repo for governance, info, & user/dev help questions #3561

Planning releases:

• 3.x.y patch release approach #3528
• 3.x minor release approach #3529
• Define process for issues addressed in Moonwalk #3508

Managing the backlog:

• Audit, reorganize, and document labels (and probably also milestones) #3509
• Github Create Issue button need refactoring #3517
• Define criteria for filing/closing issues vs discussions #3518
• Define process for the "proposals" directory #3527
• PR template with guidance on branches and files #3533
• Who and how many people need to sign-off on a PR, exactly? #3581

We may add other process tickets here during this batch of work, but we should close it when we feel like we've reached a new steady state. I'll assign this to myself to keep the checklist up-to-date and close the issue when appropriate.

[handrews]

All issues listed here are now tracked in one of the following projects:

• Contributor Guidance project (for topics requiring TSC agreement)
• Automation & Infrastructure project (for non-spec, non-policy work that anyone with appropriate GitHub/javascript/automation/etc knowledge is encouraged to pick up)

In #3509, we decided to no longer use meta-issues as a process, and in #3610 we decided to give projects a trial run with these two areas of focus.