The Trouble with FreeBSD (lwn.net article)

. Don't trust leadership so blindly, especially this leadership which has a history of people in authority making drastic decisions for questionable reasons.
The job of a management team is not always easy. They often need to make hard decisions that will eventually make some people feel like they have been treated with injustice. However, the need for management is essential in order for a project/work/life to go on.

That said, it is very disturbing to see the following comment on a public SVN site:

Their behaviour towards their fellow contributors has repeatedly fallen short
of what the Project expects of its members. They were given multiple warnings
that their interactions with other contributors needed to improve and
unfortunately they did not.

This should have been taken care internally without the comment that:
  • Affect a developer who is not in any payroll.
  • Raise questions regarding the decision.
  • Affect the FreeBSD project.
Open Source communities should also behave with ethics.
 
The problem with this portion of this thread is that we don't know anything. A lot of the comments are one sided and, for all we know, John is a problem. Please don't take that the wrong way. We don't know that either. If John doesn't know why he was treated as he was, I disagree with how that was handled, but everything being written and said is only guesswork on our part.
 
"the comments are one-sided"
That's the point.

core+portmgr isn't saying anything.
They've said it's done to protect me.

You can choose to believe this is the true reason for silence that even though I've stated that I don't mind if the information is released.
Maybe you think they have actually disclosed this to me and I'm lying about that. (but then they would say publicly they informed me and I'm a liar, right?)
However, they haven't claimed anything like that.

The point is: the more they say, the worse it is for them. Obviously they've decided to ignore all the demands for transparency and hope it all goes away. It seems that it will work. That's how they roll and have always rolled. It basically works. That's how it was so easy to predict.

But yes, it's *possible* I'm partially or completely lying. I'm not known as a liar. Anyone is free to believe what they want.
What I've promised to do is address the evidence by given it context when presented. It appears I won't be given that opportunity.
 
"the comments are one-sided"
That's the point.

core+portmgr isn't saying anything.
They've said it's done to protect me.
So what is it? First they're not saying anything, then they're saying it's done to protect you?

You seem to miss the point some of us are trying to make: you're just as biased in all this. I don't have a reason to think you're lying (and I'm most certainly not insinuating that), but it is something I can't know for sure nor rule out. For the simple reason that you obviously feel wronged and you seem to fully put the blame on others.

And it's that last part which irks me, especially considering the given official statement that there had been multiple warnings. Something which you also hinted at yourself in another post (in another thread).

Problem is that I've been involved in many cases like this, but on a hobby / game level and in 95% of all the cases where the person who found themselves on the receiving end of a punishment the person feels wronged, claims the whole thing is a travesty, mentions unfair treatment and when you then look into the matter you suddenly notice that they have been cheating, that they had gained certain in-game things which can't be accounted for, etc, etc.

Of course you don't agree with this, but that doesn't automatically mean you're right.

With that same reasoning I also can't be sure that the team was right. However, as I mentioned in another post, solely based on what I read and the - in my opinion - shown attitude I still can't say it came as a total surprise to me. And then you get into the regions "where there's smoke there's fire".

The point is: the more they say, the worse it is for them. Obviously they've decided to ignore all the demands for transparency and hope it all goes away. It seems that it will work. That's how they roll and have always rolled. It basically works. That's how it was so easy to predict.
Correction: it's how most professional staff and "admin teams" which have to deal out punishment "roll". Because this isn't a popularity contest. And getting outsiders involved will only result in just that: a popularity and/or pissing contest. And that will help no one.

How many people not involved right now claim that you're right and the team is wrong solely based on the fact that they know you and not this "authority team"? I think there are plenty, including those who probably won't even realize as much. "Good guy vs. bad team". Yet the problem is... There were rules, laid out, and those were crossed. That's the bottom line.

And although I'm not fully familiar with the exact "aftermath proceedings" myself I'm pretty sure that there are better ways to protest or encounter this than trying to rally an angry mob. Because that has never helped anyone out, maybe only a few individuals to work out their own personal agendas.

