5 ms·
In 15 years, I've read my fair share of "open source developer's lament", and when the projects mentioned are stuff like Requests or SQLObject I honestly don't
by toyg 11y ago
In 15 years, I've read my fair share of "open source developer's lament", and when the projects mentioned are stuff like Requests or SQLObject I honestly don't understand. If you step back and try to look at these problems in a structured way, you can see that it always boil down to the following algo:
1. Is it a money problem? Then ask for money every time anyone asks for a piece of you (i.e. bug fixing, event patronage, whatever).
2. Is is a time problem? Then hire someone. If you can't afford it, it's a money problem: goto 1.
3. Is it a skills problem? Then hire someone. If you can't afford it, it's a money problem: goto 1.
I mean, requests alone is worth hundreds of thousands of dollars a year. with all due respect to Kenneth and Ian, I find it hard to believe that it cannot pay one developer salary, even at Californian rates, unless they simply cannot be bothered to ask for money. Stuff like adding a "donate" button on the page looks lazy.
There are tons of ways to get money out of big corporations. Get a rotating-sponsorship deal where a company pays one salary for one year -- between Amazon, Google and Twitter (all heavy requests users, I'm sure), you already have three years of full-time development. They get quick bugfixes, you get a better life, win-win. These companies make billions with your code, I cannot believe they can't cough up some spare cash. I mean, look at the OpenBSD Foundation: they asked for some change to pay a month of server time, and they got Microsoft to dole out huge cash to port OpenSSH to Windows. Microsoft, FFS!
- cwyers 11y agoI agree with a lot of this, but it's more than asking for money. You have to offer things of value in exchange for money and ONLY in exchange for money.
- toyg 11y ago- Asking to fix a bug without submitting a patch (or with a crappy patch)? Money please. - Asking to fix a bug NAO NAO NAOOO? More money please. - Want to move some_lib to python 3? Money please. - Want to backport some_fix to unmantained_old_crap_runtime? Money please. - Want to discuss a particular choice in our roadmap? HUGE money please. - Want to support device_x before device_y? Money please, and testing equipment if you could be so kind. - Want me to help you with the conference you're paid to organize? Money, please. I'm sure that people can be quite creative if they really put their mind to it. We think nothing of paying hundreds of $cash_units for things like tyres and fuel and double-glazed windows, there is no shame in asking for some of that back to build the software that will actually make those companies run.
- tedunangst 11y agoThe first time somebody demands I pay extra to fix a bug is the last time I use that project.
- cwyers 11y agoSure, and the first time someone insists that you triage a bugfix based on their priorities and not yours and they don't contribute to the project, you can let them leave as a user! Everybody is happy[1]. 1) Nobody is actually happy.
- toyg 11y ago"Pay extra"? Like you were paying for it in the first place. At the end of the day, somebody gotta pay the ramen. Besides, a certain project you might be familiar with is basically monetizing automated security patching, so throwing stones is really not a great sport. (also, projects like requests are not desperate for users. One user paying to contribute to the well-being of the codebase is worth hundreds of users who won't even bother sending in a patch. Again, a certain project you might be familiar with is awfully aware of this state of things.)
- enraged_camel 11y agoThe problem with the "pay them to fix the bugs" model is that it turns bugs into a source of revenue and creates the wrong incentive for the developer. I'm much more inclined to agree to a "pay for additional features" model instead. Because then, by definition, you are paying for extra stuff, vs. fixing what should have been working correctly in the first place.
- nickpsecurity 11y agoThat's clever but wrong here: labor is what's being monetized. The people that they're asking probably require payment for their own labor and pay others w.r.t. other goods. Then, they OSS developers owe them free products and support of highest quality. Quite a double standard. Requiring pay for fixes only incentivizes pay for labor, which is rare for OSS.
- rodgerd 11y agoAnd the things of value are measured by the person with the money, not the person producing them. That's often a very direct conflict with the "scratch an itch" culture. Red Hat (for example) give me value (for which I pay them) by giving money to people to work on the 20% of free software (bugs, polish) that are apparently an anethma to many developers.
- imron 11y ago> Stuff like adding a "donate" button on the page looks lazy. Not only that, but from my own experience, relatively few people (as a percentage of total users) will ever donate. Explicitly asking money for things of value has much better results.
- madeofpalk 11y agoDan Aramov ran Patron campaign to raise money to work on developing Redux.js full time https://web.archive.org/web/20150721215514/https://www.patreon.com/reactdx?ty=h https://web.archive.org/web/20150721215514/https://www.patre... And then there's Andrew Godwin raising £17,952 to work on Schema Migrations in Django https://www.kickstarter.com/projects/andrewgodwin/schema-migrations-for-django https://www.kickstarter.com/projects/andrewgodwin/schema-mig... Asking for money for open source software does work.
- CrowderSoup 11y agoBoth of those developers asked the community for money. They should have asked the companies that use their projects directly. I world imagine they'd hey far better results that way.
- gtaylor 11y ago> They should have asked the companies that use their projects directly. I world imagine they'd hey far better results that way. Better results? Both efforts were funded almost immediately and well in excess of what was being asked for. I think these two cases are great examples of how this could work.
- shangxiao 11y agoNot to mention that Tom Christie raised £32,650 for DRF 3 https://www.kickstarter.com/projects/tomchristie/django-rest-framework-3 https://www.kickstarter.com/projects/tomchristie/django-rest... :)
- lambda 11y agoI work at a company that uses a large amount of free software. For much of it, if we find a bug, we either fix it ourselves locally, or go through the normal process of submitting a bug report, possibly submitting our own patch, and waiting for a fix from upstream, while finding some way to work around it or the like. For some of the software that is central to our business, we have a contract with a company that provides support and development services. If we have a bug that we need fixed right now, we get in touch with them and pay an agreed upon rate to do so. We don't do this for everything we use, because most of it works off the shelf, or we just replace it or work around it, or the open development process works well enough. But for those things that are absolutely key to our business, and for which there's a consulting company that employs several of the core developers on the project, it's definitely worth it to pay for the support that we need.
- Radim 11y agoAgreed. We support gensim (a Python machine learning library) entirely through commercial projects and consulting. We never asked users for money, while keeping the lib 100% open source. BUT you have to realize a lot of OS development is subsidized. This takes the form of "free" work by students, undergrads, graduates, government grants etc. A lot of the suggestions people throw around are simply not feasible for hobby OS projects, which don't have access to free students or free government money. It's a race to the bottom if you want to state this as a business problem. It also confounds the moral issue somewhat, as corporations (and individuals) then rightly feel they are entitled to development & support -- after all, the subsidies have come through their taxes!
- fijal 11y agoHi toyg. You clearly haven't tried raising money for an Open Source project. It's really really difficult and the amounts of money you get range a lot. Usually you also want to underpromise and overdeliver, so it's about raising 10-20k USD to deliver a project that will take three to six months of full time work to deliver, ADDITIONALLY to fixing bugs, maintaining infrastructure and doing things for which you can't possible raise money at any rate. Contact me privately I can share more of the details, but it sounds like you're quite detached from the open source reality. PS. We work on PyPy and cffi
- toyg 11y agoI have no doubt that this is your experience (for which there might be many causes - my email is in profile unlike yours ;), but there are also extremely successful examples like the ones I and others have posted. They stand out not because they succeeded, but because they're the few who tried -- and succeeded spectacularly quickly, almost accidentally. Working in the enterprise/financial world, I can tell you that boatloads of cash get wasted on the most absurd items, so there must be ways to funnel some of this to the right places. Even VC-backed "lean" startups would/should rate publicity "in the right places" more than a lot of other things, let alone direct benefits from actual productivity gains. For example, I often don't know whom awesome_oss_developer works for; if I did, I would be inclined to rate their products and services way higher, and would probably want to work for them more. Every single OSS release from major projects should carry a sponsor highlighted in README and release notes. Advertising somehow pays for billion-dollar companies in the real world, but the same companies don't rate it enough to sustain their own infrastructure? I'm not doubting that reality is dire, what I'm doubting is the effort placed on changing it. There are many elements of the engineering culture dominant in OSS that are just not right from a commercial perspective and could/should be fixed with brutal honesty.
- fijal 11y agoUh, the lack of email was an omission - fixed. I worked for the past few years on making PyPy & satellite projects more business friendly. We've established a company (baroquesoftware.com), I went to conferences, advertised it etc. Granted, I'm not the right person to do the job - I'm generally a technically-oriented nerd. The community is welcoming for both commercial interest and newcomers and if there are hiccups, we're trying to fix them. This is not an easy project to get your hands dirty, we definitely don't need extra barriers to entry, for example it's extremely easy to get a commit bit on pypy. There are some spectacular success stories, but even Django had a hard time raising money for someone to work full time on fixing bugs, while noone doubted usefulness of that. Now PyPy is far less successful than django, but it does save companies tons of money. I would welcome advice/help/whatever in how we can make PyPy more commercial friendly in a way that brings revenue - I'm not interested in making businesses happy for free all that much.
- rbobby 11y agoThere does appear to be a donate button on the Requests page. It's hidden as a "Buy Requests Pro" which is really just a donate (same code, unclear whether different license).
- detaro 11y agoNope, it is the same license as well. But it probably looks better on an expense sheet than a "donation".
- _Marak_ 11y agoWe should have Open-Source agents who can represent projects and pitch corporations for paid sponsorship. The agent gets 10% for closing the deal. Sounds like an opportunity for a new start-up. I'd sign up for it.
- eru 11y agoThat's just a standard software consulting. Lots of clients wouldn't mind you open sourcing what you worked on for them.
- _Marak_ 11y agoNot consulting. It would be having a person pitch a business or groups of businesses to sponsor an open-source project. The overhead of communication, negotiation, and writing contracts is outside the scope of what most open-source developers are willing to do in terms of time. Simply put, there is a disconnect between the value of the open-source software and the availability / willingness of open-source project maintainers to monetize a project.
- dunkelheit 11y agoWhat you propose is sensible and funneling more of the wealth that corporations derive from using OSS projects back to the development of these projects is certainly a desirable thing. But there are other problems discussed in the post and I'm afraid some of them cannot be solved with money alone. Suppose you are overwhelmed with a thousand meaningless pull requests. Whom you are going to ask for money? Suppose you are called a douchebag for rejecting an ill-thought out pull request. How is money going to mitigate the vitriol? Suppose you are called a douchebag for asking money to fix bugs. Same thing. Attitudes need to change too. There needs to be growing recognition of the respective contributions of users, developers and maintainers of OSS projects and their value.