Open Source Contributors - A promising alternative to idea based fundi

We’ve recently finished a proposal outlining the opportunity to experiment with an open source contributor funding process. This suggested funding process could become a highly effective and scalable approach for Web3 ecosystems to more consistently generate impact.

The opportunity to experiment with a contributor funding approach is better highlighted by understanding some of the problems that exist with idea based funding:

  • For contributors, the proposal submission process can require a large amount of effort and time upfront for contributors to participate and then also handle the ongoing burden of proposal writing and budgeting complexities to get involved in an ecosystem. The structure and incentives of this funding process result in a reduced amount of contribution flexibility and income stability that can deter contributors from participating or limit their ability to easily generate high impact.
  • For voters, it is often highly complex to compare and select ideas effectively. Many voters lack the sufficient context, skills and experience required to be well informed and effectively participate in these decisions. The selection process can be highly time consuming and complex for the voters. Voters can rarely express their exact preferences with their voting decisions and also do not have enough accountability or incentives to be expected to spend a meaningful amount of time on voting to make more optimal and well informed decisions.
  • For Web3 ecosystems, ideas are often treated as ephemeral yes or no funding decisions rather than being a collaborative process that looks to discuss and explore different solution approaches. In larger funding processes it can also become easier for innovative ideas to be ignored due to being less well understood or known. The allocation of assets can also be more inefficient in situations where the allocated funds are not actively being used to generate contribution outcomes, this can increase the percentage of deadweight assets that are not being fully utilised at a given point in time.

To understand these problems in more detail you can review our analysis on the current funding landscape - Current funding landscape | Contributors

The good news is that most of these problems can be either greatly reduced or fully resolved! An open source contributor funding process can help with resolving these problems and also could become a highly reliable and effective process for maintaining and improving Web3 ecosystems over the long term.

Our proposal outlines the suggestion of experimenting with directly funding a small number of open source developers that would help with developing any open source initiatives - this could include improving any existing pieces of software used in the ecosystem or creating entirely new tools and libraries.

The advantages and long term opportunities for adopting a contributor funding approach are numerous. We’ve covered the advantages and opportunities of this suggested funding process in more detail in our proposal - Open source contributor funding | Contributors

You can alternatively watch our videos that cover the same content from our proposal:


Experimentation in Radix

The Radix ecosystem has a number of initiatives to fund different ideas and reward contribution in the ecosystem as shown on their grants page. Many of these funding processes are great for people that already have an idea to execute but most of them only partially help with situations where developers are keen to join the ecosystem but do not have an idea to execute at the moment.

Experimenting with an open source contributor funding process could simply mean adding in an extra form process to enable software developers to indicate their interest in contributing to the Radix ecosystem as a contributor. These individuals could then help with existing open source solutions being built or new ones that the Radix Foundation suggest to them.

The immediate opportunity with experimenting with a contributor focused funding approach would be that it would make it easier for software developers to indicate their interest in working in the Radix ecosystem. The Radix Foundation could then identify if there are any promising candidates that could be suitable for contributing towards any relevant initiative in the ecosystem. Contributor funding proposals could end up bringing in impactful talent that otherwise might not have got involved due to the more time consuming upfront idea proposal process. The idea process can make it more difficult for these individuals to just express their interest in working in the ecosystem. A contributor focussed process could provide a more collaborative path for identifying promising talent and matching them with ongoing work that could create impact in the ecosystem.


Experiment facilitation

If any ecosystem was interested in experimenting with this suggested funding process but doesn’t want to handle the process fully themselves I am eager to collaborate with them and help wherever I can with setting up and running any of these experiments that are focussed on contributor funding.

In either event, contributor funding experiments across many ecosystems could be highly beneficial for the wider industry. The outcomes from these experiments can be analysed to better compare the strengths and weaknesses of this suggested approach against the widely adopted idea based funding approach that we see being more widely used across Web3 ecosystems today. Analysing and documenting these experiment outcomes is something that we intend to work on at the Web3 Association!


Community discussion

General thoughts & feedback
There’s likely going to be many opportunities and problems that could be better explored and addressed. If you have any immediate thoughts and feedback please share anything below in a comment!

Organising a wider discussion
If there are already weekly or monthly organised discussion events that happen internally or publicly I’d be delighted to join one to listen to peoples different perspective about this funding process suggestion to better understand any of the different viewpoints around this approach. Alternatively I could also help to facilitate a one off discussion instead. Please share below if you would be interested in having a dedicated discussion in the near future about this suggested experiment.

Direct communication
If anyone would prefer to chat about this funding process suggestion with me directly then please feel free to reach out to me on Discord - lovegrovegeorge or Telegram - georgelovegrove. Otherwise just throw any questions in the comments below!

3 Likes

Very interesting and I think that something like this is vital. Before I do a deeper dive on your content I thought it might be useful to point at some existing work in this area.

Radix Works is offering a variety of developer incentive programs right now. Not community funded of course, but low hanging fruit for those pursuing a project concept.

Radix Name Service is in the process of bootstrapping their DAO which will support development of utility for domains that they service. Worth keeping an eye on.

CrumbsUp is hosting DAO voting and the like on their site and so has a running start on this space. It’s a useful place to go to find opportunities.

Dexter is an open source community-built front end for AlphaDex. It is a strong proof of concept for the proposition that the open source community for Radix can take on and achieve meaningful work.

Gitcoin V2 was the topic on the latest podcast released by The Defiant. Well worth a listen for people interested in this topic.

More later as I find some time… Carry on!

1 Like

Yeh the developer incentives are the closest thing they have currently to a contributor model. A good starting point for this suggestion I’ve made would be to invite devs in the ecosystem to be funded to work on different blueprint components that could be impactful for the entire ecosystem or other libraries and tools.

I imagine in the early stages it will make sense to offer some guidance from the Radix team on what blueprints, tools and libraries could be impactful based on their deeper understanding of the current state of the ecosystem. This layer of contributors can be seen as a collaborative effort that sits between the Radix team and application builders and supports both these groups of stakeholders in developing tooling, libraries and blueprint components. Looking forward to hearing your thoughts and feedback!