#FOSS etiquette question
I run into this situation pretty often: I encounter a bug in a FOSS project that has a codebase I don't know well, but I find a workaround that solves my particular use case. I'd like to be helpful and report the bug, but getting it fixed won't really benefit me and I'm not willing to submit a PR.
So here's the question: is there a concise way to report the bug as a FYI for the maintainer, while making it clear that I'm not asking them to do anything for my benefit?
@codesections just submit an issue/bug with your reproduction steps and how you worked around it. If the maintainers think it needs priority and a fix they’ll fix it or ask you if you can. If they don’t at least there’s a crumb for other users to follow when they run into the same problem.
