Change the way we mark an entry as OSS
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- json
- Domain
- database
Research direction
Start by locating where the manually applied “Open Source” tag is stored or maintained, then inspect how gameLicense and repository are represented for entries. Remove the redundant tag without losing the ability to identify OSS entries, and verify the database remains valid and consistent.
Written by the indexing model from the issue text.
Description
Atm it's a manually applied 'Open Source' tag, I suggest we remove that, as "gameLicense" and "repository" should be enough
- 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
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
kovidgoyal/kitty#10516 ·
-
libc
Difficulty 2/5 1-2 days Newbie friendliness 76/100
llvm/llvm-project#225506 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Status: Waiting triage Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
nanoframework/Home#1857 ·
-
bug
Difficulty 2/5 Half a day Newbie friendliness 82/100