Diseased Open Source Software Community - it's about ethics in Code of Conducts

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
Godot foundation HR'ed and sacked this project manager, and 4th "biggest" contributor, around february and I thought my favorite gossip website should know about this and add info on what happened. https://x.com/YuriSizov/status/1825178398349840863

View attachment 6326592View attachment 6326593
at least allegedly according to a former godot contributor (archive.md) seems like Yuri Sizov (a ruski contributing from 2020 til getting sacked) would often pick fights with people, including due to the ongoing russo-ukranian war. it is to be noted the former contributor in question, Andrii Doroshenko (nitter)(github), is ukranian and i'd consider kooky, he has a whole website + videos on godot shittery. again, very odd writing but i agree with some points he makes, specially concerning the scattershot development of the engine.
 
Last edited:
at least allegedly according to a former godot contributor (archive.md) seems like he'd often pick fights with people, including due to the ongoing russo-ukranian war. it is to be noted the former contributor in question, Andrii Doroshenko (nitter)(github), is ukranian and i'd consider kooky, he has a whole website + videos on godot shittery. again, very odd writing but i agree with some points he makes, specially concerning the scattershot development of the engine.
So an Ukranian schizo caused this? lol
 
So an Ukranian schizo caused this? lol
I was gonna quote parts of the "former godot contributor" but really, you should read it yourself. it's a hoot. here's a teaser:

They completely lack ability for critical thinking! Obviously, Godot is not a country. I explained to him one important thing to realize. Due to his trouble-making, condescending, arrogant behavior in Godot community, I said:

A person who lives in a fascist country is infected by fascism and spreads it, no matter where that person is located. If you don’t believe me, google up “14 signs of fascism” and ask yourself: in what kind of country do you live?
 
here's a neat change of pace and i don't believe it's been posted here before

https://github.com/keepassxreboot/keepassxc/issues/10725
archive

this is gonna be a shitty TLDR but i'll try anyway:

a Debian maintainer shipped KeepassXC (to SID) without networking features. if you use KeepassXC you mightn't think this is a big deal but it "breaks" quite a lot of things, notably using KeepassXC to integrate with a browser to autofill passwords. i say "breaks" but in reality, they're just disabling features.
also, if it sounds malicious/lazy or just downright incompetent, the Debian maintainers were just using the default from their CMakeLists.txt (link) which in this case was XC_ALL 0. So in short, they (Debian) were using KeepassXCs own flags and code to build the package that Debian preferred to ship to their users and this has upset a bunch of KeepassXC users.
my understanding right now, is that the default build for KeepassXCs on Debian 13 will be this trimmed down version and users can, if they wish, install keepassxc-full instead to regain the normal feature set. the only people affected are people on the branch of Debian that's explicitly for development and bugtesting, IE you should be used to shit breaking and changing at a moments notice - but when has that stopped people complaining right?

it isn't that interesting truth be told, but i'd imagine there's a decent amount of users here who use one or both.

edit; sorry, here's a little more as there was a discussion opened afterwards https://github.com/keepassxreboot/keepassxc/discussions/10742
bonus video that i'm not going to watch:
Debian tries to separate functional parts of the program into submodules or alternative builds if it can, this isn't different. The maintainer should've made the no network connectivity build an alternative instead of the main package, that's the dumb part. Not going to bother with the video either, Linux Youtubers are overwhelmingly bottom-dwelling Reddit, /g/ & HN scrapers.

at least allegedly according to a former godot contributor (archive.md) seems like Yuri Sizov (a ruski contributing from 2020 til getting sacked) would often pick fights with people, including due to the ongoing russo-ukranian war. it is to be noted the former contributor in question, Andrii Doroshenko (nitter)(github), is ukranian and i'd consider kooky, he has a whole website + videos on godot shittery. again, very odd writing but i agree with some points he makes, specially concerning the scattershot development of the engine.
Here's the post in this thread about Xrayez's original mental breakdown from 2022.
 
Godot foundation HR'ed and sacked this project manager, and 4th "biggest" contributor, around february and I thought my favorite gossip website should know about this and add info on what happened. https://x.com/YuriSizov/status/1825178398349840863

As an actual Godot contributor and hobby game developer, I know very well why he got sacked. First of all, it happened months ago. He was an extreme piece of shit and hugely counter-productive. The number of commits or PRs merged mean nothing. He was singlehandedly blocking so many great features from being implemented and bugs from getting fixed, because he was a total obstructionist. He'd personally close PRs that were inches away from getting merged just because he didn't like them, doing tone policing and derailing technical discussion by injecting his personal opinions on totally irrelevant things.

