Alice Ryhl

And you get to explain why did you pick this design and not some other design.

And I think that's usually a pretty big part of an RFC.

And then, of course, it's good to look at what did C++ do and what can we do in the future as well.

Well, somehow people get people to look at it.

There is an IFC's repository and you can open a pull request there with your Markdown document with RFC and people can discuss it.

You might also write up your doc somewhere else.

We call it a pre-RFC if it's not in the RFC directory, but it's kind of the same thing.

Let's say that the language team, like it's a language team RFC and they're happy with it.

So I said the RFC was how the language makes big decisions, but then they actually use a process that comes up for all decisions essentially called the final comment period.

And so the idea is,

They tell the bot to please start the approval process, and then it will create a comment on GitHub with a checkbox for every team member.

And then team members check their own checkbox.

And once everybody from the team, except for at most two, have checked their checkbox, then the final comment period will begin, which is two weeks.

I mean, you know, let's say that everybody checks that bug immediately and then the two other people didn't get a chance to look yet.

So it's to make sure that everybody has a chance to see it.

So there's another part of the process, which is concerns.

Team members can file a concern, which basically pauses the process until it's resolved.

And then once the two weeks pass, it's accepted.

So that's essentially how the team makes decisions.

And this is not just IFCs.