mirror of
https://github.com/semver/semver.git
synced 2026-07-11 05:12:48 -05:00
[GH-ISSUE #574] Please make my ban permanent, I won't be returning anyway. #6409
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/semver#6409
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jwdonahue on GitHub (Jun 11, 2020).
Original GitHub issue: https://github.com/semver/semver/issues/574
I wish you all the best, but I think you are too PC for my tastes.
@FichteFoll commented on GitHub (Jun 11, 2020):
What happened here? I have been following the repository's issues on and off for years, but I need more context.
@jjlharrison commented on GitHub (Jun 11, 2020):
See #571
@FichteFoll commented on GitHub (Jun 11, 2020):
Thank you for the reference. I opt to refrain from commenting on the situation otherwise.
@alexandrtovmach commented on GitHub (Jun 11, 2020):
@jwdonahue You made a lot of contributions to this project, perhaps even more than anybody, please, reconsider. I feel like it's my fault and I'm really sorry and sad to see you go. Guy with your experience would really help to move this project forward and I wish that this situation would never happen, and we'd just move on and focused on making open source better.
@jwdonahue commented on GitHub (Jun 13, 2020):
@alexandrtovmach, it's not your fault (you should easily figure out how to contact me directly). Please don't let any of this dampen your zeal for the project. You're doing a good job and the project needs you. I'll be focusing on what comes after SemVer 2.0.0.
I've been refraining from criticizing the current maintainers, since they took over. @steveklabnik has contributed more effort than most over the past year, but the rest of them seem to be more willing to let the project stagnate, than the previous two maintainers. I fully understand their motivations, but I don't think they've acknowledged the level of frustration that many in our community have felt over the past six or seven years or so.
I certainly never anticipated the COC being applied the way it has recently, when I pushed to have it committed to the repo (I think somebody warned me about this actually). While I think the maintainers should not hesitate to step in when a community member is being harassed by someone unnecessarily, I think the maintainers should have thicker skins. They volunteered to run this project, and they can do with it as they see fit, so I have nothing more to contribute as long they think indirect's actions w.r.t. @runeimp have been reasonable.
As a young colleague once told me, a decade ago, "sometimes you have to have poke the bear".
@Saklad5 commented on GitHub (Jul 21, 2020):
I feel like this “issue” should be closed.
@ljharb commented on GitHub (May 3, 2022):
@jwdonahue has your position changed?
@jwdonahue commented on GitHub (May 3, 2022):
Actually, they never suspended or banned me.