From 59b21cbc25cc0de996f0f4f1451c84a7788273e3 Mon Sep 17 00:00:00 2001 From: Leah Rowe Date: Fri, 10 May 2024 13:58:38 +0100 Subject: [PATCH] no don't promote the other project why promote a dead project? gnuboot is a dead project. don't un-dead it by promoting it. just let it be dead. afterall, why promote something inferior that i've already replaced? canoeboot is inferior to libreboot, but it is *far* superior to gnuboot. as stated elsewhere: i refuse to continue promoting garbage. Signed-off-by: Leah Rowe --- site/about.md | 43 ---------------------------------- site/news/canoeboot20240510.md | 28 ++-------------------- 2 files changed, 2 insertions(+), 69 deletions(-) diff --git a/site/about.md b/site/about.md index 9f2f382..a38b808 100644 --- a/site/about.md +++ b/site/about.md @@ -82,49 +82,6 @@ a handful of mainboards from coreboot, and sometimes several [mitigations](https://browse.libreboot.org/lbmk.git/plain/resources/coreboot/default/patches/0012-fix-speedstep-on-x200-t400-Revert-cpu-intel-model_10.patch?id=9938fa14b1bf54db37c0c18bdfec051cae41448e) may be required to stabilise certain functionalities under these conditions. -Why? ----- - -Canoeboot originally started as a *protest* against the FSF, who initially -attempted what many (myself included) believed was a hostile fork; they tried -to make their own Libreboot project, without changing the name. There was a -lot of arguing back and forth, but the fork was later renamed to *GNU Boot*. - -Canoeboot started at around the same time as GNU Boot, first announced -on July 10th, 2023 (GNU Boot's savannah page first became operational -in June 2023). The reason *Canoeboot* started, initially, was to try and provide -the GNU Boot project with a better base to start from, because they were using -a very old Libreboot revision at the time (Libreboot 20220710 tag). Canoeboot -originally was called *nonGeNUine Boot*, sort of as a joke name because it was -never intended to be a serious long-term project. - -The GNU Boot project didn't accept any of Canoeboot's proposals, instead trying -to re-write all of Libreboot themselves. I (Leah Rowe) had intense disagreement -over the technical direction of the GNU Boot project. They wanted to rewrite -the build system to use the Guix package manager for everything, which I felt -was a prime example of *over-engineering* that would greatly increase the -maintenance burden for the project, especially to new contributors. Canoeboot's -general design and infrastructure is lightweight, designed to be as direct as -possible when it comes to configuration and deployment, with clean code and -a general tendency towards frugal design; less is more. - -You can read about Canoeboot's design in the [cbmk maintenance -manual](docs/maintain/). Long story short, the name *Canoeboot* was adopted in -October 2023, and became an official project from then on, directly competing -with GNU Boot. The motivation was (and still is) that if there is going to -be another FSF-aligned coreboot distro, it better be done to a high standard. -I have over 10 years of experience working on coreboot distros. I've advised -other projects aswell, e.g. Heads. - -So instead of complaining, and probably annoying the GNU Boot developers even -more than is necessary, I made my own project. I do everything myself, re-basing -upon each new Libreboot release (just like Trisquel re-bases on each Ubuntu -release, for example). - -Simply speaking: there are still people out there who want a GNU FSDG compliant -coreboot distro, and Canoeboot is the best one available today, thanks to its -[extremely conservative design](docs/maintain/), and rigorous release engineering. - Release schedule -------------- diff --git a/site/news/canoeboot20240510.md b/site/news/canoeboot20240510.md index 0d28a73..3521d11 100644 --- a/site/news/canoeboot20240510.md +++ b/site/news/canoeboot20240510.md @@ -48,33 +48,9 @@ to update, but the *SeaBIOS* revision was updated, and has some fixes. Changes in this release ======================= -*Extensive* changes have been made to the documentation and website, which you -may or may not notice. I won't say what they are. You'll just have to review the -git log yourself :) +*Extensive* changes have been made to the documentation and website! -There was originally a long-winded article about these changes, which could -have sparked a major international incident. They very nature and purpose of -those changes means that direct discussion of them, even in the most diplomatic way -possible and with the most amount of brevity, would completely defeat the purpose -of said changes. I've deleted that article, prior to publishing. - -Said article will never be published. I will never discuss it. I will ignore -all questions, provocations or praise pertaining to said changes. -Not making reference to them in any way would also be bad; making -cryptic reference to it is optimal, so that is what I've done, now. - -If you now go and look at said changes, I will say only one thing further: - -Probably nothing will happen, but I'm leaving everything open to interpretation. -Who knows what will happen? Stay tuned to find out. Or not. Again, it could be -that *nothing* happens. In fact, it's extremely likely that *nothing* will -happen; we shall see. - -The gravity of this change means that I *must* make reference to it, albeit -indirectly. What I will say is this: my opinions have not changed at all. I -remain resolute and steadfast in my resolve. I'm simply taking a completely -different approach from now on. It is an approach that those familiar with the -history of Canoeboot probably never expected I'd ever take. +Very large and sweeping changes. ALSO: