| 13 Mar 2026 |
raitobezarius | But I understand the strategy | 15:27:33 |
Lisanna | a lot of my background is low level C so honestly even just seeing stuff like conn << var is like "WOW that's so nice and convenient" for me a little bit still ^-^ | 15:27:55 |
Lisanna | East coast US near DC, unable to move because of partner's in-person job (research reactor tech!), so unfortunately I'm mostly limited to remote. Doesn't have to be working directly on Nix or Lix, maintaining nix-based infra or build systems would also be killer | 15:30:37 |
raitobezarius | i heard antithesis is hiring if that's your cup of tea | 15:32:45 |
raitobezarius | i can throw in a referral | 15:32:52 |
Lisanna | I'd be happy working at antithesis | 15:33:14 |
Winter | ;-) | 15:33:15 |
Lisanna | they already have a nix supergenius tho so what even are my chances lol | 15:35:04 |
raitobezarius | winter would probably give a more direct referral ig | 15:35:10 |
Winter | We are always strapped for people so the chances aren’t low!
IIRC you already applied in the past, right? (Let’s maybe move to DMs.)
| 15:36:56 |
Winter | and ideally not on Matrix (you know how to reach me) bc i hate this platform too much | 15:38:57 |
@rosssmyth:matrix.org | antithesis looks really cool but I do not want to move to VA | 18:46:07 |
@rosssmyth:matrix.org | or sf | 18:46:54 |
raitobezarius | Ah true they have a strong in person policy | 19:17:13 |
raitobezarius | I forgot that | 19:17:15 |
| 15 Mar 2026 |
| isabel changed their profile picture. | 20:54:47 |
| isabel changed their profile picture. | 20:55:03 |
Lisanna | Tomorrow I think I will go through my merged nix PRs and port any applicable ones to Lix. Nothing too extravagant, just minor things. There are a few unmerged ones that are a bit more interesting, but I'll hold off on them for now in case they end up changing from review feedback. Later this week I'll probably join a Nix team meeting and bug them for reviews. | 23:11:13 |
Lisanna | but feel free to comment on the unmerged ones in case there's anything applicable before I get them accepted and port them to Lix | 23:15:57 |
| 16 Mar 2026 |
| draupnirchanged room power levels. | 10:16:20 |
| draupnirchanged room power levels. | 10:16:31 |
Lisanna | Getting used to gerrit again, I'm working on porting https://github.com/NixOS/nix/pull/15105. That PR has two commits, one for the build hook signals and one for the progress bar shutdown message. Should I open these as different changes? | 13:31:30 |
raitobezarius | Yes, but be aware that Lix codebase is quite different in some areas (notably interruptions wise) from cppNix | 13:56:30 |
| 17 Mar 2026 |
| zoë (she/her) joined the room. | 00:10:50 |
zoë (she/her) | this is probably very dumb but: I'm trying to follow "Getting Started with Gerrit", and since it specifically points out "Now you can just git commit your change. No need to create a separate branch", i committed on main directly, but then the no-commit-on-branch commit hook failed because i tried to commit to main, so... am i missing something? | 03:11:46 |
Lisanna | It's still probably a good idea to separate your changes into their own branches, otherwise you'll have to rebase just to edit changes that happened before you make another, unrelated change | 03:16:34 |
zoë (she/her) | right, that makes sense, i was just a little confused at the docs ^^; | 03:17:23 |
zoë (she/her) | aaaand first CL submitted :D
...it's an 8-bytes diff x) | 03:24:38 |
Lisanna | * | 03:58:07 |
piegames | In reply to @blokyk:matrix.org this is probably very dumb but: I'm trying to follow "Getting Started with Gerrit", and since it specifically points out "Now you can just git commit your change. No need to create a separate branch", i committed on main directly, but then the no-commit-on-branch commit hook failed because i tried to commit to main, so... am i missing something? I think that sentence was about remote branches, but you're right it's confusing | 09:14:57 |