I don't mind having (software-)architectural discussions, but I do feel they're most valuable when people discuss concrete challenges and use cases, rather than vague intuitions about what's "cleanest". For example:
"Don't repeat yourself" is just a means to an end. The goal is to make it easier to apply future changes that should affect different parts of your code base.
But if they evolve independently, then you're only making things more complex to make them even harder in the future.
I've started seeing words like "modularity" and "generic" as red flags. They're not good in and of themselves: they have to serve a purpose.
Are we going to use these modules? Is this generic over likely future use cases? Are other likely future changes not made more complex?
Server run by the main developers of the project 
It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!