Pull request bounties

[kc64]

I have a lot of respect for the MicroPython core team and the work they’ve done for the embedded Python community and certainly don't want to be presumptuous. I wanted to ask about project norms: would it be appropriate to offer a bounty for work on a specific PR or feature? I haven’t seen much discussion of this, so I thought it would be best to ask first.

[peterhinch]

A bounty might solve the problem of recruiting a developer to work on the feature and submit a PR. It won't guarantee that the maintainers will accept the PR. For example if the feature is judged to be highly specialised, the PR might be rejected.

You may want to raise an RFC to gauge maintainer interest at the outset. Alternatively you may want to consider the implications of maintaining your own fork in the event that the PR is not accepted.

[Josverl]

Also it is possible to sponsor a feature, though I'm not sure if the exact process or scope.
If you look at the recent release note you will find a mention of the sponsors.

[kc64]

Thank you for the thoughtful response.

I think the features I have in mind would be considered generally-applicable and valuable to the project. My experience with two PRs shows that the dev team is willing to consider them and also offered guidance on how to improve them. I think it is more a matter of resource levelling. If there are more important features, less important ones are triaged down the schedule timeline. I get it. You have to set priorities.

I don't want to be gauche, but the purpose of the bounty, as I'm thinking of it, is like an expedite fee.