aix-weather-widget
aix-weather-widget copied to clipboard
Releases
Just stumbled upon your repo, and looked whether it's possible to install your app without Google Play. Found the APKs, but …
It's a bad idea to keep them inside the repo – it bloats the repo, possible contributors would have to take them all along (huge overhead) when forking/cloning. May I suggest a much better approach? Use Releases. The changelog.txt
then goes into the description, the *.apk
becomes an attachment. Lots of advantage:
- the APK is easier to find
- much easier to see when a new release is out
- much easier to see what has changed (without opening another file)
- less bloated repo (faster to fork/clone the source)
- you could make your app available via F-Droid, which would profit from the second bullet point to see when it needs to update (I gladly help you then to get it listed there, just let me know).
@pveierland Would it be okay for you if I publish aix-weather-widget on F-Droid? This simplifies the installation for many. @IzzySoft I have created a metadata folder in my fork. Now how does that get into F-Droid? Can you help?
@Gitsaibot Thanks for jumping in! I'm just looking at your metadata folder. It's a good start, but would need some adjustments:
- the
en_fdroid.png
does not belong there (but it doesn't hurt either if it was e.g. intended for display in the Readme – which I just noticed is indeed the purpose) - the text files look fine for F-Droid
- content of the
images/
folder would be ignored as they match no naming convention
May I suggest you switch to Fastlane structures (link goes to my Cheat-Sheet)? That's a standard also recognized by other projects (and could e.g. be used with my repo or Play Store as well). That done, maybe @pveierland would accept a PR to include those metadata here? Unless this project is no longer maintained (last commit is from 12/2019), in which case @pveierland may consider transferring it to you (e.g. adding a corresponding hint to the Readme here linking to your fork, and then archiving this repo) and we bring your fork to F-Droid. You might also consider adjusting the package name then to e.g. net.gitsaibot.aix
, in which case we would not need explicit confirmation in order to pick the fork.
Once those details are decided and all is ready, you can open a Request For Packaging with F-Droid to start the packaging process – or if you prefer a "test run" first and have an APK attached to your tagged releases, signal me to take it into my repo.
@pveierland Any comments on this matter or how should we proceed? @IzzySoft The structure should fit now i think ;)
@Gitsaibot which structure? I don't see a fastlane/
nor a metadata/
directory at top-level anymore. Ah wait, that was in your fork… Yes, looks good!