| 20 Jun 2023 |
 @piegames:matrix.org | In reply to @infinisil:matrix.org
What we could do is post a comment in https://discourse.nixos.org/c/announcements/rfc-announcements/22 I tried, and nope | 14:00:24 |
 infinisil | Oh wow you cannot even reply to a topic posted there | 14:00:44 |
 hexa | contact ryantm | 14:00:48 |
| infinisil | This should be the job of the steering committee | 14:01:05 |
| @piegames:matrix.org | In reply to @hexa:lossy.network
I had no idea the other category existed Tbf it is now linked in the RFC repo's readme | 14:01:17 |
| @piegames:matrix.org | In reply to @infinisil:matrix.org
This should be the job of the steering committee I'd honestly rather just have permission. Don't burden them with trivial tasks like this | 14:02:08 |
 ryantm | Made it so anyone can post and reply there. | 14:25:40 |
| infinisil | Yay! piegames ^ | 15:03:56 |
 figsoda | In reply to @infinisil:matrix.org
piegames: Well hexa just posted RFC 127 FCP into the Announcements category, not the RFC Announcements one: https://discourse.nixos.org/t/rfc-0127-fcp-nixpkgs-problem-infrastructure/29349 I moved it | 15:14:33 |
| @piegames:matrix.org | In reply to @ryantm:matrix.org
Made it so anyone can post and reply there. Now I'd also have permsisions to reply to https://discourse.nixos.org/t/rfc-0140-fcp-simple-package-paths/28589 instead? Should I do that or a new announcement? | 15:27:11 |
| infinisil | piegames: I'd say a reply to that one sounds good, it will push it to the top in discourse | 15:56:53 |
 Gytis Ivaskevicius | I found what yall been looking for - typed nix 😄 https://www.npmjs.com/package/nijs (tho needs to be converted to ts :D) | 16:07:37 |
| Gytis Ivaskevicius | in all seriousness, I'd love to see someone implement some project using dhall (thus treating nix as compilation target). tho probably not the most productive use of anyones time | 16:09:07 |
| figsoda | nijs (assuming it's pronounced nice) | 16:10:19 |
| Gytis Ivaskevicius | oh, i did not realize that 😄 | 16:11:17 |
| Gytis Ivaskevicius | Just searched github, unfortunatelly it does not seem that anyone did any progress on that front. till this day this is the closest we have:
https://github.com/dhallix/packages
https://github.com/dhallix/nix-derivation/tree/master/examples | 16:19:27 |
 emily | Nickel is more likely to succeed on that front | 18:59:08 |
| emily | Dhall is I think not sufficiently powerful nor ergonomic for nixpkgs | 18:59:35 |
 profpatsch | dhall is also not lazy nor efficient | 20:43:33 |
| 22 Jun 2023 |
|  @archive:matrix.org set their display name to archive.matrix.org/faq. | 05:26:27 |
| 23 Jun 2023 |
 Robert Hensing (roberth) | We should really really write down migration guidelines | 10:23:47 |
| Robert Hensing (roberth) | "manually" holding off migration disasters like this is a fucking drain https://github.com/NixOS/nixpkgs/pull/238331#pullrequestreview-1494880730 | 10:24:34 |
| Robert Hensing (roberth) | apologies for the rude language | 10:24:41 |
 raitobezarius | I would argue that it would be a good occasion to clarify | 10:27:05 |
| raitobezarius | (1) Nixpkgs Internal Changes "release notes" (how to communicate API breakages, etc.) across our users and more | 10:27:20 |
| raitobezarius | (2) Public API vs private API promises (not necessarily a solution, but maybe have an easy way to declare from the get-go "this is private", "this is public") | 10:27:46 |
| raitobezarius | (I don't think versioning at this step makes any sense) | 10:28:04 |
 Alyssa Ross | I don't see how a public vs. private distinction could make sense for Nixpkgs | 10:28:43 |
| Robert Hensing (roberth) | The release notes are often quite useless with stuff like renames that are already handled by the system. Just look at the log. | 10:29:15 |
| Robert Hensing (roberth) | Public: everything that's documented | 10:29:22 |
