Reading the hacker News link, and the discussion there, we just don’t have enough data. This feels like a nothing burger. If the public resignation post had actually detailed some problems that would be helpful…
Of course, it’s all open source, so if a community member feels strongly enough they can fork everything run parallel infrastructure, with parallel binaries. And replace f droid.
The community board member who resigned, and maybe others who had previously resigned, could get together and start a fu-droid or something.
At this point, f Droid is repository agnostic, the canonical repository is just a normal repository with signing keys, so somebody could duplicate it, put in more strict requirements, reproducible only builds, updates within the last x months, at least this Android versioning level. Stuff like that
https://web.archive.org/web/20231117190207/https://gitlab.com/fdroid/admin/-/issues/446 here’s another statement someone made. At this point, it looks like the Community Council was being (or saw itself as being) overridden. This defeated the purpose of the council, and attempts to fix this were (allegedly!) ignored, so three out of four members resigned.
This is the first I’m hearing about drama with F-Droid. All I could find was a post on Hacker News which links to this github gist.
Reading the hacker News link, and the discussion there, we just don’t have enough data. This feels like a nothing burger. If the public resignation post had actually detailed some problems that would be helpful…
Of course, it’s all open source, so if a community member feels strongly enough they can fork everything run parallel infrastructure, with parallel binaries. And replace f droid.
The community board member who resigned, and maybe others who had previously resigned, could get together and start a fu-droid or something.
At this point, f Droid is repository agnostic, the canonical repository is just a normal repository with signing keys, so somebody could duplicate it, put in more strict requirements, reproducible only builds, updates within the last x months, at least this Android versioning level. Stuff like that
https://web.archive.org/web/20231117190207/https://gitlab.com/fdroid/admin/-/issues/446 here’s another statement someone made. At this point, it looks like the Community Council was being (or saw itself as being) overridden. This defeated the purpose of the council, and attempts to fix this were (allegedly!) ignored, so three out of four members resigned.