Collaborator Changes - More Privacy

[benjamingr]

I’d like to propose the following change to the collaborator nomination process:

• The “private part” of the nomination does not include discussion of the collaborator being nominated in the thread, instead people email the nominator and CC the TSC with any objections. This is for better privacy of the collaborator nominee.
• The “public part” of the nomination does not allow for blocking the nomination with a comment, instead people email the nominator and CC the TSC with any objections. This is for better privacy as well.
• If someone wants to block and not let the nominator know they’re the blocker they are welcome to email the TSC or a TSC member directly and they will communicate that with the nominator and the TSC.

I’d like to propose the following amendment to moderation

• Opening an issue in the private moderation repo to discuss members’ conduct is no longer allowed, instead people requesting moderation of members’ posts should email report@nodejs.org , this is for better privacy of the member.
• Opening an issue in the moderation repo about a non-member or spam is still allowed and it’s the preferred way to report spam.

The changes are to better let people save face and since handling these issues in private often leads to better conclusions.

[ovflowd]

I agree with all the statements here, but I wonder by making "blockings/ -1" privates we loose the chance of being able to convince the people providing the "-1" of a counterargument.

Because by the bylaws even a single -1 would result in the nominee not being accepted.

[Trott]

• Opening an issue in the private moderation repo to discuss members' conduct is no longer allowed, instead people requesting moderation of members' posts should email report@nodejs.org , this is for better privacy of the member.

I imagine we'd also want to be clear that people can reach out to individual Moderation Team members instead if they are more comfortable with that. This would be particularly useful in the case where the behavior being discussed is that of another Moderation Team member (although hopefully that never comes up).

[Trott]

(Aside: I wonder if the email address might routinely send things to the spam folder. We should probably get someone to look closely at the DMARC setup there.)

[benjamingr]

I agree with all the statements here, but I wonder by making "blockings/ -1" privates we loose the chance of being able to convince the people providing the "-1" of a counterargument.

Usually when a collaboration is blocked the nominator goes to objectors and tries to work things out (e.g. ask what the nominee has to do in order to get accepted), this is to the best of my knowledge is already done in private.

[ovflowd]

I agree with all the statements here, but I wonder by making "blockings/ -1" privates we loose the chance of being able to convince the people providing the "-1" of a counterargument.

Usually when a collaboration is blocked the nominator goes to objectors and tries to work things out (e.g. ask what the nominee has to do in order to get accepted), this is to the best of my knowledge is already done in private.

But if the objection becomes private, how does the nominator knows who to reach out to?

[benjamingr]

The objection is private to the nominator and the TSC so ideally through that, people can block without doing so publicly today too if I understand our process correctly.

[ovflowd]

The objection is private to the nominator and the TSC so ideally through that, people can block without doing so publicly today too if I understand our process correctly.

Aha! Didn't get that from the initial thread; maybe I missed it or you might want to clarify that. But that's good to know.

Edit: re-reading the initial thread made it clear!

[mcollina]

I’m -1 with this change. I think a better approach is to run the nomination process through the TSC mailing list. In this way everything could be done privately.

[benjamingr]

@mcollina presented in the TSC meeting is:

• You can block by sending an email to the TSC or a TSC member privately.
• You can block by sending an email to the nominator and try to work out the differences

Does that address your concern?

[mcollina]

No. I think we should change this process completely to maintain privacy in a better way.

If the nomination is public to the collaborators and if it does not go through, people would know about that (even if the motives are not clear).

Here is a process that have more privacy:

1. the collaborator that does the nomination send an email to tsc@iojs.org
2. the TSC approves or rejects via email

This has the advantage of not having disjoint communication across multiple medium. It's easy to miss to correlate a mail with a github issue and viceversa.
The disadvantage is that only tsc members can object, however I consider this a minor concern give the current number of people in the TSC.

[GeoffreyBooth]

We can't have the TSC be the only deciders on whether new collaborators can be added. We can maybe have an initial round veto, but assuming no TSC member objects via email we still need to run a nomination by all collaborators before it can be approved.

[benjamingr]

I feel strongly that the project should let collaborators object to nominations since the TSC while big isn't aware of all interactions and context in the project.