3 ms·
I believe there are four reasons why people open source their code, and what the reason is directly affects the quality of what they put out in the open; 1. Th
by onion2k 9y ago
I believe there are four reasons why people open source their code, and what the reason is directly affects the quality of what they put out in the open;
1. They want their code to act as their resume. These people put a ton of effort in to making their code work well, look good and read nicely.
2. They genuinely believe in the Open Source movement, and want to share what they build so other people can add to it, improve it, and use it more freely. Their code looks good and reads well, but often not as well as the people in group 1 because the results actually matter more than the code.
3. Pure vanity. They want to be famous and think making their code open is a way to build their rep. They'll give things a bit of polish before putting it on Github, but often quality is second to quantity.
4. They put things on public repos without really caring whether anyone sees the code because they write the code for themselves, so it's technically open source but only because it's not private. The code is usually really hacky but no one sees it so it doesn't matter.
By the sounds of things you're in the second group. In your position I'd tidy up the code as best as I can but I wouldn't stress if it's not the best there is.
(I'm in group 4)
- jordigh 9y agoIt's not technically open source if it's merely visible. It's only technically open source if you explicitly license it to be so.
- enkiv2 9y agoGenerally speaking, people in group #4 throw an athena license or BSDL on it (though sometimes they'll throw a GPL or something on it instead). Group #4 accounts for most individual open source projects (though not most code, since big projects tend to be huge); we discount it at our own risk.
- imauld 9y agoMost of the work I do for myself is on Github and it almost never gets a license. The one thing I have added to PyPi got MIT because according to the online license picking tool I used it was the most open. I actually intend to more widely open source that lib but I have so many projects I'm working on currently it's hard to pick one.
- onion2k 9y agoIn my corner of the internet most projects use the ISC license that Node sets as a default. I have no idea if that's ever been challenged in court, but at least in theory everything is open unless someone has specifically set it not to be.
- anonymousrex 9y agoThanks. I'd add a 5th group—trust & verification. Maybe that could be considered an extension of #2, but the ability to know (and trust) the integrity of the software your're running on your hardware has become the most important aspect of open-source software for me as a user. Now, as a vendor, I want my users to have the same piece of mind. Both of my projects are predicated on privacy, so there's a solid business case in each case.