Turning a side project into an open-source project
1–10 of 41 posts
Re: Turning a side project into an open-source project
#2Hey, I'm the author of this blog post. Hit me with questions if you got some!
Re: Turning a side project into an open-source project
#3Hey, I'm the author of this blog post. Hit me with questions if you got some!
TL;DR: how to turn a side project into an OSS side project: start by scratching your own itch, timebox tweaking, write a good README, hit publish. Easier than you'd think.
here's the project https://github.com/jehna/ga-lite
Re: Turning a side project into an open-source project
#4Nice work! I especially appreciated the emphasis on writing a good README… but I think it's missing the most crucial thing you need on top your README. That's the motivation aka why the project exists at all, why it's better than the alternatives, etc.
Re: Turning a side project into an open-source project
#5i love the idea of just finishing - anything - and doing another. this is the only way to go, in any endeavor. try, fail, learn, fix. repeat.
Re: Turning a side project into an open-source project
#6Nice work! I especially appreciated the emphasis on writing a good README… but I think it's missing the most crucial thing you need on top your README. That's the motivation aka why the project exists at all, why it's better than the alternatives, etc.
The differentiating qualities of the project is indeed very important. But I think it's more than okay to also say that "this is a clone of xxx I'm using to learn yyy".
Re: Turning a side project into an open-source project
#7i love the idea of just finishing - anything - and doing another. this is the only way to go, in any endeavor. try, fail, learn, fix. repeat.
Deadlines are a bliss. They help you to both reduce the unnecessary, but also to fail faster.
Sunken cost fallacy is a real thing even in side projects.
Re: Turning a side project into an open-source project
#8I think that adding a (permissive) license is the missing step from this "tutorial". If you want people to use your project you are going to need to give them permission to do so.
Re: Turning a side project into an open-source project
#9I think that adding a (permissive) license is the missing step from this "tutorial". If you want people to use your project you are going to need to give them permission to do so.
I agree that it's crucial to have a good license for your project to spread. But I think it's one of those things that takes a lot of mental effort when you do it the first time.
Fortunately GitHub helps you quite a lot nowadays with choosing the license for your project.
Re: Turning a side project into an open-source project
#10I think that adding a (permissive) license is the missing step from this "tutorial". If you want people to use your project you are going to need to give them permission to do so.
Only because so much FUD has been spread about the GPL