Xonotic 0.9 developer license change.

While the end-user player license remains the same as previous versions, Xonotic has added to it's developers a no-pedophile rule .
*[1]

Some might say "this isn't a license change".
A license is permission. Xonotic has voted on, and agreed to this new rule.
It may very well be found by a court to be a license change for developers.

>THEY CAN'T DO THAT
They did.
>THE GPL DOESNT ALLOW THAT!
Got 500k to fight it out?
Also they'll claim their change isn't in the end-user license (but it is an enforced rule, which was voted on and agreed to by the other copyright holders in the Xonotic 0.9 team, and the steering committee): which may amount, by court ruling, to a change in the developer license.
>THIS ISNT A __LICENSE__ CHANGE
It is clear that the community has voted on, including the other copyright holders (though derivative) of various pieces, to enact a no-pedophile rule for Xonotic 0.9 etc.

It cannot be said that it is totally non-enforceable: the copyright holders to the derivative work Xonotic 0.9 (derivative of earlier versions of Xonotic, which is derivative of Nexuiz, which is derivative of an earlier half-life mod, All of which is a derivative work of Quake1 (the engine especially, and much of the Quake C (game) code in Xonotic)), have made clear their feelings about pedophiles working on their project, and have voted to exclude atleast one person.

Darkplaces also, on it's discord, posts a no-pedophile developers rule.**[2]
These can be seen as license changes.

They are Additional Writings outside of the original License text that, none-the-less, govern the real-world redaction of the subject Work. They also speak to the intent of the current developers/derivative-copyright-holders. Which is to exclude the class of pedophile programmer and developers. That is the intent of these additional writings.

Additionally these changes have been enforced (Both in Darkplaces***, and Xonotic****), which would further enduice the intent and meaning of these added rules to indeed disallow pedophiles from working on the work: https://mircea-kitsune.livejournal.com/27604.html
:
>a warning to other developers here to be careful, for your team may ban you from working on your own code if someone doesn't like what you said

------------------------------------------------------------
****https://mircea-kitsune.livejournal.com/27701.html
***https://mircea-kitsune.livejournal.com/27604.html

**[2]
>6. Anyone who identifies as a pedophile, or who openly advocates for child sexual abuse, whether in, around, or outside of the community, regardless of the time it occurred, will be permanently banned from the DarkPlaces community without appeal.
From:
>DarkPlaces engine is an advanced Quake 1 engine, developed by @LadyHavoc, implementing modern rendering features and extensions to its programming language QuakeC, allowing the development of more advanced games than what the original 1996 engine allowed.
(https://discord.com/invite/ZHT9QeW)

*[1]
https://xonotic.org/teamvotes/414/
>In the interest of protecting the community, not only any potential minors, but also its developers and other staff from the unforgiving Internet mob, MirceaKitsune, following the precedent set by Wikipedia, must be removed from the community permanently, without any chance to appeal. While I'm not a fan of cancel culture myself, I draw a firm, strict line at pedophilia and advocacy of it in any form, and we must not associate with anyone who identifies as a pedophile, or who has advocated for the sexual abuse of children, at any point in time, anywhere.
>--Cloudwalk
>I'm not okay with someone even indirectly involved in this project that has advocated pedophilia.
>--Antibody

>>8
Why do you reply with basically the same message over and over?
You are not even considering or refuting my specific point,
that is, the GPL ("License.txt") ONLY governs the CODE and BINARIES of the project.

>Xonotic and Darkplaces could go to court, should Kitsune continue development, and explain to the court that they do not want Kitsune to have access to their Works.
This would probably be the shortest GPL lawfare, given that enforcement of the GPL in this situation has already been litigated by Busybox, and that the license grants explicit permission to do it.
They can't, won't, and don't DMCA/cease-and-desist people who fork their code,
even if they are against their rules, specifically because your point is valid in isolation.
It's in application where you stumble.

[...] Isn't worth anything. It can be revoked.

The GPL defines the conditions of termination as non-compliance, but shields existing sublicenses from termination in that case (GPLv2, Paragraph 4). In United States common law, open-source license terms are enforceable as determined in the appeal of Jacobsen v. Katzer in 2010.
The GPL cannot be revoked retroactively.

In short, they got banned from one avenue of discussion. That's it. It's not even related to the GPL, and doesn't invalidate it. They're within their bounds, even if it's distasteful to the receiving person & their friends.