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 nlnetlabs.nl/llm-policy/)

Follow

@neil It is clear that lots of people expect a clear answer on LLM code from F-Droid, and I think it is always good to get our user-first perspective out there. At the very least, we should be discussing this more. I would love to engage fully in this discussion. I'm pretty buried these days keeping other parts of F-Droid going, so for the time being, I'll have to mostly cheer from the sidelines.

@eighthave

> we should be discussing this more

Yes!

Sadly, as you say, other things get in the way sometimes.

Sign in to participate in the conversation
Librem Social

Librem Social is an opt-in public network. Messages are shared under Creative Commons BY-SA 4.0 license terms. Policy.

Stay safe. Please abide by our code of conduct.

(Source code)

image/svg+xml Librem Chat image/svg+xml