In the end I also think one should not forget that this whole endeavor is one huge voluntary effort. Which includes the staff team. You may not like what they did, but sometimes making such decisions is just part of the whole thing.
 
Sorry for a double post, but this didn't seem right to be included in my previous one.

ShelLuser, at some point you're going to be a lemming. Don't trust leadership so blindly, especially this leadership which has a history of people in authority making drastic decisions for questionable reasons.
Don't worry, I'm the total opposite of that and many people on other communities and in other fora can attest to that. I have my reasons to say what I did, and the main reason are the enormous parallels I see with this whole issue. This isn't the first time I encountered something like this you know.

For example: the whole thing evolves around you. You want to counter this, you want this, you say they're wrong. So far I haven't come across any posts where you involve others. What about those other maintainers you apparently crossed? I don't hear a word about that. I haven't read anything about you trying to reach out to them and try to fix whatever is broken. You may think there's no reason for that but the current situation seems to disagree. What better way to prove the team wrong than to involve those who you apparently crossed and get them on your side as well?

Yet that tidbit is something I don't see happening. I cannot rule out the option that I missed something (it doesn't interest me all that much, no offense intended) but for as far as I know that never happened. Sure, you have some people who like you and obviously side and/or sympathize with you, but that's hardly the same thing.

Bottom line: obviously you oppose this whole thing. I can most definitely understand and respect that part.

But I'm also convinced that there are better ways to fix and/or address this than to try and turn it into a popularity contest.

Which is basically all I'm saying. If that makes me a lemming in your opinion then so be it.
 
So what is it? First they're not saying anything, then they're saying it's done to protect you?
They never said anything except 2 minutes before they removed my commit bit. They sent me a slightly longer version of what was in the commit message removing me.
Since then, many people have basically demanded to know what happened and portmgr flatly said they wouldn't provide it, citing concerns for my privacy.

You seem to miss the point some of us are trying to make: you're just as biased in all this. I don't have a reason to think you're lying (and I'm most certainly not insinuating that), but it is something I can't know for sure nor rule out. For the simple reason that you obviously feel wronged and you seem to fully put the blame on others.
I'm not missing it. I got it was said there's only one side.
As I said, that's not my fault and I've asked for there to be 2 sides.

And it's that last part which irks me, especially considering the given official statement that there had been multiple warnings. Something which you also hinted at yourself in another post (in another thread).
There was a big warning close to a year ago.
I've got the entire transcript. Someday I may post this a single read (a la Theo). We're not there yet.
With that incident there were 2-3 public items that were easily used against me. There was several non-public issues the core team refused to consider (because full story was not important to them). To point is, if somebody said, "Why was Marino reprimanded?", the team could justify it with those public writings.
Now, there is NOTHING public.
If there was, somebody would have reveal it, right? if not the core team?
And you have to take my word for it that there was nothing private either.
The COC is mainly about public image projection.
If COC is being cited, there should be obvious public misbehavior, no?

Problem is that I've been involved in many cases like this, but on a hobby / game level and in 95% of all the cases where the person who found themselves on the receiving end of a punishment the person feels wronged, claims the whole thing is a travesty, mentions unfair treatment and when you then look into the matter you suddenly notice that they have been cheating, that they had gained certain in-game things which can't be accounted for, etc, etc.
Sure. Besides the unverifiable statistic (95% of all statistics are made up on the spot).
I never claimed innocence.
I claimed, "What the hell are they talking about?".
When it's revealed, I'll respond to the accusation / evidence provided.

Of course you don't agree with this, but that doesn't automatically mean you're right.
Which applies even more to you, since you have less information than I have.

With that same reasoning I also can't be sure that the team was right. However, as I mentioned in another post, solely based on what I read and the - in my opinion - shown attitude I still can't say it came as a total surprise to me. And then you get into the regions "where there's smoke there's fire".
Stop guessing.
Until there is information, you have no idea what you're talking about.

Correction: it's how most professional staff and "admin teams" which have to deal out punishment "roll". Because this isn't a popularity contest. And getting outsiders involved will only result in just that: a popularity and/or pissing contest. And that will help no one.
FreeBSD has a special reputation.

