Contributors Guide

Who is a contributor?

A contributor is anyone who supports our Mission by actively participating in our Projects, co-editing research and publications, providing structured feedbacks, volunteering at events, or starting a whole new project.

Contributors are typically organized into Workgroups aligned with their skills and interests, each guided by one or more shepherds.

Frequent contributors have the opportunity to become Core Contributors and be rewarded for their contributions to open source.

Projects

Project is the basic unit of work by which we coordinate ourselves.

An example of a project is Research or Events or Privacy Explorer. Each of these top-level projects is a separate unit with its own autonomy and may have other sub-projects (such as a specific event or specific research report, etc.).

Every project is open for collaboration! Check our Projects registry

How to join a project: If you want to get involved in a project, you can either navigate the ones we are carrying on and do pull requests (see below) or write to the people leading it, the shepherds.

How to start new project: Publish and discuss a concept of your project in our Projects registry detailing the necessary requirements for initiation and maintenance, such as timing, funding, social media outreach, and design.

For any question or doubt don’t hesitate to dm us on Twitter or Signal.

Contributors Guide

Here is a list of our ongoing activities. Feel free to contribute on GitHub or DM Shepards expressing your willingness to commit for receiving instructions.

⎆Jobs

Shepherds: Adam, Mykola

• improve project
• test and find bugs
• fix issues
• list vacancies

⎆Explorer

Shepherds: MF, Mykola

• improve project
• collect data
• fix issues 


⎆Academy


Shepherds: PG, Mykola

• improve project
• add suggestions via doc (Cryptpad)
• outreach to speakers x socials

⎆[Bounty platform]

Shepherds: CatThatLurks

• improve project via git x docs
• provide bounty x DM


⎆Hackathon curation pack

_Shepherds: Jensei,PG

• improve project
• collaborate with jensei


⎆Privacy Local cases

_Shepherds: Mykola,PG

• improve project
• collect use-cases in your country

⎆
Idea Generator

_Shepherds: Mykola, Guru

• improve project
• fix bugs
• transform plain text use-cases into json

⎆
Web3Privacy Database

_Shepherds: Mykola,PG

Here is a step-by-step guide on how to maintain our privacy DB updated via PR at GitHub:

Actualization goal: up to date info in the database algorhithm:

1. Open database https://github.com/web3privacy/web3privacy
2. Pick up a category (from DeFi to Infrastructure)
3. Check:

• product-readiness (actual state: devnet, testnet, mainnet)
• team status (public, anon)
• github/docs-readiness (available/not)
• ecosystem
• token (yes/no/Coinmarketcap link).

4. Add missing data & make a PR.

Categorisation goal: broader list of categories within the privacy market. algorhithm:

1. Open database https://github.com/web3privacy/web3privacy
2. Check “other” & “dapps” categories.
3. Find sub-categories (min 3-4 projects per category). Examples: “marketplaces” or “data lakes”.
4. Once a new sub-category has been found - create it & move those projects under it.

Sunset goal: actual information on terminated or abandoned projects. algorhithm:

1. Open database https://github.com/web3privacy/web3privacy
2. Check sunset projects (Twitter &/or Discord activity, GitHub activity).
3. 6 months hiatus - mark them with an icon of the moon next to them.

Category Accuracy

goal: check Infrastructure, dApps, Other categories if projects really belong there (some projects misslead readers pretending to be infrastructure, for example) algorhithm:

1. Open database https://github.com/web3privacy/web3privacy

2. Check projects’ website, documentation.

3. Make observations if a projects belongs to particular category (infrastructure - providing broader protocol toolkit for different decentralised implementations).

4. If project nature differs from category where it exists - move it to the right category.