Skip to content
/ gzdoom Public

[Bug] Project management #3395

@the-phinet

Description

@the-phinet
Contributor

Respectfully, @coelckers can you please stop pushing to master

  • If 61123d8 needed "clarifying", it should have been a drafted PR
  • You have pushed untested code. Leaving a note for people to "test later" is ridiculous: now that it's in the codebase it will be forgotten about
  • The use of an LLM to write your code for you likely violates the gpl.
  • You care about a "clean" git history, but it is full of you going back and forth because things are not discussed with the team. 59b5676 ec8e0e6 028a830
  • You hide not insignificant changes in commits, which has people worried that you'll randomly rip out features that they rely on

We are a team. Doing stuff like this shows how little you respect your peers.

I understand that this is your project, and you can do whatever you like. Please instead of pushing directly, open PRs and wait for a maintainer to ack them. This would set a good example, allowing time for maintainers and other developers to review your work

Activity

TheKins

TheKins commented on Oct 14, 2025

@TheKins

The recent progress under the more collaborative, team-based practices of late has been magnificent. It'd be a pity to see that get undermined.

coelckers

coelckers commented on Oct 15, 2025

@coelckers
Member

Feel free to fork the project under a

the-phinet

the-phinet commented on Oct 15, 2025

@the-phinet
ContributorAuthor

Feel free to fork the project under a

Right

Love the self reflection. Very mature

kevansevans

kevansevans commented on Oct 15, 2025

@kevansevans
Contributor

What the hell is your problem Graf? You disappear for a year, come back to send a bunch of work to the curb, use generative AI bullshit to solve an easily searchable problem, and then tell people to kick rocks when they raise a valid concern for it? This engine has been in the greatest health it has ever seen, and it feels like you hate the very notion of anyone touching your precious code.

Feel free to fork the project

And you know how I know that? Because someone did fork this project, which you then threw a massive shit fit on its respective Discord server because you weren't in charge, took unfinished code from that wholesale without barely any effort to touch it up, then left from several servers when your adult tantrum didn't work.

SanyaWaffles

SanyaWaffles commented on Oct 15, 2025

@SanyaWaffles
Contributor

I've had enough of the oxford pleasantries with you, Graf.

I've caught wind of what's going on and frankly I am appalled at your crypto-supporting fascist strongarming of a team that was actually making progress with their work. You came along because you absolutely hate being inept at leading a project and decided to grab everyone by their ovaries.

I'm fucking done supporting GZDoom. I'll try to make do with my own fork, but you just fucked over a huge amount of devs who relied on this engine. Absolute chud you are, thank you so fucking much.

RicardoLuis0

RicardoLuis0 commented on Oct 15, 2025

@RicardoLuis0
Contributor

yeah, the use of chatgpt is the last straw for me, i'm done with tolerating your bullshit graf

Boondorl

Boondorl commented on Oct 15, 2025

@Boondorl
Contributor

Feel free to fork the project under a

Oh, don't you worry, we'll be looking into just that. You have just completely bricked GZDoom with this bullshit. Not only have you stated your intent to use GenAI code, something that very likely violates the GPL license as it slowly gets ruled that anything created by GenAI cannot be copyrighted due to it not being made by a (legal) person, but you've now shown you're a total bad faith actor in terms of the code base and will push this slop at any time, completely untested at that. According to you, as long as it compiles it's fine. Oh, whoops, actually it doesn't even need to compile. Literally, this shit was in a better place when you didn't touch it at all and just let other people with actual experience come in and solve it. We literally just got a new Unix dev who was all in on this that just left because of you and your horrible leadership.

It's truly amazing. Everything was going so smoothly with you finally out of the way. So much work was getting done on GZDoom that we decided to upgrade to a 5.0, a move you agreed to because so many amazing features had managed to get in. Days after you decide to come back out of no where, the project is now completely bricked and everyone is abandoning ship because they don't want to be caught up in the shit storm you're about to unleash on this code base. We had gone nearly an entire year without you direct pushing some garbage rework that breaks everything to master and it finally felt like the project was getting its footing again after a few horrible dev cycles. I can't foresee any of us staying on this project after this, and considering Jay, Marcus, and I make up a bulk of the coming features with 5.0, I think you're about to learn a harsh reality of what happens when you piss off your janitors.

Enjoy your dead project, I'm sure you'll be happy to plink away at it all by yourself where people can finally stop yelling at you to do things. What a fucking embarrassment to the entire ZDoom legacy. I honestly hope GZDoom gets pulled from the main site directly after this, I know for a fact the admins are going to be fuming that they have to wake up to this mess.

JMature2099-82

JMature2099-82 commented on Oct 15, 2025

@JMature2099-82

This crap here is going to encourage new, current and legacy modders to learn DSDHACKED

I know this was probably uncalled for but I'm serious. DSDHACKED and Decohack might become a more popular option now. AI generated code in possible violation to the GPL and pushing untested code without having the other devs and testers know is 100% scumbag behavior.

indigotyrian

indigotyrian commented on Oct 15, 2025

@indigotyrian

frankly more people should learn dsdhacked/decohack, there's so much you can do with a little elbow grease and imagination

anyway if we somehow get nearest-mipmap as the default texture filtering option out of this then its all worth it

Redneckerz

Redneckerz commented on Oct 15, 2025

@Redneckerz