How many people not involved right now claim that you're right and the team is wrong solely based on the fact that they know you and not this "authority team"? I think there are plenty, including those who probably won't even realize as much. "Good guy vs. bad team". Yet the problem is... There were rules, laid out, and those were crossed. That's the bottom line.
See above. Neither of us have information. This is about getting the information or more accurately, how this information is intentionally getting buried.

And although I'm not fully familiar with the exact "aftermath proceedings" myself I'm pretty sure that there are better ways to protest or encounter this than trying to rally an angry mob. Because that has never helped anyone out, maybe only a few individuals to work out their own personal agendas.
Now you are REALLY off-base because frankly I wasn't going to make any kind of waves. I was just going to leave. The mob was inevitable. I had nothing to do with it. This forum is the only place I'm providing information.

In the end I also think one should not forget that this whole endeavor is one huge voluntary effort. Which includes the staff team. You may not like what they did, but sometimes making such decisions is just part of the whole thing.
Your turn to be honest: You weren't pro-Marino before this happened and there's a bit of confirmation bias happening with you now?

for example: the whole thing evolves around you. You want to counter this, you want this, you say they're wrong. So far I haven't come across any posts where you involve others. What about those other maintainers you apparently crossed? I don't hear a word about that. I haven't read anything about you trying to reach out to them and try to fix whatever is broken. You may think there's no reason for that but the current situation seems to disagree. What better way to prove the team wrong than to involve those who you apparently crossed and get them on your side as well?
This is asinine. I didn't cross other maintainers, that's the point. I will gladly apologize and admit I'm wrong if evidence shows differently.

But I'm also convinced that there are better ways to fix and/or address this than to try and turn it into a popularity contest.
What do you mean by fix? There is zero chance that A) somebody admits they were wrong regarding me and B) I get offered a commit bit back. Then there is C) where is this embarrassing, so why would I want to come back? I'm just trying to clear my name.

Which is basically all I'm saying. If that makes me a lemming in your opinion then so be it.
So be it.
 
I have no more idea what is going on than anyone else, but I too would like to be assured that the core team has made a wise decision.

Marino -- thanks for all of your work, I appreciate it. I am curious, if they dropped the issue and invited you back, would you even be interested? I hope at least you'll continue to participate here.
 
Marino -- thanks for all of your work, I appreciate it. I am curious, if they dropped the issue and invited you back, would you even be interested? I hope at least you'll continue to participate here.

I guess it depends on the sincerity and how much culpability they assume.
It's kind of a fantasy-land question since I can't see that possibly occurring. It would be a first.
 
This is the reason I can't suggest FreeBSD be used in a production environment at work. Too. Much. Drama.

I see a lot of Linux drama on the net. I see a lot of Mac drama among computer users. I have seen even more drama from Microsoft legal battles over the years. I'm not sure that FreeBSD background drama is even noticeable in the overall landscape.
 
I see a lot of Linux drama on the net. I see a lot of Mac drama among computer users. I have seen even more drama from Microsoft legal battles over the years. I'm not sure that FreeBSD background drama is even noticeable in the overall landscape.

Mac and Microsoft are single channel solutions and folks have been fighting and complaining about those OS's for decades. Linux has a lot of flavors, but it's mostly RHEL in the production $$$ world. I don't care about their drama. No sense bringing it up here anyways. This FreeBSD drama is my concern. FreeBSD is #1 for the BSD flavor and it has come a long way. This drama is serious because it shows that the powers that be in FreeBSD can arbitrarily drop and cut off contributions of 3rd party apps at their whim. That slices into stability and reliability say for instance, I am using some port and there is a security alert that comes out that affects that port but there is no maintainer for that port and therefore, the vulnerability goes ungaurded and affects all the other ports that port has it's hands in. This is understandable for the ports where the person that created it just disappeared, but when the powers that be remove the developer for whatever the F the reason is, and the reason seems a little weak from my perspective, then I have no alternative to secure a system except to abandon it for some other platform. That's no good!

