From mboxrd@z Thu Jan 1 00:00:00 1970 From: HiPhish Subject: Re: Promoting the GNU Kind Communication Guidelines? Date: Sun, 28 Oct 2018 12:58:51 +0100 Message-ID: <11169507.O9o76ZdvQC@aleksandar-ixtreme-m5740> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43494) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gGjie-00023r-Fj for guix-devel@gnu.org; Sun, 28 Oct 2018 07:59:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gGjia-0008D9-8I for guix-devel@gnu.org; Sun, 28 Oct 2018 07:59:00 -0400 Received: from mout01.posteo.de ([185.67.36.65]:50246) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gGjiZ-0008CH-Oe for guix-devel@gnu.org; Sun, 28 Oct 2018 07:58:56 -0400 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id A8F7D20E89 for ; Sun, 28 Oct 2018 12:58:52 +0100 (CET) Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 42jbqH6yPBz6tmL for ; Sun, 28 Oct 2018 12:58:51 +0100 (CET) List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org I have had two packages merged, which I guess that makes me technically a contributor, so here is my takes on the issue. In my opinion Codes of Conduct (or CoCs in short) are one of the worst thin= gs that have happened in recent years to Free and Open Source projects (hold t= hat though, I will address it soon enough), and the Contributor Covenant (CC in short) is the worst offender. I will explain shortly why this is, but please allow me to elaborate first. There is no problem of harassment in FLOSS, there is a problem of socially awkward nerds in FLOSS. Harassment presupposes malice, i.e. that the offend= ing person is intentionally being abusive. If you have never said anything that made you want to vanish into the ground the moment it came out of your mouth you are not human. Some people will slip up more often than others, and let= 's face it: the people who are more likely to slip up are also more often the= =20 ones who are good at programming. Why is it this way? I don't know, I'm not a psychologist or anthropologist, I just need to know that this is the way=20 things are. Now here is the important part: for an offensive act to be committed it tak= es two sides, the offender and the offended. Part of social competence is know= ing not to slip up, but part of it is also knowing to just let it slide when someone else slips up. Again, I'm not talking just about online discourse, = but social interaction in general. When someone says something stupid just igno= re that person, and if it keeps happening try to correct them in a friendly manner. This is how we grow as humans. This leads me into why the CC is a harmful CoC. The CC presupposes malice by default, more than half of its content is focused on punitive measures, not= on helping each other. In contrast, the GNU Kind Communications Guidelines (GK= CG in short) explicitly promotes a cooperative two-sided perspective: > Please assume other participants are posting in good faith, even if you > disagree with what they say. When people present code or text as their own > work, please accept it as their work. Please do not criticize people for > wrongs that you only speculate they may have done; stick to what they > actually say and actually do. > > Please do not take a harsh tone towards other participants, and especially > don't make personal attacks against them. Go out of your way to show that= =20 you > are criticizing a statement, not a person. > > Please recognize that criticism of your statements is not a personal atta= ck > on you. If you feel that someone has attacked you, or offended your perso= nal > dignity, please don't =E2=80=9Chit back=E2=80=9D with another personal at= tack. That tends to > start a vicious circle of escalating verbal aggression. A private respons= e, > politely stating your feelings as feelings, and asking for peace, may calm > things down. Write it, set it aside for hours or a day, revise it to remo= ve > the anger, and only then send it. There is nothing like this in the CC, but there is this: > Instances of abusive, harassing, or otherwise unacceptable behavior may be > reported by contacting the project team at [INSERT EMAIL ADDRESS]. All > complaints will be reviewed and investigated and will result in a response > that is deemed necessary and appropriate to the circumstances. The project > team is obligated to maintain confidentiality with regard to the reporter= of > an incident. Further details of specific enforcement policies may be post= ed > separately. > > Project maintainers who do not follow or enforce the Code of Conduct in g= ood > faith may face temporary or permanent repercussions as determined by other > members of the project=E2=80=99s leadership. The CC is claiming to foster "an open and welcoming environment" while at t= he same time holding a gun to every maintainer's head. The accused is not even allowed to know what the accusation is about (confidentiality clause), so h= ow are they supposed to know what they did was wrong? There is no clause that allows the accused to defend their position, only punishment is defined. Th= is applies even to the maintainer, so if they maintainer wants to protect an unjustly accused person, the maintainer will be on the chopping block. To m= ake matters worse, the CC never defines what constitutes offensive behaviour. = =20 Take a look at the following list: > * The use of sexualized language or imagery and unwelcome sexual attentio= n=20 or > advances > * Trolling, insulting/derogatory comments, and personal or political atta= cks > * Public or private harassment > * Publishing others=E2=80=99 private information, such as a physical or e= lectronic > address, without explicit permission > * Other conduct which could reasonably be considered inappropriate in a > professional setting The fourth point is clear, but what exactly constitutes any of the remaining four? Is "Wow, thank you so much, I could kiss you!" considered "unwelcome sexual attention" or just an exaggerated expression of joy? Is overhearing people talking about "dongles" and "forking repos" considered unwanted sexu= al attention? If I wanted I could consider it the former and pull the trigger metaphorically. I am asking because this is not a hypothetical question,=20 people have been loosing their jobs over these issues for real. Do you think this makes for a healthy community? The GKCG does not even attempt to define what qualifies as unacceptable, because unless you pay a lawyer to write a tens of pages long document whic= h=20 no one will read, you will never have a sufficient definition. Truly money well spent. As for the last point, if you really want to remove anything that would be inappropriate in a professional setting, you have to go all out. No "I could kiss you", but also no informalities, no emotion, and the project maintainer will have to sign all his mails not with "Ludo'" or "Ludovic", but as "Mr Court=C3=A8s", RMS becomes "Dr. Stallman", Guix becomes "The GNU Guix proje= ct", no Hacker culture jokes and quips the manual, and so on. If this what you want? As a closing thought, I wish to address my opening statement that CoCs are = one of the worst things to happen in recent years to FLOSS. The argument with=20 which CoCs are "sold" to FLOSS projects is that there is problem of harassment in= =20 the community which prevents people from contributing. And yet I have to see any project where contributions have improved as a result of adopting a CoC, wh= ere people who were previously harassed became contributors. In fact, I have ye= t=20 to see any actual harassment, and not just socially awkward nerds being social= ly awkward. On the other hand, I have seen enough examples of existing long-ti= me contributors being expelled from projects and being harassed, especially by proponents of the CC. The CC's own author is one of the worst offenders of = the CC's own terms, going after people's private social media accounts and quote-mining them to demand their expulsion or even extort money. Yet none = of those people end up contributing to the projects they disrupt. Is the damage you invite really worth it? Guix is too important of a project, functional package management is the on= ly proper solution to package management. I believe there are interest groups = of proprietary software companies who would rather want projects like Flatpak succeed, which are more applicable to proprietary software. Please don't let them hold a gun to every contributor's head by inviting trouble into the project. You have people in this very thread who are afraid of contributing, and even I was considering leaving my packages just sitting on my local hard drive rather than submitting them upstream, but as the GKCG says: "Please assume other participants are posting in good faith, even if you disagree w= ith what they say." PS: I agree that there is no point in having both the CC and the GKCG at th= e=20 same time