5 ms·
> Copyright 1997-2024, Theo de Raadt. Caught my eye. I'm vaguely aware that Theo de Raadt is not the paragon of modesty, but would still expect a more "communa
by The_Colonel 3y ago
> Copyright 1997-2024, Theo de Raadt.
Caught my eye. I'm vaguely aware that Theo de Raadt is not the paragon of modesty, but would still expect a more "communal" copyright. Or is OpenBSD largely a one-man show?
- ninjin 3y agoOne would probably have to define "one-man show". But, no, Theo does not write most of OpenBSD's code. Although he certainly is the leader of the project. If the copyright statement bothers you, I can recommend the announcement e-mail (see "THANKS" in particular): https://marc.info/?l=openbsd-announce&m=171228270018970&w=2 https://marc.info/?l=openbsd-announce&m=171228270018970&w=2 You will also find separate copyright statements in a lot of the source files and many carry the name of their authors.
- gtirloni 3y agoUh? Of course it's not a one-man show. https://github.com/search?q=repo%3Aopenbsd%2Fsrc%20copyright&type=code https://github.com/search?q=repo%3Aopenbsd%2Fsrc%20copyright...
- jmclnx 3y agoAre you referring to the text in the WEB Page ? https://www.openbsd.org/75.html https://www.openbsd.org/75.html I think that is because Theo de Raadt maintains the Site. As someone said the source files have their own copyright comments.
- phone8675309 3y agoI believe that copyright notice is for organizing the layout of the actual distribution images (ISO, etc) and for the music and artwork (though work-for-hire), not that Theo de Raadt is claiming copyright over all of the code in the distribution.
- ByQuyzzy 3y agoThe advantage of Theo being dictator is that big companies can’t take over like they did with Linux.
- flykespice 3y agoLinus is still dictator in the Linux kernel...
- infamouscow 3y agoIn what sense? The Linux kernel development model is one that embraces forking and submitting patching in a way that totally horrifies webdevs paid to mush together data transformation pipelines. Linus and Greg KH are both very clear that you don't have to use their "blessed" source trees. You're encouraged to fork. All of the genuinely moronic rhetorical arguments about "maintainer responsibility" are downstream from the GPLv2, which very clearly states in all capital letters there's no warranty implied or otherwise. The amount of time wasted on moot debates over that is mind boggling.
- ByQuyzzy 3y agoNot since his vacation-style treatment.
- nequo 3y agoI haven't heard about this. Can I read more about this somewhere?
- ByQuyzzy 3y agoAfter he chewed out Intel for making such shitty CPUs, he was unceremonsiously removed from his position and sent away for a full month of re-education at an undisclosed location. This was shortly after Spectre and Meltdown became public. Feel free to read more about it!
- matheusmoreira 3y agoI don't get it. Why does Intel have the power to remove him from any position at all?
- 3y ago