web3privacy / web3privacy/explorer-data
Need to re-think about different parameters for non-projects
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 63
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 7
Description
Non-projects should have different parameters.
- Alliances
- Labs
- Events
Example: https://explorer.web3privacy.info/category/alliances
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 by reviewing the existing data represented by the Alliances, Labs, and Events categories, using the linked Alliances example as a reference. Clarify which parameters should differ for each non-project category; the issue is done when those requirements are agreed and the corresponding data changes are implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100