geerlingguy
commented
4 years ago Two major motivations for making the code public:
- Forces me to follow all best practices in always keeping secrets and 'proprietary information' out of the codebase. I almost always follow that rule on personal projects... but not always.
- The issue queue can contribute to my 'google-ability' for all the annoying little issues I run into and then document in the issue and in PRs.
The latter is the more important. I could miss out on sharing a lot of great data about setting up, migrating, running, upgrading, etc. a Drupal site and codebase if I leave it closed.
As I've said for two decades: "information wants to be free!"
The code is technically already open source.
And the content of my site is still my copyrighted, proprietary content—and won't be shared via a database dump or anything. Plus, if someone really wants to rip off my site, they could already write a scraper and do it, so it's not like having the codebase gives anyone a competitive advantage!
The biggest risk, I guess, is the fact that anybody could replicate my site's look and feel (not that I care too much about that—I'm a pretty open-source-friendly dude), or that someone could see my custom code and find security holes... but I'm pretty sure my code is always 100% bulletproof! (/s in case you were wondering).
If this were a static HTML site I wouldn't be as twitchy... but as it is, I think I'm in favor of opening up the repo.
So: