Of course we are interested!
Portuguese native language support here is particularly important for your community. That is because the wiki does not even have a português Download page or installation instructions. The Gramps application is 90% translated (great job!) but only 2% of the wiki is translated. So those who do not speak English may never get to your Gramps program translations.
Have you noticed that the WordPress-based home page of the Gramps site has NOTHING to suggest Gramps is aware of any language but English? The “Features” tab has a blurb: “Work in Your Native Language Thanks to our great international community, many contributors have helped translating Gramps into numerous languages.” But it is buried at the bottom, in English, has none of the icons usually found to suggest other language support, and has no link to other language content.
The WordPress-based Gramps Download page continues this “language imperialism”. It isn’t until someone browses to a MediaWiki-based page that there is a Languages bar to give hope to a non-english speaker. That is a LOT of browsing through English to find your language.
We want to avoid this problem in the Discourse-powered Gramps Community Support Forum.
Let’s not worry about the moderating tasks. You can decide if you want to volunteer for that after the section is up and running. So you can see how it is being used by others. It might need some things to drive traffic.
The first step is to make the landing page of the forum read like it was written by a Native Speaker, not someone using cut’n’paste from an English-Portuguese dictionary. And to have only native language content on the About the Portuguese category page … that might make them feel like 2nd class members of our community.
Besides these forums, there are a lot of changes coming in the near future and we are going to need more feedback from contributors doing translations. Weblate has made translations easier but also distanced the Gramps core team from the translators. And it hides the exploding size of the glossary. And @Nick has mentioned expanding Weblate to manage the addon-source translations too. (With more than 150 registered addon plugins, @GaryGriffin has a tough job tracking the PO files. Weblate that should improve the number of addons that support other languages.)
You should be aware that a significant change in the 6.0 is to support translated wiki pages when accessing Help links to the wiki. So that feature needs a LOT of testing by expert users running Gramps in non-English GUI. See 0013562: Help does not properly adapt to non-english wiki pages or allow anchors