> I usually open a PR with at least a proof of concept implementation without prior discussion. I find that trying to discus a new feature without a concrete th

> I usually open a PR with at least a proof of concept implementation without prior discussion. I find that trying to discus a new feature without a concrete thing to look at often goes nowhere or even goes completely unanswered. You should do both: get a soft ok that they'll consider the change ("If I put up a PR/POC will you be able to take a look? Will you be able to approve? If not you then who would I reach out to?") and then put up the PR so there are concrete things to discuss. This saves you time because why put together even a POC if they're never gonna approve it.