Our great sponsors
-
Joplin
Joplin - the secure note taking and to-do app with synchronisation capabilities for Windows, macOS, Linux, Android and iOS.
-
Home Assistant
:house_with_garden: Open source home automation that puts local control and privacy first.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
Gitea
Git with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
If that strategy works for you then you should continue doing so. However, I noticed that in the read me for your project (https://github.com/laurent22/joplin) you are not explaining that this is how you handle bug reports. Perhaps as a courtesy to users you could add that? Then people like me who think that strategy is bonkers could avoid wasting our time by filing bug reports to your project.
We are probably talking about the same feature. What I meant was this kind of page https://github.com/home-assistant/core/issues/new/choose
A Github issue for OpenZFS I was following for a year was recently closed via stale bot. I just assumed the feature was dead, however on Twitter (yesterday) they announced the feature's author was giving a talk about implementing it, so I guess it's back on!
I personally wish issues weren't auto-closed as it can give the wrong (i.e. feature is dead) impression, however I know popular OSS maintainers get a TON of issue requests and are doing a work of love.
So, thank you OSS maintainers, you the real MVP.
P.S. For those interested, the issue[1] is NVMe performance for OpenZFS[2]
[1] https://github.com/openzfs/zfs/issues/8381
A counterpoint off the top of my head: gitea has close to 1700 issues open, but the project is very much alive and is improving at a fast pace.
https://github.com/go-gitea/gitea/issues