I love that Tobi is willing to offer up some funds for this feature! Just keep in mind that the OBS team (especially Jim) is ultimately the arbiter of what will make it into the repo.
This is intended to increase the likelihood that a PR will be mergeable and increase the likelihood that the developer will be successfully paid the bounty. The feature should be programmed according to the new spec, and only PRs that follow the spec will be accepted. Once a spec is considered complete, it should be treated as essentially a design document for the feature. An RFC is essentially a draft spec for a feature that people can discuss ahead of time. That concrete set of requirements is defined and ironed out in the RFC process. Thus, the only way I think we as OBS would be comfortable offering a bounty is if we have set concrete requirements for the PR ahead of time. What we don't want to happen is for someone to come along and do a bunch of work on a bounty, submit a PR, and have it denied due to egregious design issues. The most important thing to understand about bounties is that they shouldn't be considered complete until they are merged into the OBS master branch, but the only way that is going to happen is if the pull request (when it happens) is considered mergeable. To expand more on what Fenrir said regarding RFCs: Good to know there are people out there willing to help out with funding them! Setting up an official bounty program for OBS is something I plan to work on over the next couple weeks.
0 kommentar(er)
