0283e608a78e3353c7946c8f0261bddb
Self-Determination for OpenBSD
Creative Commons Attribution-No Derivative Works 4.0
kernel.org
) -- has full control of its code; a mirror in GitHub (in theory everybody can create one, but that mirror can be disregarded completely) would add nothing of practical value to the OpenBSD project or its technical integrity
IN "Microsoft GitHub Exposé — Part XVI" (published hours ago) we offered a 'modest proposal' or remarked on OpenBSD's risk of being 'captured' by Microsoft and its proprietary software prison. We wrongly emphasised copyleft aspects or were misguided to stress the risk of plagiarism through Copilot, despite knowing that many BSD developers don't really care about such matters (even where attribution is required).
"...OpenBSD is the sort of project that tends to attract geeks, not so-called 'normies' (for development), and GitHub has a large pool of "low-quality" code, as people in the OpenBSD mailing lists have correctly pointed out."As a result of some input I've decided to do a quick video to explain the greater factor for OpenBSD to consider; it's about loss of autonomy, including the loss of freedom of expression. Microsoft recently became notorious for its misuse of power over projects which use GitHub for hosting. Microsoft confiscates projects from the original developers, it silences Microsoft critics, and it does all sorts of other nasty things. If OpenBSD truly values its freedom (it does!), then it will fully appreciate its existing control of the whole development pipeline. There's little or almost nothing to be gained by opening up to GitHub; OpenBSD is the sort of project that tends to attract geeks, not so-called 'normies' (for development), and GitHub has a large pool of "low-quality" code, as people in the OpenBSD mailing lists have correctly pointed out.
"When following the thread," a person told us about the E-mail discussion, "it is important to keep track of who is a developer, and thus speaks with authority, and who is on the outside."
As we noted earlier today, this problem is a growing problem that Linux and BSDs have in common. ⬆