Create a plan for repo organization (labels etc)

[funnelfiasco]

As discussed in this week's meeting, we should do this. Here are my initial thoughts.

Changes

• Remove the following labels in favor of issue types:
  • bug
  • enhancement
• Remove the following labels because they seem unnecessary:
  • maintenance (if we want to keep this, we should define it)
  • ux (it’s not clear that this adds anything not covered by the interface-* labels below)
  • quality
• Create the following labels:
  • module-core: for darnit core
  • module-baseline: for the OSPS Baseline module
  • module-amber: for the Amber module
  • (Future modules will also get a module- label)
  • needs triage: auto-applied to all new issues. Indicates that a maintainer should look at it to see if it’s valid. If it is, add the appropriate labels
  • interface-mcp: for the MCP interface
• Rename the following labels:
  • invalid -> closed-invalid
  • wontfix -> closed-wontfix
  • cli -> interface-cli
  • question -> need info (this reads more clearly to me as "we need someone to answer questions". "question" can be taken as "i have a question about this project and therefore am opening an issue" which ought to be a discussion instead)

Thought process

Here's what I had in mind as I wrote this out:

• Only have labels we'll actually use.
• Group relevant labels together (GitLab has scoped labels. In GitHub you have to fake it by just naming them similarly)
• Labels are mostly for issues, not PRs. Sure, people can and do use labels on PRs, but it seems like most people focus on using them on issues.

Next steps

So we'll argue about this for a while. Once that's done and we've achieved something that passes for consensus, I'll:

1. Add/edit/remove the labels in GitHub
2. Update the issue templates accordingly
3. Add some info to CONTRIBUTING.md