Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create rfc-admin-guide.md #165

Merged
merged 1 commit into from
Nov 20, 2019
Merged

Create rfc-admin-guide.md #165

merged 1 commit into from
Nov 20, 2019

Conversation

ewilderj
Copy link
Contributor

Describe what community admins do as part of the RFC process

Describe what community admins do as part of the RFC process
@bhack
Copy link
Contributor

bhack commented Nov 19, 2019

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
Copy link
Contributor

bhack commented Nov 19, 2019

Just some example:
#130
#133
#77

@theadactyl
Copy link
Contributor

@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
Copy link
Contributor

bhack commented Nov 19, 2019

@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
Copy link
Contributor

theadactyl commented Nov 19, 2019 via email

@bhack
Copy link
Contributor

bhack commented Nov 19, 2019

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.

@ewilderj ewilderj merged commit 4f2a1d0 into master Nov 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants