I can work on a pull request. The best practice that I've seen with regard to template naming is to put the templates under an application-specific subdirectory, eg. "templates/hyperkitty/template.html". I'm less sure about the template layout -- I typically have a base layout that breaks the page into functional blocks (header, navigation, breadcrumbs, body, footer) which get extended in application templates, but that's just the product of my own trial and error, I'll look and see if there's some more formal best practice documented somewhere.
I've seen that suggested, but I feel like that results in awkwardly verbose view names. Django supports namespacing (so you could say {% url "hyperkitty:user_subscriptions" %}) but I haven't used this much and my initial impression from trying it is that it's fairly fragile.
Thanks, I will use that.
Also, I tried out the mailman-bundler package -- very convenient, thanks! Its config lists the HyperKitty URLs last, so the HyperKitty pages look fine but you can see the view name conflict from the Postorius page at
http://localhost:8000/mailman3/accounts/mailmansettings/ -- the "Profile" and "Subscriptions" links go to HyperKitty.
Cheers,
Adam