3 ms·

This isn't about one individual. Offensive, sexist, bigoted communication is standard in the industry. There are mini-Torvalds (and mini-ESRs and mini-DHHs) eve

This isn't about one individual. Offensive, sexist, bigoted communication is standard in the industry. There are mini-Torvalds (and mini-ESRs and mini-DHHs) everywhere who think making derogatory comments about women or otherwise being gratuitously rude is how you prove your worth/"manliness" and a good way to run a project. Bad behaviour filters down, especially when people on HN or slashdot applaud it. >Where are all of these people with patches that they have been holding on to for feel of the wrath of Torvalds, and why haven't they banded together and just ignored him? On my hard drive and a million other people like me. Not for the linux kernel in my case, but other open source projects that I don't post my fixes to because it's probable that I'll just get flamed and it isn't worth the stress. If you don't realise how endemic this problem is then I can only presume you don't know any programers who aren't part of the 'boys club'. Torvalds can get away with it because linux is huge, but there are hundreds of other projects that struggle through lack of contributions. Next time some software you use crashes or hits some kind of bug, consider that you are probably not the first person to experience it and somebody somewhere probably already fixed it but didn't upload the patch because they didn't want to get abused.

jlgreco 14y ago
No, Torvalds doesn't get away with it because Linux is huge. In a world where Linux is huge and people didn't value his input, then he wouldn't get away with it. The open source ejects people with bad attitudes who are not worth the trouble, just look at glibc and Drepper's reign of terror. If there are really millions of developers sitting on patches because they don't want to deal with mini-Torvalds, then you really should start a movement.
- anon1385 14y ago
  It seems like you still don't believe me that people keep patches to themselves because the open source community is so unpleasant to deal with. We had several huge threads about this the last time some alpha jock devs got called out for being assholes. Here are some examples: https://news.ycombinator.com/item?id=5112713 https://news.ycombinator.com/item?id=5112713 https://news.ycombinator.com/item?id=5112665 https://news.ycombinator.com/item?id=5112665 https://news.ycombinator.com/item?id=5112513 https://news.ycombinator.com/item?id=5112513 https://news.ycombinator.com/item?id=5112763 https://news.ycombinator.com/item?id=5112763
  - jlgreco 14y ago
    Oh, I believe it happens, I just don't believe that it is as pervasive as you suggest. If it were millions sitting on good patches for no reason other than a few people in the "in crowd" being caustic, then the developer-power represented by that group would rival the developer power of the big meanie "in group". Seriously, if that is actually the case, organize. Here is my perspective though: for the past week I have been sitting on a few commits for git that I would get flamed for if I aired them publicly. Why am I so sure I would get flamed? Because if I am honest with myself, it is because the change is shit. The change is not backwards compatible, has only hypothetical use-cases, and has questionable support in the UI. Until I resolve those things I know it would be flamed (or worse, and more likely, ignored). Now, I'm not sitting on it because I know it would be flamed, I am sitting on it because I know it is shit. If I fix those things, and I don't conduct myself like an asshole when my baby gets curtly shot down, I am fairly confident that I won't be verbally abused. If I am, who gives a shit? I suspect most people sitting on patches for fear of being flamed, if they are honest with themselves, are so sure that they will be flamed because they understand why they would be. Are there a few who have good changes that are irrationally afraid of being flamed? Yes, I am certain of it. Are there some projects currently headed by people who flame good patches? Absolutely, glibc a few years ago was such a project... but Linux is not one of those projects today.
    - networked 14y ago
      >Seriously, if that is actually the case, organize. Perhaps this is the case but people who are naturally timid online are also less likely to organize?
    - rachelbythebay 14y ago
      It happens in the corporate workplace, too. http://rachelbythebay.com/w/2012/10/14/2gb/ http://rachelbythebay.com/w/2012/10/14/2gb/ I found a problem in production, figured out what was going on, wrote a workaround, mailed out a patch, and ... they hated it. I didn't want to fight forever. So, I took my ball and went home, so to speak. Months later, a different, nicer, person came to me and asked if I still had it. Fortunately for him, I had kept a copy of the change separate from our SCM in my home directory. I handed it over, he merged it, and that was the end of that problem.

jlgreco 14y ago

No, Torvalds doesn't get away with it because Linux is huge. In a world where Linux is huge and people didn't value his input, then he wouldn't get away with it. The open source ejects people with bad attitudes who are not worth the trouble, just look at glibc and Drepper's reign of terror. If there are really millions of developers sitting on patches because they don't want to deal with mini-Torvalds, then you really should start a movement.

anon1385 14y ago
It seems like you still don't believe me that people keep patches to themselves because the open source community is so unpleasant to deal with. We had several huge threads about this the last time some alpha jock devs got called out for being assholes. Here are some examples: https://news.ycombinator.com/item?id=5112713 https://news.ycombinator.com/item?id=5112713 https://news.ycombinator.com/item?id=5112665 https://news.ycombinator.com/item?id=5112665 https://news.ycombinator.com/item?id=5112513 https://news.ycombinator.com/item?id=5112513 https://news.ycombinator.com/item?id=5112763 https://news.ycombinator.com/item?id=5112763
- jlgreco 14y ago
  Oh, I believe it happens, I just don't believe that it is as pervasive as you suggest. If it were millions sitting on good patches for no reason other than a few people in the "in crowd" being caustic, then the developer-power represented by that group would rival the developer power of the big meanie "in group". Seriously, if that is actually the case, organize. Here is my perspective though: for the past week I have been sitting on a few commits for git that I would get flamed for if I aired them publicly. Why am I so sure I would get flamed? Because if I am honest with myself, it is because the change is shit. The change is not backwards compatible, has only hypothetical use-cases, and has questionable support in the UI. Until I resolve those things I know it would be flamed (or worse, and more likely, ignored). Now, I'm not sitting on it because I know it would be flamed, I am sitting on it because I know it is shit. If I fix those things, and I don't conduct myself like an asshole when my baby gets curtly shot down, I am fairly confident that I won't be verbally abused. If I am, who gives a shit? I suspect most people sitting on patches for fear of being flamed, if they are honest with themselves, are so sure that they will be flamed because they understand why they would be. Are there a few who have good changes that are irrationally afraid of being flamed? Yes, I am certain of it. Are there some projects currently headed by people who flame good patches? Absolutely, glibc a few years ago was such a project... but Linux is not one of those projects today.
  - networked 14y ago
    >Seriously, if that is actually the case, organize. Perhaps this is the case but people who are naturally timid online are also less likely to organize?
  - rachelbythebay 14y ago
    It happens in the corporate workplace, too. http://rachelbythebay.com/w/2012/10/14/2gb/ http://rachelbythebay.com/w/2012/10/14/2gb/ I found a problem in production, figured out what was going on, wrote a workaround, mailed out a patch, and ... they hated it. I didn't want to fight forever. So, I took my ball and went home, so to speak. Months later, a different, nicer, person came to me and asked if I still had it. Fortunately for him, I had kept a copy of the change separate from our SCM in my home directory. I handed it over, he merged it, and that was the end of that problem.