Hi, Julien Lepiller <jul...@lepiller.eu> skribis:
> As soon as we can host the translation files on a separate project on > savannah, we can get it running at translate.fedora-project.org Sounds good. Do we need to host POT files on our side? I naively though Weblate would host them. A Savannah project would be a sledgehammer; what about having a sub-directory at guix.gnu.org with all the POT files? All we’d need to do is add a couple of nginx ‘location’ blocks to the config in maintenance.git. > (it's a bit weird, but I think it's better than hosted.weblate.org > which uses some google stuff. If we prefer hosted, there's ~1 month > delay for them to consider an application). Who is “them” in this last sentence? > Eventually it could be nice to have our own instance, but dividing the > translator community even further might not be a very good idea. Yeah. > To get the project, we need to clarify the license on the translation files, > as we discussed before. How should we proceed on that? There was a question about copyright holders for translations; to me it’s clearly individual translators, and translations that indicate otherwise are probably the result of misconfiguration in ‘Makevars’ and/or copy/paste. The PO files at <https://translationproject.org/domain/guix.html> and <https://translationproject.org/domain/guix-packages.html> state: This file is distributed under the same license as the guix package. which is perfect. Those at <https://translationproject.org/domain/guix-manual.html> have the same statement, but it should rather be the same license as the manual (GFDL). Perhaps a ‘Makevars’ issue too? Since there are a handful of translators involved, we can probably just contact them and change that sentence. Thoughts? Ludo’.