News for hackers. Stuff that matters.
Re:Bounties Damage Open Source Projects by rendaw on Sunday September 17, 2023 @06:34AM (#37543536)
So... 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 say 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.

Re:Bounties Damage Open Source Projects by kristoff_it on Sunday September 17, 2023 @07:33AM (#37543901)
> 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

Not exactly, the main issue we have with this thing is that it's a process that in the blink of an eye had multiple Zig contributors do duplicate work to implement a PR under implicit conditions that are completely skewed against the individuals.

The Zig project has spent a lot of time and effort in growing a community of contributors that is respectful and collaborative, and we don't appreciate startups trying to turn our community into Mad Max, especially when the same exact amount of money could have been used to move the endeavor forward in a more sustainable way.

It would have been trivial to post an offer to pay for have that PR implemented, interview a few candidates, pick one, offer a contract and have the PR delivered after the contractor maybe even takes a moment to polish it past "passing a test suite", on top of it being a nice starting point for a potential continued collaboration for eventual follow ups.

Instead we got duplicated efforts, stress and ultimately everything would have resulted in a rushed PR that then most probably would have been on us to clean up and maintain going forward.

Our way of leading development is more sustainable and one big reason why we have such a big contributor community.

We're not going to let startups burn our contributor community so that they can squeeze one extra tweet out of their moat-building efforts.

Re:Bounties Damage Open Source Projects by jadbox on Sunday September 17, 2023 @08:19AM (#37544264)
Thank you for the additional context. Is there any issue in principal with Zig supporting WASIX in the future (in a sustainable fashion)? Or is there any technical debate to just not support it?
Re:Bounties Damage Open Source Projects by kristoff_it on Sunday September 17, 2023 @08:28AM (#37544342)
Generally speaking we're open to support all kinds of platforms going forward.

We do have a roadmap and a series of priorities so adding new platforms is not our first priority right now.

That said, interacting with the Zig project is not just a matter of code. Software development, especially when it comes to open source, happens as a result of a delicate social process, and the impact on our contributor community does factor in our decision making.

Re:Bounties Damage Open Source Projects by epilys on Sunday September 17, 2023 @10:17AM (#37545308)
WASIX is not even a standard by the Bytecode Alliance, which makes the webassembly specs.
Re:Bounties Damage Open Source Projects by brighteyes on Sunday September 17, 2023 @12:02PM (#37546497)
To clarify, WebAssembly specs are made by the WebAssembly W3C community group here:

https://www.w3.org/community/webassembly/

Its true that many of those companies are also members of the Bytecode Alliance. But the W3C community group is where actual specs and standardization happen. That's where votes occur, and that's the Github organization in which they are published, and so forth.

Re:Bounties Damage Open Source Projects by fdjsfasdhkj on Sunday September 17, 2023 @08:54AM (#37544547)
> It would have been trivial to post an offer to pay for have that PR implemented, interview a few candidates, pick one, offer a contract and have the PR delivered

What's trivial about posting an offer, interviewing candidates, picking one, and making a contract?

Re:Bounties Damage Open Source Projects by kristoff_it on Sunday September 17, 2023 @08:58AM (#37544590)
You're right, it's not trivial, I take that back. It requires some effort from the company that is interested in having the work done, but why put that effort when you can toss 5k in the ring and watch the best candidate self-select at the expense of everybody else who lost.
Re:Bounties Damage Open Source Projects by fweimer on Sunday September 17, 2023 @08:01AM (#37544122)
> 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...

Maintainers may not want to determine who gets to feed their family, by choosing which contribution gets merged (either by deciding between competing implementations, or deciding which contribution to review). That's even more extreme than typical management tasks like bonus allocation.

Maintainers might also be worried that it turns open-source development in to a gig economy, with all the resulting problems. The Zig developers seem to alude to this, too.

I'm not sure if open source in general has a funding problem. The corporate takeover started in the mid-90s, and is fairly complete by now. If you look closely at some of the often-quoted examples for serious underfunding, it's more about disputes about prioritization, such as long term, bug-for-bug compatibility support vs ongoing development.

Re:Bounties Damage Open Source Projects by bdzr on Sunday September 17, 2023 @02:50PM (#37548175)
> Maintainers may not want to determine who gets to feed their family, by choosing which contribution gets merged (either by deciding between competing implementations, or deciding which contribution to review).

Aren't they making such a determination already by disallowing bounties altogether?

Re:Bounties Damage Open Source Projects by fweimer on Monday September 18, 2023 @08:03AM (#37555046)
No, the would-be contributors could work on something else. That's no longer about preferring contribution X from would-be contributor A over would-be contribution Y from non-contributor B.
Re:Bounties Damage Open Source Projects by candiddevmike on Sunday September 17, 2023 @08:29AM (#37544347)
I am testing a solution to the problem of funding open source through a custom license based off the AGPL, the Candid Public License: https://github.com/candiddev/cpl

The goal is to be ridiculously FOSS and require companies to do the same in order to use your project. If they don't want to embrace the copyleft aspect, they can purchase an exemption from it (see https://yaml8n.dev/pricing/ for an example).

In this model, the FOSS ecosystem can still thrive and build off of each other, and projects can negotiate license exemption to help sustain themselves.

Re:Bounties Damage Open Source Projects by HideousKojima on Sunday September 17, 2023 @09:36AM (#37544930)
Have you run your license by a lawyer to see if it's legally enforceable?
Re:Bounties Damage Open Source Projects by candiddevmike on Sunday September 17, 2023 @09:59AM (#37545135)
Yes? I had them help me draft it. Why wouldn't a license be enforceable?

You can write a license that has any kind of requirement in order to use it, such as "you must stand on one foot while using this software". If they don't agree, they can't use the software, and you can take them to court saying they aren't meeting the requirements of the license and must stop using the software.

When writing a license, or any kind of contract, you need to balance your rights and the folks using it. Licenses like MIT rob the creator of their rights, and no license gives the user no rights.

Re:Bounties Damage Open Source Projects by HideousKojima on Sunday September 17, 2023 @02:04PM (#37547752)
> Why wouldn't a license be enforceable?

No offense, but you might want a better lawyer if you don't think there is such a thing as an unenforceable software license. At a bare minimum, consider a license that requires committing a crime in order to be compliant with the license. And copyright law and contract law are far more complex than just that.