add Rustc Trait System Refactor Initiative

[lcnr]

cc rust-lang/types-team#58

I've added every one who is already a part of an existing team and mentioned that they're interested in rust-lang/types-team#58 to the initiative for now: @BoxyUwU @cjgillot @compiler-errors @spastorino.

Not sure if opening a new repository for the initiative is too useful as it would only contain 2-4 documents and in my experience initiative repos are somewhat hard to discover. I don't know, maybe having that repo is actually really useful '^^ can still make a new one at that point

@rust-lang/types for review/approval

[lcnr]

changed it to be a subteam of compiler as types is already a subteam of it and having subteams of a subteam isn't allowed.

[jackh726]

I think rewrite -> refactor. Other than that, LGTM.

[lcnr]

👍 changed to refactor.

[jackh726]

Ah wait, do we want a zulip stream? Do you think it'd be useful?

[rylev]

Zulip streams aren't yet configured through this repo. You'll have to ask #infra on Zulip for that for now.

[rylev]

@pietroalbini do you know why this restriction was put in place?

[lcnr]

maybe because we of the governance webpage as there's currently a 1 to 1 correspondence between the parent team and the governance page: https://www.rust-lang.org/governance/teams/compiler 🤔

[lcnr]

Ah wait, do we want a zulip stream? Do you think it'd be useful?

Will try and experiment with project boards for this: https://github.com/orgs/rust-lang/projects/26/views/1. For that each area should then have a project board entry and a https://github.com/rust-lang/rust issue.

We could have a zulip stream with a thread for each of these issues, but I don't think that's too helpful. If we just need a place to discuss the impl of issues or general questions, staying in the #t-types stream is probably better as its easier to discover. Don't expect that we're going to have too many zulip topics for this initiative so using the #t-types stream should not drown out other work.