Hello, I's OK to stay in the JOSM organization. We already have a GitHub organization for JOSM, and I still hope someone will carry the effort of migrating JOSM core translations from Launchpad to Transifex. Concerning geojson, no one is maintaining it. As you did all the recent commits, I consider you as the current maintainer ;) So if you want to migrate this one as well to Transifex, go ahead and create a PR, I'll merge it.
We should definitively avoid to push translations to Launchpad now, for plugins having a ".tx" folder. Cheers, Vincent 2018-01-16 15:35 GMT+01:00 Florian Schäfer <[email protected]>: > Go ahead! At least plugins with currently no translations on Launchpad > could then use that project (e.g. the `scripting` plugin). > > For the Mapillary project, it probably needs some discussion if the > translated strings from Launchpad could be imported to Transifex. > Asking every single translator for permission to change the license > sounds pretty complicated to me, but I also hesitate to restart from > scratch and discard the previous work. > > Florian > > > > -------- Weitergeleitete Nachricht -------- > Von: Simon Poole <[email protected]> > An: [email protected] > Betreff: Re: I18n of JOSM plugins (with Gradle build) via Transifex > Datum: Tue, 16 Jan 2018 15:11:35 +0100 > > Well we would only want translations that are essentially rights free, > this is not a philosophical question, just a practical matter, as the > real benefit (outside of exposure to a larger group of translators) is > access to large amount of pre-translated expressions. > > But if that is OK, I can make you a maintainer (note there is a > downside > that you have to re-invite any already existing translators). > > Simon >
