From kde-community Tue Apr 16 08:14:31 2019 From: Boudewijn Rempt Date: Tue, 16 Apr 2019 08:14:31 +0000 To: kde-community Subject: Re: Anonymous contributions Message-Id: <2870034.oQG6cxJYpO () boud-thinkpad-t470p> X-MARC-Message: https://marc.info/?l=kde-community&m=155544736313081 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart2870034.T6tuE24KAt" --nextPart2870034.T6tuE24KAt Content-Type: multipart/alternative; boundary="nextPart15742845.OOtf3Q10qU" Content-Transfer-Encoding: 7Bit This is a multi-part message in MIME format. --nextPart15742845.OOtf3Q10qU Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" There's another, related thing. We've got a "full name" checking git hook which tries to force commits to have "real names". This hook is, of course, broken: no software developer can ever make a check for names that's not brokenm because there _are no rules for names_. This check thinks that a full need needs to have two parts separated by a space: a first name and a surname. This assumption is untrue for instance for many Tamil people. See https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ for an incomplete list of wrong-headed assumptions about names. On donderdag 11 april 2019 19:24:15 CEST Nate Graham wrote: > Hello everyone, > > I've seen the subject of anonymous contributions come up more and more lately as we have a few contributors who are not comfortable providing their real full name. This convention seems rather at odds with the Privacy goal that the KDE community has adopted, and I can think of a few reasons why it could be reasonable for an open-source contributor to not want to use their real name: > - Having been stalked online > - Being a protestor or political dissident who might be targeted by their government > - Career protection due to negative employer attitudes about open-source software > > Being somewhat new here, let me ask the question: what's the historical reason behind why we ask contributors to provide their full names? And do we think it's still necessary going forward, or are there alternative means we can employ to arrive at the same ends? > > > Nate > > -- https://www.krita.org --nextPart15742845.OOtf3Q10qU Content-Transfer-Encoding: 7Bit Content-Type: text/html; charset="us-ascii"

There's another, related thing. We've got a "full name" checking git hook which tries to force commits to have "real names".

This hook is, of course, broken: no software developer can ever make a check for names that's not brokenm because there _are no rules for names_. This check thinks that a full need needs to have two parts separated by a space: a first name and a surname. This assumption is untrue for instance for many Tamil people.

See https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/ for an incomplete list of wrong-headed assumptions about names.

On donderdag 11 april 2019 19:24:15 CEST Nate Graham wrote:

> Hello everyone,

> I've seen the subject of anonymous contributions come up more and more lately as we have a few contributors who are not comfortable providing their real full name. This convention seems rather at odds with the Privacy goal that the KDE community has adopted, and I can think of a few reasons why it could be reasonable for an open-source contributor to not want to use their real name:

> - Having been stalked online

> - Being a protestor or political dissident who might be targeted by their government

> - Career protection due to negative employer attitudes about open-source software

> Being somewhat new here, let me ask the question: what's the historical reason behind why we ask contributors to provide their full names? And do we think it's still necessary going forward, or are there alternative means we can employ to arrive at the same ends?

> Nate

https://www.krita.org

--nextPart15742845.OOtf3Q10qU-- --nextPart2870034.T6tuE24KAt Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part. Content-Transfer-Encoding: 7Bit -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEKKrMccLjzO6E5wd+LciAUOopVHIFAly1jucACgkQLciAUOop VHJJ9xAA3oGUNw4dH74+ep7bftRGRKJ4XffaZDPUzCDme8zp1WNznQ93dHutuGGZ 0m8Dx7NMsnMvosqyQu9ak5i0Z4tOIzlVllq1F76+nmDl0AyULhmLw6HNl1ATZEXv vJPk+MIKSsrGH98N5E/cvcIXRECUXdFOjNBrujcvtlqpzprWaKSlJXLtdbI4ZofR /HKUkICWxJjPOf8NJuTwyG2mqcqLCieOuRp5dnBWsVCM0FWLUYtOXiZuZTkJixVW CWlsLr7zcrGS22FpVjS0wIWtT6mYWuktpT3h4nnvZFsKfomgMVt3y6x3ByaXEqGf g7aFX0zpzcsxmdUNwcgO3vm9lL4Xye9KPTLVreUZXCvBlzByQgMSD9Mdv52uLbn1 JoveghzUzrUNTMsm40xmUJ0dZMYb66b6hc9QzEKquCPP1XGHb21aVP4AmdsILkb8 wT9o97TihDucZNQugopIVEtqkA6+NGQmOay6G6WBEByV99z4rGpFVJ6hA99fGmB9 HGLYCVvYL8M9JYQ9qKOyiv3hW3E/VfJBhh3meu3wKhpQToNIX+KNlDVqnWwNajgr EjAckIvwyBuEsSfcEd0R0X++zhHjcJOTvTzpaR5tOSUHHCISik+HtD3kH7QoeSQR gMFTisOELKsjMHaDpxE/QLLK9idWUUH9kqiTW2I8Dh9HYEJN+JY= =Wf36 -----END PGP SIGNATURE----- --nextPart2870034.T6tuE24KAt--