Note: this is a V2 after feedback on the proposal here.
The purpose of this proposal is to elevate the scope of Grants as the main body that manages the technical funding behind Radworks’s broader mission:
Radworks is a community dedicated to cultivating internet freedom. In a world that almost entirely relies on software, maintaining the resilience and health of the free and open source ecosystem is more important than ever. We strive to demonstrate the viability — in cost, labor, quality, and resiliency — of open-source software and its development. (1)
The Radworks Grant Org’s (Grants) goal is to fund development that enhances, expands, and enriches the Radworks ecosystem. This includes Radworks-specific third-party integrations, tooling, and alternative interfaces, as well as mission-aligned free and open-source projects.
Our Grants budget is:
- 250,000 USDC
- 100,000 RAD
Please see the “Timeline & Budget” section for more details on how funds will be allocated.
The Radicle Developer Tooling (RDT) emerged from the long-standing relationship with @Yorgos’s team – a community contributor who has worked on previous grants, such as IDE plug-ins for VSCode and JetBrains. Their focus has and will continue to be on integrating Radicle with external developer tools. The main goal is to lower friction for developers who want to integrate Radicle into their existing workflows which supports easier user onboarding (i.e. quicker adoption) as well as user retention.
The funding for the RDT team is an interim stopgap until they find further funding via their own upcoming Org Proposal from Q2 2024 - onward.
Hypothesis: IDE plug-ins with the most popular IDEs will help developers feel more comfortable integrating their existing workflows into the Radicle ecosystem. This will help with user onboarding.
IDEs are where most developers start writing their code and locally, where they do most of their organization of work. It is crucial to have plug-ins with the most popular IDEs so that developers feel comfortable integrating their existing workflows into the Radicle ecosystem. Without this, Radicle becomes a tough sell.
V1.0 dependency: this project does not have any significant dependency on Radicle v1.0
Hypothesis: Planning boards will help teams better facilitate work. The existence of planning boards will help with user adoption by showing potential users that more of their workflows can be supported within Radicle. And this should also help with user retention by keeping users plugged into Radicle across the lifecycle of their projects.
One of the missing features that has been highlighted by every single team that is has moved their daily workflow to Radicle is some kind of board view of their backlog items, so the team can better plan their work and roadmap.
This has been highlighted by:
- @zlatan by the Radicle Heartwood team,
- @daniel from the Radicle Web UI team and
- … Yorgos’s own team, as that has been something we have still not been able to migrate to Radicle from GitHub, as explained here in more detail.
As this is not on the Web team’s priorities / roadmap for 2024, an early prototype has been developed, as a kind of proof-of-concept of how we could independently work on a separate web app that could be integrated as part of the web interface and offer this missing functionality.
Hypothesis: CI integrations will ensure that Radicle can handle developers’ end-to-end workflow without needing to continue relying on other tooling. This should help with user acquisition and user retention.
Continuous Integration (CI) is the go-to paradigm for ensuring that code is properly tested, verified, and built. By adding CI tooling, we will ensure that one of the most important steps in software development workflows is integrated with Radicle. Without this, migrating to Radicle is a harder sale.
We have already funded basic research and development for CI integrations.
V1.0 dependency: this project does have a significant dependency on Radicle v1.0. Thus, we have listed it last. There may be nominal work in the beginning of the year, however, if there are any delays with v1.0, this project can and will be pushed out later.
The total budget for roadmap outlined above is estimated at 150,000 USDC.
Any unused budget will remain with the Grants multi-sig.
The Radicle Developer Tooling Team (Yorgos, et al) consists of 4 full-time, including 2 senior developers, and 3 part-time members. Comparing to our Core teams, this is roughly 3/5 the size, for 1/3 the cost. Comparing to industry, it is also a very reasonable (source: levels.fyi), where the budget would likely range between 650-750K. Apart from team wages, the budget also includes 25K USDC of yearly operational costs and 20K USDC to fund the team’s participation in Radicle offsites.
The Grants Committee will oversee the progress of the Radicle Developer Tooling Team. The team will be required to:
- Submit quarterly applications that outline specific milestones and updates on current progress
- Receive quarterly approval from the Grants committee for continued funding
- Participate in the reporting to Radworks during the quarterly community calls (independent to the Grants Orgs updates)
The Grants Committee will be responsible for reviewing the team’s progress with representatives from the Radicle Org on a quarterly basis. This is to ensure that the team’s proposed quarterly objectives are in alignment with the Org’s roadmap & goals.
The reason for earmarking this budget is to put this work in a solid position to allocate labor towards tools that we feel are essential for onboarding new users.
While we are allocating financial capital, we are also allocating human capital. Having this budget set aside will make sure that the people working on it have better confidence and ability to be full-time with the work, rather than haphazardly coming and going.
Grants can be funded retroactively (i.e. paid out after a product is already finished) or proactively (i.e. paid out before work is started).
All grants will be streamed to grantees via Drips.
This category focuses on projects that develop tools and integrations to enhance user’s experience with Radicle and/or Drips. The aim is to improve the interoperability between different software systems, streamline workflows, and provide utilities that aid in development, deployment, or monitoring. This could include developing plugins for popular platforms, creating APIs that connect disparate systems, or building tools that simplify complex processes. The emphasis is on making Radworks’ technologies more efficient and user-friendly.
150,000 USDC or 60% of the grants budget.
This category is aimed at funding the development of new interfaces for interacting with Radworks’ technologies, with a focus on increasing client diversity and enhancing technical resiliency. The goal is to broaden the appeal and accessibility of Radicle and Drips by encouraging a variety of use cases and user bases.
100,000 USDC or 40% of the grants budget.
The Grants committee includes all members of our Gnosis Safe multi-sig, found here.
In alphabetical order:
- Abbey (Radworks)
- Bordumb (Radworks Community; Lead)
- Nader (Aave/Lens, DevDAO founder)
- Nas (ex. Safe, ex. Radworks)
- Recruitment of Grantees: engage with core teams (Radicle, Drips, Governance) to create requests for proposal (RFPs) that address peripheral needs of core teams, which will be the foundation of grantee work.
- Reviewing Applications: reviewing applications in detail. If a committee member does not understand something, they are expected to be resourceful in learning or finding outside council on a topic.
- Reviewing Milestones/Completions: reviewing milestones/completed work in detail. If a committee member does not know something, they are expected to be resourceful in learning or finding outside council on a topic.
- Multi-Sig voting: participate in voting on and funding grants.
- Meetings: most work will be done asynchronously, but committee members are expected to actively participate on Discourse, community, and governance calls.
Members will be expected to participate in recruiting new grantees via RFPs directly from core teams (Drips, Radicle).
If a member fails to actively participate in voting, they may be removed from the committee. As this is all on-chain, it will be a fairly straightforward process. For now, we will expect members to evaluate and vote on at least 1 grant per 3 months. If there is no grant to be voted on, this will not apply for the 3 month period. Members may abstain from a vote, but must publicly declare their abstention.
The rules above will apply retroactively for 2023 voting, and will effective immediately upon approval of this proposal.
If a member is found in violation of our community guidelines, they may be removed from the committee.
In the case of committee members departing, we will use OtterSpace Badges to vote new members in. Voting will be available to any Radworks member and grantees who have completes >3 grants.
Grant applications are the primary documents that outline what is being worked on.
You can find more info on Discourse here: https://community.radworks.org/c/grants/24
All of our long-term documentation, including various templates (proposals, grant applications, RFPs, etc.), as well as organizational structure can be found in our repos below.
- Radicle: TBD
- GitHub: https://github.com/radicle-foundation/radworks-grants
Through Q2 2024, the Foundation Org will provide monthly financial reporting to Radworks on behalf of the Foundation, Radicle, Drips and Grants Orgs. Therefore, starting in Q3 2024, the Grants Org will publish monthly financial reports on Radworks-granted funds spent by the Grants Org.
The Grants lead (Bordumb) regularly gives updates on current and prospective grantees in all quarterly community calls and provides written quarterly updates on community.radworks.org.
Each grant-funded team will present quarterly progress seperately to the Org Lead as part of the quarterly community calls. They will also provide written quarterly updates on community.radworks.org.
- 100% of new features delivered
- 100% of tools tested by users
- 100% of tools get feedback from users
- 100% of grants paid out via Drips
- 100% of code delivered via Radicle
The primary goal with Radicle Developer Tooling (RDT) grants is to cover key integrations for Radicle code collaboration. These include integrations across the typical software development stack.
Starting from writing code in IDEs, to instant messaging for teams, continuous integration/development (CI/CD), these grants are aimed at making it easier for developers to plug Radicle into their existing workflows.
The aim is to make sure we have integrations across each part of the software development life-cycle, as shown below. So far, we are focused on the most basic components around Coding and Deployment of software.
Each tool we integrate with is generally prioritized by a combination of market share.
All costs will be spread out over 2024.
250,000 USDC for Grants
- 150,000 for Yorgos’s team
- 100,000 for other grants work
- 70,000 RAD for other grants work, where grantees are willing to take RAD
- 30,000 RAD for Grants Committee invoices
The analysis for 30,000 RAD for Grants Committee invoices is as follows:
- In 2023, the Grants Lead received 52,000 USDC worth of RAD (see here, here, and here)
- Over the past 2 years of Grants, we have been paying committee members based on hours of work. In analyzing this data, the Grants Lead has worked 7.5X more hours than others.
- Overall, we’d like to keep the “management fee” within 7-10%.
The Grants Org - also the “Grant Recipient” of Radworks, if this proposal is passed - hereby agrees to use the amount granted by Radworks in support of fulfilling the purpose outlined in the “Purpose” section above. The Grant Recipient understands and acknowledges that the awarded amount may be used only for this Purpose. Furthermore, any part of the grant that goes unused in the calendar year outlined in this proposal (for 2024) will either be returned to the Radworks Treasury (by March 2025) or rolled over into and applied towards the Org’s 2025 proposal and future grant from Radworks.
All assets will reside in one of two locations: Gnosis Safe or Drips. These will be used both for paying grantees and committee members.
Any remaining funds will roll-over into the 2025 budget.
Paying for Grants work is inherently risky. We do not know which projects will succeed in delivering work.
However, luckily with Drips, we can pause and completely stop Streams at will. In the event that a Grantee needs to pause work or stops working entirely for any reason, we will be able to either pause or stop the Stream.
Please see 2023 retrospective here: Grants Org Retrospective 2023