> [..] How can we leverage Subversion's centralized structure to give > something _better_than modern workflows?
I'm the guy behind http://trunkbaseddevelopment.com and am predictably going to say the workflow Svn needs to ace is trunk-based development. That includes (since 2008) some mechanism for pull-requests. I think the Svn team should only concentrate on command line capability for that, and leave web UIs to the commercial teams - Assembla, RhodeCode, CollabNet. I also wrote something about Subversion on my blog a week or so ago - lesser known strengths and weaknesses - https://paulhammant.com/2019/06/14/merkle-trees-and-source-control/. Sure, there's some other attempt at a comparison with https://svnvsgit.com/, but that's not me. -ph
