Create rfc-admin-guide.md

[ewilderj]

Describe what community admins do as part of the RFC process

[bhack]

A meta-RFC :)
What I see Is that RCF management started quite well but currently all the deadline are a little bit out of control.
Many RFC seems in a not so clear status.

What about a weekly or biweekly admin pass over the RFC PR?
Generally there are not so many parallel RFC so could be easy to have an internal biweekly day/clock for a status review pass.

[bhack]

Just some example:
#130
#133
#77

[theadactyl]

@bhack I think there's a challenge when the people doing the RFC management aren't able to meaningfully influence the resolution of RFCs that are in a tricky/unresolved state. Newer RFCs than those you noted that were more straightforward have progressed fine. We could have an internal reminder to review, but we may also need time frame guidelines around when to move RFCs to "Abandoned".

[bhack]

@theadactyl I understand your point of view but honestly without internal informations we really don't know where the Team "attention" is (a limited resource in every context).
Was It abondoned? Does It need a new public deadline? Is it stalled?

Without off the band/internal informations we really cannot classify the RFC status.

If we have a regular clock from TF management team over RFC you can codify GitHub labels and it will be a keep alive signal for community.

Expecially when RFC are open months after the reported deadline an there isn't any public signal to understand what It is happening.

This Is in topic here cause this PR Is about RFC admin and community and IMHO recrusive ping It Is not a nice solution.

I think that we need to handle a clock to pass over RFC PR and use labels or deadline extension on every pass if needed.

[theadactyl]

This is really helpful feedback, will mull it over to figure out a better solution.

…

On Tue, Nov 19, 2019 at 2:37 PM bhack ***@***.***> wrote: @theadactyl <https://github.com/theadactyl> I understand your point of view but honestly without internal informations we really don't know where the Team "attention" is (a limited resource in every context). Was It abondoned? Does It need a new public deadline? Is it stalled? Without off the band/internal informations we really cannot classify the RFC status. If we have a regular clock from TF management team over RFC you can codify GitHub labels and it will be a keep alive signal for community. Expecially when RFC are open months after the reported deadline an there isn't any public signal to understand what It is happening. This Is in topic here cause this PR Is about RFC admin and community and IMHO recrusive ping It Is not a nice solution. I think that we need to handle a clock to pass over RFC PR and use labels or deadline extension on every pass if needed. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#165?email_source=notifications&email_token=ABREJVKAYVUMFXJ2REQ2YO3QURTC7A5CNFSM4JDHX7IKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEEQA32Q#issuecomment-555748842>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABREJVPGEGTXIZTTYT7ZALLQURTC7ANCNFSM4JDHX7IA> .

[bhack]

If you see also recently merged MLIR PR was accepted after implementation and months after the deadline:
#115 (comment)

IMHO we are losing a little bit the RFC role.