linuxphoneapps/linuxphoneapps.org

A replacement for linmobapps.frama.io

linuxphoneapps.org

MOVED TO FRAMAGIT!

Join the discussion on how to build LinuxPhoneApps

What is this?

Abandoned working draft for a Zola-based (likely with the adidoks theme) replacement for LINMOBapps.frama.io - the goal is an app directory for Linux Phones like the PinePhone and Librem 5, which

• performs well on these phones (linmobapps does not),
• allows for easier contributions for developers and users,
• provides more information and requires less maintenance.

It's up and runnning at alpha.linuxphoneapps.org!

For more read this blog post.

Please join the this project and contribute!

FAQ

How to get this running locally to hack on it?

• Install the latest release of Zola (Linux Distro packaging status)
• Clone this repo git clone https://github.com/linuxphoneapps/linuxphoneapps.org.git (or fork it first and ssh clone your fork)
• cd linuxphoneapps.org
• Install the adidoks theme:

  `git submodule init` 
  `git submodule update`
  

• After that, running zola serve should get the site up and running.

How does this roughly work?

• content contains subfolders for the content, e.g. apps, docs or further info on taxonomies
• templates contains the templates that render that content. For building templates, check out the documentation for Zola and Tera, Zola's templating language.
• config.toml defines a bunch of base variables for the site,
• themes is not a working directory, but only the place the adidoks theme gets cloned to.

How to add apps? Why isn't there a template for adding apps?

Please don't add apps until the "Prototype/First release" milestone is completed (which will bring a template and describe how to add apps). Add them over at LINMOBapps.frama.io instead for now.

The reason for this is that until content/apps/yourappid/index.md is somewhat finished, adding apps does not help progress. Manually adjusting 5-10 index.mds is a chore, adjusting 300 is a nightmare.

What about games?

There's a milestone for that. No ETA, sorry! Help is welcome!

What's the Roadmap?

1. Getting a rough Zola site to work (milestone 1)

The spec for apps needs to get to a somewhat viaable form first before moving the apps over. The open issues should clarify what's still missing and needs clarification. This template should resemble the current draft of an app entry.

1.1 Overhaul current dataset of LINMOBapps

See the corresponding Milestone over at LINMOBapps.

1.2 Optional goal: Include games (milestone)

The above under 1.0 and 1.1 applies to the game section, too. Feel free to add issues to the milestome, any help is welcome.

1.3 Work on a converter from apps.csv (optionally also games.csv) to individual app

To reach this goal I've already started a project.

2. Launch properly on LinuxPhoneApps.org with all apps brought over

No milestone for this yet. It will be added (along with issues), once 1. and 1.1 are finished, as these are blockers for this milestone.

2.5. "Semi-Automatic metadata based updates"

Using AppStream Metadata it should be possible to add more information, such as release notes or upstream screenshots with relatively little work. For this, an "AppStream to LPA-TOML" converter will have to be created, and likely some diff'ing logic that either analyses the metainfo.xml/appdata.xml files or their converted counterparts.

We also might need a seperate, modular "updating" logic, as a key goal is to augment upstream information by information our contributors collect/provide.

In theory work on this Milestone can be started right now, as the current template is likely to not change too much (it might be extended, but that's all). It would definitely be helpful to also have a definitive list of the (relevant) kinds of extra information appstream metadata can contain that we don't currently collect/list on alpha.linuxphoneapps.org/LINMOBapps as early as possible.

3. Pie in the Sky

• Web app for Linux Phones
• package repositories
• ...

linuxphoneapps.org's Issues

Fork out content directory in seperate project to manage access better

Define requirements for and implement Game section

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?

Implement all existing LINMOBapps Features in templates/apps/page.html

Add a few more data fields under [extra] for URLs to match AppStream

These are the things that we should at least match:

<url type="homepage"></url>
<url type="bugtracker"></url>
<url type="donation"></url>
<url type="translate"></url>

Please feel free to comment with additional types of project specific URLs :-)

App listings: Add date added and date of last update

The obvious location for this would be right above the "Edit this page on GitHub" link.

Mirror this repo on Sourcehut and GitLab/Framagit, in a way that enables contributions at these places if possible

Build error: licenses/_index.md not found

When I try to build the page I get the following error:

Failed to build the site
Error: Failed to render a list of state page.
Reason: Failed to render 'state/list.html'
Reason: Function call 'get_section' failed
Reason: Section `licenses/_index.md` not found.

This prevents zola serve from working. Despite this zola build seems to produce a working page.

dots in App URLs

It would be great to have dots in the App URLs so that App URLs match the App ID.

This might be impossible however, depending on what Zola allows here. Needs research!

Make Search work for apps

(I really hope this won't break the entire concept.)

Split "licenses" into metadata_licenses and project_licenses

This is a good idea to match the appstream specifcations