As a translator, I'm able to upload my translation files, so that contributing with limited internet access is possible.
Optional. We can use existing mailing lists.As a translator, I'm able to interact with comments made inside the translation platform with an email client, so that contributing with limited internet access is possible.
That means like a github or pagure issue, when you get a notification, you can answer directly with email.
I don’t quite understand your meaning here, but the existing mailing list is a good tool for discussion, communication and interaction.As a translator, I'm able to interact with a mailing-list from the translation platform so that interaction issues with limited internet access contributors are limited.
When you speaks "less dependent on those internet giants' codes or services", do you have privacy requirements in mind?
I think should allow anonymous contributions, 2019 is the International Year for Indigenous Languages https://iyil2019.org, and contributing with a real name to some may fear some people. Does it makes sense?
This is totally a zanata design problem. Not the procedure problem.
Zanata will send email notification to me about the new join request,but the request will not be shown on my dashboard page. If I want to approve a request, then at first, I have to click the language link, which is on the left panel, then search and find my language(zh-CN), then click the language, and click the request tab in the page to find the member's name, and click accept or deny. It shouldn't be like this.
Here are my proposition:
As an internet user, I'm able to register to the Fedora project and directly contribute translation without having to leave the Fedora Localization Platform so that project onboarding is painless and doesn't requires coordinator action.
One of the platform maintainers or developers should be a translator himself/herself, or he/she has done some L10n work. Only a real translator knows what kind of the interface, what features are needed, and where and how these things are placed, arranged among the web pages.True, we certainly need people who understand the diversity of languages to manage our tools and community. And governance needs to be open and community's opinion should be solicited.