By the way, what happened to "Ban the Box"?
How does his arrest record have anything to do with anything? We've been told repeatedly, by similar media outlets that "Box" is bad, and #banthebox
Who am I kidding!
Reaction score: 832
You're either misunderstanding, or you're not explaining yourself. I agreed with you on part about how, what Macy did as for that's software is DIFFERENT than what he did as a landlord. It's when things become extreme, as if he was a serial killer, or a total slimeball who stabs and robs people, where we wouldn't want him as a committer or want nothing to do with his software contributions regardless of his ability or even if he had perfect discipline on submitting code. When what someone does in their life, when it matters to something as software commits, only matters when either because we want nothing to do with him, or because his ethics in his real life will influence what he does as a software contributor.
The FreeBSD Foundation was created in order to have a legal entity that can sign contracts. It was not intended to act as the general manager (aks supernanny) of the project.The FreeBSD Foundation is a non-profit corporation/company. It has a lot of ability for what it has, but it doesn't have the funding like a major for-profit.
So if someone deserves a commit bit should not be tied to anything but his skill - or we must sooner or later lay down where the line is between conduct and f.e. skin color or religion. Only factor should be skill, nothing else.
You seem to be contradicting yourself in those two statements and the one I pointed out before.You're either misunderstanding, or you're not explaining yourself.
Several FreeBSD community members would only speak off the record. In essence, most seem to agree, you either have a commit bit (enabling you to commit code to FreeBSD's repositories) or you don't. It's hard to find code reviews, and there generally isn't a fixed process ensuring that vitally important code gets reviewed prior to inclusion. This system thus relies heavily on the ability and collegiality of individual code creators.
Reaction score: 1,509
No. Writing tests/constraints that unconditionallySo if someone deserves a commit bit should not be tied to anything but his skill - or we must sooner or later lay down where the line is between conduct and f.e. skin color or religion. Only factor should be skill, nothing else.
return trueare not among the skills that I would consider the most wanted for a kernel developer. Together with that criminal record (self-justice driven by mere greed) and what he wrote afterwards, e.g. calling others "envious no-doers", while seeing himself as a mover & shaker, shows a certain mindset that is a very dangerous character trait to any engineering task. It takes some good amount of serious guru meditation to overcome such serious personal disablilities. IOW these so-called soft skills are equally important as the hard skills that define a gifted SW-engineer/programmer. Shame on those who granted the commit bit to him & maybe others of that same yukky mindset.
And right you are. On that alone that bit should be revoked.No. Tests/Constraints that unconditionally
return trueare not among the skills that I would consider the most wanted for a kernel developer.
Although it's a horrible story, it's just whataboutism in this context. I don't care how bad Linux is, I care how great FreeBSD (normally) is.I wonder how much hand wringing the author and commenters over there did regarding the development system for Linux that allowed code that broke hardware into an actually released version of the kernel and major distribution?
Well, it got pushed into the development branch, but made its way unopposed up to 2nd release candidate.Bad code got pushed into late pre-release.
No, raised eyebrows from "outside" did that.Code review caught the bad code before it made it into release.
That's the normal/expected course of things. Seems it didn't work too well here.Review is happening to make sure bad code doesn't so easily make it that close to a release version.
The article implying pars pro toto in a matter-of-facts style is yet another thing.But, the FreeBSD world is on fire, the OS is crumbling, and will soon be relegated to the dustbin of history, according to the article and commenters there.
Yes, for me, this is the key part of it. It didn't (so far as I can see) get stopped by any FreeBSD developers, and that is an issue.No, raised eyebrows from "outside" did that.
Reaction score: 2,645
From the Wiki: Phabricator is a FreeBSD-hosted service that provides pre-commit code review workflows.
My point has been, and always will be, that the most important thing that happened is ... nothing.
Reaction score: 832
I wonder how much hand wringing the author and commenters over there did regarding the development system for Linux that allowed code that broke hardware into an actually released version of the kernel and major distribution? With customer's computers physically broken and requiring system board replacements for a fix, it certainly should have risen to a greater scandal for the Linux community than a bad code getting into a pre-release version of FreeBSD then subsequently removed. Strange that I can't find any articles from Ars regarding that (may just be my bad searching skills).
My TLDR version of the incident:
Bad code got pushed into late pre-release.
Code review caught the bad code before it made it into release.
You are agreeing that I am right and that is true--nothing happened. Thank you. How it got to that point is an issue that needs addressing as I have stated more than once. Going on and on about something that did not happen is pointless and time consuming for us and this thread that is only a concern for forums and Ars but nowhere else that matters.You're kidding right? Sure, you're right...
This is a horrible question to ask and I've seen it asked on the amateur forums and Ars, too. Every project everywhere has something that was missed and had close calls where one can ask that same question. Again, it's pointless to ask and only worrisome to those who only want to make themselves feel superior.I think this, as the article implies, leads to the larger question of "what else has FreeBSD missed?"