“Open source code has enabled trillions of dollars to be generated by software companies that use it, but the communities that develop that code typically haven’t had a means to capture much of the value directly.” - Jesse Walden
Open source software is the backbone of the internet. A movement that started in response to the rise of proprietary software, publicly-available code soon became the foundation on which GAFAM built their powerful platforms. Today, many significant open source projects are backed by big tech. While the pros and cons of its involvement are highly debatable, it’s hard to ignore the influence these corporations have had on the open source ecosystem.
If you think about it, the very fabric of human coordination at this point is hierarchical. Hierarchy successfully allowed a few individuals to assert power and authority to control the coordination of large groups of people. Since then, it has become the de-facto form of organization for most institutions.
This reality is reflected in the way Big Tech has designed the internet. For example, centralized platforms like GitHub have made it easy for developers to produce and distribute open source software. However, convenience comes at a price — freedom. Access to your GitHub account and repositories can be banned or limited at any time, leaving your developer identity, work, and reputation confined within a walled garden.
Radicle is an open source and community-led project. One priority of the project is to support the development and growth of collective community infrastructure that can be employed to further decentralize the project.
“Community infrastructure” includes the project’s content hubs. While radicle.community is the official forum for discussions related to Radicle development & governance, our website blog is also used to distribute project-wide content and announcements.
As the project grows, Radicle’s community team sees a need to create more accessible channels for content contributions from the Radicle community. We believe that as an open source project, not only should anybody be able to contribute blog posts, onboarding guides, tutorials, and other content.
On Monday, January 10th, the Radicle community voted to fund the first wave of the Radicle Grants Program. With six months and a $1M budget, the Radicle Grants Program will fund contributions that improve the Radicle ecosystem, and in turn, improve tooling for decentralized, open-source collaboration.
With these Treasury-funded community grants, we believe we are planting the first seeds of will grow to become a new model for funding open source. The aim is to directly support open source initiatives that help grow the Radicle product, the Radicle community, and the greater FOSS and Web3 community at large.
In essence: funding open source to grow open source 💫
An 💎 Ethereum protocol for generating 📮 recurring income with subscriptions and memberships
Drips is a new Ethereum protocol and social network that allows anyone to generate continuous income, without relying on bank accounts or extracting platforms.
At its lowest level, Drips allows any Ethereum user to stream funds periodically to any other Ethereum user, while also enabling collecting from multiple streams with just a single transaction.
A step-by-step guide for onboarding your DAO to Radicle with orgs. Join the Radicle Community Discord if you have questions or need support, and follow @radicle on Twitter for project updates & announcements.
Radicle is a Web3 network for software collaboration. Radicle provides truly decentralized infrastructure for developer communities, enabling anyone to fund and manage software using NFTs and multi-sigs. It features an opt-in Ethereum integration that enables unique global names, decentralized organizations, and experiences that help maintainers sustain their open-source work. A more detailed overview of Radicle can be found here, and more technical details about the protocol here.
At Radicle, we see DAOs as a necessary part of the emerging Web3 stack. That is why we built Radicle Orgs, a decentralized code management tool for DAOs coordinating the development of open source software (see more here👇)
By Shelby Steidl & Abbey Titcomb
2021 was the year the Radicle project introduced the Radicle token (RAD) - its native governance token - making it the first open-source, community-led, and self-sustaining network for software collaboration. A major step towards the decentralization of Radicle, RAD has enabled a number of Ethereum-based features as well as the communal ownership, collective governance, and long-term sustainability of the Radicle network. The first year of governance held some exciting new developments for Radicle as well as provided a lot of learning opportunities for the core team. This is a summary of the most notable developments and summary of important proposals.
The Governance Working Group
The creation of the Governance Working Group has helped grow the capacity of our governance capabilities and bolstered expansion of governance resources. The Governance Working Group has primarily consisted of Abbey Titcomb, a core Radicle contributor, and Shelby Steidl, a governance facilitator, as well as key partners such as Larry Sukernik and Derek Hsue from Reverie. The Governance WG is in charge of facilitating and coordinating the governance process for the Radicle community. The governance team launched the Radicle Governance Hub, a collection of all important information and resources needed to get started with Radicle governance as well as outlines the Radicle governance process. We also launched the Radicle Governance Twitter page which acts as a ticker account for all important governance-related announcements and reminders.
The Radicle project has released its native governance token, making it the first open-source, community-led, and self-sustaining network for software collaboration.
Throughout the last decade, open source has become a standard for software development. Sharing code freely and publicly has made it drastically cheaper and easier to build software—and tech innovation is surging as a result.
Code hosting and collaboration platforms like GitHub and GitLab have contributed heavily to the growth of open source by bringing it to a mainstream audience. They defined standard vocabulary and behaviors, made git accessible to a greater audience, empowered social coding, and created global communities of developers. It is an undeniable fact that they have completely changed the way people write code.
As the status quo for code collaboration, these platforms also host the largest repositories of open source development made up of not just code, but issues, pull requests, reviews, and comments. Even the social relationships—stars, likes, follows—exist solely within these platforms.
Behind every repository is a version control system—the most popular of these being Git, created in 2005 by Linus Torvalds for the development of the Linux kernel. Git marked the rise of distributed version control systems as developers realized the centralized model of SVN and CVS didn't scale well with the number of contributors. In fact, Git was only created when Linus’ free Bitkeeper license was revoked after a Linux kernel contributor tried to reverse engineer its networking protocols. Git brought distributed version control to the forefront and changed the way software is developed today.
Code collaboration platforms, or "forges", started building on top of Git: they introduced search and discovery, canonicity, and social collaboration (issues & code review) to Git-based workflows, albeit not always following the same distributed model that Git was designed for.
Radicle was designed to provide this same functionality while retaining Git’s peer-to-peer nature, building on what made distributed version control so powerful in the first place.
When coming to Radicle from a centralized code collaboration network like GitHub or Gitlab, users might be puzzled by Radicle’s unique social model at first. In contrast to centralized code collaboration platforms, on Radicle:
This post attempts to contextualize the Radicle social model, the trade-offs it makes, and how it differs from the models of well-known centralized platforms.