Important Announcement: All NGINX mailman mailing lists are retiring on September 30

[Jeffrey Walton]

On Thu, Sep 25, 2025 at 10:51 AM Sergey Budnevich <sb at nginx.com> wrote:
>
> All NGINX mailman mailing lists are retiring on September 30, as the NGINX
> development process has moved to GitHub. The mailing lists archives will remain
> accessible for historical reference at https://mailman.nginx.org
>
> You can find our GitHub repo here: https://github.com/nginx/nginx
>
> If you have questions about using NGINX or need technical help, visit
> the NGINX Community Forum at https://community.nginx.org. You can also find
> announcements, latest content, and our event schedule on the forum.
> The forum aims to provide an engaging environment to interact with our
> community.
>
> To file bugs, please create a GitHub issue.
> Subscribe to GitHub for release announcements.
>
> To submit a security alert, please report a vulnerability within the nginx GitHub
> repository, or directly to the F5 Security Incident Response Team at F5SIRT at f5.com.
>
> Thank you for being a part of the NGINX community. We appreciate your participation
> in the mailing lists over the years, and look forward to seeing you on GitHub and
> the NGINX Community Forum in the future.

I agree with Paul <paul at stormy.ca>.  Trying to use GitHub Issues as a
mailing list is an absolute disaster.  It is the wrong tool for the
job.  There are no threaded discussions per se.  What we will get is a
flood of GutHub Notifications, including a lot of unwanted junk for
just about every minute action taken.  Many of the notifications will
be automatically classified as spam by email services, like GMail.  So
we will have to combine email messages from Inbox+Spam to try to
follow a "thread."  And a "thread" in GitHub is actually the
conversation for an issue, code review, etc.

I endure it with WebAuthn and a few other important projects which I
try to stay at the bleeding edge.  Please do not make me endure it for
Nginx.

And for completeness, GitHub is fine for issue tracking.

Jeff