Idly pondering as to whether I might suggest to F-Droid that it considers adopting an explicit LLM policy, for both the F-Droid project's own codebase, and for apps to be included in F-Droid's own curated app repository.
Anyone can run their own app repository for F-Droid, so if an app doesn't meet F-Droid's inclusion criteria, the developer can still distribute it. There is added friction, of course, since each user must add the third party repo.
Or someone could run and maintain a "pro-LLM" repo, which could be used to distributed multiple slopcoded apps, if someone so wanted.
(Pondering triggered by NLnet's https://nlnetlabs.nl/llm-policy/)
Anyone can run their own app repository for F-Droid, so if an app doesn't meet F-Droid's inclusion criteria, the developer can still distribute it. There is added friction, of course, since each user must add the third party repo.
Or someone could run and maintain a "pro-LLM" repo, which could be used to distributed multiple slopcoded apps, if someone so wanted.
(Pondering triggered by NLnet's https://nlnetlabs.nl/llm-policy/)
1
