Core maintenance
Maintainer time, test machines, CI, domains, and docs sites.
Contributor program
Updated 7 September 2026
This is an open-source thank-you, not a salary, contract, or copyright purchase. Sponsorship is booked quarterly. If the fund is too small, it rolls forward in public.
Back to sponsorshipMaintainer time, test machines, CI, domains, and docs sites.
Quarterly pool plus optional bounties.
Upstream projects in the mini-app ecosystem.
The core maintainer is paid from the 60% bucket and does not take from the 25% contributors fund. Receiving money is not employment or moonlighting, does not buy copyright, and does not create on-call duty. Contributions stay MIT. Recipients handle their own taxes.
Only confirmed open-source sponsorship, net of payment fees, including the ¥20 / ¥200 / ¥1,000 personal tiers and Gold business partnerships. Future Pro, Team, implementation fees, and the 15% template author share stay on the product ledger.
A quarter needs at least 5 points: one production fix with a reproduction or test, or equivalent features, tests, or docs. Typos, formatting, dependency bots, and unmerged PRs do not count. One person may receive at most 40% of the fund in a quarter. The core maintainer does not take from this bucket.
Up to 40% of the quarterly fund may be labeled as bounties for platform matrices, minimal reproductions, or full documentation chapters. Payment goes out within 14 days after merge and a release. Bounties come from the 25% bucket only.
Contributor: at least one eligible merge. Regular: two consecutive eligible quarters, 1.1× weight next quarter, and first pick on bounties. Reviewer: maintainer invite only. None of these are employment.
No automatic pay-per-PR, no monthly salary, no corporate labor contracts through this fund, no mixing in product revenue, and no inflated share promises to look busy.
| 8 | Features | Ships with tests and docs, merged to the default branch. |
|---|---|---|
| 5 | Production fixes / platform support | Includes a reproduction or test across real WeChat, Alipay, or Douyin differences. |
| 3 | Tests, reproductions, CI | Linked to a specific issue and narrows the failure. |
| 2 | Docs and troubleshooting | Not typo-only edits. |
| 1 | Substantive review | Invited reviewers only, and the review has to catch a real problem. |
Varo is independently maintained and is not in this program unless that maintainer opts into the same rules. weapp-sqlite is counted on the same basis once it is stable.