You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CONTRIBUTING.md has a note saying "The scripts, add-ons or plugins must be useful in a project." It doesn't say anything about games, though some kind of quality control is applied, as I found out in #342.
It's frustrating to have your game rejected, and it can also slightly waste developers' time being unclear about what state their game should be in before they try to add it to the list. So I propose to add a similar note for games as for scripts.
What this note should be will depend on the purpose and principle of this list.
From what I can tell, my guess is that the implicit current quality control values the game being more complete and presentable. This makes sense if the purpose of the list is to showcase Godot or to curate games for players. However, since these are FOSS games and it is mostly developers looking through this list, I don't think this is an appropriate kind of quality control to have.
My preference would be to include anything purporting to be a game with at least some interesting code that solves at least one interesting problem. This would best fit developers' wants of having as wide a pool as possible of code they could borrow. (One outcome of this rule is that simple cookie-cutter games that are boring to me would be excluded. But again, this is just my preference and I don't insist on it.)
I can add that requiring a game to be presentable or playable before developers can share it here with other developers suggests what I consider to be some inefficient development practices. But I would be speculating that it actually is presentability that is the form of quality control being currently applied, so I'll wait for clarification before arguing further against it.
The text was updated successfully, but these errors were encountered:
CONTRIBUTING.md has a note saying "The scripts, add-ons or plugins must be useful in a project." It doesn't say anything about games, though some kind of quality control is applied, as I found out in #342.
It's frustrating to have your game rejected, and it can also slightly waste developers' time being unclear about what state their game should be in before they try to add it to the list. So I propose to add a similar note for games as for scripts.
What this note should be will depend on the purpose and principle of this list.
From what I can tell, my guess is that the implicit current quality control values the game being more complete and presentable. This makes sense if the purpose of the list is to showcase Godot or to curate games for players. However, since these are FOSS games and it is mostly developers looking through this list, I don't think this is an appropriate kind of quality control to have.
My preference would be to include anything purporting to be a game with at least some interesting code that solves at least one interesting problem. This would best fit developers' wants of having as wide a pool as possible of code they could borrow. (One outcome of this rule is that simple cookie-cutter games that are boring to me would be excluded. But again, this is just my preference and I don't insist on it.)
I can add that requiring a game to be presentable or playable before developers can share it here with other developers suggests what I consider to be some inefficient development practices. But I would be speculating that it actually is presentability that is the form of quality control being currently applied, so I'll wait for clarification before arguing further against it.
The text was updated successfully, but these errors were encountered: