Shocking open source code
I received the following issue on GitHub:
I was literally shocked to discover that nuget.exe is committed into version control.
The thing is, this kind of feedback doesn’t help. If we want to encourage more people to share their code with the world then we need to be more careful with how we communicate. Yes, you have to put up with my awful projects on GitHub if you want to avoid putting off the developer who has something really awesome that she is considering gifting to the world, for free.
I think it is important to keep things in perspective. All of the projects I post on GitHub represent little ideas and experiments that I have shared in case someone finds them useful. Most are dormant unless someone finds a bug and is unable to fix it for themself. I use highly permissive licences so people can take snippets that they like and generate entirely competing projects.
Being shocked by something found on some small project on a code sharing site is a disproportionate reaction.
Of course there are lots of things that could be improved, but like most open source developers I have to find that elusive spare time to dedicate to open source in amongst having a fulfilling family life, and a challenging job.
My experience has led to values I hold at this stage in my life that tell me that I won’t regret not fixing a project structure on GitHub when I’m on my death bed – even if I have failed to add NuGet.exe to the gitignore file.