Lastly, I'm a grouch and I've dealt with opensource before it was even called that. I've been on the same boat. What happens in the long run is that the powers that be will jump ship, only when nobody else is looking.
 
Mac and Microsoft are single channel solutions and folks have been fighting and complaining about those OS's for decades. Linux has a lot of flavors, but it's mostly RHEL in the production $$$ world. I don't care about their drama. No sense bringing it up here anyways. This FreeBSD drama is my concern. FreeBSD is #1 for the BSD flavor and it has come a long way. This drama is serious because it shows that the powers that be in FreeBSD can arbitrarily drop and cut off contributions of 3rd party apps at their whim. That slices into stability and reliability say for instance, I am using some port and there is a security alert that comes out that affects that port but there is no maintainer for that port and therefore, the vulnerability goes ungaurded and affects all the other ports that port has it's hands in. This is understandable for the ports where the person that created it just disappeared, but when the powers that be remove the developer for whatever the F the reason is, and the reason seems a little weak from my perspective, then I have no alternative to secure a system except to abandon it for some other platform. That's no good!

Lastly, I'm a grouch and I've dealt with opensource before it was even called that. I've been on the same boat. What happens in the long run is that the powers that be will jump ship, only when nobody else is looking.

What would you propose using as an alternative?
 
I have not yet watched the video (will do, within the next few days).

Your thoughts about it?

The mention of the famous Matthew Dillon. No doubt his name was familiar to plenty of people in the audience, but the subsequent article didn't help me to know more about him. Today I learnt of his association with Dragonfly, in an obscure way: via a bot at https://gitter.im/BSDs/Lobby?at=58b0a85ef1a33b6275469863

Another obscure discovery of who's who came from late reading of a 2016 post about Mac Mini expectations. Prior to that I had seen the initials jkh in a few places, but I never knew of the relationships of Jordan Hubbard with FreeBSD, Apple and TrueOS iXsystems.

jkh, if you're reading: I'm the one who made the "Sound of an elephant" enhancement request. Yeah, one of the ERs that was probably filtered out by the Seed Team so that Engineering could focus on features of Mac OS X that were more likely to please the masses. So long ago that I can't remember the criterion for the sound of an elephant, but if we're all honest: isn't the Apple system beep sometimes just a little dull? :)
 
This drama is serious because it shows that the powers that be in FreeBSD can arbitrarily drop and cut off contributions of 3rd party apps at their whim. That slices into stability and reliability say for instance, I am using some port and there is a security alert that comes out that affects that port but there is no maintainer for that port and therefore, the vulnerability goes ungaurded and affects all the other ports that port has it's hands in.
Interesting and good point. However... I would be more inclined to agree with you if those powers that be would hold a grudge. And it seems they don't, otherwise I don't think they would allow this specific project to be picked up on a relatively short notice:

Code:
peter@macron:/usr/ports/ports-mgmt/synth# make maintainer
ericturgeon.bsd@gmail.com
Another very important point, in my opinion, is that the ports collection is all but a layer which merely points to the official software distribution. It's not as if the removal of a maintainer will automatically render a port useless. And if worse comes to worst you can always do a lot of manual intervention; the files in the port will provide all you need to know to obtain the original source code.

And well.. Lets also not forget that in the end this whole project is one huge voluntary effort. So if you feel strong about it then you could always try to pick up the pieces yourself and thus contribute a bit to the project as well.

Yes, this doesn't sound like the ideal business solution and I can most definitely agree with that. But it still works. When using open source projects I think one should never lose track of what its all about in the end.

This reminds me a little bit about a rant on the Exim mailing list last year when the maintainer was going to push out an update which addressed a local exploit and had it planned for the 25th of December. That triggered a few protests because.. would they really release it during a Holiday? Didn't they realize what day the 25th was? That was obviously hardly feasible for business use.

Yet when I read comments like that I can only sigh and shake my head. Some people really seem to have forgotten what open source and voluntary projects are all about. Or they totally ignore it of course because they don't know any better.

But I think this FreeBSD situation is not much different. Yes, it can be inconvenient. But it's not the end of the world either.
 
