Contribution Program
Overview
Contribute code to Polkadot Cloud applications and get tipped in DOT or USDT for your work. The Polkadot Cloud Contribution Program utilises the OpenGov treasury to disburse tips to contributors.
With the Contribution Program you can expect:
- Mentorship: Polkadot Cloud will provide mentorship to help you complete your tip.
- Guaranteed Backing: For every completed tip, Polkadot Cloud will automatically give 50,000 DOT Aye conviction.
- Full transparency: The tip amount will be decided by the Polkadot Cloud team based on the complexity of the task prior to works starting.
- DOT or USDT: The tip currency will be applied based on your choosing.
- Improved GitHub Portfolio: Boost your GitHub history and CV by contributing to Polkadot Cloud Applications. Work on real-world problems to improve application-side Web3.
Upon completing a tip, Polkadot Cloud will open an OpenGov proposal on your behalf and disburse the tip amount upon the referendum successfully passing.
Eligibility
To be eligible for a tip, contributors must:
- Resolve an eligible Issue on GitHub with a merged Pull Request (PR).
- Address issues marked with the "Active Tip" label.
- Meet quality standards set by the Polkadot Cloud team.
- Complete the task within the specified time frame.
- Be in good standing with the community (no history of malicious behavior or consistent non-delivery).
Discovering New Tips
We cannot document every bug, issue and idea to grow our apps. Therefore, we promote users raising their own issues, which could then be used as new tips.
Process for user-discovered tips:
- User posts an Issue or Discussion on Github describing what works they want done. Could use a label "Tip Request".
- We then review, and if eligible, we will assign the label to the Issue and update the project board.
- If the user wants to work on the issue themself, they will immediately be assigned. If not, wait until an assignee expresses interest.
Tip Logistics
Badges and Recognition
- Participating repositories will display a badge in their README files promoting the Polkadot Cloud Pioneers program.
- An infographic or short paragraph in READMEs will provide additional visibility for the program.
Time Limits and Accountability
- Default time limit: 30 days from assignment to completion.
Getting Started
-
If you have an idea you wish to develop for Polkadot Cloud, start a Discussion on GitHub.
-
If you would like to contrinute to an eixisting Issue that is eligible for a tip, check the Issues page on GitHub and rquest to be assigned to the Issue.
Tip Conventions
The following practices are maintained for Contribution Program tips:
- For Discussions opened to discuss tip ideas,
- The
D0: Tip Discussion
label will be assigned.
- The
- For Issues opened for tips,
- The
T0: Tip Request
label will be assigned. - The
S0: Needs Contributor
label will be assigned to indicate that the tip is open for contributions. - One
U
label will be assigned to indicate the type of tip. - One
L
label will be assigned to indicate the time limit for the tip.
- The
- For Pull Requests opened for tips,
- The
T1: Active Tip
label will be assigned.
- The
For Pull Requests, the issue number should be mentioned at the top of the PR description. For example:
Addresses #<Issue number>.
<PR description>
GitHub Labels
The following labels are used to categorise discussions, issues and pull requests for contribution tips:
GitHub Labels for Discussions
D0: Tip Discussion
GitHub Labels for Issues
S0: Needs Contributor
T0: Tip Request
Tip Type: (U):
U0: New Feature
U1: Bug Fixes
U2: Refactors
U3: Tests
U4: Performance Optimisations
TIme Limits: (L):
L0: 30 days
L1: 60 Days
L2: 90 Days
GitHub Labels for Pull Requests
T1: Active Tip