4 ms·
re: "Developers free time is where it often starts..." Words matter. We need to stop calling it free time. It's not free. Nothing is free, and certainly not a
by chiefalchemist 8y ago
re: "Developers free time is where it often starts..."
Words matter. We need to stop calling it free time. It's not free. Nothing is free, and certainly not a limited resource such a time.
Personally I'd like to see one of the major OSS code hosts (e.g., GitHub, GitLab, etc.) incorporate payments (read: donations) into their system. If I could load say $25.00 in credits to my account I could make a donation with a click. The receiver - or anyone for that matter - could keep the "cash" or put a bounty on a bug or new feature.
- notafraudster 8y agoPatreon currently exists, and a lot of game emulators make use of it. There are a variety of one-off tip mechanisms too (kofi is a popular one). And feature bounties also exist (elementary, for example, uses Bountysource for a lot of their development). I think all of these things work for certain projects. They work less for mission-critical but un-flashy components (i.e. the "how do we adequately fund OpenSSL?" problem, which was solved by having big money corporates endow funding for it). They work more for user-facing stuff. So they're a good option. But I don't think they're materially superior to the other models for sustainable OSS (maintainers working on OSS projects as 20% type tasks at their day jobs; companies selling service agreements and hosted versions of OSS components; very large companies simply being public good providers). They're just another part of the puzzle. I do agree it might be slightly more convenient to offer them as part of the public-facing code repo stack. In this case, it's not clear to me Patreon style development funding would have worked near as well as Redis Labs being a corporate sponsor.
- voltagex_ 8y agoOne emulator earning 20k (!) a month is an outlier - it's also not open source. There's still the marketing issue. If I was to work on open source full time I'd need to get about $2kAUD a month. That kind of income doesn't just happen - you've got to have an extremely popular project first. Also remember that Patreon's gotta start making money for the VCs soon so there will be user hostile changes eventually. Bring on universal basic income.
- chiefalchemist 8y agoYup. But I think the game changes when you bake those things into the platform (e.g., GitLab).
- m3mpp 8y agoWhen you see that donations come only from individuals, corporate don't care, it's definitely not the answer.
- toyg 8y agoThe real game-changer would be to link downloads/checkouts to user accounts. Like, you can download this repo anonymously once or twice a day; more than that, and you have to pay -- on a sliding scale, so that companies with build systems and so on are forced to pay more. If Github and Gitlab (and maybe Bitbucket) had the balls to build something like that, I think things would improve. Users would be impacted, so it would be essential to get some help on the PR side from established projects and bodies like FSF, Python Foundation, and so on. Getting the big companies onboard should be easy enough - just give them a flat-fee yearly subscription option that they can spin in a nice Bloomberg release on how they support innovation and blablabla. You would likely still see cheapskates setting up their internal mirrors and so on, but with the right price structure, I bet most medium-to-big shops would accept it and start generating substantial amounts for OSS projects.
- sytse 8y agoSo a paywall similar to newspaper sites? And make it per project per organization? You work at ACME Inc. and you already used your 2 free downloads of Redis for today? One problem I see is that most open source doesn't get consumed as source code but via language package servers (Rubygems/NPM) or OS distributions (Debian packaging Redis).
- toyg 8y agoLanguage-specific packagers that source directly from VCS services, could easily accommodate the need to specify credentials for source repositories -- in the same way you need cloud-provider credentials to run cloud-provider command-line utilities. So that's not a problem. For other packagers and OSes: packages don't happen out of thin air: someone has to write recipes and scripts, and test them. So that's already some revenue right there, especially from the big players. Companies like RedHat and Ubuntu could just cut a flat $10m check every year, distributed to projects proportionally in accordance with OS-provided stats like popularity-contest. That's the easy option. Ideally, you would also have some buy-in from the major OS distributions that could somehow "trickle down" the model to their own packages (say, linking a VCS repo to an OS package and reporting activity accordingly: "You asked to apt-get install Redis, but I've checked with a webservice and you have already downloaded it 2 times from Github.com today: time to pony up!". In most cases, this sort of link is already documented formally, somewhere in the package definition.) Like newspaper paywalls, it doesn't need to be perfect; it just has to be enough hassle that most people who can afford to make the pain go away, will just do that.