6 ms·
So, I read through the list of guidelines, and while I have some minor quibbles with them, overall they seem fine and reasonable. But what happens if someone r
by joshuamorton 8y ago
So, I read through the list of guidelines, and while I have some minor quibbles with them, overall they seem fine and reasonable.
But what happens if someone refuses to be kind? What happens if that person is a major contributor? What would happen if, in some strange alternate reality, Linux was a GNU project, and Linus-of-2012 said he'd really rather not care about all this politeness nonsense, and would prefer to continue on the way he was?
The problem I see with your bees/honey comment is that there is no commitment here from the maintainers and leaders of the project. This is just a more verbose "Be kind to each other", but without any commitment from the leadership of the project to actually maintain a kind, welcoming environment.
A non-committal claim to be kind may be honey, but its on a flytrap, and many people recognize this.
- whatshisface 8y agoHow much damage have Linus's snippy emails really caused, in light of how they have benefited us? I and many other people like reading them because they are fun, so you have to take that in to account. Different people like different things, and that principle extends to writing styles and personalities. Indeed, if you really want to have diversity you should have some emails that I like to read in addition to having emails that you like to read, which by necessity implies that every email thread needs at least a few glib comments. I have heard that Matz and by extension the Ruby community is nice, maybe that project needs to recruit a Linus to fill out their personality lineup.
- JoeAltmaier 8y agoI think that whole issue was, while it may be amusing to watch the drama unfold, that valuable contributors were being disaffected. No, its not about how entertaining the email chain reads. Its about getting work done? And it's disingenuous to describe the vicious attacks as 'snippy' and 'glib'.
- whatshisface 8y agoDifferent people saw those emails in different ways. In fact, some people are invigorated by strong words as opposed to being cowed and driven away by them. I'm not saying that you didn't perceive them as vicious attacks, I'm saying that the spectrum of human behavior includes people who think being harsh is fine, and give and take it freely. You can't just throw out everyone that behaves in a way that makes you uncomfortable, that's just xenophobia sneaking in through the back way. What's really wrong is when someone consciously goes out of their way to target another person's emotions, but that has little to do with the average niceness of their writing (which is mostly set by their natural personality baseline).
- jakelazaroff 8y agoI think you realize that at some point a line has to be drawn, given you called "targeting another person's emotions" wrong; and also that everyone's line is in a slightly different place and what's reasonable to some will be uncomfortable or hurtful to others. Given that, why is it wrong for people to try and influence their community in such a way that it minimizes people's discomfort? Shouldn't every community have the right to self-determine what conduct they're okay with?
- whatshisface 8y agoI've always believed that you should be liberal in what you accept but conservative in what you generate. It's fine to strategize your own behavior to come across well to as many people as possible (for example not eating meat in front of a conscience-driven vegan) but when it comes to other people's behavior you have to be very judicious about the difference between uncomfortable (but natural) signals and malicious actions. In this case, I'm highlighting intent when I say "targeting." I shouldn't become upset when someone that always comes across as abrasive comes across as abrasive to me, but if someone goes out of their way to consciously be more abrasive than usual then that's a signal I should pay attention to. If someone who is usually very meek says something slightly harsh, then I should multiply it by a large factor to get back to their internal mental state (which is what I really care about). Likewise if it's a case where I should take what they say and divide it.
- pjc50 8y agoIt's not about whether you "like" to read them or not, it's about whether the people they're directed at (and the audience) read them and decide to withdraw from the project (or never join it).
- trhway 8y agogood software engineering requires some minimal level of mental strength, and if a one cant take a snippy (in the one's opinion as in my opinion Linus' emails are very reasonable, precise and thorough explanatorial) email i'd question whether that one would be a valuable member at all.
- pjc50 8y agoLike the "you should be retroactively aborted" one?
- trhway 8y agoyep. I think it gets the point - irreconcilable differences in the foundations and applications of intelligence - more efficiently across than the alternative of an attempt at long winded logical based explanation of that irreconcilable difference to somebody who just doesn't understand/share your logical apparatus because of that difference.
- kadendogthing 8y ago>How much damage have Linus's snippy emails really caused Don't downplay how he acted by using words like "snippy." There are contributors who have either left the project or actively avoid directly talking with him. There is a reason why Linus admitted he had a problem. It wasn't productive or useful. https://plus.google.com/+LennartPoetteringTheOneAndOnly/posts/J2TZrTvu7vd https://plus.google.com/+LennartPoetteringTheOneAndOnly/post... >But more importantly, I'd actually put some blame on a certain circle of folks that play a major role in kernel development, and first and foremost Linus Torvalds himself. By many he is a considered a role model, but he is quite a bad one. If he posts words like "[specific folks] ...should be retroactively aborted. Who the f*ck does idiotic things like that? How did they not die as babies, considering that they were likely too stupid to find a tit to suck on?" (google for it), than that's certainly bad. But what I find particularly appalling is the fact that he regularly defends this, and advertises this as an efficient way to run a community. (But it is not just Linus, it's a certain group of people around him who use the exact same style, some of which semi-publically even phantasize about the best ways to, ... well, kill me).
- patrickg_zill 8y agoSystemd, invented by the guy you are quoting, is, however, objectively crap. I am about to start a separate, new service and have wide leeway in how it will run. I am moving away from Linux towards a mix of BSD and Solaris/Illumos. And Systemd played a part in this technical decision.
- scrollaway 8y agoFeels like you might not know the meaning of the word "objectively".
- patrickg_zill 8y agoSystemd breaks fundamental Unix principles. Those principles have been around since the 1990s at the latest. So yes the use of objectively does fit...
- Sir_Substance 8y ago>But what happens if someone refuses to be kind? Then you work as a group of not-socially-incompetent people to find a compromise solution that hits the local maxima of what can be done with the situation, or make a considered decision to move down from the local maxima in the short term to find a higher maxima in the long term. Maybe discuss with that person the possibility of continuing their work but having a small group of other people between them and the general public as an interface layer that handles the less important work. If you think that setting up such a compromise might either be too expensive, might risk burning out the interface people or has some other downside, maybe have a frank discussion with them about the benefits and costs of their contributions to the process. Talking to people always works better than talking at people.
- joshuamorton 8y ago>Maybe discuss with that person the possibility of continuing their work but having a small group of other people between them and the general public as an interface layer that handles the less important work. So you mean you want to unseat me from leading the project I'm in charge of? What kind of punishment is this for violating some silly guidelines? [1] >If you think that setting up such a compromise might either be too expensive, might risk burning out the interface people or has some other downside, maybe have a frank discussion with them about the benefits and costs of their contributions to the process. Wait, but I thought that this was a guideline. Are you saying that there's actually an implicit threat within this guideline that I might be removed from the project against my will? Why wasn't that stated explicitly? How am I, a valued contributor, able to make informed decisions if rules are arbitrary and decided on behind closed doors without any ability for public input, comment, or even knowledge? In case my point isn't obvious here, an explicit CoC has a number of advantages over a document like this one when it comes to actually resolving conflict, instead of trying to prevent it. It makes value judgements, but only because at some point in the conflict resolution process, leadership will be forced to make value judgements. Making those value judgements explicit, and public, is a commitment from project leadership to not favor the in-group over the outgroup either explicitly or implicitly, when resolving conflict. It allows people to cite a prior commitment from the leadership to act in a certain manner. You still must trust the leadership to resolve conflict in the manner they stated they would, but you can verify that their resolution was in-line with the process and commitments they provided. This doesn't mean that a CoC prevents leadership from attempting to mediate conflict when it comes up, and come to mutually agreeable solutions in cases when that is possible. But it does mean that in those rare cases when it is no longer possible to assume good intent that everyone is aware of the values that leadership and the decision-makers opted in to, and can hold them accountable to making decision in line with those values. With this, Stallman hasn't made a commitment. He's written some nice platitudes, but when it comes down to it, how am I supposed to know if (again, hypothetically speaking) I'd had bad interactions with GNU or its members previously, Stallman would really value my experience strongly enough to take action instead of just letting me suffer to maintain the status quo? How can I try to hold him accountable when I don't know his values, and it would be completely possible for him to write off my complaint as simply not assuming good intent on the part of other contributors? I can't. That's the problem. [1]: Note that in this little hypothetical, you're my "boss", so the suggesting to put someone between me and the people I lead can be reasonably interpreted as a demotion or attack on my authority.
- stcredzero 8y agoThis is just a more verbose "Be kind to each other", but without any commitment from the leadership of the project to actually maintain a kind, welcoming environment. "Be kind, generous, and accepting, or there will be consequences!" is just a few steps removed from, "The beatings will continue until morale improves." The conundrum with linux, was that it was organized in a self-contradicting way. It's fine to have a meritocratic leader who is exacting and demanding, even harsh. You just don't mix that up with an ethos of accepting all contributors in public. Instead, there needs to be a public tier which is concerned more with outreach, and only once people are ready for the next level, should they be given access to the level where they have to stand and deliver.
- joshuamorton 8y agoSee my longer comment[1]. At some point, with some hopefully small fraction of members, the maintainer will need to make a call between keeping the member and letting other people suffer, or kicking someone out of the project. Stallman even mentions this: >the appointed maintainer(s) of a GNU package can, if necessary, tell a contributor to go away; but we do not want to need to have recourse to that. in his email, although leaves that out of the guidelines themselves. Why on earth is being forthright about the fact that abuse will lead to exclusion worse than being cagey about that fact? If the end result, you can be kicked out, is the same, why would you prefer that the circumstances be entirely up to each individual maintainer's discretion instead of a somewhat objective (and importantly, public and available!) set of criteria? [1]: https://news.ycombinator.com/item?id=18275994 https://news.ycombinator.com/item?id=18275994
- jf- 8y ago> why would you prefer that the circumstances be entirely up to each individual maintainer's discretion Exactly so that the same judgement isn’t applied everywhere. Different maintainers will end up having different audiences. I see that as acceptable, maybe even preferable.
- joshuamorton 8y ago
- brobdingnagians 8y ago> "the appointed maintainer(s) of a GNU package can, if necessary, tell a contributor to go away; but we do not want to need to have recourse to that."