forgejo/discussions
49
43

Should Forgejo-the-org be helping coordinate a feature bounty program? #68

Closed
opened 2023年10月06日 00:52:03 +02:00 by earl-warren · 4 comments

One lightweight approach:

  • add a "sponsored" issue tag
  • set up an Open Collective with Open Source Foundation as the fiscal sponsor with a 'sponsored features' or 'bounty' sub-project
  • encourage people who want to monetarily support a feature to state what they've donated to that project and link to the public transaction in a comment, noting that it is not refundable and no guarantee the feature gets in (or in exactly the way they want)
  • encourage people who contributed to resolving the issue to submit an invoice for (a portion of) what has been pledged, and link that in a comment

Followup of @mlncn post forgejo/governance#34 with their permission

One lightweight approach: - add a "sponsored" issue tag - set up an Open Collective with [Open Source Foundation as the fiscal sponsor](https://opencollective.com/opensource) with a 'sponsored features' or 'bounty' sub-project - encourage people who want to monetarily support a feature to state what they've donated to that project and link to the public transaction in a comment, noting that it is not refundable and no guarantee the feature gets in (or in exactly the way they want) - encourage people who contributed to resolving the issue to submit an invoice for (a portion of) what has been pledged, and link that in a comment --- Followup of @mlncn post https://codeberg.org/forgejo/governance/issues/34 with their permission

@mlncn do you have pans to work on implementing that idea?

@mlncn do you have pans to work on implementing that idea?

I like the idea of bug or feature bounties, but we also need to be very careful in how it is implemented. I recommend reading https://ziglang.org/news/bounties-damage-open-source-projects/ to see how it can possibly lead to negative outcomes.

We should ensure that any bounty system, if implemented, does not:

  • create duplicated effort by people competing for the bounty rather than collaborating

  • create an imbalance where people with money have greater influence over the project than people without money

With that said, I always welcome more funding to free software. We just need to be careful in how we implement this so that we produce positive outcomes.

I like the idea of bug or feature bounties, but we also need to be very careful in how it is implemented. I recommend reading https://ziglang.org/news/bounties-damage-open-source-projects/ to see how it can possibly lead to negative outcomes. We should ensure that any bounty system, if implemented, does not: - create duplicated effort by people competing for the bounty rather than collaborating - create an imbalance where people with money have greater influence over the project than people without money With that said, I always welcome more funding to free software. We just need to be careful in how we implement this so that we produce positive outcomes.

I don't have plans to work on implementing this idea, but i can give support on using OpenCollective.com and help review what we write about this— as rome-user is getting to, a lot of doing this well is setting expectations and then active connecting when people do express interest (and that's the part i'd be terrible at).

I don't have plans to work on implementing this idea, but i can give support on using OpenCollective.com and help review what we write about this— as rome-user is getting to, a lot of doing this well is setting expectations and then active connecting when people do express interest (and that's the part i'd be terrible at).
Owner
Copy link

Since no one has worked on this idea, I think it can be closed. Other means of sustainability have been created, and especially the steady income via Liberapay is probably the best.

Since no one has worked on this idea, I think it can be closed. Other means of sustainability have been created, and especially the steady income via Liberapay is probably the best.
Sign in to join this conversation.
No Branch/Tag specified
No results found.
No results found.
Labels
Clear labels
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
forgejo/discussions#68
Reference in a new issue
forgejo/discussions
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?