Temporarily Blocking User: installgen2

[jasnell]

I am temporarily banning Github user installgen2 from the nodejs org for making an inappropriate comment in the nodejs/inclusivity issues. /cc @nodejs/tsc

[mikeal]

cool, post a screenshot next time for context (assuming the post was
removed)

On Thursday, November 12, 2015, James M Snell notifications@github.com
wrote:

I am temporarily banning Github user installgen2 for making inappropriate
comments in the nodejs/inclusivity issues. /cc @nodejs/tsc
https://github.com/orgs/nodejs/teams/tsc

—
Reply to this email directly or view it on GitHub
#8.

[jasnell]

Comment was deleted. Here's the screen grab from my github home page:

What's a reasonable length of time for banning, btw?

[mikeal]

what does IRC typically do @emilyrose?

On Thursday, November 12, 2015, James M Snell notifications@github.com
wrote:

Comment was deleted. Here's the screen grab from my github home page:
[image: ban]
https://cloud.githubusercontent.com/assets/439929/11138435/127aefdc-8977-11e5-9c0e-11ca9453ccbd.png
What's a reasonable length of time for banning, btw?

—
Reply to this email directly or view it on GitHub
#8 (comment).

[Trott]

Here's another comment that showed up in that repo. (I deleted it after consulting with @jasnell on IRC about the correct course of action.)

I think stuff like this is actually a pretty good example of why the consensus on that WG is that there needs to be a way to report these things privately. Posting to a public issue like this one means:

• Potentially rewarding the trolls by drawing attention to their activities
• Marginalized individuals may be reluctant to report harassment in a public forum like this for what I hope are obvious reasons

[mikeal]

Can we get a tmp ban on this one too?

[jasnell]

I'd say yes. I'm not able to do it at the moment tho.
On Nov 12, 2015 8:57 PM, "Mikeal Rogers" notifications@github.com wrote:

Can we get a tmp ban on this one too?

—
Reply to this email directly or view it on GitHub
#8 (comment).

[bnoordhuis]

As a bit of counterweight, it is a homonym. I've heard people comment on it before.

As counter-counterweight, the account is only three days old (but with the only other activity a reasonably worded request on the rust-rfc repo.)

Maybe try contacting that individual privately? Let's not assume malice off the bat.

[affinity-matrix]

Honestly when someone does something so clearly intended to be nothing other than a disruption (or worse, triggering) I ban them immediately.

If they engage me privately in a reasonable discussion on why their behavior was inappropriate we will typically negotiate a reinstatement with the understanding that they're expected to abide by the CoC.

Sent from my iPhone

On Nov 12, 2015, at 7:56 PM, Mikeal Rogers notifications@github.com wrote:

what does IRC typically do @emilyrose?

On Thursday, November 12, 2015, James M Snell notifications@github.com
wrote:

Comment was deleted. Here's the screen grab from my github home page:
[image: ban]
https://cloud.githubusercontent.com/assets/439929/11138435/127aefdc-8977-11e5-9c0e-11ca9453ccbd.png
What's a reasonable length of time for banning, btw?

―
Reply to this email directly or view it on GitHub
#8 (comment).

―
Reply to this email directly or view it on GitHub.

[Trott]

@bnoordhuis I think the wording ("quite frankly, brazenly phallic") makes it impossible that this comment was intended as a serious contribution to the conversation. "brazenly"? Come on...

I would agree that exact intent is difficult (if not impossible) to discern. Stupid ill-advised joke not intended to harm anyone? Mocking attempt to derail the conversation? Something in between? Who knows?

But I'm also not sure intent matters here. I have no comment (at this time) on whether a temporary block is appropriate or not in these situations other than this: I would suggest that it not be viewed as a punishment but as a mechanism to prevent abuse similar to the way systems might lock an account for some temporary period of time if there are thousands of failed logins in a short period of time.

(I also wonder if @jasnell and/or I or someone else should block out the usernames on those screenshots. No reason to call attention, positive or negative, to the users in a public forum.)

EDIT: I just updated the screenshot to obscure the username for the second comment. If anyone who doesn't already have it has a legitimate need to know it, I can provide it.

[jasnell]

If we don't already, we need a private mailing list similar in nature to
security@nodejs.org to report these matters.
On Nov 13, 2015 4:39 AM, "Rich Trott" notifications@github.com wrote:

@bnoordhuis https://github.com/bnoordhuis I think the wording ("quite
frankly, brazenly phallic") makes it impossible that this comment was
intended as a serious contribution to the conversation. "brazenly"? Come
on...

I would agree that exact intent is difficult (if not impossible) to
discern. Stupid ill-advised joke not intended to harm anyone? Mocking
attempt to derail the conversation? Something in between? Who knows?

But I'm also not sure intent matters here. I have no comment (at this
time) on whether a temporary block is appropriate or not in these
situations other than this: I would suggest that it not be viewed as a
punishment but as a mechanism to prevent abuse similar to the way systems
might lock an account for some temporary period of time if there are
thousands of failed logins in a short period of time.

(I also wonder if @jasnell https://github.com/jasnell and/or I or
someone else should block out the usernames on those screenshots. No reason
to call attention, positive or negative, to the users in a public forum.)

—
Reply to this email directly or view it on GitHub
#8 (comment).

[piscisaureus]

Maybe try contacting that individual privately? Let's not assume malice off the bat.

@bnoordhuis I think the wording ("quite frankly, brazenly phallic") makes it impossible that this comment was intended as a serious contribution to the conversation. "brazenly"? Come on...

I would also recommend not assuming malice in general; I think everyone has had their "come on..." moments, finding out later that there are people who care deeply about a certain subject.

In this particular case, my suspicion is that both accounts may be the same person and I would suggest temp-banning them both.

• dangerrust is clearly a throwaway account, and both accounts are commenting on this issue as well: Rust Needs The Ternary Conditional Operator (-?-:-) rust-lang/rfcs#1362 (comment).
• installgen2 doesn't look like a throwaway, but a lot of things that are in this user's profile & repos look less than professional so it seems like a good idea to have a conversation with said person before letting them comment again.

If we don't already, we need a private mailing list similar in nature to
security@nodejs.org to report these matters.

+1
moderation@nodejs.org ?

[Fishrock123]

lot of things that are in this user's profile & repos look less than professional

I agree. If they feel so strongly about this let them just ask us to be unbanned, though I do not expect responses to improve, at least anytime soon.

[mikeal]

How do they ask us? On IRC moderators are known and can be DM'd, what can
we do on GitHub though?

On Friday, November 13, 2015, Jeremiah Senkpiel notifications@github.com
wrote:

lot of things that are in this user's profile & repos look less than
professional

I agree. If they feel so strongly about this let them just ask us to be
unbanned, though I do not expect responses to improve, at least anytime
soon.

—
Reply to this email directly or view it on GitHub
#8 (comment).

[orangemocha]

I am a bit on the fence on this one, so let me play devil's advocate. The remark could be seen as an honest observation, if it wasn't for the slight humor added to it. Which makes the intent unclear. It could be observation + pun (passable) or simply a joke for joke sake (troll-like behavior). If anything, we could have called him up on it, and make it clear what's acceptable and what not, and if he persisted on the troll-side then ban him. Wouldn't that be a good exercise in a forum about inclusivity? 😄