This the first time I've seen this view of GitHub, and I'm struggling to figure out what specifically he's referring to.
This the first time I've seen this view of GitHub, and I'm struggling to figure out what specifically he's referring to.
I find a lot of projects because I follow people on github that star or fork really neat projects. I download projects from bitbucket, gitlab, and other self-hosted instances.
I don't know that I've ever contributed a PR back as it's just a more friction-prone process. However, I've opened hundreds of PR's and Issues on github because it's already a part of my daily process.
Thanks again
If I want to, I can signup for yet another site and do git-things with this codebase, but I have to change my daily process to include a one-off change to a new location. There are real costs with this mental flow change.
But thanks for the explanation; I don't feel it myself but it's good to know!
And let's put it this way: the moderation tools at GitHub are a bad joke. Can't even disallow abusive language, so they're 100% ineffective.
Not everything needs to be turned into an embedded discussion forum.
I also object to how the platform encourages low-effort drive-by participation from bots and the like.
You mean "image board user", right?
So yes, they deserved the abuse.
Secondly, the Sneedacity incident was abuse targeted at a fork of the Audacity project, not at the original 'hostile takeover' project itself. The fork was intended to remove said abuse you feel is deserving of more abuse.
Reactions are not really about fostering “social” aspects of code review and issue triage as much as they are to prevent the need for a build up of low effort “+1” style comments. I view them as a community management tool that OSS maintainers would be much worse off without.
Because it is easier to set up?
It doesn't bother me personally, but perhaps I've already been indoctrinated over the past ten years.