| 10 Dec 2023 |
 raitobezarius | Original discussion: https://matrix.to/#/!CJXQiUGqNPcFonEdME:nixos.org/$hBVZb-GTvVO0m3OYkZs49AZkNtwt6EU-d36yad9AD3g?via=nixos.org&via=matrix.org&via=in.tum.de
Continuation of https://matrix.to/#/!CJXQiUGqNPcFonEdME:nixos.org/$lrWwDhdMexWOE6r0EUDDInCZnQseWdc5bZ-IssiEBGI?via=nixos.org&via=matrix.org&via=in.tum.de
| 20:54:43 |
|  joepie91 🏳️🌈 joined the room. | 20:55:25 |
| raitobezarius | joepie91 🏳️🌈: so to answer to | 20:56:25 |
| raitobezarius |
I find it difficult to build a full mental picture in an ad-hoc conversation like this, and aside from it not really being on-topic for this room, it seems like trying to discuss this in such an ad-hoc manner here is not going to be a good thing for the energy levels of anyone involved. this is why I suggested clarifying it fully in an RFC that describes the full rationale - it gives the space and time to evaluate the rationale, and address specific points in a system that's more conducive to this sort of discussion
| 20:56:26 |
| raitobezarius | I will not do an RFC over this because I have spent a lot of cycles on all of that already and I believe that an RFC would make more sense as a part of a generalized problem around what is the mutual understanding of what does that mean to be a maintainer in nixpkgs | 20:56:55 |
| raitobezarius | Like, expectations, etc. | 20:56:58 |
| raitobezarius | Nonetheless, I don't honestly believe it will make go away the fundamental problem you are hinting at on the heavy reliance on GitHub as a contribution platform | 20:57:23 |
| raitobezarius | There's no RFC on that because it was performed before the RFC process | 20:57:32 |
| raitobezarius | And everyone has kinda their interpretation of the things | 20:57:39 |
| raitobezarius | To make it short, here's mine, we are stuck with GitHub, people tried to go on Codeberg and we made it crash, GitHub server is not performant enough for our own usecases, alternatives like Gerrit are probably too user-unfriendly and would create other sorts of problems, because of that and how unclear the timeline of the existence of a high performance Git server with user friendly stuff, is. I prefer to declare that I want to prioritize the comfort of everyone dealing daily with nixpkgs in GitHub and heavily depending on them does not exclude backupping everything, this is what I have urged colleagues to do like in https://discourse.nixos.org/t/data-dump-of-all-nixpkgs-pull-requests/34457 and what I wish we would continue to do by mirroring the issues, PRs, comments, users, etc. in another silo to preserve our history and make export / migration easy in the potential future we can ditch GitHub. | 21:00:01 |
| raitobezarius | Now, if it's impossible to record the GitHub handle information of someone inside the maintainer-list.nix because of control concerns over the data stored in the visible part of the Git repository (the git objects part being invisible and containing information about the handle of that someone) and the reason invoked for that is GDPR and what not and if, we, as a community cannot come to a conclusion on this, which seems to me, a trivial question in the context (but I do understand why someone can be opposed to it). I will spare myself the mixed and complicated feelings I have regarding this whole situation and will move on to build stuff and ignore folks that didn't record enough data like OfBorg does. Whether this will creates further issues is left to the future who will tell us if it works in practice or not. | 21:02:46 |
|  Artturin joined the room. | 21:03:39 |
 infinisil | I don't feel great discussing this here because not everybody can write messages here.. | 21:04:34 |
| raitobezarius | Right... | 21:04:42 |
| raitobezarius | I forgot about that after writing all those messages | 21:04:49 |
| raitobezarius | Searching for my rooms I found https://matrix.to/#/#platform-governance:nixos.org | 21:05:44 |
| raitobezarius | Moving on to https://matrix.to/#/!VyoUhyWvlhSpFWWxHL:matrix.org/$cg7CQdQhNw8kD7PG26TgZ4Prop8p78CkoixR5BuhAn0?via=nixos.org&via=matrix.org&via=hufschmitt.net | 21:06:41 |
| raitobezarius | Apologies for the noise here | 21:06:45 |
 hexchen | In reply to @raitobezarius:matrix.org
Apologies for the noise here don’t worry, it’s all good. | 21:07:01 |
| hexchen | important topic with an unclear forum, not exactly a far stretch to talk about it in here | 21:07:27 |
 fricklerhandwerk | Could be a task for the all-teams meeting preparation to collect stances on the problem and then in the meeting draft a joint statement | 22:14:50 |
| 12 Dec 2023 |
|  cdepillabout joined the room. | 04:04:04 |
| 16 Dec 2023 |
|  a-kenji joined the room. | 13:24:03 |
| 20 Dec 2023 |
 @theophane:hufschmitt.net | In reply to @theophane:hufschmitt.net
Let's plan for another gathering right now: https://lettucemeet.com/l/oel7O . Since Christmas is coming, it'll be hard to do it before next year, so I've scheduled that for the week of Jan 8 Friendly ping on the above, please fill in your availability before going on vacations :) | 16:52:52 |
| 23 Dec 2023 |
| raitobezarius changed their display name from raitobezarius to raitobezarius (DECT 2128). | 22:22:45 |
| 25 Dec 2023 |
|  @julienmalka:matrix.org changed their display name from Julien to Julien - DECT 4575. | 20:03:40 |
| 27 Dec 2023 |
|  @gdesforges:matrix.org left the room. | 11:24:10 |
|  flokli changed their display name from flokli to flokli (DECT TVIX). | 12:48:17 |
|  Mic92 changed their display name from Mic92 to Mic92 (DECT: 7934). | 14:31:11 |
| 29 Dec 2023 |
 ronef | Hey! It's almost happy 2024 <3 | 18:04:00 |
