Community repository minimum maintenance

[bhack]

Can we expect to have a regular maintenance of this low traffic community repository?

• Many RFCs go regularly out of the comment deadline and we don't know the public status of the process for months.
• Many very trivial fixes on docs are not merged or if approved we need to wait for months.
• Many sparse topics issues like Gsoc/Code in are not closed or redirected to the right place.

I think that a regular 10 minutes check one or two times at weeks it is enough triage and maintain this repo in an healty and useful status as is the many communication channel between the internal team and the Tensorflow community.

[bhack]

/cc @theadactyl I hope to not open another meta ticket over this as this is the "TICKET". Please take care of the community repo cause it is really a bad marketing to not care a so low traffic repo.

[bhack]

To improve the public communication It could be nice if the implementation start after the RFC it is public approved (merged) #182 (comment)

[mihaimaruseac]

Agree, but note that that commit you mention landed after the RFC approval, not before.

[ematejska]

The problem here was with the process (I run the RFC process nowadays and take full responsibility.) The design was was reviewed but the communication was not good afterwards. Thank you for this feedback.

[bhack]

@mihaimaruseac I don't see this in our governance https://github.com/tensorflow/community/blob/master/governance/rfc-admin-guide.md#rfc-acceptance-process.
You can always open a PR to change our governance.

[bhack]

@ematejska I am glad that you are the owner of the RFCs. I hope that we could improve the labeling governance after the comment public deadline.

[bhack]

@mihaimaruseac Don't take it as personal by downvoting. You are internal and sometimes you cannot understand that we are totally unaware of what will happen with respect to your internal threads. As a community we only know what is public.

[bhack]

Can you give a pass to noise tickets?

[bhack]

@ematejska I think that we could evaluate to close almost all the open issues in the repo.

[ematejska]

@bhack @theadactyl and I have started to go through these on a periodic cadence. We should get to these issues early next week at the latest.

[bhack]

Thanks

[theadactyl]

Got to the issues! We are working steadily on the RFC backlog as well, so closing this issue.