Hacker News Reader

Comment by Rjevski | Hacker News Reader

I agree with this. I can deal with Trac (although I’d still prefer GitHub) but mailing lists are a big no-no for me.

The funny thing is that I read this post yesterday and thought about contributing to Django... and they lost me when I saw “mailing list” somewhere in there.

View on HN

..and what's wrong with mailing lists? Too complicated? A need to have discussion of the patch in question?

it's very easy to write an email and there are some benefits to it. I.e, you don't need an account on a proprietary (Microsoft owned) system.

It’s just a bad user experience.

If Microsoft is an issue there are self-hosted options available like GitLab.

If you know of something which is easy to set up, easy to administer, easy to use and provides better handling of multi-way threaded discussion, I'd be interested to hear about it.

(I know Python is experimenting with a forum-based solution, but I worry about the burden of both yet another account to create and site to check, and finding people to maintain and moderate it)

1. Lots of self-hostable solutions are available. 2. Unfortunately for mailing lists, those self-hostable solutions very often make it way easier to plow through conversations. 3. Out of sheer curiosity - have you ever had an actual e-mail conversation with multiple persons involved in replying to each other's e-mails? I do it daily and it sucks.

The mailing list is really only used for decision making and proposals. An issue is usually discussed on the issue tracker until some kind of deadlock occurs.

Then once a PR is developed the discussion happens in PR comments.

The mailing list isn’t used for commenting on patches like some other projects.

Reply on news.ycombinator.com