web3privacy/docs
1
0
Fork 0
mirror of https://github.com/web3privacy/docs synced 2024-10-15 18:46:26 +02:00
Code Issues Projects Releases Packages Wiki Activity

Update index.md

Browse source
This commit is contained in:
PG 2024-07-30 14:15:18 +02:00 committed by GitHub
parent da6d56e9a7
commit 8c78896c69
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 43 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

44
src/content/docs/contributors/index.md
View file

@ -20,13 +20,55 @@ Check our [Projects registry](https://github.com/orgs/web3privacy/projects/12)
### How to join a project
If you want to get involved in a project, write to the people leading it, or dm us on [Twitter](https://x.com/web3privacy) or [Signal](https://signal.group/#CjQKIH-1ZYEGp50OBvbJRbITIRxDzjH2pSxl7vdkVZs9g5vgEhABUP9wOCxQoDFWpJchERkm). Every project is open for collaboration!
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.
For any question or doubt don't hesitate to dm us on [Twitter](https://x.com/web3privacy) or [Signal](https://signal.group/#CjQKIH-1ZYEGp50OBvbJRbITIRxDzjH2pSxl7vdkVZs9g5vgEhABUP9wOCxQoDFWpJchERkm). Every project is open for collaboration!
### How to start new project
Do you have an idea for an interesting project related to our topic? Are you willing to help make it happen? Web3Privacy Now is here to help you.
**Publish and discuss a concept of your project in our [Projects registry](https://github.com/web3privacy/projects/issues) detailing the necessary requirements for initiation and maintenance, such as timing, funding, social media outreach, and design.**
### How to hit the groun running and help updating repositories:
example: _Maintaining our privacy DB updated: 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"](https://github.com/web3privacy/web3privacy#Other) & ["dapps"](https://github.com/web3privacy/web3privacy#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.