As a guix user and package maintainer I’m ecstatic.
I’m so proud of the community for rallying around the needs and pain points of everyone and making this decision. This reduces so many pain points for a guix user and will hopefully smooth out the package maintenance process a great deal. Email is simple but trying to do code change communication over it can be very complex and time-laborous.
If you’re curious about functional packaging systems grab guix on your distro and give it a try!
Special shout out to anyone burnt out on Nix lang. Come feel the warm embrace of Scheme’s parentheses. :)
It would have been better to self host forgejo, rather than trusting a cloud git service using forgejo. But to be honest, its TOS, as well as the sourcehut’s TOS which I even like it better, sound way better than GH’s…
As a guix user and package maintainer I’m ecstatic.
I’m so proud of the community for rallying around the needs and pain points of everyone and making this decision. This reduces so many pain points for a guix user and will hopefully smooth out the package maintenance process a great deal. Email is simple but trying to do code change communication over it can be very complex and time-laborous.
If you’re curious about functional packaging systems grab guix on your distro and give it a try!
Special shout out to anyone burnt out on Nix lang. Come feel the warm embrace of Scheme’s parentheses. :)
It would have been better to self host forgejo, rather than trusting a cloud git service using forgejo. But to be honest, its TOS, as well as the sourcehut’s TOS which I even like it better, sound way better than GH’s…