-
Notifications
You must be signed in to change notification settings - Fork 59
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
Who gets messages sent to [email protected]
?
#526
Comments
Any maintainer can, in principle, check this account. I'm not sure how many actually do check it regularly. |
At this moment it's at least any maintainer and also me. I was recently added related to the payment for the election system we are using. If this is our point of entry for COC complaints, it needs to be pretty clear who can see these. Alternatively, I wonder if we need to have one specific designated person as the point of contact for CoC complaints, so it's very clear whether there is any potential for conflict. The revised CoC will also include a list of alternative people. Yet another option is to say: "you can contact any of these people individually or by cc'ing several of them on your message", so people registering a complaint can choose how to go about it. |
I guess I would say let's have a list of contact people rather than a shared address. I would suggest we should have at least a maintainer and a steering group member at all times, avoid clustering at any given institution, and ideally not all be male. I'm okay being listed as an point of contact. |
Any reason for the "potential contact" list not to be all of the maintainers and all SG members? |
The main reason was that not everybody might want to sign up for that responsibility. e.g., Stefan is only committing to an hour a week for maintenance at this point. Either way, though. |
I think it would be good to clarify who (precisely) are the people who get an email when a message is sent to [email protected], and possibly outline a process whereby people get added and taken off this list.
The text was updated successfully, but these errors were encountered: