Hacker News new | ask | show | jobs
by WhatsCracking 513 days ago
I know this topic has been debated often (especially on HN) and has been controversial in terms of what's the best solution.

With the advent of AI, I believe this topic is getting more important and we need a solution to foster the growth of OSS ecosystem. Here is what we are thinking.

Challenges in the OSS (Open-Source Software) Market

- Contributions to OSS are primarily driven by goodwill, making it difficult for contributors to receive monetary rewards for their efforts. This often leads to the departure of key maintainers or a lack of contributors.

- As a result, even OSS projects with significant user bases and high utility face challenges in maintenance and sustainability, including security measures, dependency management, and collaboration with other projects.

- From the perspective of organizations and developers leveraging OSS, these issues present risks and reduce the efficiency of using OSS.

A Potential Solution: Voluntary Monetary Rewards from OSS Users

OSS users, as beneficiaries of the OSS ecosystem, can voluntarily provide small-scale monetary rewards (bounties, tips) to OSS maintainers and contributors in a convenient manner directly within GitHub.

- For OSS users: By attaching monetary rewards (bounties) of their desired amount to urgent or high-priority issues in the OSS they use, users can expect faster and more effective resolutions to these issues.

- For OSS projects with large user bases and high utility: 1) Maintainers can focus more on improving software quality without worrying about monetization. 2) Contributors are encouraged to actively participate, motivated by the potential for direct rewards.

- For the OSS ecosystem: Unlike the current donation or sponsorship-driven models, this approach enables a direct flow of funds from users (demand) to contributors (supply). This can have a positive impact on the entire OSS ecosystem by enhancing project sustainability and overall efficiency.

How it works

1. Every GitHub account is automatically assigned a Crypto Wallet (EVM address), eliminating the need to create an account on a separate service.

2. Any GitHub user can utilize their cryptocurrency to create a bounty for a specific GitHub issue or send a tip to a particular developer’s account. examples: - Bounty Creation: /bounty 10 $USDC, /bounty 0.1 $ETH verify - Tip Payment: /tip @xxx 3 $USDT

3. Bounties are deposited into an escrow account at the time of creation and are directly transferred to the contributor’s GitHub account once the payment conditions set by the creator are met. Tips, on the other hand, are sent immediately.

4. Contributors who receive bounties or tips have full ownership and control over their Crypto Wallet, allowing them to freely utilize the cryptocurrency at any time.

We would really appreciate any feedback or comments on our approach. Even better, would be helpful if you can partake in the survey as well (https://docs.google.com/forms/d/10TxDVcZhxbqPJPJ-VRzRNamePEO...)

Thanks!

1 comments

The main problem with this approach is that there’s a normal distribution of quality of contribution for OS but the community of OS users only benefits from the highest quality contribution. This is normally best achieved by the continuous contribution of the original author(s) who created or maintain the project, as they were the ones capable of designing a project complete and correct enough to achieve traction.

Most projects will actually deteriorate in overall quality if they accept average level contributors work, and certainly face harsh consequences if they accept below average contributions. Highly competent contributors demand higher salaries for their work which can’t be met by the limited funds available to OS, hence most high quality work comes from company sponsored OS or from people who have other means of financing their lifestyle outside of open source.

Thanks for the input. The potential decline in work quality is definitely an issue. We believe this can be mitigated by designing a system where:

1) The maintainer has the final say as to what gets merged. Hence those that submit subpar solutions won't be compensated.

2) As this system grows and more data is acquired, we can implement a reputation system based on a contributor's quality of submissions.