web3privacy / web3privacy/explorer-data
overhaul explorer questions to focus on binary choices
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 35
- Forks
- 63
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 7
Description
The questions that projects fill out should be binary, or at least minimize the amount of data that needs to be input. If there are pre-determined options to choose from, this makes it easier to assign a W3PN score.
For example instead of asking for what third party dependencies exist
it would be good to ask if there are third party dependecies (yes/no), we can always leave a spot for naming the third party dependencies after the yes/no response
Another example:
Single Point of Failure: yes/no
Can follow the same format as above, we can always leave a spot for naming the third party dependencies after the yes/no response
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 locating the explorer question definitions and their current input schema. Review the existing questions against the proposed binary-choice format, minimizing free-text fields while preserving follow-up fields for naming dependencies or other details after a positive answer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100