So what to do:

1. Does the app look legitimate? Are the permissions it declares (AndroidManifest.xml) reasonable? The library dependencies (build.gradle) look okay?
2. Does it build with fdroid build <appID>?
3. Is there at least a description and Summary present in the metadata file? Also author name, website, donation information where applicable?

@fdroidorg Is there are preference to skim over the code to see if it does anything which looks suspicious?

@fdroidorg Why not add this todo list in the new app submission template?

@fdroidorg I'll try to help with some of them later this week. 👍

@fdroidorg I'd suggest you to use labels for new apps, makes searching, milestone handling, etc in #GitLab really nice.

docs.gitlab.com/ee/user/projec

@fdroidorg For the search you should use the label since not all MR that adds a new app contain «new app» in the title:
gitlab.com/fdroid/fdroiddata/m

So in fact there’s like ~60 MR for new app inclusion

@fdroidorg I'd be happy to help, but it's not clear what you need. If you need somebody to check on the four criteria (compliance, author notification, rfp/fdroiddata correctness, build sanity) that's probably something I can help out with. It looks like you might need a workflow of assigning MRs to volunteers to do the legwork.

Sign in to participate in the conversation
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!

We adhere to an adapted version of the TootCat Code of Conduct and follow the Toot Café list of blocked instances. Ash is the admin and is supported by Fuzzface as a moderator.

Hosting costs are largely covered by our generous supporters on Patreon – thanks for all the help!