"Open source" is about providing software users with the information they need to maintain and improve the software they run, either for their own purposes, or preferably by contributing improvements for everyone's benefit.

It is definitely not about "devs" having a "job" of defining and providing software for free, especially in a totally voluntary project like Geany where all the major contributors do it unpaid in their own time. They need helpful contribution, not complaints, not blanket statements like "too broken to be useful", no matter what stage of the development cycle the software is in. (In fact they probably need the helpful input even more so in the alpha stages).

There are many resources on the internet on how to make a useful bug report eg first google hit or request for an unimplemented feature.

Of course bug reporters/feature requesters are not forced to be helpful like that, but they get the benefit of more likely and rapid fixes if they help by contributing the fix or improvement, or if unable to do that themselves, by providing the information, as described in those resources, that is needed for someone else to fix/improve the software. That way it is more likely to happen because the contributor doing the change doesn't have to use their own time to try to work out for themselves what the bug is, or the features that are missing are, and exactly how they should work.

@howdev you reported a bug, which we narrowed down to what the fix is, and no doubt @techee will fix that, but I don't understand why you did that if the plugin is not useful as it is, and you are not even willing to list what you think is missing that would make it useful. If you think it will be useful to you when it has more features, then it would help you to get it faster if you helped.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.