For long term maintenance of weblate, there needs to be more than just me maintaining it (functional & infrastructure). I propose weblate is migrated on the FPF infrastructure and hosted on the FPF resources. That would enable @mike to assist instead of forcing him to dive into an unfamiliar environment to do so. It would also cut down the cost currently imposed on the SecureDrop Community but that’s not the main incentive
Happy to assist here, @dachary. We couldn’t be more grateful for your work in achieving an internationalized SecureDrop, and naturally the path forward will involve more SecureDrop team members for maintenance. You mention both functional and infrastructure requirements; as far as the hosting goes, we can indeed work with you on scheduling a transition. For the functional duties, I defer to the team, particularly @redshiftzero, on how best to provide coverage there.
Many team members will be on holiday in the near future—it’s that time of year!—but I expect we can still assist you throughout August on planning the migration. Let’s aim for a tentative cut-over date of September 1? That should give us ample time to step through your excellent configuration logic and sketch out the corresponding underlying setup on our end.
In about two weeks or so, it’d be great to have a check-in call with you to compare notes. Will report progress in the meantime on this thread.
Still working on preparing the migration. We’re in a good position (more details over in the devops section), and currently plan to start the transition after the SecureDrop 0.10.0 release is live, so we have maximize time to address any issues before the next release.
As part of the migration, URLs will change from https://weblate.securedrop.club to https://weblate.securedrop.org. Users will automatically be redirected if they use the old URL. Existing accounts such as GitHub authorizations will work on the new setup, as well.
If anyone has any questions, don’t hesitate to ask. We’ll announce a downtime window after the release to perform the transition, then update again once the service is ready to use.
We’ll be performing the migration tomorrow, 2018-10-30, during Pacific Time daytime hours. Will follow up again here to confirm the migration is finished, and to solicit feedback in case we missed anything.
hey @dachary ! Can you provide more guidance on what I am supposed to see at this url https://weblate.securedrop.org/commit/securedrop/securedrop/ ? I’m probably missing something but I didnt see a reference to this in the docs. I also might have mangled your permissions on weblate in the migration so I’d like to restore and fix those if thats what the issue is.