[halostatue]

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);

2) if I don’t use the project, I will _never_ use the project and generally question why people are using the project (remarkjs).

Having an issue template is fine. Closing issues that don’t follow the template is (mostly) fine. Taking me to an entirely _different_ website to fill in your form and yelling throughout the whole thing that your bug will be closed if you don’t follow the steps of the time warp _exactly_…is user hostile. I get it that there are entitled users of projects. But by disabling issues or putting a form in front of issue reporting…you have told me that you don’t actually _want_ users, so I’m happy to oblige.

I was looking for an excuse to try Svelte anyway.

[orf]

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.

[Wowfunhappy]

> 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...

[halostatue]

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.

[realPubkey]

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

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

[MrJohz]

> 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. My dependence on their project is to a certain extent a burden on them, and I'm grateful to people who are willing to put time into maintaining projects that I (and moreover the company I work for) regularly use.

However, I do think the open source community works much better in terms of reciprocity. When I can create an issue and get some feedback there, there's a good chance I'll also try and fix the problem myself, because to me that seems like the responsible thing to do as someone who depends on open source code. If I have the feeling that the maintainers just don't care about my feedback, then I'm just going to be more loathe to contribute.

And specifically when it comes to Vuetify, much like yourself, I'm now in the situation where I'm looking to remove it from projects I'd previously been using it in, because when future problems come up, I think it'll be more of a maintenance burden than just solving the problem myself.

[tdy_err]

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

[MrJohz]

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.