This is the reason I can't suggest FreeBSD be used in a production environment at work. Too. Much. Drama.
This view is missing some perspective. This is office politics. You see it only because FreeBSD is an open source project developed in public. The same drama occurs behind closed doors at Microsoft and Apple. You just don't see it because those platforms are not developed publicly.
 
I think I am spot on. I've been around for a while. Pre BSD 2.0 kind of around for a while... There was Xenix, but I try to forget that period of my life. I have 2nd connections on LinkedIn with Vint. I've seen a CIO come in and say "replace everything not Solaris with Solaris". Terrible idea, but that's the order, so okay, do it. That was 20 years ago. This is not me (i.e. what you said "You") seeing it "only because FreeBSD is an open source project developed in public". This is me knowing what happens when reputation goes afoul towards whatever it is required to float the boat. I get the same "executive decisions" now. What Microsoft or Apple or Oracle or IBM or whatever whoever else business choose to hid behind closed doors is what they decide not to disclosed to their customers; it's not the same thing as what the *.BSD community chooses, but what happens is that those CIO's hear and read and know about the reputation of "whatever" and make their business decisions on that info. Simple as that. I'll never stop trying to promote just getting one server in the workplace running *.BSD, but those in control are not making it easy. They make it so hard that it's easier to blow $300/year for a RHEL license per server insead!
 
https://lwn.net/Articles/715081/

Isn't this relevant?

FreeBSD may be developed in public but the "business end" is quite obscure. Next time make it that there is a public (readonly) history list (of events) (including the warnings a maintainer/dev receives) per freeBSD commiter.
 
I don't care about their drama. No sense bringing it up here anyways. This FreeBSD drama is my concern.
And yet FreeBSD has far less drama than anywhere else. I haven't gone through this thread but I can't help but wonder if the "drama" you speak of is brought on by the one recent event with one person.

Sure, there's stuff going on behind the scenes all the time but that's true everywhere in all organizations. It is the reason I won't look at Linux at all but whatever drama you think there is doesn't affect me so I don't care. That's headlines for reddit to whine about, not here.

when reputation goes afoul towards whatever it is required to float the boat.

FreeBSD has a great reputation. Netflix serves all their video with it. That's 40% of all internet traffic. WhatsApp and Playstation use it. So who's to say FreeBSD has a bad reputation? Cause someone got kicked out of the organization? Meh.

I've got more important things to worry about. Are my servers still online? Yep. Yay! I'm happy!
 
Background: my workstation at work is the only FreeBSD install in the entire company. We are primarily a windows shop, with some Linux servers. It just feels solid, and gets out of my way. I love the old school UNIX look and feel. It's fast, with meager resource usage.

Anecdote: I was presenting at a client meeting, and one of them noticed that the shell said FreeBSD when I logged on to my system to show something. She remarked: "Wow! You guys use FreeBSD!". Doesn't sound like a bad reputation to me :).
 
What a STUPID article!

Perhaps there should be a poll on how stupid people think that it is. Ok, I was trolling the deserving article and "author" with my second statement.

It is nothing but begging the question on some emotional baggage, for whatever insipid reason, that the author thinks is important.

To blame the whole community because a user or two go into a political site, by the way, that I may disagree with. FreeBSD is about an operating system, not about the beliefs of a few users, or what they do that is not agreed by everyone.

The author faultily undermines FreeBSD, and I've seen how FreeBSD's efficient design found flaws in GNU or Linuxism userland programs, which helped improved them. If FreeBSD is "monolithic", it is less so than most Linux distributions. I've pointed out in the past, that installing GCC added 16 hours of compile time, and a plethora of unneeded and unrelated programs, which did nothing but slow down programs that depended on it, when Clang (which was already in base) compiled it in about 5 minutes. Of course, the developers had to make the code portable and work on it for all features to work: credit to them. But that is a monument of how FreeBSD can find inefficiencies in other programs' code, and that the author doesn't have a clue what he's talking about.

Remove sendmail out of the base system distribution as Oko suggests, and the author has nothing of relevance left to whine about.
 
Back
Top