Web3 Association - Open source contributor funding experiment setup

[lovegrovegeorge]

Project Abstract

This is a research proposal to experiment with an open source contributor funding process. Developers in the ecosystem would be funded to help with developing the most impactful open source initiatives in the ecosystem. Contributors could work on new initiatives or improvements to existing open source solutions.

This funding process will trial a number of approaches from our funding analysis (https://funding.treasuries.co). This funding process and the approaches being trialled could become long term funding solutions for Polkadot if this experiment proves to be successful.

This proposal is for the setup of this experiment. A future proposal will be submitted that requests approval for the actual funding process once the experiment has been setup.

Grant level

• Level 1: Up to $10,000, 2 approvals
• Level 2: Up to $30,000, 3 approvals
• Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read the application guidelines.
• Payment details have been provided (Polkadot AssetHub (DOT, USDC & USDT) address in the application and bank details via email, if applicable).
• I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
• I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
• The software delivered for this grant will be released under an open-source license specified in the application.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
• [] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @lovegrovegeorge:matrix.org (change the homeserver if you use a different one)

[lovegrovegeorge]

Questions / some areas to discuss:

• Unknown funding amount until after voting stage is completed - The actual funding amount required cannot be stated until further into the setup of the experiment. Therefore this proposal could either stay in a draft state until that can be determined or it could be approved and merged and then updated in the future. The value used in the proposal so far is the maximum amount we could suggest for the experiment, however the actual value could be much lower depending on the final agreed experiment parameters.
• Confirming and agreeing on funding allocation after priority suggestions and contributor proposals are known - Our suggestion with this experiment is to discuss and agree whether the experiment should continue or not after seeing what priority suggestions and contributor proposals are submitted. This information will help with making an informed decision about the total funding to allocate to the experiment based on the funding period duration and the number of contributors that can receive funding.
• Vested DOT concern - The experiment would pay developers monthly once their contribution logs are approved. The main concern i'd have is around how long the vested delay of funding is as this could make it difficult for the participating developers that would have rent and bills to pay.
• Full-Time Equivalent on milestones query - The experiment would select developers to work full time for a set duration of time such as 4 or 6 months. I’m unsure whether the milestones FTE value should include these participating contributors in the number or if this value should only focus on the efforts required to operate the funding process experiment itself.

[keeganquigley]

Hi @lovegrovegeorge thanks for your comments. Happy to give my opinions below:

Unknown funding amount until after voting stage is completed - The actual funding amount required cannot be stated until further into the setup of the experiment. Therefore this proposal could either stay in a draft state until that can be determined or it could be approved and merged and then updated in the future. The value used in the proposal so far is the maximum amount we could suggest for the experiment, however the actual value could be much lower depending on the final agreed experiment parameters.

The committee most likely won't vote to approve a grant with an unknown funding amount, especially for this amount. I would recommend reducing the scope/cost to include only what you need to get started, and then you can always apply for subsequent follow-up grants. For example, the committee might be more inclined to approve just the first milestone of $3k to help you bootstrap the experiment setup. Then you might be able to better determine how much more you need.

Additionally, any ask greater than $100k needs to be voted on by the W3F council, in addition to the 5 approvals required to sign the grant. This could take a while, and might prove hard to get. Any changes down the line would need an amendment with the same amount of approvals. Whereas if you lowered it to a level 1 grant to get started, only 2 approvals would be needed to hit the ground running.

Vested DOT concern - The experiment would pay developers monthly once their contribution logs are approved. The main concern i'd have is around how long the vested delay of funding is as this could make it difficult for the participating developers that would have rent and bills to pay.

The DOT is vested linearly, on-chain over a two year period. Therefore a bit will unlock with each block, but yes the majority of it would be locked to start with.

Full-Time Equivalent on milestones query - The experiment would select developers to work full time for a set duration of time such as 4 or 6 months. I’m unsure whether the milestones FTE value should include these participating contributors in the number or if this value should only focus on the efforts required to operate the funding process experiment itself.

Yes I would recommend including these contributors in the FTE value, since they would be working full-time. Especially if their payment would be part of the total costs.

I hope these answers help.

[lovegrovegeorge]

Thanks @keeganquigley, I'll update the proposal this week

[lovegrovegeorge]

@keeganquigley I have updated the proposal to now focus only on the experiment setup phase. The the other milestones have been removed. The first milestone now focuses on capturing the communities priority suggestions about what open source initiatives could be the most impactful to work on and setting up the contributor proposal process so that I can invite developers to indicate their interest in the funding process. I have removed the voting stage part from the first milestone as voting should only happen if the funding experiment was approved and actually going to be executed. Voting would become the first thing that happens if a future proposal is accepted to fund the experiment.

Two points I'd like to highlight:

Funding experiment parameters
After executing this initial experiment setup process we should have some priority suggestions from the community and some developer candidates that are interested in participating in the funding process. I would look to suggest what I think is sensible in terms of funding process parameters in a subsequent proposal based on the priority suggestions and contributor proposals that have been submitted. I believe it could be valuable for us to discuss these parameters and any initial thoughts about them before the proposal is finalised and submitted for review. We could have this conversation in the comments of a future proposal.

Voting participants
If the experiment was approved then the selection of voters is an important part of the experiment. I would be very interested in members from the Web3 Foundation or Parity being involved in the voting process. Members from the Web3 Foundation are very familiar with their own idea funding process so participating in this experiment and providing their feedback should be very insightful. Another open source funding proposal that was shared to me recently could also have some of its members be involved in this experiments voting process to get further insights from them - https://polkadot.subsquare.io/referenda/1080. This experiment could operate fine with 5 voters similar to the other proposal I just shared. However a lot more insights and feedback could be generated using 10 to 20 voters, so I'd always prefer to increase the number of voters where possible. So my question is whether members of the Web3 Foundation would be happy to participate in this voting process? This is obviously assuming that the future funding proposal got approved. The voting process is designed to be simpler than idea funding so it shouldn't take up a large amount of time and the feedback given should be highly relevant and insightful.

[Noc2]

Sorry for the delay here. I'm happy to go ahead with it and share it with the rest of the team.

[keeganquigley]

Thanks for the changes @lovegrovegeorge much appreciated. To answer your question, I can only speak for myself, as I'm not sure what the interest level would be like for other W3F & Parity colleagues, but personally I'd have no problem participating in a survey or something similar. But I'm assuming you'd want to get input from technical fellowship members and community voters as well, since members of both W3F & Parity will have varying levels of participation in OpenGov.

I'm happy to approve it and see how it goes, but one minor comment about the milestone tables. The formatting is a bit funky here, for numbers 1 - 4, could you move these descriptions to the Specification column instead? Then you can give them a quick title on the left side. That way it will adhere better to our template and be uniform with other applications. Thanks!

[lovegrovegeorge]

@keeganquigley Yes I'm keen to include anyone from the Polkadot who is experienced with OpenGov, the technical fellowship or governance / funding / treasuries in general in the voting process. So i'll look to invite multiple people if they're interested after reaching out to many people.

I've updated the formatting as requested, also updated some of the spacing across proposal, should look good now after properly reviewing the preview!

What else do I need to do with W3F agreement / setup wise with this proposal?

I will reach out to the other open source proposal and look to start collaboration tomorrow to get that going. In terms of starting this proposal I would look to start it sometime next month. I started working on a new economic model recently that ties in very well with the work i've been doing for the last few years. It's taking my full attention over the short term until I can get a first version out next month to start getting feedback. Should be a good read, happy with it so far! After that is out, I would be ready to be full time on setting this up and reaching out to everyone I can in the ecosystem.

[keeganquigley]

Thanks @lovegrovegeorge I have one more comment:

Could you please define what "collaboration with Web3 Foundation" would mean in this case? Does this essentially mean you would send us surveys to fill out? As we don't typically provide any kind of technical support or partnership collaboration for the grants program.

In other words what would "finalizing the expirement parameters" consist of?

[lovegrovegeorge]

@keeganquigley Updated title to "Finalising proposal parameters" and added the parameters into the specification.

[Polkadot-Forum]

This pull request has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/bounty-proposal-open-source-developer-grants-program/9445/4

[keeganquigley]

Hi @lovegrovegeorge great, thanks for the changes and happy to see the forum post too. I'm willing to go ahead and approve it as well.

Before merging, we ask all grantees to complete KYC/KYB. Please submit for verification there before we can fully accept the grant. Thanks!

[github-actions]

Congratulations and welcome to the Web3 Foundation Grants Program! Please refer to our Milestone Delivery repository for instructions on how to submit milestones and invoices, our FAQ for frequently asked questions and the support section of our README for more ways to find answers to your questions.

Before you start, take a moment to read through our announcement guidelines for all communications related to the grant or make them known to the right person in your organisation. In particular, please don't announce the grant publicly before at least the first milestone of your project has been approved. At that point or shortly before, you can get in touch with us at [email protected] and we'll be happy to collaborate on an announcement about the work you’re doing.

Also, if you haven't yet, consider signing up for the Polkadot Alpha Program. The program offers plenty of resources for people building on Polkadot. Lastly, please remember to let us know in case you run into any delays or deviate from the deliverables in your application. You can either leave a comment here or directly request to amend your application via PR. We wish you luck with your project! 🚀