3 ms·
> And if you open an issue or pull request and you're not on the OpenCollective, it's usually immediately closed, by policy. I don't know enough about the resu
by zelphirkalt 4y ago
> And if you open an issue or pull request and you're not on the OpenCollective, it's usually immediately closed, by policy.
I don't know enough about the resulting system, but this sounds quite silly and contra-productive. Issues often hint at important flaws. If the community is not open (Ha!) to outsiders notifying them of important flaws, then that is a recipe for bad software. Some people might go there and start asking for features, instead of describing issues (although even that can be valuable input), but in my experience people are more often reporting bugs or asking how to do something, because it is not well described in the docs, or the docs are not as visible as they should be, or probably many other good reasons. Closing ones door to these valuable inputs can only result in worse software.
- pie_flavor 4y agoClosing the door to people that are drive-by posters who cannot be bothered to fork over three dollars can only result in better inputs. The issue with open source tip jars isn't that they're expensive, it's the psychological barrier in front of giving anything at all. That's the subject of TFA and Fody's model is the only real way to circumvent it. Ninety percent of people who submit issues are people who are invested in continuing to use Fody and so should be patrons, and the remainder of the issues are unlikely to be high on the signal-to-noise ratio.
- zelphirkalt 4y ago> Closing the door to people that are drive-by posters who cannot be bothered to fork over three dollars can only result in better inputs. We are not talking about the same kind of issues or people. Aside from the strawman: People creating an issue with all the detail are already investing time into reporting an aspect of your project. Immediately closing the issues is like giving them a middle finger, for investing their time, trying to help the project. Sometimes, when I have a problem with some tool being buggy, I consider opening an issue, but sometimes I don't do it, because I know it would be time-consuming. However, when I open an issue, I usually try to provide all required information and maybe even an example to reproduce the issue. I invest time to make it easy for the maintainers to see the actual issue. If they closed that issue immediately and wasted my time like that, I would be very careful to ever invest time again into anything those people create.