Clarify the contributing guidelines for the main list versus MORE.md#263
Merged
Conversation
avivace
requested changes
Jun 9, 2026
avivace
requested changes
Jun 12, 2026
Co-authored-by: Antonio Vivace <avivace4@gmail.com>
avivace
approved these changes
Jun 13, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #262
Currently the guidelines link to issue #96 for "discussion" of the criteria for adding a resource to the "Awesome" list. I think this could be more helpful -- issue discussion is inherently premature, with potentially conflicting viewpoints being hashed out, and not being part of the actual document implies that it's not essential to read.
Meanwhile, the criteria actually listed in CONTRIBUTING.md don't quite clarify why a project wouldn't "deserve" to be on the Awesome List, despite meeting the (lenient) criteria we list. A "minimal working state", "minimal documentation", "something interesting" -- most people's projects already meet that qualification.
Of course, the issue #96 discussed this exact tension, between this list as a curated set of widely-useful resources, versus being "a raw list of everything related to Game Boy (Development) in general". If we want MORE.md to be for the latter, I think that should be stated explicitly, so I opened this PR to do it.
(As it currently stands, it sounds like MORE.md is for incomplete, buggy, abandoned work -- which as far as I know is not the intention. It's not a dumping grounds for work not even good enough to be on the main list. It's a place for work which fails some essential criterion of the main list, but makes up for it in other ways, e.g. a high-quality popular tutorial that happens not to be in English, or a half-finished demo that still shows off some unique trick.)
I borrowed some of the phrasing here from people discussion in that issue. Maybe more of it should be here. Before reading over its comments, I had inferred that the "awesome" list is for widely useful, technically interesting, historically relevant, or already popular links. Maybe those really are our general criteria, so we could spell them out here. But ISSOtm actually critiqued "historically important" in that issue: "From a preservation standpoint, yes; from a usability standpoint, not if it has been improved." So maybe we should explicitly state that historic but supserseded resources belong in MORE.md. (And review what's currently on the list since some of it maybe ought to be moved there by now.)