The patch mentions me by name so I went ahead and added a sign-off and reference to the discussion saying I've signed off on the wording as-is. I tried to say I liked the version I contributed wording for just fine, but during the council meeting other folx had other ideas which seemed to directly contradict Anna Vyalkova's original intent: more inclusive language, with less disparate impact for queer / nonbinary / plural / transgender folx. - kuza On 11/30/22 16:32, John Helmert III wrote: > This was a topic in the last council meeting where many concerns were > raised. Council tabled the topic until after further discussion on > these issues happened on the mailing list. Is anybody going to raise > those issues? > > On Tue, Jul 12, 2022 at 09:59:50PM +0000, Robin H. Johnson wrote: >> (CC to gentoo-project as required by the GLEP itself). >> >> On Tue, Jul 12, 2022 at 05:28:36AM +0500, Anna Vyalkova wrote: >>> This patch uses more friendly language towards potential transgender >>> and plural contributors. >>> >>> No other projects require to use a legal name, e.g. Linux says to use >>> your real name[0]. >>> >>> Government issued documents are really a bad example since in some >>> countries it's really hard to get your name changed there. >> Hi Anna, >> >> There was a very long discussion in #gentoo-council IRC about this >> today, with many sides represented. >> >> I apologize I didn't follow who suggested some of the ideas first, so if >> something was mis-credited, the fault lies with me. >> >> The need is for GLEP76's name requirement to balance copyright protection with >> complexities of jurisdictional naming complexities [4][5]. >> >> The kernel DCO says: >> "using your real name (sorry, no pseudonyms or anonymous contributions.)" >> >> Copyright law itself, at various levels (including US law and WIPO treaty >> [CR001EN]) treaty does permit copyright held by pseudonyms in many cases. >> But Copyright law also makes assumptions that some body, be it publisher or >> government office, holds the "real" identity (which can be discovered by legal >> or other actions), and the publisher holds some liability in this process. >> >> Thus Copyright law tries to impose the need to associate a person with a >> a copyrightable work. >> >> Thus it raises two questions: >> - Is the open source organization that receives a contribution a publisher in >> this case? >> - If the organization is a publisher, does this mean they are required to >> implement some level of Know-Your-Customer (KYC) system? >> >> This is all so messy :-(. Maybe we can approach it from a different angle. >> >> The older version of the GLEP did use the term "real name", and it was >> changed to "legal name" because the advice at the time is that "real >> name" wasn't well-defined. >> https://bugs.gentoo.org/653118 >> https://gitweb.gentoo.org/data/glep.git/commit/glep-0076.rst?id=5713e7e0fbeb37a74743f11c80da2d8bdd87acf2 >> >> I previously proposed amending it further: >> https://archives.gentoo.org/gentoo-project/message/26d68349541e4db54a93edf57d6e7404 >> >> But in further discussion, even my proposal didn't go far enough. >> >> Neither "real name" or "legal name" correctly convey the underlying intent >> here, and both of them have additional unwanted baggage [1][2][3], and >> disproportionately impact some population groups. >> >> Tying this back together: >> The Foundation has *zero* desire to implement a KYC system, or to be the >> holders of any non-public personal information. Esp. The Foundation does >> not want to even have to look at ID documents. So it's not acceptable to >> just have: "send your linkage between pseudonym and name-on-ID to >> trustees". >> >> What's really needed? >> GLEP76 must show that Gentoo (as a legal entity: the current Foundation, or >> future umbrella), has undertaken due diligence in accepting the contribution. >> >> The discussion in #gentoo-council ended up producing a potential text that I'll >> attached as a patch. >> >> I'd like to thank the following for their contributions to the text. >> >> kuzetsa CatSwarm ** significant wording >> Richard Freeman >> John Helmert III >> Ulrich Müller >> Alec Warner >> >> [1] https://en.wikipedia.org/wiki/Battle.net#Privacy_and_Real_ID >> [2] https://en.wikipedia.org/wiki/Facebook_real-name_policy_controversy >> [3] https://en.wikipedia.org/wiki/Nymwars >> [4] Depending where you are, it can range from very easy to almost-impossible to change your name. >> [5] In https://archives.gentoo.org/gentoo-project/message/26d68349541e4db54a93edf57d6e7404, I linked many other examples >> [CR001EN] https://wipolex-res.wipo.int/edocs/lexdocs/laws/en/cr/cr001en.html >> >> -- >> Robin Hugh Johnson >> Gentoo Linux: Dev, Infra Lead, Foundation Treasurer >> E-Mail : robbat2@gentoo.org >> GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 >> GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136 > >> From 77a948ffecf97035a42359be0a0b40ad5059fe2f Mon Sep 17 00:00:00 2001 >> From: "Robin H. Johnson" >> Date: Tue, 12 Jul 2022 14:52:23 -0700 >> Subject: [PATCH] glep-0076: clarify name policy >> >> Signed-off-by: Robin H. Johnson >> --- >> glep-0076.rst | 29 +++++++++++++++++++++++------ >> 1 file changed, 23 insertions(+), 6 deletions(-) >> >> diff --git glep-0076.rst glep-0076.rst >> index 2216483..ce98ac8 100644 >> --- glep-0076.rst >> +++ glep-0076.rst >> @@ -5,12 +5,13 @@ Author: Richard Freeman , >> Alice Ferrazzi , >> Ulrich Müller , >> Robin H. Johnson , >> - Michał Górny >> + Michał Górny , >> + kuzetsa CatSwarm >> Type: Informational >> Status: Active >> -Version: 1.1 >> +Version: 1.2 >> Created: 2013-04-23 >> -Last-Modified: 2022-07-02 >> +Last-Modified: 2022-07-12 >> Post-History: 2018-06-10, 2018-06-19, 2018-08-31, 2018-09-26 >> Content-Type: text/x-rst >> --- >> @@ -136,9 +137,8 @@ the Certificate of Origin by adding :: >> >> Signed-off-by: Name >> >> -to the commit message as a separate line. The sign-off must contain >> -the committer's legal name as a natural person, i.e., the name that >> -would appear in a government issued document. >> +to the commit message as a separate line. The Name used is discussed in >> +the next section. >> >> The following is the current Gentoo Certificate of Origin, revision 1: >> >> @@ -179,6 +179,21 @@ commits with the Linux Kernel DCO 1.1 [#DCO-1.1]_. This shall be >> indicated by adding ``(DCO-1.1)`` at the end of the ``Signed-off-by`` >> line. Using the Gentoo Certificate of Origin is strongly preferred. >> >> +Contributor Name >> +---------------- >> +Contributors must sign off on contributions with a name that can be made >> +public and would pass copyright due diligence. >> + >> +Nothing further is required if the name matches a government issued >> +document of the contributor. >> + >> +If the name does not match any government issued document, it must be a >> +name that can be verified by simple records search, and/or attestable in >> +a written statement, with a witnessed signature as before a notary. >> + >> +For the purposes of this policy, the Gentoo Foundation will not request >> +any verification of the name until such time as required by government >> +action or legal proceedings. >> >> Copyright Attribution >> --------------------- >> @@ -344,6 +359,8 @@ In particular, the authors would like to thank David Abbott, >> Roy Bamford, Kristian Fiskerstrand, Andreas K. Hüttel, Manuel Rüger, >> Matija Šuklje, Matthew Thode, and Alec Warner for their input. >> >> +For revision 1.2, further thanks are extended to kuzetsa CatSwarm, >> +Richard Freeman, John Helmert III, Ulrich Müller and Alec Warner. >> >> References >> ========== >> -- >> 2.35.2 >> > > >