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

Unreasonable bullet-point in workmode.md #76

Open
eladalon1983 opened this issue Jul 20, 2022 · 3 comments
Open

Unreasonable bullet-point in workmode.md #76

eladalon1983 opened this issue Jul 20, 2022 · 3 comments

Comments

@eladalon1983
Copy link
Member

The newly published workmode.md reads:

Github issue etiquette
...
4. You can attract someone's attention to an issue where their input would be useful, by including an @ sign followed by their github id; but once someone has been flagged in an issue, and if you want to draw their attention to a new point, use discretion in flagging them again publicly (vs contacting them out of band, e.g. by email).

I think this is counter-productive. The real issue is not that people flag others too often; the real issue is that repeated flagging over weeks and months is often necessary in this WG. And emails and other reminders sent out-of-band are often ignored. What we need are SLOs for a reasonable response time, and a mechanism to escalate when progress is delayed. If anyone in this WG repeatedly ignores requests to engage with an issue - which happens all too often - we need a clear procedure other than begging by email and chat.

@dontcallmedom
Copy link
Member

if an issue or PR is blocked for lack of reaction, the expected procedure would be to raise the attention of the chairs to this blocking pattern and put the onus on them to figure out how to move forward (and how to prioritize these different requests for attention from a limited pool of resources)

@eladalon1983
Copy link
Member Author

eladalon1983 commented Jul 20, 2022

if an issue or PR is blocked for lack of reaction, the expected procedure would be to raise the attention of the chairs to this blocking pattern and put the onus on them to figure out how to move forward (and how to prioritize these different requests for attention from a limited pool of resources)

Thanks.

I think this thread is a good place to clarify some of the fine details and edge-cases.

  1. What is a reasonable number and spacing of ignored @mentions/emails/pings before contacting the chairs with such a complaint? (I.e. what is a reasonable SLO to expect?)
  2. If the non-responding person is a chair, and has not responded to direct emails, should one appeal to the remaining chairs? Could we document the mailing list for chairs in workmode.md?

@dontcallmedom
Copy link
Member

Let me clarify that contacting the chairs shouldn't be viewed or taken as a complaint or an appeal: the idea is if, as an editor or an implementor, your progress is stuck due to lack of input on an issue or a pull request, you would let the chairs know with some contextualization on the priority of the said discussion.

I've submitted for review by the chairs a document that tries to document in more details how we would operationalize that workmode - that will include information about how to contact the chairs, with what information, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants