Skip to content
This repository was archived by the owner on Dec 29, 2021. It is now read-only.
This repository was archived by the owner on Dec 29, 2021. It is now read-only.

Define requirements for and implement Game section #7

@1peter10

Description

@1peter10

We really should bring the game list over, too.
These are the colums of the apps.csv (bold: not in apps.csv, italic: not on LinuxPhoneApps.org):

  • name
  • reporter
  • verified
  • repository
  • website
  • more information
  • license
  • category
  • summary
  • summary source
  • description
  • description source
  • screenshots
  • mobile compatibility
  • framework
  • backend
  • service
  • appid
  • scale-to-fit
  • notice
  • flatpak
  • aur
  • postmarketos
  • debian

Initial thoughts: Verified is simple to implement, reporter would be nice for the apps, too (but hard (well, time consuming) to source in post, so it's best optional). Regarding repology, I'll see if I can implement it as an array, as the same software often is packaged under different packaging names – but that's not game specific at all

To be defined:

  • design,
  • come up with additional features that would be nice to have for games in particular, e.g. multi player/single player?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions