Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why users cannot create Issues directly

github.com

Post reply on HN
Print view View original

11–20 of 320 posts

Re: Why users cannot create Issues directly

#11

Post by nine_k »

1123581321 wrote: post #9

I agree with the general philosophy about user submissions. Browsing closed discussions looks a lot like browsing closed issues. So I'm not sure that the policy is successfully turning bug reports into discussions. But it's at least keeping Issues free from noise for contributors. Github could do more to nudge users into approaching Discussions differently. https://github.com/ghostty-org/ghostty/discussions?discussio…

The point is the opposite, AFAICT. Any user complaint starts as a discussion. If an actionable bug report results from it, it goes to the tracker, which serves as list of problems to work on. A lot of discussions do not end this way, even though they may solve a user's issue anyway, e.g. by providing advice and reference.

Definitely discussing things could also happen in the issue tracker, and some tag could be used to mark issues that are ready to work upon. But I suspect that Discussions are better suited for, well, discussions, while the facilities of the issue tracker can then be used by maintainers / contributors.

I find this separation pretty smart.

Re: Why users cannot create Issues directly

#13

Post by sammy2255 »

keyle wrote: post #4

Issues simply don't scale. Using discussions as a filter is a good idea. If you spend more time closing issues than creating them manually from discussions, the math adds up.

Why do you say that? Curl (arguably one of the most used open source software in the world) currently has 5 open issues https://github.com/curl/curl/issues

Re: Why users cannot create Issues directly

#15

Post by hitekker »

Maxious wrote: post #6

For example, memory leak investigation is currently spread across discussions, x/twitter and discord https://x.com/mitchellh/status/2004938171038277708 https://x.com/alxfazio/status/2004841392645050601 https://github.com/ghostty-org/ghostty/discussions/10114 https://github.com/ghostty-org/ghostty/discussions/9962 but has not graduated to issue worthy status

The author says in the first link he only heard it reported twice, which I'm guessing is the latter two links (the two discussions)

Your second link looks like an X user trying to start a flamewar; the rest of the replies are hidden to me.

Re: Why users cannot create Issues directly

#16

Post by paxys »

So they are using Issues as a project board to track and manage ongoing work items, but Projects is built for exactly that. May be better in the long term to move project management to Projects and let people file bugs with as little friction as possible.

Re: Why users cannot create Issues directly

#17

Post by nh2 »

keyle wrote: post #4

Issues simply don't scale. Using discussions as a filter is a good idea. If you spend more time closing issues than creating them manually from discussions, the math adds up.

What is the actual difference?

As a maintainers, if you want to be be able to tell real issues from non-issue discussions, you still gave to read them (triage). That's what's taking time.

I don't see how transforming a discussion into an issue is less effort than the other way around. Both are a click.

Github's issues and discussions seem the same feature to me (almost identical UI with different naming).

The only potential benefit I can see is that discussions have a top-level upvote count.

Re: Why users cannot create Issues directly

#18

Post by mi_lk »

sammy2255 wrote: post #13
keyle wrote: post #4

Issues simply don't scale. Using discussions as a filter is a good idea. If you spend more time closing issues than creating them manually from discussions, the math adds up.

Why do you say that? Curl (arguably one of the most used open source software in the world) currently has 5 open issues https://github.com/curl/curl/issues

Not sure curl is a good example since it’s already very mature and boring (in a good way)

Re: Why users cannot create Issues directly

#20

Post by mi_lk »

quantummagic wrote: post #8
Maxious wrote: post #6

For example, memory leak investigation is currently spread across discussions, x/twitter and discord https://x.com/mitchellh/status/2004938171038277708 https://x.com/alxfazio/status/2004841392645050601 https://github.com/ghostty-org/ghostty/discussions/10114 https://github.com/ghostty-org/ghostty/discussions/9962 but has not graduated to issue worthy status

That's a shame to hear. I had to give up on Ghostty because of its memory leak issue. Granted, it was on an 8GB system, but that should be enough to run a terminal without memory exhaustion a few times a week. Foot has been rock solid, even though it lacks some of Ghostty's niceties.

I’m sure they would appreciate a report as it doesn’t seem that it can be reproduced yet
Post reply on HN