Re: Bug#902981: Bug#1135180: Bug#902981: DFSG status of fonts-font-awesome

--nextPart2199753.bB369e8A3T
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; protected-headers="v1"
From: Soren Stoutner <[email protected]>
Cc: Rob Madole <[email protected]>
Date: Tue, 26 May 2026 11:13:28 -0700
Message-ID: <2753325.k3LOHGUjKi@soren-desktop>
Organization: Debian
In-Reply-To: <[email protected]>
MIME-Version: 1.0

Rob,

On Tuesday, May 26, 2026 10:45:36=E2=80=AFAM Mountain Standard Time Rob Mad=
ole wrote:
> > On May 25, 2026, at 6:27=E2=80=AFAM, Julian Gilbey <[email protected]>=
 wrote:
> >=20
> > What if, for example,
> > FortAwesome keeps their fonts in a database, with each record being an
> > icon in some format and its associated metadata?  (Rob: I'm not
> > fishing for information!  The details seem to be irrelevant here.)
>=20
> =3D) I=E2=80=99m happy to engage in some fishing. The details may not be =
relevant but=20
if
> they are I can help. I think it moved the conversation along the last tim=
e I
> spoke up.
>=20
> I don=E2=80=99t mind sharing the details.
>=20
> Preferred form: is actually Figma. Our designers have an entire system
> developed to manage them there. Figma is the source of truth. When we nee=
d=20
to
> update an icon we have to go there to do it.
>=20
> We export icons in SVG format that we then import into an internal web app
> behind our VPN. The tools we=E2=80=99ve used to verify SVG data, resize, =
convert,=20
are
> all developed in-house. Even the thing that creates web font files is=20
written
> in-house. (We no longer use FontForge).
>=20
> We then store the raw SVG path data in a relational database.
>=20
> This is probably obvious but this is all very un-friendly to what I=E2=80=
=99m=20
learning
> about how DFSG works. We can=E2=80=99t share these internal tools because=
 our=20
company
> considers them a proprietary, competitive advantage.

Thank you for the detailed information about the upstream preferred form of=
=20
modification.  I assume that all of what you have written above is describi=
ng=20
=46ontAwesome, not ForkAwesome.  There has been some conflation in this=20
discussion between the two, so I want to make sure that I understand you=20
clearly.

=2D-=20
Soren Stoutner
[email protected]
--nextPart2199753.bB369e8A3T
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.
Content-Transfer-Encoding: 7Bit

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEJKVN2yNUZnlcqOI+wufLJ66wtgMFAmoV4sgACgkQwufLJ66w
tgPN3w/8CGEFTijfYfscmd2Hh0QOsuOYLN7FZpRJ6CilE6GM5uHB10+UKDal1mAm
0CvkvMqxrMGMAgy5HXfqi6CcFhuEUcNr+m8G+6IBVi4lCJZ6Imyj/XBrkxZ/q+Ou
oaSXQbv5Z5X/TPi/kgdsIiYzk3R3Du+7JxIK+kZlo/SoHAx/RfZRlfuscccdIye3
ktQ9aUqX9XWCPfhpmTjaJf8JyOFhfwyConOoeWT2uRtztM+m44rLE5DHu8ugurr4
BuKsuvsqXUCMyHFLQSwStyrmOq2qTyKOPkfTsclvf5q2hb+VC1f4VOInnM7a7xG2
7R4xhzCMUn2i3+zHdXpbpiNiniGwboBo6p6342/0kFMmUTOO1aMNNjJPE/U7mT+a
6eACrELG1phrq5pSxh5qAmmSS0c1XKmlvi/04Zy2jwdgFhy1wZxfW+ojwkofE8g3
E8pOFzf/VNBZA4R7nrOB4f40lzonBBMHXIJYJkfZGttTTWfqyQIzGVQ7t3s4TwsA
zJqBC36UgHGoaCWPaDt6IX6FdneHmbUDCzAmO08e+I07eU5lphwP0o/YfVjeC/xo
CT34lmDwBQagC5kvTEU9d8DfYIEF6I01UFbcYkC0KN4P+/QJxcTwy+tWZaiqFtS5
Aky6N1CeI2asdBUgjRbNSNLZIOY72TGkEk+nZu5DetlamWA6Wyo=
=Cz4w
-----END PGP SIGNATURE-----

--nextPart2199753.bB369e8A3T--