4 ms·
Another part of it is how technology and networking has made contributing to OSS so low-friction that even if there was no possibility of a perceivable return o
by danso 11y ago
Another part of it is how technology and networking has made contributing to OSS so low-friction that even if there was no possibility of a perceivable return on investment, there's also little cost to the participants as well.
I did much less development than I did before Github came along...so I don't know if Github (which of course itself depended on the existence of other OSS and infrastructure advancements) is a cause, rather than just a correlation with my career trajectory. But I can't imagine having the same willingness to work on OSS if the status quo were SourceForge (even before its current bloatware incarnation) or even Google Code, which was a pretty good service.
It's not that free software back then was less free than it is on Github. It's just that the barriers for dilettante developers to take that first step into OSS are lowered in very important ways. Without knowing anything about a library other than the part of its API that I use, I can make what I consider to be useful addition to the library and have immediate and reasonable confidence, given a decent test suite, that I didn't break the countless other moving parts in a library. Sure, test suites have existed just fine long before Github, but at least I can _see_ that a library has a test suite before even downloading it.
My involvement with OSS could be done there, but I'm literally a short commit message and a couple of button-clicks from giving my work to the library's maintainer as a pull request. If it were any harder than that, I know I would put that pull request in my nice-to-do-someday pile of things and then completely forget about it.
On the mainatiner's side, not only does Github provide a pretty nice notification system and workflow for them to organize, browse, and comment on incoming pull requests...but the way continuous integration services have decided to hook into Github means that the maintainer literally has to do nothing to have a first-pass confidence that I didn't break the library in all the ways anticipated by the test suite. This obviously does not ensure that the feature addition is not-shit, or even completely safe...but the maintainer has more time and energy to evaluate those important questions.
And then on top of it, if the maintainer accepts the pull request -- within a span of minutes if not seconds, anyone in the world who then downloads the library or updates their copy has what I added to the library, without me having to do a single thing beyond submitting the pull request. Even besides the hope that rising tides lifts all ships...the instant gratification from the OSS process alone could be enough for otherwise disinterested developers.