-
Notifications
You must be signed in to change notification settings - Fork 150
Template Bounties
Railway has shipped a bunch of new primitives that move Templates beyond simple language starters (remember when we called them Starters?) to full featured applications. We also now have new authorship tools that make creation and management of templates better… but that’s still not enough.
We are in the middle of a chicken and egg problem. We don’t have enough high quality examples of templates, some of them are woefully out-of-date, and some, well- would just be REALLY cool to have.
If you ever been to a dance party before, it’s not enough to have a DJ. You need people willing to dance so that the first person on the dance floor doesn’t seem like a lunatic. Then what happens is that you don’t need to seed the dance floor, people then feel comfortable to join the fun.
Let the Template party featuring M.C. Nixpacks and DJ Soon(tm) commence.
We in the past paid out small contracts (under $1,000) for pieces of work that could be spun off. This is part of that long-running tradition. Nixpacks language support was bootstrapped via this way, and now, we wish to bootstrap the Templates ecosystem this way by working with industry partners and community members like you.
From Aug 4th - Sept 15th
Mid-program check-in: August 25th You can join us on Discord for office hours on this day!
Payouts: $50 - $500
Railway needs high quality Templates to whats possible on the platform itself.
We want Templates that work, but also well-documented that help all developers reach for proven tools like... duplo blocks!
For anything not on this table- pitch us! We also wanna see templates that take advantage of the Railway API, exposes debug data to users, and complete real-world applications that show off the potential of Railway. Open an issue requesting a bounty.
We will create issues on this Repo's project within the Railway Templates Github (that's here!) with a description of our request.
Users will then be asked to open an issue against the repo filling out the form to determine review. We will then undergo the review process. If accepted, then we will begin the payout process.
We will have a channel #templates on Discord to answer any questions related to Template authorship and creation. Any Discord member who got a payout will be given the “Bounty Hunter” role.
We will operate on a Net-60 model. Once a template goes under the review process, we will confirm with you that it is eligible for payout. If considered eligible, we ask that you give us 60 days to process the payout as we need to report this within our financials. (Railway accounts for every penny we spend, only way we stay compliant.)
After template review, our operations team will confirm the payout once approved, we will then ask for preferred payout and we will send over the value amount of your work.
Templates must:
- Deploy and be replicable
- We will be checking the public endpoints within the parent and offspring templates that are made to see if they are replicable.
- Have three sections of documentation, photos encouraged.
- Overview, Highlights, More Info
- Great examples we have seen that we consider to be close to the bar as it stands:
- Must be able to receive payment via, https://www.buymeacoffee.com/, or accept payment through GitHub Sponsorship
For more info on how to make a Template: https://docs.railway.app/reference/templates
Happy hunting!