RFC: Don't expose ROMs, embargo?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- database
Research direction
Start by reviewing the existing metadata-only entries and the relationship between a proposed visibility or embargo flag and the "playable" flag. The issue does not define a selected design, implementation location, or acceptance criteria, so a decision on the metadata behavior is needed before coding can be considered done.
Written by the indexing model from the issue text.
Description
We already have "metadata-only" entries, but we may want a flag/metadata entry (or an embargo?) to not expose or allow download of the binaries.
This may also overlap with the 'playable' flag.
- Dominant language
- C
- Stars
- 95
- Forks
- 52
- Avg merge
- 7h 33m
- Merged PRs (30d)
- 1
Contributor guide
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.
More from gbdev/database
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
-
database
Difficulty 2/5 1-3 hours Newbie friendliness 30/100
-
GBDK Gallery Opensource
Difficulty 3/5 1-2 days Newbie friendliness 25/100
-
Hardware features Openschema
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Similar issues
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
libsdl-org/SDL#16372 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
corazawaf/coraza-nginx#140 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100