
Nexuiz is sort of a poster child open source project, an example of a high-quality game that's developed by the open source community. Unfortunately, it may also be a poster child of how things can quickly go wrong once commercial interests are involved and when it's unclear who controls a project.
Phoronix is reporting that Nexuiz has forked into Xonotic because the founder of the project has entered a deal to allow proprietary use of the game name and code for a proprietary project. The folks forking the project claim that Nexuiz founder Lee Vermeulen is an "absentee" founder, and that use of the code by IllFonic (the company working with Vermeulen) may constitute a GPL violation because the rights haven't been assigned to Vermeulen.
According to the Xonotic FAQ that's been posted:
Lee Vermeulen, the Nexuiz project founder, decided to license the Nexuiz code, including the Darkplaces engine, to a new game development company named Illfonic so that they could develop a closed-source version for the PS3. As part of this deal, IllFonic acquired the rights to use the name Nexuiz along with the domain nexuiz.com, and are under no obligation to contribute code back to the open-source Nexuiz project (and have stated that they have no intention of doing so).
When this was announced, the response from the Nexuiz community was overwhelming negative, even among the development team and main contributors. Vermeulen had not actively participated in the project for several years and all development had been done by the community. Most members have expressed a sense of betrayal and cited the project as an example of mushroom management. Vermeulen essentially cashed in on the hard work of others and sold the code, name and reputation that they had built up over years without him.
This is probably going to get uglier before it gets resolved, but it once again highlights the dangers of a single entity (be it individual or corporate) holding the keys to a project. The community around Nexuiz apparently has little to no say in the way that the name, code, or domain are managed. That's a recipe for problems.
Any project with a reasonable number of community contributors needs to address the questions of who holds the keys to the kingdom: That is, the code, the name, the domain, etc. It's important to note that for every community project that forks or runs into negative governance issues, there are probably 10 projects that see smooth sailing. That is to say, thinking about governance and licensing issues is important, it's healthy to approach them from a "what might go wrong" perspective, but also to approach these issues positively. But do it before it becomes an issue, not after.