The "different point of view" here seems like you're determined to interact with their community in a way they've explicitly asked you not to [0]:
> Please don’t use bounties to incentivize Zig development.
They explained their reasoning extensively:
- Bounties foster competition at the expense of cooperation.
- Bounties are an utterly simplistic way of dealing with the business management side of creating software:
- Instead of scouting for a suitable candidate, you’re letting battle royale dynamics pick a winner for you, at the expense of everybody who’s going to lose the competition.
- Instead of creating a clear contract where you take on some of the risk, you implicitly put the entirety of the risk on the contestants (eg partial solutions don’t get any payout).
- Instead of allocating time and resources to proper due diligence, you instead penalize any form of thoughtfulness in favor of reckless action (eg a solution just needs to pass a test suite).
- Instead of planning for the full lifecycle of software, which also includes maintenance, you end up with a quickly bitrotting artifact that is of no practical use to anybody.
- Instead of spreading unease to all the people involved, it would be preferable you instead learned how to do business properly.
- On projects less radical than Zig, you might also put pressure on the development team to accept the winning submission, which, given the above, will probably not be the most well-thought-out and maintainable solution.
> Info: while ideally the PR should be merged into Zig master, is not a necessary requirement to receive the bounty. As long as a fork exists that fulfills the requirements laid out before, the bounty will be awarded
To an outsider, this looks like you slapped a new name on the exact thing the Zig team asked you to stop.
Do you feel your new request adaquately addresses the team's issues?
[0] https://ziglang.org/news/bounties-damage-open-source-project...