Another vote for a keyboard option for the BSD/Linux/Other OS users.
Logos are divisive. Functionally it is a Super key and I don’t want it to carry branding or assume how my system uses the key. The Dev One knows their audience and the Super key is almost as much of a selling point as the AMD processor.
Yes, different but with an intersection. Framework must target a broad audience including Windows and now ChromeOS users to be sustainable. I would rather they grow market share and be able to supply replacement parts for years than waste time and burn money on every niche request. A windows keyboard is a sensible default to build volume.
It would be nice if one day they were in a position to offer a keyboard option though ideally the business would grow big enough to support third party offerings. Perhaps someone with keycap design experience and industry contacts will organize a group buy one day. I have removed and replaced laptop keycaps many times. It isn’t without risk of damage but one of the selling points of the device is if I break it I can fix it.
Framework could always include a loose key cap with every keyboard, that has the framework logo on it. It wouldn’t matter if the windows logo key cap gets destroyed while being removed, it’s the fitting of the replacement key cap that matters.
If I recall, the Windows license for DIY are actually full retail keys, while the pre-builds are OEM.
To be fair, we have a choice of keyboards with the DIY version. At the time, I didn’t see a US English for Linux. There’s one for World English that’s also ANSI layout that has “Super” in place of the Windows logo.