What a horrible name. I literally had to search for "aux nix" to find a Reddit post mentioning the URL. Every other search term combination was giving me results for ps aux.
Thanks for sharing them. Looking at the thread and the author's responses, it doesn't seem like he's open to changing the name. Not sure if that's off to a good start, but we'll see...
Hopefully it is delay due to setting up self-hosted options. I would support it if I didn’t have to use Microsoft GitHub—Nixpkgs is the reason my account hasn’t been deactivated.
These aren’t well established where you can see the post was created in ’18. If they were established, you would seem them in the raw CONTRIBUTING.md. You can see folks having issues with using Discourse as a mailing list since it doesn’t quite work as expected & still requires review by someone with merge access to the primary repository. There is a SourceHut one that actually has some activity & I believe was once listed under the one of the contributing guides, but I can’t remember where it was listed. I doubt many maintainers are properly checking their email too despite listing them on the maintainer.nix file. I would hedge to say that unless the community migrates away, you would see folks complaining the tread above about disliking that there is no pull requests with instead push to the default branch so we would asume all contributions in practices will be expected to be done thru MS GitHub. As it stands going thru the mailing list puts a lot of friction on everyone & wastes time of other maintainers that are expected to then raise a PR on your behalf for review. Say that PR does get opened on your behalf, now you want to follow it since it’s your patch… well too bad since MS GitHub has no way of subscribing to PR threads like it does some aspects of by adding .atom to the end of a URL. As such, if you really want the in-practice option to not be under Microsoft’s domain, you’ll need to remove Microsoft from being the primary forge, relegating it to a mirror or dropping it outright.
Mailing lists are a platform/protocol not really a UI. IRC is trash if all you are using is some terrible web UI, but much better with proper native apps designed around its use cases. Mailing lists are a massive improvement over Discord that so many projects tend to use instead. I'd take a mailing list over a Discord "server" every day.
Yeah, I'm not even talking about the UI, but the UX of mailinglists. The UI is terrible, but I find the UX even worse.
IRC is yet another protocol from another era. Most clients don't parse links and don't provide link previews, don't support code blocks or syntax highlighting, don't support threads, don't support listing the slash commands, don't support images, don't support markdown, no audio, no video, servers can't group chat rooms like matrix, there's no encryption either, ...
It's just shit.
If it were the choice between mailinglist and discord, I wouldn't take either and not communicate altogether. Fuck those both.
Edit: sorry, I really dislike IRC, mailinglists and discord. It's fine if you do like mailinglists and IRC. You do you 👍
It's not really worth it IMO except for lisp and Emacs packages. The biggest issue for me was that nearly every other package I need was seriously out of date.