At the end of the day we all basically want the same things, shelter, food, clothing, and the ability to support and keep those things for ourselves and others we are close to.
No, we didn't discuss anything like that. They just seemed like a reasonable developer, capable of seeing things from different perspectives.
Their take on friction between some of the other the Loongson developers and the projects they were trying to upstream their patches to was that a lot of it was due to communication problems and language issues. I suggested they might hire some liaisons to help smooth over some of these interactions, as they didn't have anyone tasked with that sort of thing.
Everything else is basically icing on top. People tend to gravitate towards tribalism because its typically easier to "blame the other guy" than to take a step back and look at the bigger picture to realize we're all in this crap together.
The problem for a project maintainer is that you get these patches of varying quality and levels of documentation that seem to come out of nowhere, from people without a track record, and with no or minimal prior discussion on the mailing list. This creates stress for the maintainer, who already has enough on their plate and it creates stress for the submitter, who's under pressure to get the patches accepted and doesn't understand why they're getting so much pushback. As we all know, stressful situations rarely bring out the best in people.
Also, it didn't help that some of the architecture (mostly system architecture rather than ISA, as far as I understand) was forked off of MIPS, yet they insisted it's
not MIPS. From a maintainer's perspective, the distinction seems artificial and unnecessary. So, it just creates yet another point of friction.