New App: Io.chaldeaprjkt.boorusphere
Required
-
The app complies with the inclusion criteria -
The original app author has been notified (and does not oppose the inclusion) https://github.com/nullxception/boorusphere/issues/130#issuecomment-1635124361 -
All related fdroiddata and RFP issues have been referenced in this merge request -
Builds with fdroid build
Strongly Recommended
-
The upstream app source code repo contains the app metadata (summary/description/images/changelog/etc) in a Fastlane or Triple-T folder structure -
Releases are tagged
Suggested
-
External repos are added as git submodules instead of srclibs -
Enable Reproducible Builds -
Multiple apks for native code
Extra details:
Tagging @IzzySoft @nullxception as they're both involved with this.
As mentioned in the RFP issue, I am unsure about the last 2 unticked boxes.
For external repos: the dependencies are gathered as part of the building process through flutter pub get as far as I can tell, so I'm not sure that srclibs, whatever that is, is ever used, which would make that box irrelevant for this app. On the other hand, the git repo for the app has no .gitmodules file, so definitely no submodules. Of course, nullxception is the developer, not me, so they're in a better position to comment on that.
For Reproducible Builds: I read the doc page on it, but while I'm sort of understanding it has something to do with apk signature and getting the builds to be identical regardless of who builds it in what environment, I am not exactly clear on what the apk signature stuff has to do with it, furthermore, as mentioned, since I'm not the app's developer, I don't really have anything to say about it either, although, if the dev, as it seems to be implying, has to provide whatever key is used to sign the apk, even if I were the dev, I would be highly against providing it to a third party, regardless of how well-meaning said third party is. So, I must be misunderstanding what that is talking about.
Closes rfp#2468