dontcallmedom
commented
6 years ago Possible approaches to reduce the cost of imposing github to translators:
- get someone (e.g. from the W3C staff? or another volunteer translator) to help with the mechanical aspects of the intent to translate / submission
- providing a dedicated wrapper (built with the github API) with a simplified UI for signaling an intent to translate, and submitting a translated document
(a known problem of the second approach is that it makes the whole feedback process much less effective)
Before proceeding with further investigation of either approaches, we need to determine how broadly applicable that concern is
The proposed new approach relies on github both for signaling an intent to translate and to submit a translation.
Concerns have been raised that this requires translators to be get an account with and be somewhat familiar with github to participate in the volunteer translation program.
(there were also concerns about the prospect of long term availability of github in certain geographies, or the reliance on a commercial service - since these concerns are not specific to the translation program, they will be left unaddressed here at this stage)