| 17 Jul 2025 |
msgilligan | I'm not sure what assigning yourself on Issue on GitHub means to the Nixpkgs community, but I've started using it to mean "I am interested in contributing to this when I can". Will that confuse or upset anyone? | 18:44:42 |
Infinidoge 🏳️⚧️ | I've always seen it as "$X is working on this", with varying definitions of 'working on' | 18:45:23 |
msgilligan | Does "thinking about it" count? 🤣 | 18:46:06 |
emily | I don't think it gets used that much honestly | 18:47:47 |
emily | so you can probably assign whatever semantics you want | 18:47:52 |
emily | but I would say that it will make someone else less likely to pick it up, because "someone else is already on it" | 18:48:03 |
emily | so if you'd rather invite someone else to take it up and don't plan to get to it any time soon, then maybe skip the assignment | 18:48:15 |
msgilligan | I don't want to discourage anyone! Good point. | 18:50:16 |
msgilligan | I wish there was a way to mark an issue as "I'd like to help". i.e. one step beyond giving it a 👍 | 18:51:27 |
emily | you can just comment :) | 18:52:09 |
msgilligan | I do that. But it would be nice to be able to find all the issues I'm interested in helping on with a search on GitHub. | 18:53:44 |
msgilligan | Like a bookmark or something | 18:54:01 |
Infinidoge 🏳️⚧️ | Subscribe to the issue, then you can bookmark it from notifications | 18:54:28 |
Infinidoge 🏳️⚧️ | It'll also just be in notifications in general | 18:55:23 |
msgilligan | I'm already overwhelmed by notifications haha | 18:55:47 |
msgilligan | ... but the bookmarking from notifications looks like it should work. Thanks for that suggestion! | 19:03:14 |
msgilligan | @emily do you mind if I copy/paste this into Issue #313213? | 19:09:36 |
emily | sure thing | 19:10:49 |
emily | but I'm excited to be proven wrong when I see a build error and go "oh no OpenJDK is really doing something cursed" :) | 19:11:13 |
emily | (I do think it's probably only a day or two's job these days though, now that our macOS support is much better) | 19:11:31 |
msgilligan | "a day or two" probably means a week for me, but the Nix tasks I have on my to do list between now and September should probably help me level up. | 19:14:02 |
emily | diving into the deep end is the best way to learn :P | 19:15:43 |
emily | I'm happy to try and give pointers for anything that comes up but my available proper-review time is pretty limited sadly | 19:16:02 |
msgilligan | That is so true! But it does take time. | 19:16:05 |
emily | yeah for sure I don't want to trivialize the learning curve | 19:16:16 |
emily | I have a vested interest in believing Darwin package porting is fairly easy these days since I was involved in the 24.11 rework 😅 | 19:16:46 |
msgilligan | Vested interests in getting the right thing done are good! | 19:17:10 |
msgilligan | In the short term, I'm going to focus on getting binary JDK 25 (probably Zulu) and GraalVM 25 (probably Oracle) working in Nixpkgs. And also the JDK Dashboard tool, which seems like a cool way for me to learn more about Nix programming since it seems to basically require two things:
- Learning how to pull information about packages out of Nixpkgs
- Learning how to process attribute sets with various functional transforms
| 19:20:28 |
emily | I would recommend Temurin, if you had to pick (because it'll be needed for the source bootstrap later) | 19:21:09 |
emily | though it's still a way aways from being stable right? | 19:21:26 |