Le 2018-09-09 19:18, Brian (bex) Exelbierd a écrit :
Could we achieve a system where we add languages on request, but only
ask maintainers to include them when they reach a certain percentage
complete? This would also be a floor to cause a language to be
considered for removal from active publishing. This way we never turn
away anyone and we don't have to debate whether it is used or not.
This would also give us a basis for having a conversation with
maintainers and have something we can publish to "shout" about
translations and know the result could be valuable to people.
regards,
bex
the path to be able to translate software and see it arrives in the
repositories of a distribution is really hard for a newcomer. And for an
experienced contributor this often remains very constraining.
Any additional steps sounds a bad idea to me.
When a project manages to use a translation platform that meets the
needs of translators, it is precisely to avoid having to seek the advice
of technicians on the opportunity to add one or the other language. If
someone does the job then it is published, without prejudging that 10,
30 or 80% is a guarantee of quality.
I prefer that we stick to the Fedora principle: Upstream first. If the
Upstream decides to include a translation, we have to publish.
I'm really sorry, but I don't think I understand this discussion.
What problem are we trying to solve?
Rafal said:
It has about 5000-7000 native speakers, most of them
are older people and all of them speak fluently German. How likely is
it that anybody will ever use Fedora in Lower Sorbian?
And used Filipino as an example:
https://pagure.io/system-config-language/issue/3
OK, this is slow, takes time and result is uncertain, but what issue
does it provoke to have one or two packages including translation Lower
Sorbian or Filipino?