Hello Community,
we need to decide how to proceed with DotCodeSchool.
The Situation
Batman - the original creator of DotCodeSchool, the platform every PBA and PBA-X student goes through - is stepping back from active maintenance. While he may still contribute occasionally, he’s no longer in a position to actively maintain or drive the project forward.
That leaves an important question:
Who will take responsibility for maintaining, updating, and supporting the platform going forward?
It’s worth noting that DotCodeSchool has already received $159,500 in funding through past proposals. We need to decide whats next.
Whats Next?
DotCodeSchool belongs to the Polkadot Community and the Community shall decide.
I guess the first question which needs to be answer is:
-
Do we want to drop the project and let it slowly go out of date - probably only cover the fixed costs which are ~$13/month.
-
Or, do we keep maintaining, maybe extending it, if yes who is willing to do that?
Proposition
I enjoyed using DotCodeSchool while prepping for PBA. Its already a established platform in the ecosystem. I am convinced we can use this positioning to make it even greater.
Here Is What I Offer
Because of my conviction and fit I’d be willing to take care of the platform. Here is what I can offer:
-
I am able to spare 20h/week
-
I have a track record in EdTech
-
My experience in content creation is a key advantage
-
I have experience with the Tech Stack
-
I already work on Gitorial - which is another EdTech Project. This will be a great opportunity for synergies
-
I have Batman’s backing
-
I already work on a DotCodeSchool Project (Hands-on Video Tutorial + Video Streaming Functionality)
The Plan
Tasks
My job can be described in two simple words. Improve & Extend
This translates to:
-
Maintenance
-
UI/UX Improvements
-
Extension of Functionality (like the Video Streaming feat.)
-
Community Need Analysis
-
Onboard Contributors
-
One idea is to set up a small monthly incentives pot to reward contributors who improve the platform, write tutorials, or help grow DotCodeSchool. It should act as a tip and not be the primary reason for the contribution.
The idea would be to primarily target Web2 developers who stumble into blockchain technology. The funnel is simple:
-
Make a meaningful contribution
-
Set up a wallet
-
Receive their first on-chain transaction
This approach could be a lightweight but powerful way to encourage early engagement, grow the community, and make the platform more self-sustaining over time - even with a modest recurring budget.
That said, Batman raised an important point:
Low incentives might actually backfire by diminishing intrinsic motivation, as shown in the the study “Pay Enough or Don’t Pay at All” by Gneezy and Rustichini. If contributors perceive the reward as too low, it might demotivate rather than inspire. So this is something we should approach thoughtfully.
Two Possible Distribution Models:
-
Option A – Direct Rewards
Contributors are compensated in proportion to their contributions. It’s simple, transparent, and directly tied to value delivered.
-
Option B – Gamified Incentives
Contributors earn “lottery tokens” for each accepted contribution. At the end of the month, one contributor is selected at random to receive the full reward pool — with odds weighted by the number of tokens earned.
This introduces chance and excitement, leveraging gamification to increase engagement and dopamine-driven motivation — particularly for newcomers.
I’d love to hear your thoughts on which approach might work better - or if you have other ideas entirely. If successful, this could even become a template for other community-driven projects in the Polkadot ecosystem.
-
-
Immediate Focus
Here are the tasks which I find most important to tackle:
-
Video functionality
-
Refactoring of the existing code
Suggested Compensation
-
Time Commitment: 20 hours per week
-
Rate: $80/hour
-
Duration: 6 months
-
Contribution Pool: $300/month
-
Total: $40,200
Feedback
I’d love to hear your thoughts, questions, or concerns.
DotCodeSchool belongs to the community, and the future of the platform should be shaped by the community. Your input matters.