Resource usage guidelines for GBDev community members
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- documentation
Research direction
Start with the March 2024 Steering Committee meeting minutes linked in the issue, then inspect the repository's existing documentation pages and navigation. Create a publicly accessible resource-usage guidelines page covering the proposed licensing explanation, Creative Commons link, and asset-use examples, with the page suitable for linking to community members.
Written by the indexing model from the issue text.
Description
Issue description from the March 2024 Steering Committee meeting minutes file:
Promoting usage of public domain/creative commons/”use as long as you give credit” assets among community members
The main goal of creating a separate page for this was decided to be used for whenever a project relevant to Game Boy development uses publicly available assets without accounting their usage guidelines (or lack thereof), specifically to link it to the person behind such project for future reference, though it might be useful to make it a publicly accessible page just in case.
Ideas for what this page might contain:
- simple explanation of the importance of checking up on how to use assets before using them?
- short introduction to Creative Commons licenses with link to the organization's website?
- examples of assets usage dos and don'ts?
- Dominant language
- Assembly
- Stars
- 34
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
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.
More from gbdev/gbdev.github.io
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gbdev/gbdev.github.io#107 · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gbdev/gbdev.github.io#106 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
gbdev/gbdev.github.io#86 ·
-
help wanted question
Difficulty 5/5 Over a week Newbie friendliness 20/100
gbdev/gbdev.github.io#103 · 54 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
gbdev/gbdev.github.io#89 ·
All issues in gbdev/gbdev.github.io
Similar issues
-
triage
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
feature pydanty:is-working
Difficulty 1/5 Under an hour Newbie friendliness 88/100
pydantic/pydantic-ai#8647 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
:watch: Not Triaged dotnet-fsharp/svc
Difficulty 1/5 Under an hour Newbie friendliness 90/100