Core maintenance
Maintainer time, testing, CI, domains, and documentation sites.
Open collaboration
Updated September 30, 2026
A public record of how contributions are recognized, reviewed, and returned to the mini-program ecosystem. The fund receives 25% of net donations without a designated project; confirmed project-specific donations are handled separately.
Explore sponsorshipTo support another open-source project, add “Donate to XXX project” to your donation note. You can also message me privately afterwards with the project name.
After I confirm the details, donations for a named project are handled separately for that purpose. Donations without a designated project follow the published default allocation.

Scan to add me, or save the original image and scan it from your photos in the app.

Scan to add me, or save the original image and scan it from your photos in the app.
For confirmed donations without a designated project, the net amount after payment fees is allocated 60% to core maintenance, 25% to the contributors fund, and 15% to upstream and adjacent open source. Confirmed project-specific donations are handled separately and excluded from this default split.
Maintainer time, testing, CI, domains, and documentation sites.
Quarterly allocation for verified contributions, public tasks, and targeted bounties.
Support upstream and adjacent open-source projects in the mini-program ecosystem.
Code, documentation, tests, issue reproductions, and community support are recorded publicly.
Maintainers update the record after merging or confirming a contribution and retain traceable repository links.
| Points | Contribution | Rule |
|---|---|---|
| 5 | Code contributions | A merged, verifiable fix or feature. |
| 3 | Documentation and tests | Additional documentation, tests, or reproducible examples. |
| 1 | Community support | Help reproduce issues, answer usage questions, or organize feedback. |
Contributions must be verifiable in a public repository or public discussion.