you mean this one https://github.com/SerenityOS/serenity/pull/6814 three years ago? yeah that was not the nicest reaction. Bridgading in that old thread and the thread about the accepted and merged PR was not nicest reaction as well.
Also the merged PR was way more of substance and didn’t just replace he with they in that one line whereas there were several occasion where that issue occured in the same file. If the original one would have been merged, the documentation file would be inconsistent.
As someone who hasn’t bothered to read any of the detail about this whole mess until just now, the comments from three years ago were all relatively civil, even if the response by the developer was dismissive. That this was corrected within 6 weeks and people are still talking about it is pretty impressive, though. Looks like people are trying to make enemies, not converts.
Teaching changing minds, influencing… it needs plenty of repeating and sleeping on things. To be fair, when all else fails applying pressure has its place as well. Nevertheless small victories are still victories.
The ability of Ladybird’s team to face scrutiny of all kinds is important for them to eventually gain traction in the browser market. But I’m still hopeful, and we need more options.
Oh didn’t you hear? It’s fine now because a PR was finally accepted well after being called out and
stepping downstepping aside from the project/s
Imagine that talking with people about issues and not just shouting and brigading them actually works. Who would have known.
Like the first time it came up, politely with a complete PR, and it was just shut down?
you mean this one https://github.com/SerenityOS/serenity/pull/6814 three years ago? yeah that was not the nicest reaction. Bridgading in that old thread and the thread about the accepted and merged PR was not nicest reaction as well.
Also the merged PR was way more of substance and didn’t just replace
hewiththeyin that one line whereas there were several occasion where that issue occured in the same file. If the original one would have been merged, the documentation file would be inconsistent.Yes, that one.
As someone who hasn’t bothered to read any of the detail about this whole mess until just now, the comments from three years ago were all relatively civil, even if the response by the developer was dismissive. That this was corrected within 6 weeks and people are still talking about it is pretty impressive, though. Looks like people are trying to make enemies, not converts.
Yeah and it’s fecking sad, no even embarrassing.
Teaching changing minds, influencing… it needs plenty of repeating and sleeping on things. To be fair, when all else fails applying pressure has its place as well. Nevertheless small victories are still victories.
The ability of Ladybird’s team to face scrutiny of all kinds is important for them to eventually gain traction in the browser market. But I’m still hopeful, and we need more options.