| 16 Jun 2023 |
infinisil | This isn't blocking | 16:57:51 |
infinisil | In reply to @piegames:matrix.org And if you let the phone render the desktop version? I might need by yubikey for 2fa, which I didn't bring of course 🤦♂️ | 16:59:17 |
infinisil | Maybe password works too, I'll try | 16:59:32 |
infinisil | It worked yay🎉 | 17:02:09 |
infinisil | Well, with a recovery code, fortunately accessible from my password manager :) | 17:02:31 |
infinisil | In reply to @piegames:matrix.org Also I'm not sure whether we'll have to wait for the steering committee We could ping them to speed things up maybe | 17:03:44 |
@piegames:matrix.org | I'll write the announcement | 17:05:58 |
infinisil | I'll leave it up to you as the de-fact shepherd leader. I think to have to be proper growpotkin ( Alex Ameen ) should accept the RFC again, and the steering committee should do the discourse post again | 17:07:41 |
infinisil | piegames: ^ | 17:08:13 |
@piegames:matrix.org | Oh I miscounted the shepherds, so let's wait for growpotkin ( Alex Ameen ) then | 17:09:34 |
@piegames:matrix.org | About the announcement, https://github.com/NixOS/rfcs has been updated in the meantime, and it now says "The FCP is advertised widely by the shepherds, most importantly in the relevant Discourse announcements category."
(people said it made more sense that way anyways) | 17:10:25 |
@piegames:matrix.org | What it unfortunately doesn't say though, is whether I should make a new post or add a comment to the old one. IMO the latter would be more proper, but not sure. | 17:11:37 |
infinisil | Yeah, but isn't that still the RFC Announcements category which is restricted to the sterring committee? | 17:12:06 |
@piegames:matrix.org | No that also has been changed in the meantime | 17:12:22 |
infinisil | Oh also the steering committee should add change the RCF label | 17:12:37 |
@piegames:matrix.org | Yeah, raitobezarius wanted a bot to do all of this for us for precisely that reason | 17:13:21 |
raitobezarius | someday I will get to it | 17:13:32 |
@piegames:matrix.org | I also see merged RFCs which still have the FCP label, same thing | 17:13:36 |
infinisil | But yeah sounds good then, let's wait for Alex though :) | 17:14:11 |
| 18 Jun 2023 |
| toonn changed their profile picture. | 20:48:34 |
| 19 Jun 2023 |
infinisil | growpotkin ( Alex Ameen ): Ping, we're still waiting for you as a shepherd to officially accept the new changes to RFC 140, please leave an accepting GitHub review | 08:19:52 |
infinisil | * growpotkin ( Alex Ameen ): Ping, we're still waiting for you as a shepherd to officially accept the new changes to RFC 140, please leave an accepting GitHub review if all is good | 08:20:02 |
@ronnypfannschmidt:matrix.org | is anyone aware of work on managing state versions and migration for components (like database server versions, database migration, data store migration)
i have had a number of times now where a upgrade that would ultimately fail at the end broke system state by runnign database migrations that the old versions couldnt use anymore (in particular nextcloud)
| 12:16:42 |
@piegames:matrix.org | Uh, that's an interesting problem. | 12:19:23 |
adisbladis | The usual answer is that you don't | 12:19:49 |
infinisil | Definitely should be fixed at some point, I don't think anybody is actively working on that, but it's something that's been discussed a number of times throughout the years | 12:21:20 |
adisbladis | The module is responsible for doing the right thing re stateVersion, which usually means to pin the version | 12:21:35 |
infinisil | My 2 cents is that each service should have its own stateVersion-like option, so you can migrate each individually. | 12:21:53 |
infinisil | And it should be a sequential number you increase whenever that specific service has a backwards incompatible change that could be migrated | 12:22:14 |
adisbladis | In reply to @infinisil:matrix.org My 2 cents is that each service should have its own stateVersion-like option, so you can migrate each individually. It's hard to create good ux around that | 12:22:28 |