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

GitHub issues disabled in "broadcast-channel" project

github.com

Post reply on HN
Print view View original

21–25 of 25 posts

Re: GitHub issues disabled in "broadcast-channel" project

#21

Post by Wowfunhappy »

orf wrote: post #11
halostatue wrote: post #9

I’ve had extremely frustrating and contentious discussions with maintainers who choose to put forms in front of their issues in their repositories. It’s bad enough that 1) if I use the project and can’t easily switch from it, I will simply not contribute in any way to the project from that point forward (I’ve filed two issues with Vue.js projects; I will not be filing any more, because they are horribly user-hostile)…

Look at the quality of issues on both large project’s GitHub issues and mailing list (or equivalent). A significant portion of them are crap. Like, worse than crap. Just “help (first line of stack trace)” or even a photo from a phone of a laptop screen showing a windows CLI with some error text on it. I can’t comprehend how people would write these issues. But they do. And it sucks.

> I can’t comprehend how people would write these issues. But they do. And it sucks.

Because writing good bug reports takes work, and people don't like doing work.

Unfortunately, the practices described in the GP frequently just create even more work...

Re: GitHub issues disabled in "broadcast-channel" project

#22

Post by tdy_err »

MrJohz wrote: post #12
halostatue wrote: post #9

I’ve had extremely frustrating and contentious discussions with maintainers who choose to put forms in front of their issues in their repositories. It’s bad enough that 1) if I use the project and can’t easily switch from it, I will simply not contribute in any way to the project from that point forward (I’ve filed two issues with Vue.js projects; I will not be filing any more, because they are horribly user-hostile)…

> forms [...] Vue.js Vuetify? I spent ages putting together an issue there, only for it to be closed almost immediately because it had already been fixed in the v3 alpha branch. That's great, but I can't use the v3 alpha branch because it's still an alpha version that's missing half the features... It's obviously always the maintainer's right to handle their project in the manner that they think works best for them.…

You are mad about an issue you reported being acknowledged and closed hastily as it was already fixed and pending release…

Re: GitHub issues disabled in "broadcast-channel" project

#23

Post by halostatue »

Wowfunhappy wrote: post #21
orf wrote: post #11

Earlier quoted context omitted.

Look at the quality of issues on both large project’s GitHub issues and mailing list (or equivalent). A significant portion of them are crap. Like, worse than crap. Just “help (first line of stack trace)” or even a photo from a phone of a laptop screen showing a windows CLI with some error text on it. I can’t comprehend how people would write these issues. But they do. And it sucks.

> I can’t comprehend how people would write these issues. But they do. And it sucks. Because writing good bug reports takes work, and people don't like doing work. Unfortunately, the practices described in the GP frequently just create even more work...

I’m _happy_ doing work. I’m _also_ happy starting a discussion instead of opening a ticket so we can determine exactly what work would be needed.

But the process should be much more interactive and less WALL than it is.

Re: GitHub issues disabled in "broadcast-channel" project

#24

Post by MrJohz »

tdy_err wrote: post #22
MrJohz wrote: post #12

Earlier quoted context omitted.

> forms [...] Vue.js Vuetify? I spent ages putting together an issue there, only for it to be closed almost immediately because it had already been fixed in the v3 alpha branch. That's great, but I can't use the v3 alpha branch because it's still an alpha version that's missing half the features... It's obviously always the maintainer's right to handle their project in the manner that they think works best for them.…

You are mad about an issue you reported being acknowledged and closed hastily as it was already fixed and pending release…

In context, the pending release is a near-complete rewrite that has been in progress for over a year now, and shows few signs of actually being completed. If it does get released, it will likely be an enormous effort to transition from one version to the other.

Like I said, it is absolutely okay for the project maintainers to maintain their project however they like, and if they don't want to maintain two separate bug fixes, that's fair enough. My point was more about the way their communication makes me feel less comfortable and and to contribute back to the project.

Re: GitHub issues disabled in "broadcast-channel" project

#25

Post by realPubkey »

halostatue wrote: post #9

I’ve had extremely frustrating and contentious discussions with maintainers who choose to put forms in front of their issues in their repositories. It’s bad enough that 1) if I use the project and can’t easily switch from it, I will simply not contribute in any way to the project from that point forward (I’ve filed two issues with Vue.js projects; I will not be filing any more, because they are horribly user-hostile)…

1) If that is your mindset, you will likely not contribute anyway.

2) Noone cares if you use my open source project.

Post reply on HN