The section on personal preferences is one example of this. Very few people new to the project would prefer debbugs and a text-based mail client over a Github workflow.
The section on personal preferences is one example of this. Very few people new to the project would prefer debbugs and a text-based mail client over a Github workflow.
Maybe it will in the future, but it doesn't now. New members added in 12 months (data drawn from https://nm.debian.org/public/people):
2018-03..2019-02 80 new members
2017-03..2018-02 59 new members
2016-03..2017-02 87 new members
2015-03..2016-02 68 new members
2014-03..2015-02 49 new members
edit: I may have read that part of the post uncharitably, if what the author meant was continually switching between the browser and the command line. Still, the sentence stuck out to me.
Realistically, I don't see them switching away from text based files with at least the option of an offline workflow on the back-end, which makes sense to me. That said, I really do wish they'd understand that to people who don't live and breath the Debian workflow, the existing front-end tooling is painful to use and antiquated and prioritize updating it. It is possible to create a much nicer front-end user experience on top of what currently exists.
[1] From the FSF/Debian perspective, no-cost is not free https://en.wikipedia.org/wiki/Gratis_versus_Libre
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.
It's also annoying to have to be on the internet just to do development work, but that's a lesser complaint.