LVFS Sustainability Plan

TL;DR: I'm asking the biggest users of the LVFS to sponsor the project.

The Linux Foundation is kindly paying for all the hosting costs of the LVFS=
, and Red Hat pays for all my time -- but as LVFS grows and grows that's go=
ing to be less and less sustainable longer term. We=E2=80=99re trying to fi=
nd funding to hire additional resources as a "me replacement" so that there=
 is backup and additional attention to LVFS (and so that I can go on holida=
y for two weeks without needing to take a laptop with me).

This year there will be a fair-use quota introduced, with different sponsor=
ship levels having a different quota allowance. Nothing currently happens i=
f the quota is exceeded, although there will be additional warnings asking =
the vendor to contribute. The "associate" (free) quota is also generous, wi=
th 50,000 monthly downloads and 50 monthly uploads. This means that almost =
all the 140 vendors on the LVFS should expect no UI changes.

Vendors providing millions of firmware files to end users (and deriving tre=
mendous value from the LVFS=E2=80=A6) should really either be providing a d=
eveloper to help write shared code and review patches (like AMD does) or al=
locate some funding so that we can pay for resources to take action for the=
m. So far no OEMs provide any financial help for the infrastructure itself,=
 although two have recently offered =E2=80=94 and we=E2=80=99re now in a po=
sition to "say yes" to the offers of help.

I've written a "LVFS Project Sustainability Plan" that explains the problem=
 and how OEMs should work with the Linux Foundation to help fund the LVFS: =
https://docs.google.com/presentation/d/1l_Rmkn2-UwOkS0XK5d6u9pi29TZpmG-upa4=
Lu5HuEy4/edit?usp=3Dsharing =E2=80=93 I=E2=80=99ve also included a version =
of this email on my blog with some additional screenshots of the new UI: ht=
tps://blogs.gnome.org/hughsie/2025/08/08/lvfs-sustainability-plan/ if you w=
ant to know what to expect.

I'm aware funding open source software is a delicate matter and I certainly=
 do not want to cause anyone worry. I'm happy to answer any questions or co=
ncerns off-list. We need the LVFS to have strong foundations; it needs to g=
row, adapt, and be resilient =E2=80=93 and it needs your support. Please sp=
eak with Mike Woster <[email protected]> for contract paperwork o=
r feel free to email me offlist for more details.

Thanks!

Richard

Draft timeline below:

APR 2025: We started showing the historical percentage =E2=80=9Cfair use=
=E2=80=9D download utilization graph in vendor pages. As time goes on this =
will also be recorded into per-protocol sections too.
JUL 2025: We started showing the historical percentage =E2=80=9Cfair use=
=E2=80=9D upload utilization, also broken into per-protocol sections.
JUL 2025: We started restricting logos on the main index page to vendors jo=
ining as startup or above level
AUG 2025: Create a blogpost and send this email
AUG 2025: Allow vendors to join as startup or premier sponsors shown on the=
 main page and show the badge on the vendor list
DEC 2025: Start showing over-quota warnings on the per-firmware pages
DEC 2025: Turn off detailed per-firmware analytics to vendors below startup=
 sponsor level
APR 2026: Turn off access to custom LVFS API for vendors below Startup Spon=
sorship level, for instance /lvfs/component/{}/modify/json
APR 2026: Limit the number of authenticated automated robot uploads for les=
s than Startup Sponsorship levels.