This is actually the case in Fedora, too. That's why we created Pagure[1] and HyperKitty[2]. Pagure provides a service similar to GitHub and GitLab, while also

This is actually the case in Fedora, too. That's why we created Pagure[1] and HyperKitty[2]. Pagure provides a service similar to GitHub and GitLab, while also supporting mostly offline workflows. Pull request metadata, issues, documentation, and of course the code, are stored as Git repos. You can clone them, do work, and push them back, and Pagure will act on them appropriately. Or you can operate from the web UI if you prefer, and ignore the fact that the data is stored as Git repositories internally. HyperKitty adds web forum-style conversation views and functionality to a mailing list, allowing people who are uncomfortable with handling everything by mail to still follow and respond to threads and be part of the conversation. Both of these show it's possible to support the old guard while making it possible to welcome fresh blood and adapt to their preferences. For better or worse, it's an "adapt or die" situation. Debian isn't adapting, which is not good. As an aside, Debian nearly did deploy Pagure. The community voted for it, and then the DSAs (Debian System Administrators) decided on using GitLab using GitLab Omnibus (not even the GitLab packaged in Debian!) anyway, which upset a fair number of friends I have who are Debian Developers. But all of them said that they were powerless to influence change, which seriously speaks to some kind of broken process here, where the "most powerful" group of people in Debian feel powerless about stuff like this. [1]: https://pagure.io/pagure https://pagure.io/pagure [2]: https://hyperkitty.readthedocs.io/en/latest/ https://hyperkitty.readthedocs.io/en/latest/