Still in the early stages of development with code changing rapidly. Not sure if it would be the best idea to get other people working on things at this stage, but I'm open to suggestions!
My suggestion: keep doing what you’re comfortable with. Having source available is better than not, full stop - and should be commended. Don’t succumb to peer pressure. If you want to make a “community” project do it on your own terms.
Open source != open contribution or project
The most well known project following this is SQLite.
There are many reasons to do this:
- ensuring that the copyright is fully owned
- ensuring security by reducing the likelihood of someone submitting secretly vulnerable code
- not wanting the overhead of running an Open Source Project
- wanting ultimate control on the architecture of the tool
- early stage of a rapidly changing codebase
There is a danger that "gate keeping" the concept of open contribution == open source, reduces the motivation of people to open source their code.
All open source, no matter the contribution policy, should be applauded.
Still in the early stages of development with code changing rapidly. Not sure if it would be the best idea to get other people working on things at this stage, but I'm open to suggestions!
My suggestion: keep doing what you’re comfortable with. Having source available is better than not, full stop - and should be commended. Don’t succumb to peer pressure. If you want to make a “community” project do it on your own terms.