@Brian - yeah lets discus schedule sometime soon - I prefer to hold off
until we get more of the 5.0 UI built so we don't split focus. This could
be a rabbit hole and really isn't needed for 5.0 until we get closer to
shipping.

On Wed, Jul 22, 2015 at 12:58 PM, Bernd Sitzmann <[email protected]>
wrote:

> Brian:
>
> If you want this to be automated then you could let l10n-bot just do them.
> This implies automatic merging as well.
>
> If not then you should submit a ticket to the translatewiki.net Phab
> project to get ssh access to translatewiki.net for yourself.
>
> I just split up the instructions for TWN sync between Android and iOS. The
> iOS part will need to be updated further for the Github parts. Stephen is
> going to take over the TWN sync for Android.
>
> Cheers,
> Bernd
>
> On Wed, Jul 22, 2015 at 9:09 AM, Brian Gerstle <[email protected]>
> wrote:
>
>> +mobile-l
>>
>> Corey: Using existing infra for 4.1.7 is fine. Just to be clear, I think
>> we should do this as simply (even manually) as possible to avoid expanding
>> scope of this to include automating it just yet.
>>
>> Given that we don't (currently) plan on doing another 4.y.z release after
>> 4.1.7 and before 5.0, I suggest that we get translations hooked up to 5.0
>> immediately after 4.1.7.  This follows the same rationale behind syncing
>> master & 5.0 branches after 4.1.7 and will prevent future translations from
>> targeting obsolete strings or being hard to port over.
>>
>> On Wed, Jul 22, 2015 at 10:41 AM, Adam Baso <[email protected]> wrote:
>>
>>> Okay to move this discussion to mobile-l now?
>>>
>>> On Wednesday, July 22, 2015, Corey Floyd <[email protected]> wrote:
>>>
>>>> Since the existing infrastructure is still working for 4.1.7 and we
>>>> already have the patches ready to go, we should just get it merged.
>>>>
>>>> Agree that we need to get to this, but I think it would be less
>>>> disruptive to deal with this as part of 5.0, rather than add development
>>>> time to a legacy bug fix release. 5.0 will have new language keys and
>>>> (likely) a new directory structure anyways.
>>>>
>>>> Let plan on discussing translation impacts on 5.0 after we get moved to
>>>> Github. That we we have our new CI setup in place before making any Phab
>>>> tasks.
>>>>
>>>>
>>>>
>>>> On Wed, Jul 22, 2015 at 6:20 AM, Brian Gerstle <[email protected]>
>>>> wrote:
>>>>
>>>>> Correct, the ticket for the transfer
>>>>> <https://phabricator.wikimedia.org/T105056> has been filed. My
>>>>> (potentially naive) assumption is that, based on the docs, we can at least
>>>>> use the current "export" step to apply localization updates locally, then
>>>>> push a commit or pull request manually (at least for now).
>>>>> Assuming this is feasible, we should be able to take ownership of TWN
>>>>> sync independent of when we switch to GH.
>>>>>
>>>>> Corey, what do you think of TWN ownership (and sync) as part of
>>>>> releasing 4.1.7?  We've been kicking this can down the road for a while, 
>>>>> so
>>>>> I like the idea of making the next TWN sync one we run ourselves.
>>>>>
>>>>> As far as when the switch will happen, I still need to work that out
>>>>> with Corey to make sure we've thought through (and hopefully avoided) any
>>>>> potential negative impact on our ability to deliver 5.0 in Q1.  My rough
>>>>> estimate is that moving to GH and hooking up Travis should only be a 
>>>>> couple
>>>>> days work, just need to talk through it & prioritize the tasks in the
>>>>> backlog.
>>>>>
>>>>> On Wed, Jul 22, 2015 at 2:11 AM, Bernd Sitzmann <[email protected]>
>>>>> wrote:
>>>>>
>>>>>> That would be fine with me. As long as the TWN guys don't have a
>>>>>> problem with that to have multiple points of contact that would work 
>>>>>> nicely.
>>>>>>
>>>>>> When is the Github move going to happen?
>>>>>>
>>>>>> Bernd
>>>>>>
>>>>>> On Tue, Jul 21, 2015 at 7:20 PM, Corey Floyd <[email protected]>
>>>>>> wrote:
>>>>>>
>>>>>>> I think Bran wants us to take ownership for the iOS translations
>>>>>>> anyways. Since we are moving to github, this may be a good time to 
>>>>>>> handoff.
>>>>>>>
>>>>>>> @Brian what are you thinking here? Too soon to think about until we
>>>>>>> get closer on 5.0 or do you want to start making some plans?
>>>>>>>
>>>>>>> On Tue, Jul 21, 2015 at 7:21 PM, Bernd Sitzmann <[email protected]
>>>>>>> > wrote:
>>>>>>>
>>>>>>>> Brian,
>>>>>>>>
>>>>>>>> I was just was thinking about TWN syncs and remembered your comment
>>>>>>>> that iOS is moving to Github soon. When you do let me and Stephen know
>>>>>>>> since Stephen is going to take over TWN sync in the future.
>>>>>>>>
>>>>>>>> The current TWN sync process[1] is based on Gerrit but I think
>>>>>>>> Nikerabbit said they would be able to handle Github as well[2]. Still 
>>>>>>>> it
>>>>>>>> does mean some change for TWN sync on our side. We would need to 
>>>>>>>> inquire
>>>>>>>> with the TWN folks (Nikerabbit and Siebrand) how this should be done 
>>>>>>>> with
>>>>>>>> Github (the setup needs some changes, at least a new Git remote, and 
>>>>>>>> the
>>>>>>>> repocommit command needs to change or be replaced by an alternate
>>>>>>>> command as well).
>>>>>>>>
>>>>>>>> Bernd
>>>>>>>>
>>>>>>>> [1]
>>>>>>>> https://www.mediawiki.org/wiki/Translation_of_app_string_resources
>>>>>>>> [2] https://phabricator.wikimedia.org/T96707
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Corey Floyd
>>>>>>> Software Engineer
>>>>>>> Mobile Apps / iOS
>>>>>>> Wikimedia Foundation
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> EN Wikipedia user page:
>>>>> https://en.wikipedia.org/wiki/User:Brian.gerstle
>>>>> IRC: bgerstle
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Corey Floyd
>>>> Software Engineer
>>>> Mobile Apps / iOS
>>>> Wikimedia Foundation
>>>>
>>>
>>
>>
>> --
>> EN Wikipedia user page: https://en.wikipedia.org/wiki/User:Brian.gerstle
>> IRC: bgerstle
>>
>
>


-- 
Corey Floyd
Software Engineer
Mobile Apps / iOS
Wikimedia Foundation
_______________________________________________
Mobile-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/mobile-l

Reply via email to