-
-
Couldn't load subscription status.
- Fork 235
Axmol Contribution Reward Guide
Revision: 1.0.0
Axmol is an open-source engine driven by community contributions.
To recognize and encourage contributors, we have established a transparent reward system funded by OpenCollective.
Note: Available funds are net of platform hosting fees (~10%) and payment processing fees (depending on the sponsor’s payment method). Additional transaction fees may also apply when funds are transferred.
- Value-Oriented: Rewards are based on the impact of contributions, not lines of code.
- Transparency: All funds and expenses are publicly visible on OpenCollective.
- Sustainability: Reward standards are designed to balance fairness with long-term project health.
- Inclusiveness: Both code and non-code contributions are eligible.
| Contribution Type | Example(s) | Points |
|---|---|---|
| Major Feature / Core Refactor | New rendering pipeline, new platform support | 5 pts |
| Medium Feature / Important Fix | Performance optimization, crash fix | 3 pts |
| Documentation / Tutorials | Guides, API docs, sample code | 2 pts |
| Minor Fix / Improvement | Typo fix, small bug fix, CI config tweak | 1 pt |
- Each quarter, 5–10% of sponsorship funds will be allocated to a Community Reward Pool for miscellaneous PR contributions.
- Contributors share the pool proportionally based on points (points are not automatically calculated, but evaluated by @halx99).
- Example:
- Reward Pool = $1,000
- Alice = 10 pts, Bob = 5 pts, Carol = 5 pts → Total = 20 pts
- Alice receives $500, Bob $250, Carol $250
- Go to the Axmol OpenCollective page.
- Click Submit Expense.
- Fill in the details:
-
Title: e.g.
PR #123 – Physics Engine Optimization -
Category:
Contribution Reward - Amount: Leave blank (system will calculate based on points), or suggest an amount based on your contribution.
- Description: Briefly describe your contribution.
-
Title: e.g.
- Submit and wait for review (usually within 2 weeks, depending on OpenCollective processing time).
- All applications are reviewed by the Axmol project lead @halx99.
- Contributions that meet the guidelines will be approved.
- If clarification is needed, maintainers may request additional details.
- Recommendation: Contact @halx99 in advance to confirm the reward amount before submitting.
- For now, please send all inquiries to axmol-fund@simdsoft.com.
- Limit: One application per contributor per month.
To receive funds from Open Source Collective (OSC) without incurring platform or processor fees, we recommend setting up a Wise PayMe link and adding it to your OSC dashboard.
-
Create a Wise account
Visit Wise Invite and register using your project’s legal representative or entity. -
Activate PayMe link
Once your account is verified, go to:
https://wise.com/pay/me/<your_wise_username>
Replace<your_wise_username>with your actual Wise handle.
Example:https://wise.com/pay/me/xiaodongg20 -
Add to OpenCollective dashboard
Navigate to:
https://opencollective.com/dashboard/<your_osc_account>/payment-methods
Select Custom Payment Method, and paste your Wise PayMe link under For Expenses. -
Funding policy
Funds you request via Open Source Collective will be transferred 100% into your Wise account, with zero transaction fees — helping preserve every dollar for the Axmol Engine community. -
Important
❗️Requests using non-Wise payout methods will be rejected.
Please ensure your Wise PayMe link is active and correctly configured before submitting expense claims.
- Core Maintainer Support: ~85–90% of sponsorship funds are reserved for long-term maintainers to ensure project sustainability.
- Infrastructure: ~1–5% is used for domain and hosting costs.
- Unused Funds: May roll over to the next quarter or be used for community activities.
- PayPal Limitation: Please note that PayPal is currently not available in Mainland China for receiving payments from Open Source Collective. Contributors in Mainland China should use Wise instead.
This reward system is designed to recognize valuable contributions and grow the Axmol community.
If you have suggestions for improvement, please open a discussion on GitHub or join our community chat.