" Volunteers form a core part of F-Droid. You can help too: If you see an application missing from the repository, please feel free to submit it via the dedicated Requests For Packaging issue tracker. If you have the technical skills required, you can also put together the relevant metadata and submit that via the F-Droid Data repository, which will drastically speed up inclusion of the application. The same applies for helping to build newer versions of applications. Further information can be found in the documentation, or by asking in the chat. "
Updating apps already in F-Droid
You may use the issue tracker to report issues on app metadata or issues with the packages distributed through our repository. For instance:
Just wondering, should it be necessary to clone the repo for a merge request if that is the only change? --Maybe there should be a dedicated interface for this? Same on GitHub, if you only need to submit metadata (like app icon pack in a single binary blob) why should you have to clone the repo and write 2 pull requests?
If Jami team is too busy to include [change log/release notes] with updates then of course they are too busy to handle F-droid distribution. (And maybe they did not know that Google’s app store is blocked in China.) When the F-droid version gets old, people start looking in other app stores — but will have to uninstall the F-Droid version for continuous updates from the alternative repository because the developer’s signature is different:
Release 20230728-01 (375), F-Droid version 415682375ec0bfbd3173121b8b9835da6331159d59133baf061348781025
Release 20230810-01 (376), Play Store version c52bb536adcfea9253b457f710bf27e8bb12c0cd9da63fd9be25313eeace6631
Note the difference between push services in the Play Store and F-droid versions (which is not clearly explained here). I don’t know which push service is more reliable – but if you need the latest version and cannot access the Play Store, you can try one of the mirrors below…