public inbox for gentoo-project@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-project@lists.gentoo.org
Cc: Joonas Niilola <juippis@gentoo.org>
Subject: Re: [gentoo-project] RFC: GLEP-76 copyright update, established pseudonyms and recruitment
Date: Sat, 29 Jul 2023 13:03:25 +0100	[thread overview]
Message-ID: <87ila23oqb.fsf@gentoo.org> (raw)
In-Reply-To: <uzg3fi3br@gentoo.org>


Ulrich Mueller <ulm@gentoo.org> writes:

> [[PGP Signed Part:Undecided]]
>>>>>> On Fri, 28 Jul 2023, Joonas Niilola wrote:
>
>> another GLEP-76 copyright related topic. To my knowledge not using a
>> real name was never a blocker from becoming a Gentoo developer, but with
>> the previous version of GLEP-76 it did prevent from committing to any
>> infra-hosted platform which then again made the developer status a bit
>> useless. Now with the relaxed GLEP it's possible to commit using
>> established pseudonyms. Therefore I'm asking what does the broader
>> community feel about recruiting individuals using pseudonyms?
>
>> I'm just gauging community feedback whether this should be made into
>> official policy, one way or another. What points are there for, and against?
>
> While GLEP 76 allows other contributors to use pseudonyms, it is not a
> contradiction if we hold developers to a higher standard.
>
> Apart from committing to our repositories, developers also can vote
> for project leads and for the council. Although we normally assume good
> faith, we should at least have the theoretical possibility to verify
> that a voter is a natural person (and that there are no votes by
> multiple pseudonyms of the same person).

Thanks - I'd wanted to make that first point, and the second is
a good one.

I also feel it could hurt our reputation if we allowed pseudonyms
from developers. It doesn't come across as professional as real
names.

There's also the question of whether the standard for psuedonyms
would be at least higher for developers - would we require them
to be e.g. polite? I recently rejected a PR because the S-o-b
line was from a particularly rude name. I asked about about this
in #gentoo-dev and some ComRel members said it definitely seemed
fine to reject it, but I don't think we have a formal rule on it
either.

It matters less if we allow a S-o-b from a somewhat juvenile
pseudonym for contributors rather than full developers with
commit access in their own right.

Maybe framing it differently: I pretty much only see downsides
to allowing it and I'm not sure it's worth us spending the effort
on.

Further, perhaps could revisit it a while after the original GLEP 76
change from April if someone is really so-inclined, but I'm
not sure my mind is likely to change.

thanks,
sam


  reply	other threads:[~2023-07-29 12:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 13:50 [gentoo-project] RFC: GLEP-76 copyright update, established pseudonyms and recruitment Joonas Niilola
2023-07-29  7:28 ` Ulrich Mueller
2023-07-29 12:03   ` Sam James [this message]
2023-07-29 11:55 ` Michael Orlitzky
2023-07-31  4:54   ` Haelwenn (lanodan) Monnier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ila23oqb.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gentoo-project@lists.gentoo.org \
    --cc=juippis@gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox