[charcircuit]

>No need to file some ticket in some random web form with some odd account, email. It's simple, and easy (note, turn off HTML mode for it please.)

Does he not realize how poor of a user experience it is to interact with mailing lists compared to actual bug trackers?

[db48x]

It’s email. How is it a poor experience? You literally just type out a description of your problem into your favorite email program, one you have used thousands of times in your life, put the address of the mailing list in the To field, and send it. Then when someone replies, you get the reply as an email. If that’s a poor user experience for you, then you are using the wrong email program.

[crote]

Where am I supposed to look for already-reported bugs? Where do I send that email? Do I need to CC people, and if so who? How am I supposed to format my email? What information am I required to include? How will I receive updates: will people CC me, or do I have to subscribe to a mailing list - which one of the 291; how do I avoid getting spammed by hundreds of unrelated emails a day? Is my email client even allowed? Am I using a domain which is on some kind of ban list?

Contrast that with the Github or Bugzilla experience: make an account, click "report issue", follow the wizard which asks me to provide all the information I need. I am automatically subscribed, and will receive updates via email.

The whole report-via-email might work for experienced kernel developers, but for a regular user trying to just report a single bug it is way too much of a hassle. If I ever encounter a kernel bug, I would go out of my way to avoid directly reporting it upstream - I'd just file it at my distro and let the maintainer deal with the upstream reporting.

[db48x]

Have you even read the instructions? It answers all of those questions.

> I'd just file it at my distro and let the maintainer deal with the upstream reporting.

They even ask you to do that _in the instructions_ that you haven’t read due to laziness.

[crote]

The instructions are fifteen thousands words, and don't even answer all of those questions. That's worse than no instructions at all, if you ask me.

You'd be hard-pressed to call me "lazy", to be honest. I'm more than happy to dig into the kernel source to determine the cause of such a regression because I actually like doing that kind of thing. I've submitted several single-digit-line patches to large projects to solve exactly this kind of issue.

Spending a Saturday morning trying to figure out a kernel bug is quite enjoyable. Spending a Saturday afternoon trying to figure out how to submit a bug report or patch is not - especially when it is literally a 5-minute process for the vast majority of other software projects. If I have to deal with that much bureaucracy, I'll just keep my patch to myself.

[whensdinner]

it's an unsearchable waterfall of noise, especially if you have to subscribe to multiple. It's such a chaotic and ephemeral way to communicate about things that should be orderly and timeless. I honestly cannot imagine trying to make a case for mailing lists when there are more robust and intuitive options available.

Saying "it's email" means nothing. Just because you announce the name of the tool doesn't make it the right tool.

[db48x]

It’s exactly as chaotic or orderly as the people who are talking to each other, and it would be no different if those same people were using a bug tracker.

And what do you mean by unsearchable? There is a search box right there for anyone to use: https://lore.kernel.org/lkml/ Long time subscribers to the list would do a local search from within their own email program, of course.

[charcircuit]

>It’s email. How is it a poor experience?

How do you search for existence bug reports to see if someone else has hit the issue? How do you subscribe to an issue to know if progress is being made on it? How do you keep track of all of the issues. Why is it the user's job to traige bugs to the right person? Microsoft doesn't reccomend you to find the email of someone on the NTFS team if you find a bug in Window's handling of NTFS.

The part about writing and sending the initial is passable using email, but everything else is terrible.

[gpm]

Even sending the initial email...

This quite tech-savvy (based on the blog post) user

- Was told how to send the email: https://social.kernel.org/notice/AbN55QfONFCPweYq7E

- Read and attempted to comply with those instructions: https://framapiaf.org/@davidrevoy/111336814871081424

- Still ended up being told they did it wrong: https://lore.kernel.org/linux-input/ZULw6AcBaD6z2UZA@debian....

[db48x]

Yea, it looks like they sent their original email to several people, but failed to send it to the list. And they didn’t include any of the specifics in the email (such as kernel versions), instead giving a link back to their blog post. Whether you use email to report a bug or a bug tracker, you _must_ include all relevant information in the report itself. Even if it means repeating yourself, or coping and pasting from your blog.

Edit: Actually, they might have remembered to CC the mailing list, but since they use Proton Mail it probably sent the email encrypted. Don't send encrypted email to mailing lists.

[tux3]

The lists reject HTML emails entirely, and most mail clients don't make the choice between sending plain-text and HTML emails obvious (if they offer it at all)

Ideally, mailing lists would make some effort to keep the plain text content in HTML emails rather than just throw it away. If lynx can render full pages in a console, surely we can degrade HTML down to plain-text without too much effort.

Rejecting people who have not taken the time to setup their email client is tradition, but not very helpful.

[yjftsjthsd-h]

> Rejecting people who have not taken the time to setup their email client is tradition, but not very helpful.

It trades unhelpfulness between the new submitter and the existing list members; HTML emails are blocked for a reason.

[db48x]

You can search the mailing list archive via the web page: https://lore.kernel.org/lkml/

You track the issue by waiting for replies to your email. With a bug tracking system you would wait for replies to the bug report in exactly the same way.

It is not the user’s _job_ to triage bug reports or direct them to the right person, but it is _helpful_ if they can take a minute to peruse the list of kernel modules and find out who the maintainer of the most relevant module is. By adding that person to the CC list of your email, you ensure that they will notice your email right away.

Microsoft has hired hundreds of people to serve as liaison between customers who pay for tech support and the developers who write the code. There’s no way for you to break through that barrier and talk to an NTFS developer directly because Microsoft prefers it that way. The Linux kernel developers cannot afford and do not desire to have that level of bureaucracy in between them and the world.

[charcircuit]

>You can search the mailing list archive via the web page

Not all bugs are sent to a mailing list. From what I can tell it is reccomended that you email the maintainer directly. You can't search for those direct emails. Also I'm not sure that search even is for the place bugs are reported, nor am I confident that it would do a quality search instead of just grepping emails with no ranking.

>You track the issue by waiting for replies to your email.

If you did not make the initial report there isn't a way to get a notification when there is a reply to it.

>There’s no way for you to break through that barrier and talk to an NTFS developer directly

You can just email them. There is no barrier that prevents your email to them or prevent them from talking to you directly.

>The Linux kernel developers cannot afford

The Linux foundation made >240M in revenue last year. They can afford people to triage bugs.

[db48x]

Now you’re just making up things to worry about.

> If you did not make the initial report there isn't a way to get a notification when there is a reply to it.

Sure there is. Send an email and ask for a status update. Be polite about it, and ask for specific information. If you suspect that the work was done and it was committed, ask whose tree it is in. From there you can follow the commit as it is merged into trees owned by people higher and higher in the community, until Linus himself merges it into the next release.

>> There’s no way for you to break through that barrier and talk to an NTFS developer directly

> You can just email them. There is no barrier that prevents your email to them or prevent them from talking to you directly.

If you know who they are, sure. What are you going to do, go on linkedin and hope you get lucky?

> The Linux foundation made >240M in revenue last year. They can afford people to triage bugs.

The Linux Foundation does not run the development of the Linux kernel. They provide support services (like the kernel.org webpage where you can search the mailing lists), legal services, advertising, conferences, etc. The actual development of the kernel is done by volunteers, many of them paid to work on the kernel by their employer.

If you want bug triage or other support services, you should pay for it. Contact Red Hat or whoever and they’ll get you started.

[charcircuit]

>Sure there is. Send an email and ask for a status update.

This sucks compared to something like Github where you can just visit an issue or subscribe to it. People don't want to have to SEND AN EMAIL to see the status of something.

>The Linux Foundation does not run the development of the Linux kernel.

But it does fund some of its development.