3 ms·
You'd think so, but there's also a good chunk of copyleft code that's just "here's our source code, go figure out how to deploy lol". You can try to fork it in
by noirscape 4y ago
You'd think so, but there's also a good chunk of copyleft code that's just "here's our source code, go figure out how to deploy lol".
You can try to fork it into something workable, but that can sometimes literally mean trying to figure out what the actual deployment process is and what weird tweaks were done to the deploying device beforehand. In addition, forking those projects is also unworkable if the original has pretty much enterprise-speed development. At best you get a fork that's years out of date where the maintainer is nitpicking every PR and is burnt out enough to not make it worthwhile to merge upstream patches. At worst, you get something like Iceweasel[0] where someone just releases patches rather than a full fork (and having done that a few times, it's a pain in the neck to maintain those patches).
FOSS isn't at all inherently community-minded; it can be and can facilitate it, but it can also be used as a way to get cheap cred from the people who are naïeve enough to believe the former is the only place it applies.
[0]: "Fork" of Firefox LTS by the GNU Foundation to strip out trademarked names and logo's. It's probably one of their silliest projects in term of relevancy.
- ghaff 4y agoPeople do release software as open source for the "street cred" (perhaps unsurprisingly given the school of thought that you don't deserve a developer job if you can't show off a GitHub repo). A lot of people also create something and figure "why not?" They may just not be interested in doing any serious community development and maintenance. There are even significant open source projects that are pretty much a closed development process.