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
void #500
Comments
I think you'd be better served if you did not climb the ladder of inference so quickly. Additionally, the sarcastic tone of your comment may work in gaming circles, but here, in open source, it just makes you sound like a jerk.
I'll remind you that this project is open source, and if the issue is SEVERE as you tagged it, you are welcome to put in a code fix yourself or bounty it. I am putting this in our |
just coded up a fix on my local.. here are the status before and after migration
|
just applied the fix in prod. here are the scripts i used => http://bits.owocki.com/0F0z143O2N3l/Archive%202018-02-28%20at%209.36.02%20AM.zip here is a prod commit 9cf610f |
"Great" is pretty sarcastic in this context. As is the inference that no one cares because there was no response in 24 hours. A better way to word this would be "This seems severe to me. Anyone else?"
I'd love to have you stick around because I think you care a lot and have good ideas . But if you can't take constructive feedback about your tone or agree to abide by the code of conduct, then I agree - it's better that you stop filling issues. I'm on slack if you want to talk more.
Please see the above fix. |
Amen brother! ❤️ alls well that ends well.. thanks for the bug report + the tough convo :) |
No description provided.
The text was updated successfully, but these errors were encountered: