Bounties system setup & wiki description

[klokan]

Propose board the bounty system.

Perhaps something like:
Direction with quarterly budget - to be approved by board.
Coordinator approves bounties - and suggest budgets
Maintainers suggest bounties

Fix bounties size ($100, $250, $500, $1k, $2k, $3k)??

Collect who is using bounties how.

[klokan]

I kind of like the https://docs.opencollective.com/help/contributing/development/bounties with labels on github issues - and instructions in github repo templates.

There is also:
https://www.boss.dev/
https://bountysource.com/
https://gitcoin.co/

[wipfli]

https://github.com/topics/bounties

[HarelM]

I like the concept of githib label for bounties. Super simple to setup, easy to search and see.

[HarelM]

We can/should use t-shirt sizes and not money, i.e. small, medium, large XL, etc...

[wipfli]

Set up categories and decide on allocation with Governing Board.

[wipfli]

The current solution at https://roadmap.maplibre.org offers everything we need:

• card format with topic title and a visual
• voting system (people provide email address when up-voting)
• life-cycle stages
  • under consideration
  • in progress
  • released

The current solution uses MapTiler's productboard account, thanks @klokan for letting MapLibre use MapTiler's resources.

I propose that we get our own productboard account, it is USD 140 per year. https://www.productboard.com/pricing/ If there are no objections I will get us an account and set up the roadmap board by Thursday, Nov 3rd, 2022 hopefully.

[klokan]

Portal starts at $80 / month plan - not at $20… It is not ideal for open-source community project IMHO Voting with GitHub account would be better. For the costs - we could even develop open-source HTML+Next.js GitHub API backend based web roadmap - on top of Issues - showing an image from the issue description in a responsive layout similar to current roadmap.maplibre.org - with tags for bounties for example… Next.js hosting is free on Cloudflare now BTW

On Wed, 2 Nov 2022 at 13:44, Oliver Wipfli ***@***.***> wrote: The current solution at https://roadmap.maplibre.org offers everything we need: - card format with topic title and a visual - voting system (people provide email address when up-voting) - life-cycle stages - under consideration - in progress - released The current solution uses MapTiler's productboard account, thanks @klokan <https://github.com/klokan> for letting MapLibre use MapTiler's resources. I propose that we get our own productboard account, it is USD 140 per year. https://www.productboard.com/pricing/ If there are no objections I will get us an account and set up the roadmap board by Thursday, Nov 3rd, 2022 hopefully. — Reply to this email directly, view it on GitHub <#125 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAOPFG5RULHJK3FZ7W3IGDWGJO27ANCNFSM6AAAAAAQZ3E45A> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- *PETR PRIDAL* CEO Zug, Switzerland +41 (0)41 511 26 12 www.maptiler.com <https://www.maptiler.com?utm_source=transactional&utm_medium=email&utm_campaign=2022+%7C+General+%7C+Brand&utm_id=2022+%7C+General+%7C+Brand&utm_content=footer+%7C+link> <https://twitter.com/maptiler/> <https://www.facebook.com/MapTiler/> <https://www.linkedin.com/company/maptiler/> <https://www.instagram.com/maptiler/>

[wipfli]

Thanks for the feedback. Yuri and I discussed the implementation of the Bounty feedback system yesterday and we came to the conclusion that we would like to keep the barrier for people to participate as low as possible. The best way to achieve this in our opinion is to use GitHub Discussions. People are already logged into GitHub and they just need to press the green button to suggest a new Bounty and they can up-vote proposed Bounties with a +1.

[wipfli]

https://www.boss.dev/ uses their own payment system. I would like to do everything via OpenCollective so boss seems not an option.

[wipfli]

https://bountysource.com/about/fees/ has a 10 percent fee which they don't explain well. We already pay OpenCollective 10 percent, so let's not use that...

[wipfli]

https://gitcoin.co/ I don't understand what it is, but it also seems to be not using OpenCollective.

[wipfli]

I suggest we start with these t-shirt sizes:

• S: $100
• M: $250
• L: $500

Then we can still do:

• XL: $1k
• XXL: $2k
• XXXL: $3k

[HarelM]

In continue to the example here: #133 I'm not sure managing the bounties here is the right solution.
My perspective is as follows:
Every repo has its issues.
We can take an issue and add a label to it to signal that this issue is now a bounty.
When opening a PR to solve this issue and this PR is merged and the issue is closed, we know that the bounty should be paid.
Every repo contributor can search for bounties in the relevant repo.
The only problem I see with this approach is that we can't see all the bounties in one place without implementing something to query all the repos, but I have a feeling something like that exists, or is very easy to do.

[wipfli]

The GitHub API might help us query all the open bounties and show them in a nice overview website as @klokan suggested above.

[wipfli]

I think the approach of managing Bounties in the respective repo works well for MapLibre GL JS and MapLibre GL Native, these probably will be the "Core Projects" in the definition of #132. If we define which projects are "Supported Projects", then they can also use the same Bounty template as the core repos.

[wipfli]

I just want to make it clear for people how they can suggest a bounty, how they can vote for one, and how we will decide and approve bounties.

[wipfli]

I guess we can document the rules for the bounty system here: https://github.com/maplibre/maplibre/wiki/Bounty-System and then then everyone will make sure that the same process is followed in the different repos.

[HarelM]

Sounds good to me.

[wipfli]

are the labels we could use

[wipfli]

The stages could mean the following:

• voting: Initial stage after someone submitted a suggestion for a Bounty. We will give people time to share feedback if they think this is a good idea. They can upvote the Bounty with 👍.
• looking for taker: A maintainer found that the Bounty in the voting stage received sufficient support and approves it. Now it is in the looking for taker stage where people can apply to take the task.
• taken: Once a person has claimed the task, they are assigned the GitHub Issue and the taken-label shows that this Bounty is now being worked on.

[wipfli]

Note that people need to be cleared as Developers to be able to work on Bounties. Like this, we know who they are, where they live, and that we can pay them with OpenCollective. The Developer role is described here: https://github.com/maplibre/maplibre/wiki/Developer-Role

[wipfli]

I suggest we launch the Bounty system in the budget period Dec, Jan, Feb, i.e., after the next Advisory Council which is scheduled for Wed, Nov 23rd, 2022.

[wipfli]

Let's start with something and iterate on that. The Governing Board allocated USD 50,000 for the next 3 months on Bounties.

[wipfli]

Proposal: Coordinator allocates a small fraction of all bounties to get the system started. Ask Governing Board for approval.

[wipfli]

We could start with a framework for collecting input and ideas from people. This could be as simple as a GitHub discussion...

[wipfli]

Let's collect some ideas with https://github.com/maplibre/maplibre/discussions/156. We should announce this feedback channel on Twitter and LinkedIn

[wipfli]

Pick 3 to 5 most important directions from https://github.com/maplibre/maplibre/discussions/categories/bounties-cross-project-directions?discussions_q=category%3A%22Bounties+-+cross-project+directions%22+sort%3Atop and suggest to the Governing Board a split of the allocated USD 50,000 on Bounties in the budget period December - February on the directions. Goal is to have the allocation on directions published by the end of the next sprint.