libp2p / libp2p/developer-meetings
[Protocol Design] Project OKRs
Open
Nobody has claimed this yet.
deep-dive
ready-to-schedule
unconf
- Dominant language
- No language data
- Stars
- 7
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
[Protocol Design] Project OKRs
Name: Organization and Governance of libp2p Project
Length (choose one): 90 min discussion meeting (40+break+40)
Title (~1-7 words): Organization and Governance of libp2p Project
Abstract (1 sentence up to a couple paragraphs, as you prefer): libp2p overall OKRs and how they connect with per-language OKRs.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue's abstract and meeting details; no files or tests are named. The work is to discuss overall libp2p OKRs and how they connect with per-language OKRs during the proposed 90-minute meeting, with the resulting decisions recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100