5 ms·
Not wanting to have toxic user requests and issues open for something you do in your spare time could be one good reason.
by buster 6y ago
Not wanting to have toxic user requests and issues open for something you do in your spare time could be one good reason.
- oliwarner 6y agoI'm not sure where you get the impression those somehow don't exist if you don't have a bug tracker. They just go to email, or Twitter. For something like this, keeping things private has allowed Troy to work out the best way to do things with complete autonomy. That's really useful if you have the time and resources to get to market on your own. Now it's stable and best security practices are nailed down, he can open it up to a bit of scrutiny and feature bloom.
- msla 6y agoIt's entirely possible to run a Git server which is read-only (for the rest of the world, anyway) and doesn't allow anyone to bother you.
- jcims 6y agoWhat's the point of doing that though? It's just chumming the water for unsolicited feedback.
- majewsky 6y agoIt allows others to easily mirror your code. The original code owner may disappear for any number of reasons (burnout, early retirement, being run over by a bus, etc.).
- msla 6y ago> What's the point of doing that though? It's just chumming the water for unsolicited feedback. You'd do it to prevent feedback.