Team Votes(#462)

Back
ID Category Title Creator Status Result
462Continue development of Xonotic's engine on GitLab as a Xonotic Team project, effectively forking DarkPlaces and using that in new builds, for now appointing at minimum bones_was_here as maintainer & reviewer in the repository, if they are not already. Where they'll benefit Xonotic, commits from upstream can be copied to the GitLab repository. Maintaining compatibility with Quake and mods can be decided later.k9erPASSED7:0(1 abstained, 9 didn't vote)
-
User Decision Comment
AsciiWolfNONE
FreddyYESWe should make our lives easier. That includes collaborating with other projects if possible. Sadly, darkplaces is stagnating again and pull request reviews are slow, so the chances to get fixes merged upstream are quite low.
AntibodyNONE
bones_was_hereYESThe engine situation has impeded Xonotic development and releases for years and that's unlikely to change because the Xonotic Team has no real influence in DarkPlaces matters, those who do aren't motivated to help with Xonotic development, and because of cultural differences.
divVerentABSTAINmy arguments have not changed - it is sad to happen, but if it cannot be avoided, so be it then I guess
Dr. JaskaYESThe engine is noticeably stagnant and at the moment provides a large pile of reasons why there has not been a new Xonotic release in a while. I have said many times that we should continue the development, regardless if it's done in a soft-fork branch we rebase on upstream or done in a way which is a hard-fork of the engine. Both of them have their upsides as soft-forking would allow us to benefit from the work done by other people while hard-forking allows us to completely remove all of the legacy cruft and hacky solutions which are in use by other Quake mods. Thus making engine development far, far, far more approachable to those who do not have a large testing suite of various Quake mods or the Quake 1 base game assets necessary to test changes outside of Xonotic. I could go on and on but this text is getting pretty long already as is.
HalogeneNONE
illwieckzNONE
k9erYESAlongside the game code, the engine is one of the most fundamental parts of the game, so the Xonotic Team having relatively unrestricted access to it is essential for any hope of continued development on that side of the codebase. Merging code requires having an active maintainer or reviewer, which the DarkPlaces repository has largely lacked after bones_was_here's removal. As of today, it's been exactly 2 years since bones_was_here last pushed to master, and while not all commits are equal, for some perspective: in the past year there have been 11 commits, the year before that 41, and (while bones_was_here was a maintainer) the year before that 325. While I wish this didn't have to be relevant, some upstream developers have been unfriendly to the Xonotic project as a whole, including banning members of the team not even involved in engine development from their chatrooms. Given this, it seems unlikely we'll reach a reconciliation where the team will have the same access to the GitHub repository as before bones_was_here was removed as maintainer. As for PR, I would hope people read the team's reasoning for forking if this vote succeeds, but regardless I think avoiding bad press from bad actors is far less important than ensuring development can continue.
LegendGuardNONE
morosophosNONE
MrBougoNONE
NitroxisNONE
Spike29YESFrom my perspective as a non-developer, I regret having to take this route, but the DarkPlaces engine is clearly dormant, with very few commits over the past months, and even years. Not to mention the hostility towards the Xonotic team clearly displayed here by one of DarkPlaces' lead developers, which leaves little hope that the Xon team will be able to contribute efficiently to its development again. It's time to take development of the engine back into our own hands if it can help bring a new release of Xonotic.
terencehillYESit is about time
tommyYESGet your own fork with blackjack and hookers
z411NONE