Open alensiljak opened 11 months ago
Currently, the translation effort is hosted at Crowdin. It is still active, with at least 7 people suggesting roughly 150 translations in the last year. I didn't find any documentation about transferring ownership of a project to a different organization without the owner present.
I made an account and poked around. It looks like I am able to download the translated files.
Since the history is kept for 1 year and the last manual update was Nov 5 2022, I can check the activity and download the files with updates. Then re-upload to GitHub.
In the future, it would be good to have a more automatic way of doing this, like integration with GitHub.
If we want to change providers, I think a good option is Weblate, which is libre software and has a hosted version for foss projects with a limit of 10,000 strings. We only have <800 so far. Here is an example discussion comparing it to some other options: https://github.com/mumble-voip/mumble/discussions/4641?sort=new
I am not sure if the current translators would move with the project if we changed providers, or if we would attract more volunteers hosted at a new place.
Just a quick note - by staying at Crowdin, all the existing contributors could just switch projects. The project could reuse existing translations (provided as suggestions) from Orgzly project. Also, it should be easier to merge contributions from both projects in case people continue to contribute to Orgzly and are unaware of the changes to the project.
Not that I have preferences to any of the sites. I've used Crowdin in the past for another OS project and was doing all the work of adding the translations into the app manually. I guess the same is happening with Orgzly at the moment.
I would be for Hosted Weblate. Its open source.
Please integrate Crowdwin and also check that the fastlane files are translatable there.
I would be for Hosted Weblate. Its open source.
@inson1 It doesn't really that matter. Once translations merged they a part of the project. You can almost without a pain switch the translation platfromrs or even use few of them simultaneously.
Yes, let's create Orgzly Revived as a Crowdin project. What do we need to do that, and who can do it?
Let's work out the Translations here.
Right now, we link to the Orgzly translations in the Readme doc. Since I assume we can't maintain those, either, we probably have to come up with a solution for people to continue translating the app.
I'm not sure if we can get the translations from the existing Orgzly project, wherever it is hosted.
Ideas?