mirror of
https://github.com/cunnie/sslip.io.git
synced 2025-09-27 03:55:56 +08:00
Please don't submit pull-requests
...because I want to keep the coding to myself; it's the most fun part of sslip.io.
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
### Contributing to sslip.io
|
||||
|
||||
Thanks for your interest in sslip.io! This project is primarily a personal
|
||||
"for fun" project and I'm not actively looking to grow a community or accept
|
||||
"for fun" project and I'm not looking to grow a community or accept
|
||||
contributions at this time.
|
||||
|
||||
If you have an idea for an improvement:
|
||||
@@ -11,14 +11,10 @@ changes you'd like to see. You can then use your own forked version.
|
||||
- If you're feeling particularly ambitious, deploy servers running your forked
|
||||
code. A diverse ecosystem is better. Period.
|
||||
|
||||
I'm generally not accepting pull requests for the following reasons:
|
||||
|
||||
- Maintaining my vision: I have a specific vision for how sslip.io works and
|
||||
evolves.
|
||||
- Time commitment: Reviewing and merging pull requests takes time and focus
|
||||
that I prefer to spend elsewhere.
|
||||
- Keeping it simple: I want to keep the project manageable and avoid feature
|
||||
creep.
|
||||
I don't accept pull requests because **coding is the most fun** aspect of the
|
||||
project, the last thing I'd want to outsource. Reviewing other people's
|
||||
code? Not so fun. Dealing with abuse reports? Maintaining servers? Paying
|
||||
hosting fees? Checking monitoring alerts? Not fun.
|
||||
|
||||
However, I might consider pull requests for the following:
|
||||
|
||||
|
Reference in New Issue
Block a user