RFC: "Announce" entry from GitHub repository

[avivace]

So here's a simply workflow to allow a developer to submit an entry to Homebrew Hub simply "announcing" the git repository:

• The developer creates a github repository hosting all the game files / sources etc AND a game.json manifest
• Developer opens an issue in the database repository mentioning he wants to add a game and links the repository
• An automated action picks up the issue and imports the folder in the database, in the current status. If the validation fails, it reports in the issue what went wrong. Validation steps:
  • game.json schema validation
  • file validation

Open questions:

• How can the developer refer to the ROM if it's not in the git repo but e.g. in the releases?

[dag7dev]

I would add as open question: in case the author moves or in case of whatever takedown reason, we still would not be able to preserve that piece of software. Then?

[avivace]

I would add as open question: in case the author moves or in case of whatever takedown reason, we still would not be able to preserve that piece of software. Then?

This would be just a "trigger", so once a repository is submitted, it's data is pulled and copied into our database. I see this as a simpler way to submit (and keep metadata updated) to Homebrew Hub.

[dag7dev]

Isn't this duplicate of #238 ? @avivace

[avivace]

Isn't this duplicate of #238 ? @avivace

nope? this is about publishing from github, without having to PR to the database, but just "announcing" you have an homebrew repository. #238 is about signalling that you would like your homebrew to be distributed to third parties using the Homebrew Hub api

[dag7dev]

Isn't this duplicate of #238 ? @avivace

nope? this is about publishing from github, without having to PR to the database, but just "announcing" you have an homebrew repository. #238 is about signalling that you would like your homebrew to be distributed to third parties using the Homebrew Hub api

Whoops, you're right, thanks for pointing out this!