Conversation

Notices

1. Embed this notice
   nina (q66@blahaj.social)'s status on Monday, 17-Jun-2024 21:17:59 JST nina

   i will not contribute to projects that ask for "real name" in patches

   • Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     Haelwenn /элвэн/ :triskell: (lanodan@queer.hacktivis.me)'s status on Monday, 17-Jun-2024 21:19:42 JST Haelwenn /элвэн/ :triskell:

     in reply to
     @q66 Weirdest about those is when they do end up importing pseudonymous patches later on when it got committed by a "real" name user.
   • Embed this notice
     nina (q66@blahaj.social)'s status on Wednesday, 10-Jul-2024 08:12:52 JST nina

     in reply to

     • leo vriska :light2:

     @leo i've had this handle over 20 years, you can be fairly sure it'll outlive my legal name

     Haelwenn /элвэн/ :triskell: likes this.
   • Embed this notice
     leo vriska :light2: (leo@60228.dev)'s status on Wednesday, 10-Jul-2024 08:12:53 JST leo vriska :light2:

     in reply to

     @q66 basically they want to ensure that it's possible to get in touch with the author of a commit even if their email dies

   • Embed this notice
     leo vriska :light2: (leo@60228.dev)'s status on Wednesday, 10-Jul-2024 08:12:54 JST leo vriska :light2:

     in reply to

     @q66 they require a "real name" for legal reasons but the Linux Foundation clarified that the intended meaning is distinct from "legal name" and things like well-established usernames would qualify

   • Embed this notice
     nina (q66@blahaj.social)'s status on Wednesday, 10-Jul-2024 08:12:55 JST nina

     in reply to

     • Tris

     @triskelion apparently kernel dropped the policy but also lots of kernel-adjacent stuff still seems to enforce it so uh, yeah guess not

   • Embed this notice
     Tris (triskelion@floss.social)'s status on Wednesday, 10-Jul-2024 08:12:56 JST Tris

     in reply to

     @q66 So not to Linux kernel, right? :P