7 ms·
Bounties Damage Open Source Projects
- drbig 3y agoI have always been of the same opinion, which I formed years ago helping with Cataclysm: Dark Days Ahead development: "development by bounty" leads to inevitable "(un)designed by a whale", i.e. a few with cash to spend on such things enforcing whatever they _feel they will like_ on everybody else. The notion of a coherent whole, whether it's a game or anything else, doesn't really go well with "voting with wallets". The article points out the more strictly technical aspects with which I agree as well, just that to me they are like worrying about pain when you have a bleeding artery. Perhaps if "design by committee" is one obviously bad end of a spectrum, I propose "designed by bounty program" as another (and I'm not saying that the space here is one-dimensional). Bug bounty programs on the other hand are excellent, so it also isn't that "bounty" is inherently bad. Discovery vs design.
- Valodim 3y agoThis seems to assume that people actually put up bounties that get any serious amount of work done. If that is the case, I missed it.
- drbig 3y agoYes. It assumes the asymptotic end condition, because to me that is the only reasonable way to judge such policies. Cases of "nothing was done because bounties weren't interesting", or "we had a feature bounty program and it done awesome!" are, for the purpose of my analysis and thus opinion formation, only more or less happy exceptions (hypothetical or real).
- swagmoney1606 3y agoYour comment posed a very interesting question to me, so I took the time to think of some other points in this multi-dimensional space of terrible software engineering. Here are some other terrible design systems: - Design by lottery (Single winners of a quarterly lottery dictate all decisions for that quarter) - Design by deliriant (same as design by committee, but all members of the committee must take Datura before making decisions (probably deeply unethical and problematic, but we're going for the worst possible here)) - Design by Anarchy (Literally anyone can commit straight to the main branch without any checks) - Design by Ouija Board (Committee members MUST consult a Ouija board before making decisions ) - Design by mob (A real-time public forum, accessible to anyone, can propose/vote up or down potential features or code changes. Highest votes within a 24-hour window are implemented immediately. Allows and even encourages raids from random sites like 4chan or corporate entities) - Design by Dog (Various options are written down on pieces of paper, scattered on the floor, and the pet's choice is determined by whichever piece it first sits or stands on. (In this alternate reality, our dog STILL hasn't decided to patch log4j. God help us.)) - Design by randomly-elected outsourced labor (Decisions are outsourced to the lowest bidder on freelance job platforms, regardless of their experience or skill level.) These are just the ones I could think of off the top of my head. Lowkey it'd be hilarious to try and build actual software with these, just for fun.
- jstarfish 3y agoHow did you see that impact development of CDDA?
- drbig 3y agoI didn't really either way. Which given a) how long ago that was and, b) I specifically declined to look at bounties - the only thing I'm close to being sure about is that I don't remember any drama nor ruin from that.
- dale_glass 3y agoWhat about bounties for boring tasks nobody is excited to do or where the main team lacks competency in the given area?
- wakeupcall 3y agoFrom by my own experience, you'll have to review/test the boring task from a one-time contributor, which is also not fun. You don't need to do that as often if the contributor is going to stay, but you're not attracting this sort of contributions with bounties. The last point is also similar. If I get a significant contribution in area where I'm not competent, I might take it, but is it going to maintain or fix problems to it in the long term? I'd rather not include a feature which I know I can't maintain long term.
- patmorgan23 3y agoGrants/Sponsorship still exist. Andrew is not arguing against people paying for specific features/work. He is arguing against 1) not coordinating that work with the core team 2) competitive 'first correct submission wins'
- MatthiasPortzel 3y agoI wish the original post had explained this better. It seemed to bash bug bounties without offering any alternative, except “employing well-designed business management processes.” Which is not a helpful statement unless you already agree with the authors.
- bawolff 3y agoI feel its unfair to expect people to have a solution just because they are discussing a problem. Just because something doesn't work doesn't mean a fix is obvious or one even exists.
- eatonphil 3y ago> It seemed to bash bug bounties To the contrary, the article explicitly called out bug bounties as making more sense.
- countWSS 3y agoIts probably distracting them from rapidly developing features. In stable projects its a much more better incentive to get programmers focus via some gamification techniques like bounties/prizes/competitions. Open source projects usually stagnate without some "competitive" incentives, because its feels like working for free.
- whatyesaid 3y agoAgreed, because nowadays big open-source projects are backed by sponsors (users, other companies) or have revenue streams (e.g. like Obsidian although that's closed). Then it really feels like working for free as opposed to helping some obscure library.
- rendaw 3y agoSo... just to get it out there, I really want to see more funding in open source development. The fact that pretty much all open source software right now is passion projects means that people are pretty free to aim at ideals, throw things out and iterate/try new ideas. I think open source as we know it exists because there's no money, but it's also limited in scale, and you still need to depend on companies like windows, adobe, google, etc because development just can't reach that scale. Adding money could absolutely destroy the current good things, but it's also totally possible that the good things could persist while making more projects viable. My dream is to work on useful open source libraries during the day so I can work on fun stuff, art, games, etc. I intend to build from those in my free time, rather than work on the libraries in my free time. But I get that people are scared of losing what we currently have. I don't think we'll know without giving it a go (obviously there are other obstacles to this too, like accounting, taxes, legal questions, etc). Back to the article, I feel like it's making sweeping arguments about a very specific implementation of bounties. AFAICT what happened leading up to this is - WASIX put out a bounty for WASIX implementations in other software - Some people started rolling forward with it in the Zig bug tracker, WASIX (?) publicizes this on twitter/reddit - Zig maintainers said no - Debate in the issue tracker - Zig maintainers said no more discussion - Bunch of deleted messages I might have missed something. It seems like the main reaction is about Zig's name being used for WASIX promotion/a 3rd party trying to exert control over Zig development, which doesn't entirely seem related to the bug bounty or bug bounties in general. WASIX put out the bounty and did the publication, they're a bad actor and this could have happened largely the same way entirely without the bounty too. The points in the article don't seem related to bug bounties. Highlighting a few: > you end up with a quickly bitrotting artifact This happens with all MRs, bounty or not. "Upstreaming" is an implicit contract where you write something you want per the maintainer's specifications and in exchange they maintain it afterwards. > Instead of scouting for a suitable candidate, you’re letting battle royale dynamics pick a winner for you Non-bounty issues frequently have people taking them who aren't capable of producing a mergeable solution. I'm not sure why a bounty would make this worse - you could easily argue that in order to get the payout people would be more careful to take work they can actually complete, or that people who are capable are can now afford to devote their time to it. > You instead penalize any form of thoughtfulness in favor of reckless action (eg a solution just needs to pass a test suite) The maintainers decide whether something gets merged or not, and I've never seen a project that says "We'll merge anything that passes our test suite". Maybe I missed something here... > Instead of spreading unease to all the people involved, it would be preferable you instead learned how to do business properly. This feels like an attack directed at the WASIX people and not a general statement. That said, there's very very little bounty driven development ATM. I think it's hard to extrapolate consequences at this point in time.
- deleted 3y ago[deleted]
- DishyDev 3y agoI've had a good experience doing a couple of bug fix bounties for urllib3 https://github.com/urllib3/urllib3/issues https://github.com/urllib3/urllib3/issues . I'd be interested in how the maintainers how found running the bug bounty and if it's given them more useful fixes or if it just adds more noise to deal with
- templix 3y agoThe Zig article specifically says bug fix bounties are different.
- zcesur 3y agoThese projects [1] would disagree. This year 498 bounties ($53,410) have been rewarded to 166 contributors from 45 countries, they were funded primarily by commercial open source founders/maintainers to support product & devrel (get more work done, grow community, reward contributors, gain visibility). There's also an experimental use case where FOSS users themselves create bounties to pay contributors/maintainers to ship new updates and features. We call these 'community bounties'. The $5,000 WASIX support bounty in Zig was created by Wasmer, but the Zig maintainers didn't welcome it (which is totally fair, it's their choice) and this blog post is a rant about it I guess? [1]: https://news.ycombinator.com/item?id=37457921 https://news.ycombinator.com/item?id=37457921
- capableweb 3y agoMaybe it's worth responding directly to the criticism from Zig rather than calling what they are saying a "rant". Actually, since you don't address anything in your comment, one could call that one a "rant" as well.
- Macha 3y agoI thought we would have learned for platforms not to facilitate bounties for non-participating projects after the tip4commit/mitsuhiko drama of years past: https://github.com/tip4commit/tip4commit/issues/127 https://github.com/tip4commit/tip4commit/issues/127
- zcesur 3y ago> competition at the expense of cooperation We've seen contributors author PRs together and split bounties. Also contributors in the Zig thread were actually trying to collaborate on a solution (comments were deleted) > Instead of scouting for a suitable candidate Open calls have faster turnaround & lower overhead > clear contract ... payout Sometimes design & implementation is not decided and spec'ed in advance and multiple perspectives & sometimes PoCs are required, at which point the maintainers can choose a plan of action and assign a developer without much duplicate work. That's classic OSS dev with or without bounties. https://news.ycombinator.com/item?id=37543536 https://news.ycombinator.com/item?id=37543536 there's more replies here that I agree with -- I also suggest you checkout the discussions deleted by Zig for a full perspective https://pastebin.com/nDA0LD3N https://pastebin.com/nDA0LD3N As a matter of fact the initial convo on the thread proved contrary to the every point made regarding competition and "battle royal dynamics" as people attempting the bounty were actually collaborating. We've seen quite a few cases where people authored PRs together and split the rewards on Algora. In addition there was no "pressure on the development team to accept the winning submission" it was explicitly stated that the work did not need to be merged upstream, and that the sponsorship would be awarded as soon as the technical requirements were met. -- Ultimately, bounties are a tool. It's in maintainers' discretion whether or not to use it. The optimal design for a bounties platform is still a work in progress. We're two bootstrapped founders (one developer) figuring things out along the way, trying to give folks a good experience and trying to learn.
- NickGerleman 3y agoA company using React Native recently used bounties to solicit bug-fixes to RN issues their app was hitting. A lot of positives came out of it, and it did improve framework quality. There are challenges with the model though. More changes than not are high quality, but some aren’t, or are just inherently risky, and it’s especially tricky to discern when first time contributors touch systems that might no longer have an active maintainer. Unlike someone employed full-time, there isn’t the opportunity to establish long term trust, and the contributor might not be around to support their change if something goes wrong. A lot of changes fell through the cracks, or needed maintainer time that wasn’t there, which creates a bad situation where someone could have done great work, but isn’t getting paid. Knowing that someone is losing money if you don’t accept a PR can also trend towards guilt-inducing as a maintainer.
- templix 3y ago> or needed maintainer time that wasn’t there That's my experience with bounties: someone does the job because they get paid, not because they have a particular interest in the issue, and then they instantly move on, leaving the submission to rot. I agree with ZSF here.
- irf1 3y ago1) clickbaity title 2) the project never created or rewarded an open source development bounty 3) the post promotes bug bounties from a platform written in Zig that sponsors Zig seems legit
- bawolff 3y agoIn a previous job i helped manage a security bug bounty program. It was worth it in that setting, because the 1% of reports that were real justified the time spent going through the mountain of BS. Security bugs are so bad we were willing to sink a lot of effort into finding them. 99% of reports were incoherent garbage often made by rude aggressive people who were difficult to deal with. And to be clear, those 1% real reports weren't neccesarily good. They were often poorly explained. Sometimes the reporter didnt even know what they were reporting and had just happened to stumble on something interesting. Now security vulns and actual code is really different but my experience with security bug bounties makes me think a code one would be an unmitigated disaster. All the bad parts of security bug bounties matter so much more when it comes to code. In development, getting working code is barely half the battle. Bad quality code can be worse than no code. Making sure the code is not buggy is hard, making sure the code integrates well is hard, making sure its well tested is hard. Even ensuring it follows the not automatically testable coding conventions is important. Bounties would just incentivize low quality drive by submissions, which helps nobody. Sorting through them would be a real cost that would outweigh any small benefits.
- throwawaymaths 3y agoTfa specifically excludes security bounties because there are often multiple security bugs, it's a discovery bounty and not a "compete for this one thing" scenario.
- bawolff 3y agoWell i agree with them but for different reasons. I also disagree about duplicates being a non issue in security bounties though. Its super common for multiple people to find the same bug. Even worse, security bugs are often kept secret so you dont know that someone has you just have to trust the project that it really is a dupe. Its one of the main reasons why sec bug bounties are unfair to researchers imo.
- deleted 3y ago[deleted]
- 3y ago
- lemper 3y agoother people have said that it's a different things compared to "anyone who fixes this problem in this free software, I will give them certain amount of real world monies." what happened in the article is: "anyone who implements our product in this free software, I will give them certain amount of monies. I haven't talked to the maintainer of this free software whether our product has net benefit or not to this project, though. so you have to fight your way against the maintainer to get it implemented." so yeah, I don't like zig and don't care about its people. but to me, the bounty giver shits on zig dudes to put it bluntly.
- laserbeam 3y agoI'm curious what led to this article. I don't disagree to the contents, but the story that led to it sounds more interesting and now I want to read about it. First, not all zig news gets posted on the official ziglang blog, quite little of it makes it there actually. There's zig.news, stuff gets posted to the discord, there's sycl... quite a lot of news comes through other channels. So the fact that this made it here is intriguing. I'd expect this to be part of an FAQ in on the "Sponsor the ZFS" section, rather than it be news. Second, development bounties are something that zig has never done. I can't remember of a time that zig offered that. Zig basically spends their money by hiring high value contributors (which I find a great approach). So, where's the fun drama behind this? I'd love to read it once and then enjoy my Sunday :).
- 38 3y agoIt's literally the second sentence of the article http://farside.link/twitter.com/wasmerio/status/1701168305103331701 http://farside.link/twitter.com/wasmerio/status/170116830510...
- laserbeam 3y agoYeah, I screwed up at "reading". Thanks X_X
- wyldfire 3y agoThe "Support WASIX" [1] link shows up there, that's what led to this. [1] https://github.com/ziglang/zig/issues/17115 https://github.com/ziglang/zig/issues/17115
- laserbeam 3y agoCan't believe I didn't spot that X_X
- deleted 3y ago[deleted]
- Ensorceled 3y agoYears ago we had a pretty critical issue in an open source project that we were dependent on. I looked into fixing it but it was pretty complex to even figure out the real cause. We reached out to the primary contributor and offered them money to fix. They countered with a largish donation to the project, we agreed and 5am the next morning there was a patch that got us up and running. Not sure a bounty would have helped us here.
- j16sdiz 3y agoI think the article was about "outsiders" offer bounty to other "outsiders" to work on arbitrary projects. These were once very popular in form of "we support oss in general, you can get $10 if you get any PR merged to any of these projects"
- Ensorceled 3y agoBounties are offered to the community at large and can be jumped on by anyone. I think a “bounty” that is offered just to the current contributors is less of an issue. But, oh man, that “get a PR merged” campaign was a disaster.
- bhouston 3y agoI done bounties on some open source projects and it worked out well. The contributors made great contributions and the owners of the projects reviewed them. It was a great way of getting a project to move faster. The project and contributions required a high degree of skill. And it also wasn’t a super popular project so it didn’t attract a lot of competition.
- matsemann 3y agoI think bounties can work. But it's important that the work being bountied comes from the project itself or at least is approved by the maintainers.
- HWR_14 3y agoI think a lot of their issues with bug bounties only apply if the project is pretty popular. If it increases the number of developers working on an issue/feature from 0 to 1, that's a win. Their analysis is why it's bad to go from 1 to many.
- syrusakbary 3y agoI respectfully disagree with the take that Bounties damages Open Source Projefts, which I also respectfully communicated to the Zig leadership team. After my communication they banned me from participating in their community (I quote from them "You're not welcome anymore on our GH repo nor any other community managed directly by us."). For those interested, we moved the sponsorship work to the Wasmer repo, so those who want to work on it can do it freely. https://github.com/wasmerio/wasmer/issues/4218 https://github.com/wasmerio/wasmer/issues/4218
- deleted 3y ago[deleted]
- ismailadi 3y agoSorry, but in my opinion you are in the wrong here. You can't just offer money and rush people for something to get merged in another open source project without even previously discussing it if the authors of that project want it in the first place. Just my 2 cents.
- syrusakbary 3y agoIt was not required for the PR to be merged upstream for the bounty to be awarded. This was explicitly stated in a comment in the original issue that for some reason the Zig leadership decided to remove
- ismailadi 3y ago(you've deleted your previous comment that I replied to) But then why did you open an issue in the Zig repo and even marked it as "Bug", while in your repo you added the "Enhancement" label? Just admit that you've communicated it poorly and move on.
- syrusakbary 3y agoHave you tried creating issues on the Zig repo? External contributors can’t select the labels of an issue. New issues get automatically tagged. In the Wasmer repo we can obviously choose the proper label just because we have the permission to do so
- kazinator 3y ago> Bounties foster competition at the expense of cooperation. If the task would get absolutely zero attention without a bounty --- what cooperation? Conversely, in a situation in which an an external party is motivated to work on something for free, let alone multiple external parties, why would you think about throwing money at it?
- zamadatix 3y agoI think the article does a good job in then showing ways it's not necessarily that the act of funding something removes existing cooperation in all cases, rather of the ways to fund something holding a bounty will foster competition at a loss of not fostering cooperation instead. For the second question: you may wish to increase time allocation to a project. Showing up with a fat wad of cash doesn't guarantee something can be done faster but if it'd make a bounty do it faster it'd almost always make the standard development process faster too.
- zcesur 3y agoHey HN, I'm one of the creators of the tool [1] that was used to post this bounty Normally it's the maintainers who create the bounties using our Github app, however in this case our experimental "community bounties" feature was used by Wasmer to create a bounty in someone else's repo (Zig). I think that's where everything went wrong We have updated the feature [2]. Community bounties are now by default shared privately with the maintainers only, and maintainers can decide to complete the bounties themselves, share them with the contributors, or discard them. That way community bounties are never intrusive to maintainers' time, roadmap & governance while also acting as a sponsorship if accepted We're sad to see our tool enabling this drama and hope the feature update will prevent this from happening again [1]: https://algora.io https://algora.io [2]: https://algora.io/bounties/new https://algora.io/bounties/new
- deleted 3y ago[deleted]
- syrusakbary 3y agoWe moved the sponsorship to the Wasmer repository, even though the work will need to be in Zig codebase: https://github.com/wasmerio/wasmer/issues/4218 https://github.com/wasmerio/wasmer/issues/4218
- Macha 3y agoThis seems to have all the same issues of pressuring the maintainers to accept your feature by making them responsible for denying a payout to a third party, even if the feature doesn't fit their codebase. Honestly, continuing this push, more than anything else in the events so far, makes me distrust wasmer's intentions.
- syrusakbary 3y agoHave you read the issue and other comments on this thread? We explicitly stated that the work would not be needed to be merged upstream for the bounty to be rewarded (a comment that for some reason the Zig team decided to delete)
- r053bud 3y agoIt’s ok, I prefer to hold on to my 0Days for when I might need them ;)
- deleted 3y ago[deleted]
- guilhas 3y agoOn a side note I am starting to think that the Zig leadership has some trouble with community management/collaboration Creator Of Zig Leaves Twitter and Reddit | Prime Reacts https://youtube.com/watch?v=8nxrHLQ_YQk https://youtube.com/watch?v=8nxrHLQ_YQk Reminds me of the GrapheneOS saga Both great projects. Zig looks like one of the most promising languages Maybe bounties are not ideal, but the entire open-source financing/collaboration model is still a bit green in general
- kristoff_it 3y agoI'm in charge of managing the community and what you're seeing here is a reflection of the fact that we care about our community and that more in general we know how to play the open source game. https://kristoff.it/blog/the-open-source-game/ https://kristoff.it/blog/the-open-source-game/
- escape-big-tech 3y agoKelley and Cro argue that bounties foster competition at the expense of cooperation. But isn’t it through competition that we Escape Big Tech’s clutches? Without competition, we’d all be slaves to the monopoly of Big Tech, a corporate monolith driven by surveillance capitalism. Competition brings innovation and diversity, giving each of us the tools to fight against centralized power. Bounties create an environment where developers are incentivized to solve problems creatively and help users Escape Big Tech through faster development and better solutions. Cooperation and competition can coexist. In fact, they must coexist if we are to Escape Big Tech. The FOSS community is not a utopia; it’s a battleground. And in a battle, we need all the weapons we can get. Bounties are one of those weapons. The FOSS space thrives when there is a race—not just against time, but against mediocrity. Bounties create an environment where developers are incentivized to push their boundaries, leading to faster development cycles and better software solutions. To argue against this is to undermine the essence of free-market capitalism, a realm devoid of governmental intrusion and packed with individual liberties. But also, one aspect largely absent from the original blog post is the financial sustainability of being an open source developer. While the love for the craft and the mission to Escape Big Tech might be enough to fuel initial enthusiasm, the reality is that developers need to eat, pay bills, and sustain their lives. If someone aspires to be an open source developer as a primary occupation, financial backing becomes non-negotiable. Bounties, donations, and sponsorships serve this very purpose—they are not just incentives for competition, but also a means for livelihood. Rejecting these financial channels out of an idealistic vision of cooperation is not just impractical but dismissive of the economic pressures that developers face. Let’s not forget, FOSS is an open market where both ideas and resources should flow freely. Monetary incentives can co-exist with the altruistic goals of the community. It’s a balancing act, but one that serves both the ideological and material needs of the FOSS world. For those of us aiming to Escape Big Tech, these financial pathways are not just welcome; they are essential.