Invest some more of your time into your request. Like said before about context. The less the maintainer has to switch into the context of the problem and try t

Invest some more of your time into your request. Like said before about context. The less the maintainer has to switch into the context of the problem and try to understand what is the underlying problem (which is often the case) the better. Always read into the projects contribution guidelines (if any) and read into the project development structure (tests/CI, style guidelines, architecture, bug report templates). Most of the times there are ways to take load of the maintainers. Take example from other contributions and similar features in the project to 'feel' the projects architecture/design/style and always look at the bigger picture of your proposed change/request. Don't make it about fixing your specific problem but about improving the project in general for everyone. And like said before, you can ask for anything, but should not take an expecting/demanding attitude. After all these people are already saving you tons of time and money.