Set up a CODEOWNERS file for this repository

[alexcrichton]

Unlike the Wasmtime repository this repository does not have automatic assignment of incoming PRs to a reviewer. By default I typically review PRs but for my own PRs I rely on others to be subscribed to this repository (which is not an assumption I'd like to have to make) or need to manually solicit a review (which I often forget about or can feel awkward doing sometimes). I'd like to instead move to a system similar to Wasmtime where a reviewer is automatically selected with the understanding that they can always pass it on as well. From a practical standpoint I'd still try to review any non-me-authored PRs, but ideally it'd help reduce the "me is the bus factor" and also help assign my own PRs to someone without requiring a subscription to the repository.

My thinking is to implement this change we'd add a new team to the BA, wasm-tools-default-reviewers, and specify that in CODEOWNERS under the * path. We could add more refined teams over time if some folks are interested in just one tool over others, but for now I'm thinking we'd have a single team.

For initial membership of this review rotation I'd imagine pulling in a subset of me, @fitzgen, @dicej, @pchickey, and @abrown. What do y'all think of this? Would you prefer to not be in such a rotation? Or do y'all know of others who'd be a good fit?

[alexcrichton]

@abrown could you go ahead and add a new @wasm-tools-default-reviewers team to the BA organization seeded with you/me/Joel? As Nick/Pat respond we can add them as well. (I think you've got admin rights as a TSC member to do this, right?)

Once the team is made I'll configure this repo and add the CODEOWNERS

[fitzgen]

SGTM 👍

[disquisitioner]

I've created the wasm-tools-default-reviewers GitHub team in our organization and seeded it with @alexcrichton, @abrown, and @dicej. LMK if that doesn't enable you to configure the repo and add the CODEOWNERS.

[alexcrichton]

I forget how github teams work, but would it be possible to add one of us as an admin of the team?

If not, mind adding @fitzgen as well? Also while I'm happy to oblige you if you'd like to review PRs on wasm-tools, you might want to remove yourself as well lest you get tagged for review

[disquisitioner]

You bet! I've given @alexcrichton and @abrown the "Maintainer" role in the team which should allow you two to add/remove members and create subteams. I also added @fitzgen to the team as a Member, and did remove myself so I don't get tagged for review.

[alexcrichton]

@abrown when you get a chance can you follow the instructions here and "Configuring auto assignment" beneath that to enable auto-assignment for this team?

I think in conjunction with #2212 that should achieve the goal here, but I also forget how we set this all up in Wasmtime so I could very well be forgetting a step.

[disquisitioner]

I took the liberty of copying the "Code review" team settings from the wasmtime-default-reviewers team and applied them to the wasm-tools-default-reviewers team. (So auto assignment is enabled and will assign one team member on a round robin basis.) LMK if you'd like more details on those settings or if I can help in any other way.

[pchickey]

Thanks for setting this up - I was on vacation while this unfolded but I'm happy to serve on the default reviewers rotation for this repo. I sent a request to join that group, but idk who gets those - @disquisitioner ?

[alexcrichton]

I was able to respond to the invite myself so you should be added now 👍

I think everything's now taken care of so I'm going to close this, thanks all!