Hey, First of all I'm not really sure who this bug belongs to. Feel free to assign as you see fit. Just going by the previous precedent (np-hardass) and therefore assigning to council. Also I do wish to keep this bug private so it's not immediately connected to anyone in public, and due to the private nature (I don't want anyone to exploit the system with information in this bug). So every now and then recruiters get approached by people who'd like to join the project but remain anonymous in public. In other words, don't wish to disclose their real names. We have a precedent with np-hardass and that's what I've been going with so far, but recently we've changed / about to change GLEP-76 and I was wondering how that affects the "real name policy" in Gentoo? Is it enough now to stay behind.... uhh "legally identifiable alias" or however it was spelled in the GLEP update? And what about cases where the developer may disclose their name to the developer community, but not public? To say if they're willing to let council know their names, but not use it in LDAP / commits. (np-hardass was denied this btw). Now if the real legal name is still a mandatory, how should recruiters proceed if they suspect someone's using an alias?
I'd say let's wait for the GLEP to reach its final shape, then we'll have a clue what to do. For the record, the original argument from kernel DCO was that since the code is public, then the records also need to be public.
*** Bug 674592 has been marked as a duplicate of this bug. ***
(In reply to Joonas Niilola from comment #0) > Also I do wish to keep this bug private so it's not immediately connected > to anyone in public, and due to the private nature (I don't want anyone to > exploit the system with information in this bug). Do these reasons still apply, or can this bug be made public?
During today's Council meeting, it's been suggested that this bug be first taken to Recruiters. After all, the GLEP's been updated and what seems to remain is recruitment policy. That said, if this needed to go through Council, a mailing list discussion should be held first.
If trustees / council has no comments to the issues raised in #c0, then recruiters can continue as normal. In other words, no change needed for recruitment process.
(In reply to Joonas Niilola from comment #5) > If trustees / council has no comments to the issues raised in #c0, then > recruiters can continue as normal. In other words, no change needed for > recruitment process. Could you please clarify what this means exactly?
(In reply to Joonas Niilola from comment #5) > If trustees / council has no comments to the issues raised in #c0, then > recruiters can continue as normal. In other words, no change needed for > recruitment process. If it was worth asking council about this in the first place (and it was!), then it should be discussed on -project to solicit the opinions of the community at large.
(In reply to Ulrich Müller from comment #6) > (In reply to Joonas Niilola from comment #5) > > If trustees / council has no comments to the issues raised in #c0, then > > recruiters can continue as normal. In other words, no change needed for > > recruitment process. > > Could you please clarify what this means exactly? "if the real legal name is still a mandatory" which I guess is a question for trustees, not really a problem for recruiters if that's allowed. That question has followups though: "people who'd like to join the project but remain anonymous in public. In other words, don't wish to disclose their real names" and repeated with a condition: "what about cases where the developer may disclose their name to the developer community, but not public" To clarify and summarize: Does "Gentoo" now allow recruiting people using an alias, without a) everyone, b) "public" knowing their real legal passport names? B. means it somehow is proven to a developer community or trustees or council, whatever entity decides and needs the information in the end.
(In reply to Joonas Niilola from comment #8) > To clarify and summarize: Does "Gentoo" now allow recruiting people using an > alias, without a) everyone, b) "public" knowing their real legal passport > names? B. means it somehow is proven to a developer community or trustees or > council, whatever entity decides and needs the information in the end. The recent GLEP 76 update allows contributed commits without a real name. This doesn't imply that we now must allow developers without a real name. The latter is a separate policy decision. IMHO it wouldn't be a contradiction if we required higher standards for a person joining as a developer, as compared to an outside contributor.
(In reply to Ulrich Müller from comment #9) > > The recent GLEP 76 update allows contributed commits without a real name. > This doesn't imply that we now must allow developers without a real name. > > The latter is a separate policy decision. IMHO it wouldn't be a > contradiction if we required higher standards for a person joining as a > developer, as compared to an outside contributor. Since recruiters don't have any policy regarding this (to my knowledge) I believe it should be voted by council. There's only "infra-limitation" currently. Question goes: Should recruiters allow anonymous developers to join? -> If "no", what should recruiters do if they suspect someone is using a bogus alias?
My position hasn't changed since https://bugs.gentoo.org/883715#c7. I'd like to see it discussed on the ML.
(In reply to Joonas Niilola from comment #10) > Question goes: > Should recruiters allow anonymous developers to join? "Anonymous" or "pseudonymous"? GLEP 76 doesn't really permit full anonymity, just established pseudonyms.
After the council meeting on 2023-08-13, I'm closing this issue with the motion that was voted on with 6 yes and 1 absence votes: The council does not see the need for admitting anonymous or pseudonymous developers at this stage (bug 883715), but is willing to reconsider the topic should a demonstrable need arise or new arguments be brought forward.