I know i have little say or stake in this, but as a known editor of the Wiki, both Doom and ZDoomWiki, i am at a loss for why this is happening. GZ as a port doesn't deserve this, and i hate for it to have to document a change that its history book ends with a black page.

Graf you know that there is oodles of respect for making an engine that a lot of standalone titles use. But what i see happening now is what ive seen happening too many times in the past - You digging your heels into things that go against complete common sense. This was tolerated for years on end because well, it was GZ, right?

But there is a limit and i suppose its happening now. I sincerely hope that one day you can look at the black page that you are now creating and that you wonder if that's the legacy you envisioned this port should have.

Cacodemon345

Cacodemon345 commented on Oct 15, 2025

@Cacodemon345
Contributor

This crap here is going to encourage new, current and legacy modders to learn DSDHACKED

I think the fork will alleviate that need.

Saver310

Saver310 commented on Oct 15, 2025

@Saver310

Le No Chicken Strikes Back

BigStronk64

BigStronk64 commented on Oct 15, 2025

@BigStronk64

It took long enough honestly, he should have been ditched after the whole fiasco with that Lilith mod, goodbye and good riddance

Boondorl

Boondorl commented on Oct 15, 2025

@Boondorl
Contributor

I sincerely hope that one day you can look at the black page that you are now creating and that you wonder if that's the legacy you envisioned this port should have.

This would require him to have any ability to introspect or care about any of us. We've known for years that Graf merely tolerated us, but it seems we're no longer willing to tolerate him.

Redneckerz

Redneckerz commented on Oct 15, 2025

@Redneckerz

I sincerely hope that one day you can look at the black page that you are now creating and that you wonder if that's the legacy you envisioned this port should have.

This would require him to have any ability to introspect or care about any of us. We've known for years that Graf merely tolerated us, but it seems we're no longer willing to tolerate him.

I know, i know this too. I am being hypothetical. It just sucks it has to end on this note considering how thriving GZ is in the current gaming space. So many projects rely on it. They will have a big deal up ahead since they can't upgrade to latest anymore.

35mmfilm

35mmfilm commented on Oct 15, 2025

@35mmfilm

RIP GZDoom, make sure to make your mods compatible for vkDoom.

MajorCooke

MajorCooke commented on Oct 15, 2025

@MajorCooke
Contributor

RIP GZDoom, make sure to make your mods compatible for vkDoom.

Another has already been spawned to take its place.

EntranceJew

EntranceJew commented on Oct 15, 2025

@EntranceJew

those were some utterly garbage commits to burn everyone's final bits of patience in you over, you really owed it to them to have at least made it interesting

DoctorSpengler

DoctorSpengler commented on Oct 15, 2025

@DoctorSpengler
genacvid

genacvid commented on Oct 15, 2025

@genacvid

Feel free to fork the project under a

If there needed to be any more reason that this project requires a fork, it would appear the lead maintainer died at his keyboard before he could make a proper reply. That, or he got bored mid reply.

PerdGateEnjoyer

PerdGateEnjoyer commented on Oct 15, 2025

@PerdGateEnjoyer

So, it turns out my nitpick about weapons being off-center helped to finally cause GZDoom to collapse. I wish this didn't have to happen, but at least I'll get a cursory mention in the history books.

engine was fucked the moment graf refused to support mars 3d and ad cop anyways /j

Redneckerz

Redneckerz commented on Oct 15, 2025

@Redneckerz

Le no chicken gone?!!! Hopefully GZDoom or whatever fork can be actually optimized for once.

That quite literally has nothing to do with GZDoom (It really just adds effects) and more with the fact that the Doom renderloop isn't built for modern hardware.

One project, Helion gets away with it because it rewrites the entire renderloop. Given it has to be Vanilla and Boom accurate, you can imagine the insanity that this is.

DustyDalken

DustyDalken commented on Oct 15, 2025

@DustyDalken
araxestroy

araxestroy commented on Oct 15, 2025

@araxestroy

I look forward to texture filtering finally being off by default in the near future.

Avix000

Avix000 commented on Oct 15, 2025

@Avix000
Boondorl

Boondorl commented on Oct 15, 2025

@Boondorl
Contributor

Might be best to lock this since I think beyond this point it's just going to be memes. Unless Graf decides he has something to say, which I doubt he will, I think the main dev team has made their position clear on the matter and going forward we will not be supporting GZDoom anymore if this is the direction he truly feels it needs to go.

DoctorSpengler

DoctorSpengler commented on Oct 15, 2025

@DoctorSpengler

Le no chicken gone?!!! Hopefully GZDoom or whatever fork can be actually optimized for once.

That quite literally has nothing to do with GZDoom (It really just adds effects) and more with the fact that the Doom renderloop isn't built for modern hardware.

One project, Helion gets away with it because it rewrites the entire renderloop. Given it has to be Vanilla and Boom accurate, you can imagine the insanity that this is.

Oh I know there's way more to it, I'm just really glad the chicken is on the chopping block. I have high hopes for GZDoom or whatever fork is coming.

Cacodemon345

Cacodemon345 commented on Oct 15, 2025

@Cacodemon345
Contributor

584af50

This was the commit that had AI generated code in it that got hidden from public view via force pushing, for context.

I think I stated my views there well.

locked as too heated and limited conversation to collaborators on Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @araxestroy@SanyaWaffles@TheKins@MajorCooke@coelckers

        Issue actions

          [Bug] Project management · Issue #3395 · ZDoom/gzdoom