What's the process to propose a new group? AVR was recently merged.
This PR adds a RISC-V group, maybe just open a similar PR for AVR? https://github.com/rust-lang/team/pull/362
Clearly we need to make a checklist
there are actually a few steps required
@nikomatsakis let me know what those are (or a link to the checklist) whenever you figure it out; no huge rush!
Any updates @nikomatsakis ?
whoops forgot about this
@Jake Goulding is this just to make a group, or did we want to declare AVR as Tier 2 or Tier 3
Mostly just the group so we can get notified about O-AVR issues people raise.
It’s nowhere near tier 2. It’s been merged, so I assumed that was tier 3 by default.
OK that sounds fine
yeah we can make a group readily enough
Cool — what should I do next?
@Jake Goulding Not on the compiler team but I believe the process is that you should propose a major change for adding AVR group similar to this one. https://github.com/rust-lang/compiler-team/issues/293
@Jake Goulding Correct me if I’m wrong but that’s a PR adding the AVR group to the team roster. I was suggesting you create a new Major Change Proposal, which would be the first step in getting a group added to team.
At least that’s how it worked for Windows & ARM.
Ah, true. My point about not inciting Niko's ire is still a point though.
@Jake Goulding OK sorry -- so -- honestly I don't think we need so much process
well, I think making an MCP could be a good idea just for the purposes of letting people know it's happening
I'll make a check-list
but also an Inside Rust blog post might be a good way to advertise
this isn't really taking on any new support obligations
OK doke, I can start up a MCP soon.
I'm creating a forge page with a list of steps
and I think I agree with @XAMPPRocky that, as a general process, let's make an MCP be a first step, it's easy and simple
@Jake Goulding draft -- have to run