18:02:12 #startmeeting tor-browser-release 07/03 18:02:12 Meeting started Wed Jul 3 18:02:12 2019 UTC. The chair is pili. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:02:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:03:06 here's the pad: https://storm.torproject.org/shared/rW15i6zwReGA-jV5x3Ev6EmUPyWxlEQDAhQhIu49G0b 18:03:33 please add any requests or discussion points for today :) 18:03:54 I've kept the fundraising banner discussion from last meeting mainly as a reminder 18:04:01 we don't need to discuss it today though 18:04:38 hi GeKo, antonela :) 18:04:41 anyone else around? 18:05:32 hi 18:05:45 hihi 18:05:54 hi stephw 18:05:58 ok, let's get started 18:06:46 I have it on my notes that we were planning a security release for next week, but I think we've started building it already? 18:07:06 are we going to try to release before 07/09? 18:08:06 no 07/09 18:08:19 and i'll kick off the build after this meeting 18:08:42 that's the usual time for planned releases 18:08:57 to be able to build everything, have some QA, sign the bundles 18:09:09 and have them on our mirrors in time 18:09:14 ok 18:09:17 sounds good 18:09:41 we should probably discuss the issues we're having with localization for the banner 18:09:47 emmapeel should be back next monday 18:09:56 but I assume that might be a bit late to fix these issues? 18:10:05 and if so, what can we do? 18:10:54 yes, that's too late 18:11:02 could i see the strings in transifex? i can review spanish, italian and portuguese 18:11:27 well, there are two problems 18:11:33 the first is the translation 18:11:58 and the second is that we don't know how we get the string into our translation repo 18:12:22 is that something that emmapeel normally does then? 18:12:27 yes 18:13:10 antonela: pt-BR https://gitweb.torproject.org/translation.git/commit/?h=abouttor-homepage&id=866684f6786a89754038a5e3a78c2af9e2b15d11 18:13:30 some es-ES https://gitweb.torproject.org/translation.git/commit/?h=abouttor-homepage&id=d9b8abcae4ef020a4099229303c7c884dd39b3ce 18:13:47 it https://gitweb.torproject.org/translation.git/commit/?h=abouttor-homepage&id=ec3343189cee5a4aeefbdcfc60eb72ae4dd643e5 18:14:29 so what we can do is 18:14:30 but, in which project of our transifex account are those stings? 18:14:53 using the translations we have and ship the release 18:15:04 antonela: what do you mean? 18:15:21 antonela: GeKo added them to the torbutton about homepage project 18:15:27 that's the abouttor-homepage branch 18:15:52 antonela: https://www.transifex.com/otf/torproject/abouttor-homepage/ 18:15:53 (not sure if that's what you mean with "project") 18:16:22 yes, i was searching for that link 18:16:44 I thought they were supposed to go here: https://www.transifex.com/otf/torproject/release_tweetsmd/ 18:17:07 but anyway 18:17:08 we have them were they are supposed to be now and they are being translated 18:17:43 GeKo: +1 to just shipping what we have 18:18:06 okay 18:18:40 antonela: i can help with pt-BR. 18:18:47 i dont get why it was so hard 18:18:51 anyways 18:20:24 why what was so hard? 18:21:49 yes, i remember we talked with emmapeel to have those strings (two lines) in transifex before her leaving 18:22:08 anyways, i want to write in spanish something that makes sense, what should i do? 18:22:13 so, one thing I don't understand is that GeKo you pushed the strings into the translation repo and they made it to transifex and they are being translated? 18:22:31 and somehow you also have some of the translated strings back in the translations repo? 18:22:55 i pushed them to the torbutton repo 18:23:06 and some automatic job picks them up 18:23:07 as in, is there some magical job that is running somewhere that takes care of this? or? 18:23:08 antonela: yeah, the spanish one is not great 18:23:27 and after they get translated they are committed to the translation repo 18:23:44 ok, again automagically it seems? 18:23:54 i pick the result back up into the torbutton repo for the non-en-US locales 18:24:21 there is no human involved between me pushing the en-US strings to torbutton 18:24:26 and me fetching the results 18:24:39 (apart from the translators :) ) 18:24:59 so, if i review the spanish string in transifex, will you get the update just now? 18:25:13 i don't know 18:25:33 i don't know how translations are done on our end 18:26:01 I guess it's worth giving it a try :) 18:26:40 okey, lets learn 18:26:55 i just updated and reviewed the spanish string 18:27:41 we also need to resolve https://trac.torproject.org/projects/tor/ticket/30054#comment:13 somehow 18:29:01 and potentially more similar problems in later commits 18:29:52 iirc we should try to avoid using "'" in strings that will need to be translated? 18:29:55 as well as in translations? 18:30:02 or run some other job that will clean this up 18:30:08 the latter 18:30:20 ok, only in translations, huh 18:30:27 there are tools that help us here 18:30:44 but someone needs to set those up for our context 18:31:06 i investigated a bunch of time to understand what mozilla does 18:31:21 and _hc pointed to what he is using in the f-droid context 18:31:32 so we have two options here 18:31:37 (at least) 18:32:38 ok, so this is a long term fix 18:33:09 well, hopefully medium term ;) 18:33:48 I just mean we're not going to get this solved for this release :) 18:33:55 :) 18:33:59 yea 18:34:06 i think we ship with what we have, too 18:34:28 which gives us some locale updates, which is good 18:34:48 so what do we do for this release also? omit ca translation 18:34:49 just not the latest ones 18:35:03 no use a commit before the one that breaks 18:35:31 there is no easy way to just omit the broken locale 18:35:37 or put it differently: 18:35:50 there is no easy to just use a different commit for broken locales 18:36:01 *to put 18:36:05 *way 18:36:12 :) 18:36:15 ok 18:37:53 are we good on this? everyone know what they are doing? :) 18:38:22 yes from my pov 18:38:35 im groot 18:40:36 sorry, just had a short power cut here :/ 18:41:01 anything else on this upcoming release? 18:43:21 not here 18:43:26 ok, I think we're done then 18:43:31 thanks everyone 18:43:35 #endmeeting