| 10 Jan 2022 |
 m1cr0man | What you mean just me making PRs for like a year isn't suffice? 😆 | 20:19:10 |
 Winter (she/her) | heh | 20:19:18 |
 hexa | I think I reviewed most of them | 20:19:40 |
| m1cr0man | true. fwiw, I approved 153942 already, we just need a merger | 20:19:57 |
| Winter (she/her) | yeah that’s what I meant by taking a look at it, wouldn’t of asked if he didn’t approve it
but again, i really do apologize for being like this >.< | 20:20:59 |
| Winter (she/her) | it was not my intention at all to come off as pushy or demanding or anything like that, as I fear I may be coming off as | 20:22:32 |
| m1cr0man | Nah don't worry Winter, hexa's just honest like that 😜 | 20:28:27 |
| m1cr0man | (also, I'd hate to tell you how long it usually takes me to get a PR merged 😬 ) | 20:29:02 |
| hexa |
leading to errors that could be fixed with a simple ownership change.
| 20:29:46 |
| hexa | I have a distaste for the whole premise of daemons not being okay with acme:acme | 20:30:12 |
| m1cr0man | Yeah, same. There was that whole thing about smtpd + postgres, in my last PR I merged a manual update to cover them explicitly | 20:30:42 |
| Winter (she/her) | In reply to @m1cr0man:m1cr0man.com
(also, I'd hate to tell you how long it usually takes me to get a PR merged 😬 ) I really wish there was some way to improve the process | 20:35:01 |
| Winter (she/her) | In terms of time | 20:35:07 |
| m1cr0man | It'd be nice if there was some automation to it, like if two members of the target team approve it, it gets merged | 20:36:08 |
| Winter (she/her) | Not a bad idea
~~RFC time?~~ | 20:39:20 |
| hexa | In reply to @winterqt:nixos.dev
it was not my intention at all to come off as pushy or demanding or anything like that, as I fear I may be coming off as don't worry about it, I think its just fair to let you know my boundaries in return. does that sound ok? | 20:39:45 |
| hexa | like nixpkgs commiters are few in numbers given the amount of changes we need to review, so it's a mess anyway | 20:40:24 |
| Winter (she/her) | In reply to @hexa:lossy.network
don't worry about it, I think its just fair to let you know my boundaries in return. does that sound ok? that’s completely fine yeah, i can’t even begin to fathom how much work it is | 20:44:56 |
| m1cr0man | In reply to @winterqt:nixos.dev
Not a bad idea
~~RFC time?~~ painful effort noises | 20:46:45 |
| hexa | I think we need to talk about maintainer expectations first | 20:47:17 |
| Winter (she/her) | What maintainers are you talking about specifically? | 20:57:54 |
| Winter (she/her) | Like, module maintainers, nixpkgs commiters? | 20:58:03 |
| hexa | package, module and test maintainers | 21:02:27 |
| hexa | basically committing to something and saying when you can no longer fulfill that committment | 21:02:58 |
| Winter (she/her) | ah | 21:28:11 |
| 20 Jan 2022 |
|  andi- left the room. | 08:30:51 |
| 24 Jan 2022 |
| m1cr0man | Wrt https://github.com/NixOS/nixpkgs/pull/156562 is this a concern? Warning: a test defined in passthru.tests did not pass The passthru test is the acme test. | 20:38:04 |
| hexa | they were built by ofborg | 20:39:18 |
| hexa | https://github.com/NixOS/nixpkgs/runs/4925831593 | 20:39:35 |
| hexa | https://github.com/NixOS/nixpkgs/runs/4925858190 | 20:39:45 |
