This repository tracks projects, initiatives and chunks of libp2p work that are (or may become) incentivized, for enthusiastic OSS contributors to pick up and tackle.
Refer to the issue tracker to browse what's being funded and/or discussed, and what's the status of proposals. Explore the labels for quicker navigation.
This repository tracks projects, initiatives and chunks of libp2p work that are (or may become) incentivized, for talented OSS contributors to pick up and tackle.
Objects of devgrants include: protocol implementation, tooling implementation, research, testing, optimization, etc. They may target one or more libp2p libraries, or they may be universal efforts to advance the entire ecosystem.
We track project proposals as GitHub issues, and specifications as markdown documents. To make browsing easier, you can find the latest project statuses and discussions in this repo's issue tracker.
Issues are categorized along various axes using labels:
The libp2p networking stack is becoming a public good. Major large-scale projects like ETH2, Filecoin, Polkadot, IPFS, Cosmos, etc. are adopting libp2p as a foundation for their networking layers.
Collaboration in the p2p space is indispensable to build truly unstoppable, future-proof p2p networks. All these projects share the motivation to propel libp2p forward towards higher robustness, maturity, and feature richness.
This repo serves as the junction between those communities to propose, enumerate, discuss, and agree on jointly funding crucial, substantial chunks of work that, when addressed, would benefit various actors synergystically, or even the entire ecosystem altogether.
Note: how devgrants are actually allocated, contracts signed and payments settled is out of the scope of this repo. This may happen through hackathons (e.g. ETHBerlin), privately, or eventually via some kind of [Decentralized Autonomous Organization] (how cool would that be š).
Each proposal/devgrant is tracked in a dedicated issue. The [issue tracker] indexes and tracks the status of project proposals and devgrants. It also serves as the discussion forum.
Specifications live in markdown documents, with their filenames referencing the devgrant by GitHub issue number.
This is all new and we're still figuring out the process and details, so bear with us :-)
Submitting a project proposal is easy. It consists of filing an issue, and an associated PR, following a simple template.
Here's the how-to:
TEMPLATES/000-project-proposal.md
to
the root of your fork.
000
with the number of the placeholder issue
you created above.That's all! Here's what happens next:
Watch this repo to stay up to date with project proposals and to engage in the discussion as potential grantees.
For questions or feedback, contact: @raulk.
Dual-licensed under MIT and ASLv2, by way of the Permissive License Stack.