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

"Ed J" Is Disruptive Of Peaceful Development Process #35

Closed
wbraswell opened this issue Sep 14, 2015 · 12 comments
Closed

"Ed J" Is Disruptive Of Peaceful Development Process #35

wbraswell opened this issue Sep 14, 2015 · 12 comments

Comments

@wbraswell
Copy link
Contributor

Hello Everyone,

Ever since I started interacting with the Inline development team a few years ago, I have received nothing but a constant stream of negative comments and sarcastic harassment from "Ed J" aka @mohawk2 . As far as I can tell, I have done nothing to warrant this treatment, and it has already been dealt with at least once in private by Inline founder @ingydotnet when I publicly retaliated against being mistreated.

At this point, I am unable to even talk to Inline::CPP team lead @daoswald about valid technical issues without being immediately targeted by "Ed J". His long-time use of online anonymity, an openly accepted practice in the Perl community, seems to support this anti-social behavior.

My best guess is "Ed J" dislikes my use of Inline to make Perl run faster via RPerl, because this will likely obviate the need for his own PDL software project. I am sorry this is the case, but I can't be expected to accept this kind of abuse or quit working on RPerl just because he has his feelings hurt. RPerl is a serious software project and deserves at least a modicum of respect.

I am a strong, decade-long supporter of the Inline project, and I have non-trivial code present in the public distributions of both Inline::CPP and Inline::Filters. It is neither acceptable nor appropriate for the Inline team leaders to passively condone this situation by continuing to allow it to go unaddressed any longer.

Earlier today, I voluntarily departed from the #inline channel on irc.perl.org due to the by-now-not-abnormal behavior of "Ed J". For the time being, I will interact with the Inline team via Github, in hopes this issue can be resolved and all parties can continue working on Inline in peace.

Thanks,
~ Will

@mohawk2
Copy link
Collaborator

mohawk2 commented Sep 14, 2015

I asked Mr Braswell to try to have a quick look into why the latest issue he is complaining about happened. This is the response.

@wbraswell
Copy link
Contributor Author

False.
"Ed J" made a sarcastic comment implying I was lazy because I asked for help with the double-build bug.

@wbraswell
Copy link
Contributor Author

Furthermore, I have just been informed "Ed J" has been privately reprimanded on multiple occasions by senior members of the Perl community, but has chosen to ignore it. The soft-handed nature of the Perl community does little to prevent this ongoing behavior. I, for one, will no longer tolerate it.

@wbraswell
Copy link
Contributor Author

Yet another 3rd-party appraisal of the long-term anti-social behavior:

"...the guy has serious problems. Confirmed."

http://irclog.perlgeek.de/perl11/2015-09-14

@mohawk2
Copy link
Collaborator

mohawk2 commented Sep 14, 2015

The guy who claimed I have "serious problems" said your ticket (this one) is silly. Want to have a think about that?

@shadowcat-mst
Copy link

@mohawk2

That's because reini's convinced nobody ever actions problems like this.

The PDL community found you a disruptive influence.

Your recent work on MakeMaker has introduced more bugs than features and you refuse to take responsibility for the problems, instead blaming the criticism on other people's attitudes rather than the shoddiness of your work.

You've nearly been removed from Inline development at least once already for your behaviour.

Want to have a think about that ?

@wbraswell
Copy link
Contributor Author

@daoswald @ingydotnet
I hereby officially request that some sanction be applied to indicate the Inline project does not consider such behavior acceptable.

@mohawk2
Copy link
Collaborator

mohawk2 commented Sep 15, 2015

@shadowcat-mst
Copy link

Please let's not drag sri's personal vendetta against me into this issue; his completely ignoring the mojo code of conduct has caused enough damage to the mojo project's reputation and community without you making it worse. Let us do damage control in peace please, this is completely non-relevant to this issue, which is specifically about your behaviour, hence Will quoting only the comment of Reini's that was about your behaviour. Bringing unrelated drama into this issue is disingenuous at best, and actively harmful to other sub-communities of the perl world at worst.

@wbraswell
Copy link
Contributor Author

As stated by @shadowcat-mst , this Github issue is related solely to misconduct by "Ed J", other concerns should be discussed elsewhere.

@daoswald
Copy link
Owner

This issue tracker is strictly for use in reporting and tracking technical issues with the Inline::CPP code base. Social issues are beyond the scope of this project. As the owner of this repo I reserve the right to remove contributors for any reason, and to close issues for any reason, including for not being relevant to the technical, code-related charter of the issue tracker. I am especially sensitive to having my time intruded upon by disputes and attacks. The only social policy for the Inline::CPP repository is that it is not a social repository. Code contributions and bug reports are welcome. I am closing this issue and locking it from further discussion. If this repository or project no longer serve an individual's needs, forking is always an option.

Repository owner locked and limited conversation to collaborators Sep 15, 2015
@daoswald
Copy link
Owner

The official collaborator list for Inline::CPP now consists of daoswald and ingydotnet. Others are welcome and encouraged to continue to participate on technical issues through Issues and Pull Requests.

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

No branches or pull requests

4 participants