Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
1–10 of 23 posts
Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#2https://lists.freebsd.org/pipermail/freebsd-ports/2018-Febru...
Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#3Moreover, there are not that many choices of decent browsers. Mozilla has their problems, Chrome/Chromium is a google project. It even gets worse when you think of how few browser engines there are.
Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#4Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#5Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#6In discussions about having more gender parity in programming, I sometimes hear people ask what benefits, specifically, it would provide to the projects themselves. Here's one possible example: if we had a more equitable gender ratio in open-source, we might have have fewer dick-waving contests like that thread. I don't even know what it's about, and I don't care: all the involved participants are just peacocking Int…
That's obvious.
Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#7In discussions about having more gender parity in programming, I sometimes hear people ask what benefits, specifically, it would provide to the projects themselves. Here's one possible example: if we had a more equitable gender ratio in open-source, we might have have fewer dick-waving contests like that thread. I don't even know what it's about, and I don't care: all the involved participants are just peacocking Int…
Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#8It's now also reviewed for removal from FreeBSD: https://lists.freebsd.org/pipermail/freebsd-ports/2018-Febru...
Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#9In discussions about having more gender parity in programming, I sometimes hear people ask what benefits, specifically, it would provide to the projects themselves. Here's one possible example: if we had a more equitable gender ratio in open-source, we might have have fewer dick-waving contests like that thread. I don't even know what it's about, and I don't care: all the involved participants are just peacocking Int…
From my experience. Being an asshole is not a gendered trait
Re: Pale Moon Official Branding Violation – Issue #86 – Jasperla/openbsd-wip
#10In discussions about having more gender parity in programming, I sometimes hear people ask what benefits, specifically, it would provide to the projects themselves. Here's one possible example: if we had a more equitable gender ratio in open-source, we might have have fewer dick-waving contests like that thread. I don't even know what it's about, and I don't care: all the involved participants are just peacocking Int…
I'm not sure what gender has to do with that thread From my experience. Being an asshole is not a gendered trait
When considering a sufficiently zoomed-out view of all the different ways to be an asshole, I think you're right. But the particular form of asshole-ishness in this thread– swaggering in and immediately starting with demands ("You will revise your mozconfig..."), responding with passive-aggressive logical handwaving about how the person will never be listened to again ("you are dismissed from all further conversation on this matter...")– is strongly gendered, in my experience, and it's all too common in the open-source world.
The Atwood/Gruber Markdown spat, the Debian/XScreenSaver version warning, and the Bootstrap/JSMin semicolon debacle are all good previous examples of the same dynamic here. In all cases, there were no or very minor actual technical disagreements; all the sound and fury was just men digging in and refusing to give an inch of ground to another person who had very good points, while being as aggressive as possible to guarantee a real resolution couldn't be reached. We could use a lot less of that.