Managing an open source project involves a bit of work and time on your behalf especially if you want to build a following. You have to keep everything up to d

Managing an open source project involves a bit of work and time on your behalf especially if you want to build a following. You have to keep everything up to date: documentation, wiki, code, issues etc… And if you want contributors then you have to make sure your code is understandable and properly organised. (and I should be following my own advice!) Once you put your code out there you must also be ready for criticism: some good and some awful. But from my experience it's the best thing you can do as a developer because it will definitely help you grow and force you to code better (hopefully). I think I was very lucky because when I posted my first open source project on HN (https://github.com/johnwilson/bytengine https://github.com/johnwilson/bytengine) it was a positive experience and when you get that kind of feedback you really don't want to "let the community down" by slacking on your commits and other project upkeep duties (which I have). So I think you basically have to ask yourself if you just want a public code archive that you can point people to once in a while and say hey I did that or if you want to build a community around your project and turn it into something great! Best of luck and thanks for posting this, it has given me a little kick in the butt!