| 10 Jan 2025 |
 fpletz | synapse is broken again :/ https://github.com/NixOS/nixpkgs/pull/371815 | 19:30:05 |
| 11 Jan 2025 |
 hexa |
nix-repl> matrix-synapse.meta.maintainers
[
{ ... }
{ ... }
{ ... }
{ ... }
{ ... }
{ ... }
{ ... }
{ ... }
]
| 01:53:46 |
| hexa | verantwortungsdiffusion 101 | 01:54:34 |
| hexa | https://en.wikipedia.org/wiki/Diffusion_of_responsibility | 01:54:42 |
 ma27 | I disagree: I would've taken a look, but first Ibwas on vacation and now in bed with fever🫠| 06:38:57 |
| ma27 | that being said, I'll update my github status next time I'm gone. Or does anybody have a better suggestion to communicate that? | 07:20:33 |
 Sumner Evans | In reply to @hexa:lossy.network
https://en.wikipedia.org/wiki/Diffusion_of_responsibility https://github.com/NixOS/nixpkgs/pull/371815#issuecomment-2578721396 I was concerned about this and didn't feel comfortable making a call to ignore it. | 07:43:56 |
| hexa | So, half the maintainers list last touched the package before more than 3y ago | 17:48:36 |
| hexa | * So, half the maintainers list last touched the package more than 3y ago | 17:52:37 |
| ma27 | I think part of the problem is that the maintainer team thingy is used for far too broad scopes: like, I'm also a dendrite maintainer because of the membership, but I haven't touched this package a single time. Same goes for a bunch of bridges.
This is a thing I observed in a few more teams and I"m not sure anymore if I consider them as reasonable as a while ago. | 18:04:44 |
| Sumner Evans | same, I think we should make the membership per-package | 18:14:13 |
 emily | I think things would be a lot better if we removed inactive maintainers as standard procedure | 18:35:25 |
| emily | and then implemented the RFC to delete packages that stay unmaintained for long enough | 18:35:37 |
| emily | (though for teams that would again mean there's packages nobody cares about but stick around because they have team overlap) | 18:40:07 |
| emily | I think teams make sense for things like platform support or ACME. maybe not so much for "anything to do with Matrix" | 18:40:28 |
|  majes1ic joined the room. | 19:44:20 |
| 12 Jan 2025 |
|  strutztm joined the room. | 00:24:21 |
|  py6m0e7i joined the room. | 19:43:48 |
| 14 Jan 2025 |
|  ⛧-440729 [sophie] (it/its) changed their profile picture. | 18:56:33 |
| 17 Jan 2025 |
|  Frédéric Christ changed their display name from Frédéric Christ (DECT 5915) to Frédéric Christ. | 08:10:29 |
| 20 Jan 2025 |
|  @n0emis:noemis.me left the room. | 11:15:33 |
| 30 Jan 2025 |
|  laurynasp joined the room. | 08:58:19 |
| 2 Feb 2025 |
|  pbsds changed their display name from pbsds to pbsds (FOSDEM). | 16:04:38 |
| 3 Feb 2025 |
| pbsds changed their display name from pbsds (FOSDEM) to pbsds. | 16:25:27 |
| 4 Feb 2025 |
|  Kira joined the room. | 22:21:09 |
| Kira | is anyone using any bridges with encryption? - i recently setup mautrix-whatsapp, but it looks like it's wiping out the encryption key on each restart | 22:28:52 |
| Kira | i'm planning on submitting a fix, but it seems surprising to me if no one else has run into this before | 22:29:35 |
| Kira | oh wait nvm, i'm seeing recommendations from other modules to define the key using environmentFile | 22:31:10 |
| Kira | * oh wait nvm, i'm seeing recommendations from other modules to define the pickel_key using environmentFile | 22:32:03 |
| Kira | i feel like it would be ideal if it automatically copied it over from the existing config though 🤔 | 22:32:18 |
