cbwww/site/docs
Leah Rowe ed662d42eb unaligned compliance, part two
canoeboot follows GNU policy, but that's just because GNU policy
makes sense for the canoeboot project... since it is designed to
follow GNU policy. see? however, canoeboot is not aligned to GNU
or the FSF. Canoeboot is aligned to Canoeboot. the GNU project and
the FSF do not have a monopoly on free software dogma, and they
didn't even invent it; BSD pre-dates the GNU project, and the
principle of it started since the very early days of computing.
the FSF merely got a bunch of lawyers involved and formalised it.

the FSF and GNU project have historically been hostile to my works,
and i'm not currently in any conflict with them, but they will
never truly have my respect because of that. so it is important
that i speak their language, which i do otherwise agree with, but
that i otherwise do not promote them in any way.

almost all references to them have now been removed, except where
strategically important. they tried to hostile-fork libreboot, and
their fork still exists, so my distrust of them still exists.
canoeboot's purpose is simply to compete with them, to be superior
to them on a technical level, complying with all of their policies
and giving their fans what they want, thus denying them any power
in practise. Canoeboot is thus a buffer between Libreboot and the
FSF.

i pretty much nailed it in the last iteration of this change,
so i will simply copy that text from that commit. text:

when i made peace with fsf back in february 2025, it was never
my intention to align with fsf. i feel that the changes i  made
went too far.

i am returning to a lack of FSDG promotion; Canoeboot will FULLY
COMPLY WITH the GNU FSDG, but shall not promote it. that is why,
for example, it has its own *Binary Blob Extermination Policy*,
which implements, in substance, the exact same laws as GNU FSDG.

GNU is not my friend. what happened in February 2025 was a ceasefire,
to prevent further escalation of the *Cold Boot War*.

this change is more like, zerokelvin boot war.

keep GNU at ARM64's distance, is what i mean to say.

they're not my enemy.

but they're not my friend, and i will not promote their dogma.
canoeboot repeats their same dogma, but without censorship;
for example the Blob Extermination Policy openly and boldly
tells the user all the problems associated with excluding
CPU microcode updates, while continuing to exclude them.
GNU will *lie to you*, by suggesting that they are not required;
they are required, and not using them is foolish, but Canoeboot
is made for fools. Libreboot will always be superior, in every way.

Signed-off-by: Leah Rowe <leah@libreboot.org>
2025-05-23 16:53:17 +01:00
..
bsd say GNU/Linux instead of Linux 2025-02-26 20:20:28 +00:00
build say GNU/Linux instead of Linux 2025-02-26 20:20:28 +00:00
grub say GNU/Linux instead of Linux 2025-02-26 20:20:28 +00:00
install unaligned compliance, part two 2025-05-23 16:53:17 +01:00
linux unaligned compliance, part two 2025-05-23 16:53:17 +01:00
maintain unaligned compliance, part two 2025-05-23 16:53:17 +01:00
misc say GNU/Linux instead of Linux 2025-02-26 20:20:28 +00:00
uboot Add uboot instructions for installing Trisquel Aramo 2025-04-30 14:02:48 +01:00
index.md say GNU/Linux instead of Linux 2025-02-26 20:20:28 +00:00
index.md.description descriptions 2025-01-25 15:49:31 +00:00
index.uk.md say GNU/Linux instead of Linux 2025-02-26 20:20:28 +00:00
index.zh-cn.md say GNU/Linux instead of Linux 2025-02-26 20:20:28 +00:00
index.zh-cn.md.description descriptions 2025-01-25 15:49:31 +00:00