Maintainer Honorarium #356
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Abstract(By ChatGPT)
Explanation
I have been thinking about this for a long time and have looked into practices in both open source projects and academia. The proposal below is a more mature and streamlined version of my original idea: a trust-based honorarium scheme that keeps paperwork to a minimum.
Let me start with the fixed honorarium. This is a common approach, but in many projects it drifts into something salary like, which is not sustainable. As the FPA, I do not believe we can shoulder that kind of ongoing burden. In a few examples I found more workable figures. Taking inspiration from Homebrew’s practice of paying maintainers USD 300 per month, and considering both broad accessibility and the euro to dollar exchange rate, I set the fixed amount at EUR 200. To qualify, I required only a very simple activity condition: at least one interaction within the month. That threshold is intentionally light, and even minimal contribution counts as activity.
I also reviewed how peer review is handled in academia. Token based models did not seem persuasive. By contrast, I saw debates and some implementations, especially in medical journals, around paying roughly USD 50 per hour. Building on that, I added an additional honorarium path for months when maintainers feel they contributed beyond the fixed amount. Here, EUR 40 per hour serves only as an internal reference rate for consistency. No one needs to submit hours; the requester states only the total additional amount.
Everything rests on mutual good faith. A maintainer can receive up to EUR 1,000 in total for a month without any vote; amounts above that go to an FPA vote. I have also left a door open for maintainers from the broader ecosystem of plugins and dependencies. For them, inclusion under the fixed honorarium is subject to an annual FPA vote, and every additional honorarium request, regardless of amount, also goes to a vote. In this way, the core enjoys a smooth, low friction process, while ecosystem participation proceeds with a bit more oversight.