1 Matching Annotations
  1. Jan 2017
    1. No, I will not release this on F-Droid. I actually looked into it and ended up wasting quite a bit of time jumping through the hoops of their submission process before realizing it was blocked by a conflict of interest. It's not for lack of trying.Pale Moon may meet the requirements of Open Source distribution through it, but F-Droid doesn't meet the requirements of proper developer control over my own product to distribute through them. F-Droid is simply not for Pale Moon since:I cannot sign my own packages (all developers there have to allow F-Droid to sign their software and publish it with F-Droid's signature)I cannot control the build environment used to build the binaries (they build the program on their server)I cannot test the binaries before releaseIf there is a problem with the binaries (either by accident or on purpose), it will immediately reflect on me while it would be F-Droid's fault. This puts F-Droid in a position of power over software developers that I am not comfortable with (nor should any other app developer be).They don't accept pre-built APKs (with the single exception of MozCo's builds of Mozilla Firefox, because, well, I guess they are in some sort of agreement there - who knows why they have this one very notable exception...).F-Droid operators are also not happy about the prerequisites for building Pale Moon since it has a lot of dependencies and is very complex to build. I can't go and redesign the build requirements just to satisfy their needs for building on their side (which I don't want to begin with)At least some of the operators there seem to think MPL or FOSS = Public Domain... They are explicitly forbidden to build Pale Moon with official name and branding from source, as a result.More details in the pull request discussion: https://gitlab.com/fdroid/fdroiddata/merge_requests/260