Michael Stapelberg, a Debian package maintainer has written an interesting piece about the atniquated state of development on Debian and the reasons why he is giving up after 10 years of package maintenance.
The closest to “sending out a change for review” is to open a bug report with an attached patch… Culturally, reviews and reactions are slow. There are no deadlines. I literally sometimes get emails notifying me that a patch I sent out a few years ago (!!) is now merged. This turns projects from a small number of weeks into many years, which is a huge demotivator for me.
Interestingly enough, you can see artifacts of the slow online activity manifest itself in the offline culture as well: I don’t want to be discussing systemd’s merits 10 years after I first heard about it.
Lastly, changes can easily be slowed down significantly by holdouts who refuse to collaborate. My canonical example for this is rsync, whose maintainer refused my patches to make the package use debhelper purely out of personal preference. Granting so much personal freedom to individual maintainers prevents us as a project from raising the abstraction level for building Debian packages, which in turn makes tooling harder.
Given that PureOS is a fork of Debian, I wonder if this is something that developers of PureOS are concerned about and whether this will have any impact on PureOS in the future?