Hacker News Reader

Comment by xinayder | Hacker News Reader

> The SourceHut web interface does not show any kind of indication that a message has an attachment. Last time I tried it, I had to download an mbox file and extract the patch from there. This was helped by the fact that I knew what I was searching for, but the experience was not pleasant anyway.

If it doesn't work as they expect, why not submit a PR to fix the issue on srht?

I'm pretty sure all of the 4 points the author listed can be easily fixed either by code or by talking to some veteran sourcehut users and finding the best solution for the issues. The blog post make it seem like the author is just expecting srht to be exactly like GitHub, which it isn't, plus it does seem like they're lazy to try to fix this issues and have decided to jump ship instead.

View on HN

Or maybe he is busy maintaining his own projects and does not have time/ don't want to onboard and contribute to SourceHut ...

Then he does not have a right to complain about SourceHut.

Right, how dare he, complaining about a paid service.

> The blog post make it seem like the author is just expecting srht to be exactly like GitHub

The author complains users don't use the mailing list correctly or at all. That's something the author expects to work the way srht intended, but the users expect it to work like github. And that's pretty much the point of the article.

>If it doesn't work as they expect, why not submit a PR to fix the issue on srht?

Because people have their own things to mind and does not always have time to commit to every oss project they use?

Seriously, "just submit a PR" is the worst comment you always expect to see in a discussion.

Because something is opensource and "easy to fix" are we expected to not talk about it?

No, it's just that srht was built with this in mind. If I were the author I would talk to some srht maintainers or people that have projects in srht to brainstorm solutions for my issues instead of just writing a blog post and jumping ship. The author doesn't mention at any time that they tried to talk to other maintainers about these problems.

The problem is that the general population do not want mailing lists. It is a self-selecting group that actively wants to use these for their projects.

Everything else you mention takes time and especially for projects like this the time is often great because you will hit roadblocks like "you are using the product wrong" when proposing changes/features.

Reply on news.ycombinator.com