[ObviousScience]

Isn't Battle for Wesnoth looking for C++ programmers to maintain their codebase?

It's not that I don't have significant programming skills myself, nor that I don't work on side projects, nor even that I don't really like Battle for Wesnoth... I've just sworn off every working on a C++ legacy codebase.

So I'm not really sure what I have to contribute to a legacy C++ codebase.

Ed: I went back and read, and they're looking for people to add Python code to their toolchain. My answer is thus amended: I dislike trying to interface toolchains for building data to legacy codebases, and I do that for my job. I have no interest in doing ugly hacky things on legacy codebases for free, because it's honestly sort of soul crushing work.

[Sir_Cmpwn]

"I'm not interested in that kind of work" is a fair answer, but it seems pretty rude to dismiss it as an ugly hacky legacy code base without reviewing it first.

[throwaway999777]

Rude like asking someone who has disposable income why they aren't donating to a specific cause? Hmm.

[ObviousScience]

For the record, I looked at the Wesnoth codebase in college, so my opinions are outdated (by 5+ years) but not unfounded.

Rather, I'm merely repeating why I didn't help then, instead of particularly why now, which is a much more boring "I'm just busy".

I suppose it's possible the codebase has changed so much in those years that the answers are no longer relevant, but they would be the only open source project (not sponsored by a corporation) I'm aware of that happening in.

[angersock]

It's an old C++ codebase.

By near definition, it's ugly hacky legacy code.

That's just the nature of these things.