Document the council's internal decision making process

[ehuss]

Currently it isn't clear exactly how or where decisions are made, or how they are communicated.

https://hackmd.io/@rust-leadership-council/ByAlBiHon contains a draft of some ideas on how to go about this.

This particularly includes where and how async decisions are made and publicized.

The RFC also suggests:

Establishing and agreeing on processes for faster decision-making for simple one-off operational matters, such as responding to emails reaching out to the Project.

[traviscross]

As this is marked as active but has not seen an update here for some time, I nominate to review this and to consider whether we should leave an update here about the status.

This should take five minutes.

[ehuss]

I plan to review and edit my original proposal, and post it to the leadership-council repo soonish.

[ehuss]

cc #71
Also @eholk mentioned clarifying our usage of fcpbot for having 100% approval instead of N-2.

[traviscross]

Thinking about it, I'd probably just propose that we adopt the normal rfcbot rule. The 10 day final comment period serves as a kind of unanimity check, as any member can raise a blocking concern during that time and thereby stop the FCP.

Following the normal process for the rest of the project here would make us more comprehensible to the rest of the project, and I don't see a strong reason for us to deviate in this instance.