We don’t need to mirror the Nixpkgs git repo, right? We just need a
I have a mild (because it’s only a mailing list, and can’t be that
difficult to get right) preference for not using SourceHut. In my
evaluation, I have found it to not work particularly well (not
unreasonably, given it’s in alpha), but what I’ve found more concerning
is the attitude of the author towards bug reports. For example, here he
tells me that it is my problem that his software doesn’t support the
common practice of posting revisions of a patchset in reply to the
That’s not to say we couldn’t mirror a mailing list to SourceHut –
that’s one of the nice things about mail, and I gather Drew is working
on support for it.
One option: I already host mailing lists for Spectrum (see
https://spectrum-os.org/participating.html#mailing-lists), and am
committed to and funded for doing so for at least the next year. I
would be happy to add an additional list for Nixpkgs. It could be
mirrorred and easily replaced should I suddenly disappear or whatever,
and should SourceHut look more convincing in future it would be easy to
migrate. Available on that server are Mailman, public-inbox (for
archiving and web browsing), and Hyperkitty (a nice modern web UI
suitable for people who don’t want to use mail).
I don’t think we should try to mirror mailing list discussion to
Discourse either – it would end up being ugly on both sides, I think.
It might be better to create a simple web application that would show
proposed changes from both the mailing list and GitHub, that reviewers