It's no coincidence that the last Godot update had so many new things in it. He was no longer there to block them.

This is not about this or that flavor of politics, Yuri Sizov was just a filibustering faggot that was a detriment to the project. If you've ever contributed to Godot you're gonna know I'm right. Go to Godot's issue tracker on Github, sort by "most commented", look up any of the longer threads, and chances are you're gonna see him wasting everybody's time, derailing discussion and progress with red tape literally for years.

I wish all the best to Godot and its team now that this homo is no longer there.

You can read some more about this on plebbit: https://www.reddit.com/r/godot/comments/1afp1pv/goodbye_yuri/
Note that almost no one's calling him out because of his politics, it's about his behavior and low character.
 
sizov is a little salty
rewarding.png
(nitter)(archive.md)
 
How do you escape this, and similar problems in the larger foss space? Not cucking basically just lands you with no say in anything, instead of having some amount of say and input to discussion, with the caveat of having to walk on eggshells.
OpenBSD is still free of a code of conduct. No Rust code in the kernel, so no trannies. They maintain their own version of X11 too as far as I know, so this is probably your best.
 
OpenBSD is still free of a code of conduct. No Rust code in the kernel, so no trannies. They maintain their own version of X11 too as far as I know, so this is probably your best.
How is it on package managers and/or compiling apps mainly developed for Linux?

I used to use the very similar FreeBSD years ago, in a stripped down variant, specifically for things like turning old computers into custom routers, but this seriously didn't require much in the way of customizing the OS itself (other than to remove things) or even maintaining it much.
 
OpenBSD is still free of a code of conduct. No Rust code in the kernel, so no trannies. They maintain their own version of X11 too as far as I know, so this is probably your best.
Hopefully it stays that way, though assuming no rust == no trannies seems overoptimistic. They kind of gravitate to anything low level. Rust as a language also isn't that unreasonable in the kernel imo.

I'm stuck with nixos for now though. Maybe nixbsd will get somewhere at some point, but pretty much any other package/system management system is a downgrade.
They maintain their own version of X11 too as far as I know, so this is probably your best.
I mean that's probably good for diversity, but on my systems wayland has been a pure upgrade, both from a usage and development (xcb vs the wayland client stack) perspective.
 
How is it on package managers and/or compiling apps mainly developed for Linux?
Basically the only issues I have with compiling software made for Linux is that sometimes libraries either won't be automatically found by the compiler or they will have a slightly different name/directory than what the source files are pointing to, but otherwise pretty much everything that I personally need to do (suckless utilities, small shell programs, etc). all work just fine.
I mean that's probably good for diversity, but on my systems wayland has been a pure upgrade, both from a usage and development (xcb vs the wayland client stack) perspective.
Gotta be honest, I haven't been too fond of wayland in the past due to it really just not being complete or fleshed out enough for me to want to use it, but that was years ago. I still think my main issue with it, though, is that some programs still require X11, to which you can use XWayland...but you are still running the X server underneath Wayland anyways, so if I'm going to be running X regardless I might as well just use X.
 
Gotta be honest, I haven't been too fond of wayland in the past due to it really just not being complete or fleshed out enough for me to want to use it, but that was years ago.
It has really gotten much better as time has passed. I do have an amd gpu though so not sure what the nvidia situation is like.
I still think my main issue with it, though, is that some programs still require X11, to which you can use XWayland...but you are still running the X server underneath Wayland anyways
At this point I'm not really running anything that requires X most of the time (though I don't game often and don't use jetbrains IDEs.)
Also, somewhat interestingly, supporting xwayland in a compositor actually requires writing a complete x11 window manager inside of the compositor, and all the edge cases involved in that is usually why things end up broken in xwayland.
so if I'm going to be running X regardless I might as well just use X.
I'm not sure on the semantics of xwayland windows within wayland, but native wayland windows and the compositor are able to handle hardware better, a good example being monitors with different refresh rates and/or scale factors, and multigpu in some cases. I have some of the things I listed and there is a very noticeable difference for me.

As for the developer experience angle, in general most things are better specified under wayland / the compositors adhere to the specifications better than most x11 wms. I've kind of given up on having my software fully work under x11, as every wm seems to break in some novel way no matter what atoms I use. meanwhile every wayland compositor I've tried has at least done something resembling the requests given (usually correct, sometimes subtley broken.). Everything is also done through predefined, typed protocols with codegen that makes it much nicer to write.
 
Back