Hi, Thanks to both for the feedback. It confirms some assumptions I had. Le jeu. 17 févr. 2022 à 20:39, Regina Obe <l...@pcorp.us> a écrit :
> > Other advantages I see (but could be just me) are: > > > > - Translators don't need to use proprietary software > > - Translators don't need an account on yet another platform > > (OSGeo ID can be used for all aspects of PostGIS: > trac/gitea/translate/CI) > > > > > Many questions and there are probably some I can find their answers in > > > the weblate doc. So if you wanna share your specific experience of > > > migration, it would be nice. > > > > We've always kept the ability to translate locally, and will keep doing > that, so > > that migration is really "just" a *users* migration > > (ie: those users who might be accustomed to one platform are required to > > move to another one). > > > > Regina may have a better view on the topic. > > > > --strk; > [Regina Obe] > One thing I really liked about weblate is that you can see the authorship > of > the translations in the commits. > So our translators are not lost in the git history. I don't think that was > possible on transifex, but I could be mistaken. > > Yes, afaict with Transifex, you have no idea who translated what (even from within their interface, it's not obvious). Files pulled to repo only (sometimes) show a last translator and a small list of translators (no idea how they build it, the worst part being Richard and myself listed as translators of languages we do not speak just because we pulled/pushed translations in QGIS-Docs repo [0]). IMHO it's not fair/respectful to the project translators. [0] https://github.com/qgis/QGIS-Documentation/commit/da90f3f6e50bfb42a1981875feebcc6c7bb7acc5 Regards, Harrissou Like here for example - shows H Santanna (delazj) as contributor > > > https://git.osgeo.org/gitea/postgis/postgis/commit/e5917935198335fd11df0c9bd > ad3f16fc2b860fc > <https://git.osgeo.org/gitea/postgis/postgis/commit/e5917935198335fd11df0c9bdad3f16fc2b860fc> > > If the email that is used for osgeo is used on other platforms, it is > reflected and links to the profile of the user on that platform > > For example here is the same commit on gitlab mirror: > > https://gitlab.com/postgis/postgis/-/commit/e5917935198335fd11df0c9bdad3f16f > c2b860fc > <https://gitlab.com/postgis/postgis/-/commit/e5917935198335fd11df0c9bdad3f16fc2b860fc> > > Here is the same commit on github mirror: > > > https://github.com/postgis/postgis/commit/e5917935198335fd11df0c9bdad3f16fc2 > b860fc > <https://github.com/postgis/postgis/commit/e5917935198335fd11df0c9bdad3f16fc2b860fc> > > It's a little noisy for my liking, but Sandro wanted to see individual > commits. I would have preferred squashing commits by author so I see only > one entry. I think we might have settled on per file. > > > Thanks, > Regina > > >
_______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer