<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Ben,</p>
<p>I was interpreting a real name as a name that requires a first
and last name (legally accurate or otherwise) compared to a
pseudonym that is usually just a single name. Because the mailing
list thread said there was no naming policy but the git hook
requires a first and last name, that was the conflict I was
bringing up.</p>
<p>However, I would make it more clear on a document of some kind
that single name pseudonyms are permitted upon request.</p>
<p>Regards,</p>
<p>Ben<br>
</p>
<div class="moz-cite-prefix">On 2/11/23 20:03, Ben Cooksley wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+XidOGix-DnWRNdGN_pKhtG6RVzMe6tzjpHx1ARnOj3kUzuYg@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div dir="ltr">On Thu, Nov 2, 2023 at 7:55 AM Ben Bonacci <<a
href="mailto:ben@benbonacci.com" moz-do-not-send="true"
class="moz-txt-link-freetext">ben@benbonacci.com</a>>
wrote:<br>
</div>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi
Josh,<br>
</blockquote>
<div><br>
</div>
<div>Hi Ben,</div>
<div> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
According to the mailing list archives from 2020 [1], "there
is no real <br>
name policy on this mailing list (or any other KDE
infrastructure.)" <br>
However, according to the community wiki page last updated
in October <br>
2022 [2], there is a git hook for authorship that states "A
name is <br>
considered valid if it is a full name – it should not be a
username or <br>
the first name of the person."<br>
</blockquote>
<div><br>
</div>
<div>Those two statements don't conflict at all with each
other, so not sure what the issue is here.</div>
<div><br>
</div>
<div>In that mailing list thread, "real name" should be
interpreted as the "legal name" that governments use when
issuing identifying documents such as a driver's license,
passport, etc.</div>
<div><br>
</div>
<div>Full name (or as I have been using in this thread "proper
name") simply means a name that has a first name and a
family name (or surname as it is called in other places).</div>
<div>A pseudonym can certainly still be a full name, however
it would not be a real name.</div>
<div> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Perhaps a formal vote or the equivalent policy for handling
these kinds <br>
of questions should be held. Then, whatever the final
verdict would be, <br>
can be documented in the Code of Conduct or a similar
document to make <br>
the policy clear.<br>
</blockquote>
<div><br>
</div>
<div>That is not required, this area is relatively well
settled.</div>
<div> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Regards,<br>
<br>
Ben<br>
</blockquote>
<div><br>
</div>
<div>Regards,</div>
<div>Ben</div>
<div> </div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
<br>
[1] <a
href="https://mail.kde.org/pipermail/kdepim-users/2020-June/013299.html"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://mail.kde.org/pipermail/kdepim-users/2020-June/013299.html</a><br>
<br>
[2] <a
href="https://community.kde.org/Infrastructure/Git/Hooks#Authorship_metadata"
rel="noreferrer" target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://community.kde.org/Infrastructure/Git/Hooks#Authorship_metadata</a><br>
<br>
On 1/11/23 12:40, Josh wrote:<br>
> Hello KDE community,<br>
><br>
> I'm not sure if this is the best ML to post it in, but
anyway - what is our<br>
> current stance on a real name policy? We were recently
asked again in a Matrix<br>
> channel and the consensus seems to be "we don't know?"
From what I can tell,<br>
> you *must* use your real name or else our git commit
hooks will reject any<br>
> pushes. From some precursory web searches, people say
to work around this by<br>
> putting spaces in the git username field. So it's
allowed, but unofficially? The<br>
> git commit hook doesn't mention this work around I
think.<br>
><br>
> I have gotten more than zero complaints/questions about
this policy, and I've<br>
> only been here for a year. When tracking down something
"official", all I've<br>
> found is a few mentions on the Community wiki. If we
dismissed the policy,<br>
> then we should update those commit hooks. These
contributors are starting to<br>
> make non-trivial commits to projects I care about, so
it would really great if<br>
> we can accommodate them.<br>
><br>
> Whatever decision we make, can we document this
somewhere so I can link people<br>
> to it? Preferably on <a href="http://kde.org"
rel="noreferrer" target="_blank" moz-do-not-send="true">kde.org</a>,
where it it's immutable and official looking like<br>
> our code of conduct.<br>
><br>
> (If the reason is "it's because of relicensing", I have
a hard time tracking<br>
> down people even when I know their full names. I would
prefer better reasons<br>
> than that, if possible 😆)<br>
><br>
> Thanks,<br>
> Josh<br>
><br>
><br>
-- <br>
Ben Bonacci<br>
<a href="https://benbonacci.com" rel="noreferrer"
target="_blank" moz-do-not-send="true"
class="moz-txt-link-freetext">https://benbonacci.com</a><br>
C0A9 E67F 8CDC B1A1 0860 1807 E018 065C C7DF 3976<br>
<br>
Quote of the Day: "Dream big and dare to fail." - Norman
Vaughan<br>
<br>
</blockquote>
</div>
</div>
</blockquote>
<pre class="moz-signature" cols="72">--
Ben Bonacci
<a class="moz-txt-link-freetext" href="https://benbonacci.com">https://benbonacci.com</a>
C0A9 E67F 8CDC B1A1 0860 1807 E018 065C C7DF 3976
Quote of the Day: "Pain is inevitable. Suffering is optional." - Haruki Murakami</pre>
</body>
</html>