@kerckhove_ts@avi_press@domenkozar@fresheyeball I have not invested a lot more than source code contributions into the Haskell ecosystem, but in the Nix community I have spent way way more than I could justify even to myself, as someone who's passionate about the tech
@GitHubStatus Webhook deliveries towards @hercules_ci have stalled since 16:32 UTC, and the GitHub UI can not retrieve details of the latest few deliveries listed.
@GitHubStatus GitHub Webhook delivery to @Hercules_CI has stalled since around 16:32 UTC, and the GitHub Apps UI can not retrieve some of the latest hook details.
Re the open letter critical of Nix's governance (https://t.co/lOndJDFB3j) and the Nix team (I have little insight into controversies elsewhere), I agree with everything @robert_hensing wrote in https://t.co/dvyDqtyTQG
@sridca Unless the moderation team can provide more information, I see no sufficient grounds for a ban.
While I may disagree with some of his political views, I find more concerning the mod's assumption that other assume ill from what they don't understand.
@grhmc I said we're working towards actually sustainable and stable flakes, didn't I?
Apparently strive was the wrong word. I've corrected that.
Either this thread is too long, or you're not asking in good faith. I'll assume the prior and stop conversing.
@grhmc "intends for flakes to be a stable feature". Nothing about time or scope. Now who's weaseling?
I've said all there is to say.
We may agree on more as a team, but I won't be pushing for anything. Would rather get shit done.
@grhmc No critters were harmed during my tweeting.
Flakes needs a bunch of work done before it's stable. Maybe that's what you need to hear?
Re strive: change that to "work toward". Non-native speaker or whatever. Thanks.
@grhmc That is the future we strive for.
Do remember that it is a large set of features that was apparently rushed and then effectively abandoned for various reasons we're not getting into.
Also Nix promises reproducibility for non-experimental features, so this needs time / resources.
@grhmc Unless you mean stabilizing the bugs or throwing reproducibility overboard, we are stabilizing the set of features that flakes consists of and builds on. Expect team based communications soon-ish.
@fmzakari There's the RFC, tomberek will give a talk at #NixCon. Maybe there's a document I'm not thinking of.
It's new and we have yet to figure out how to use a feature like this in practice.
I strongly agree with @samueldr 's views on @nixos_org Flakes.
"Anyone pushing for them to "just" be marked "stable" already does not appreciate the heavy meaning behind marking them stable"
"Nix prides itself in still allowing many years old expressions to evaluate just fine."
@mpeytonjones Unlike import from derivation, this is feasible for hydra and the NixOS cache.
Unfortunately Hydra reimplements certain logic, which has to be updated. Same for @hercules_ci for that matter.