If your changes are generally-useful to the userbase, your code is fully tested, and it doesn't break any existing features, I'd just submit a pull-request to g

If your changes are generally-useful to the userbase, your code is fully tested, and it doesn't break any existing features, I'd just submit a pull-request to get the conversation going. You never know, someone on the main team might have had the same idea for the feature long ago, but never mentioned it or had time to implement. As far as new-branch vs master branch, go with whatever precedent the repo has laid out. (Review recent pulls, and any guidance the authors have laid out in the docs). It's a personal preference thing for the authors, there's not really a right or wrong way.