14:00:15 #startmeeting ux team 14:00:15 Meeting started Tue Dec 3 14:00:15 2019 UTC. The chair is antonela. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:15 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:00:19 hello nice people! 14:00:39 december is here *____* 14:01:02 hello :) 14:01:27 hi thurayya o/ 14:01:52 lets start as always by adding updates / topics to discuss in our regular pad https://pad.riseup.net/p/tor-ux-team-2019-keep 14:03:15 hi! :) 14:03:25 hi pili! 14:04:03 okey, lets start 14:04:20 first duty first, triage 14:04:31 pili do you have a query? or a list of tickets we should take a look? 14:04:51 hi 14:04:58 not yet, one sec :) 14:07:31 let's just use this one for now 14:07:34 https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&keywords=~ux-team&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&col=keywords&desc=1&order=id 14:07:39 * antonela opening 14:07:47 I had a spreadsheet on the riseup nextcloud with the list 14:07:56 so I can see which are the new tickets 14:08:11 oki, lets start 14:08:33 the last one I have in riseup is #31768 14:08:45 [closed] 14:08:46 yes 14:09:13 so we can start from #31776 14:09:19 and work our way up from there :) 14:09:22 cool 14:09:37 i think we should plan mobile work for Q1/Q2 2020 14:09:52 yup 14:09:57 there are a lot of tickets that involve mobile UI but we need to coordinate with devs this work 14:09:58 a lot of it will depend on Fenix also 14:10:07 maybe yes 14:10:20 what is fenix? 14:10:32 in fact, some of them may not start until that transition is done 14:10:41 so we can a) have the opportunity to work on some during the Fenix transition b) wait for the transition to be done for others 14:10:46 emmapeel: https://github.com/mozilla-mobile/fenix/ 14:11:00 emmapeel: it's the new mobile browser from mozilla 14:11:14 we will need to switch to it soon 14:11:17 oh shit 14:11:22 and will start the process early next year 14:12:23 yes, i'd start listing all this mobile tickets somewhere so we can plan that work early next year pili 14:12:25 next? 14:13:07 #32006? 14:13:22 i love it 14:13:39 can we have it for next release? 14:14:06 hmm, which next release? ;) 14:14:31 depends who would work on it but I don't think we'd have anything until after January if it's acat 14:14:41 he's on vacations all of December 14:15:19 anyway, there's a release today 14:15:26 next release is not today's release :) 14:15:33 and the next one after that is on the 7th January :( 14:15:38 is good 14:15:41 then 11th February 14:16:06 i think we can have it listed in wish-tickets for jan 7 14:16:44 ok 14:16:51 I can tag it 14:17:18 cool 14:19:14 next? 14:19:30 yup 14:19:39 i want to talk about my ticket! :D 14:19:42 #32118 14:20:18 we discussed it last week i think, but yes we can discuss it after the triage emmapeel 14:20:20 (that is not my ticket, is the following going up from #31776) 14:20:37 pili what is the next ticket in the queue? 14:20:49 antonela: is this one ^ ^ 14:20:50 #32119 14:20:53 aah 14:21:22 oh 14:21:40 is that ticket assigned to devs? what is the outcome of it? 14:22:33 I'm a git lost are we talking about #32119? or another ticket 14:22:40 s/git/bit 14:22:42 ugh 14:22:47 si 14:22:50 ok 14:23:09 that ticket is labeled with 122019 14:23:22 it is assigned 14:23:23 so seems like should i review it 14:23:37 for this month :) we need to add some points to it 14:23:54 points for review? for design? for development? 14:24:03 for development 14:24:08 ok 14:24:13 i added it to my review list 14:25:12 thanks :) 14:25:27 next one is #32228 14:25:58 love it 14:26:03 will add a comment there 14:26:04 I guess this one needs another ux perspective 14:26:04 siiiiiii 14:26:08 yup :) 14:26:26 * emmapeel felt ashamed not to have noticed before 14:26:33 I think we have a couple of options for how we can do it 14:26:36 it could also be a nice one for a new contributor 14:26:47 as the code changes seem relatively easy 14:26:57 yep 14:26:58 the hardest thing is probably building tor browser to test it :P 14:26:58 also about this, i was thinking maybe on the websites we should add the onion address tiny on the footer or somewhere 14:27:19 well, we should dogfood and add the Onion-Location header really ;) 14:27:30 yeah indeed 14:27:37 i thought that was not finished or something 14:27:56 do you know if acat's patches are streamed to the latest nightly pili? 14:28:19 no 14:28:22 they still need review 14:28:34 thanks GeKo 14:28:36 and testing 14:28:38 yw 14:28:39 GeKo was too fast ;) 14:28:46 oki, next? 14:29:20 #32324 a blockbuster 14:29:34 yup... 14:30:10 mmm 14:31:02 did we ever discuss the mocks? 14:31:05 I don't remember 14:31:12 that needs more work, and maybe firefox's approach on it is just adding letterboxing silently under fingerprint protections and that is all 14:31:44 pili we didn't, i talked a bit with tjr about them in the ticket 14:32:33 is it worth discussing here or is it better left for the browser team meeting? 14:32:56 maybe we can discuss it here, after the triage 14:33:44 ok 14:34:01 #32325 14:34:02 following ticket is related, #323 14:34:04 yup 14:34:33 we are working on that ticket, yes 14:35:14 ok, next: #32330 14:36:12 i disagree with mcs there, it doesnt need to be so easy but is a good feature for advanced users 14:36:19 i'll add a comment 14:36:26 i think we should change the 'new' on the tickets we are working on 14:36:37 emmapeel: yes 14:36:43 new is like unconfirmed 14:37:11 which is somehow related with #32572 14:37:47 #32459 << this one 14:38:30 #32330 is a new for me, i should add it for january? or for december? 14:38:39 hmm, emmapeel I see what you mean, but it's not assigned or planned yet 14:38:42 let me check again 14:38:55 I'd be tempted to wait for ETP for this... 14:39:19 since we're not going to implement a new UI 14:39:42 antonela: maybe january 14:39:52 that's when it's currently scheduled for on browser side 14:40:14 cool, added to jan list 14:40:38 ah, wait I didn't realise you'd moved on to #32459 14:40:50 I thought you were mentioning that in relation to the previous ticket 14:41:23 yes yes 14:41:29 anyway, we could make it a bit easier to edit torrc from tor browser 14:41:38 but that's not anything we'll work on any time soon 14:41:39 #32460 ? 14:41:45 this is a hot topic ;) 14:41:55 oh yeah 14:41:59 we talked about this last week, we will run user research over it 14:42:07 yup, can move on to the next ticket 14:42:10 should i mention it in the ticket? thurayya do you want to jumo it? 14:42:16 *jump on it 14:42:33 #32562 14:42:36 antonela: yes! 14:42:51 thurayya: thank you! 14:42:57 I think nothing for us to do on #32562 14:43:17 not there, but we need to define what we are going to do in TB 14:43:24 the net team already did their part 14:43:49 yeah it has dissapeared from the query during our meeting! 14:44:00 I'm a bit confused about this one, is #19757 the browser counter part? 14:44:33 emmapeel: yeah, it was closed in the last 15 minutes!! :D 14:45:29 i think so pili, will comment there 14:45:39 how many tickets left? 14:45:46 * antonela wants to talk about emmapeel's one 14:45:54 not many :) 14:45:59 thanks antonela 14:46:32 #32572 14:47:10 #32572 14:47:25 zwiebelbot doesn't want to work :P 14:47:38 nope. Expose Tor advanced settings in about:preferences#tor 14:47:38 that is related with #32459, will merge both tickets by closing one - maybe 14:47:49 https://trac.torproject.org/projects/tor/ticket/32572 14:48:13 yes, i mentioned it before, that is why the bot is not doing their work 14:48:29 i see 14:48:46 * antonela btw #19757 is not related with #32562 14:49:15 so, that is all isn't? 14:49:15 I'm a bit confused about #19757 someone will have to explain it to me later... 14:49:16 anyway 14:49:29 #32645 14:49:32 yeah and i want to say something: it is onion service, not hidden service@ 14:49:33 is the last one 14:49:38 emmapeel:+1 14:49:50 that is mine and should me a must on a s27 objective 14:50:03 i'm discussing it with pospeselr and the tbb dev team 14:50:56 okey, i'll move to emmapeel's item and we can discuss the kanban update next week 14:50:59 #31963 14:51:04 i think is a YES 14:51:14 i opened a similar ticket at dip for tpo.org 14:51:15 thanks. the translator open this ticket a while ago but i slept on it 14:51:28 ok 14:51:41 :) 14:51:48 i think it is very important and also maybe it is even part of our license requirements 14:52:18 the translators names can be pulled somehow automatically from the .po files, but not from the .properties and .dtd files from tor browser 14:52:48 but there are more names to pull everywhere in the code as well 14:52:53 yes 14:52:56 i love it 14:53:10 i hope we can move it forward with the dev team as well 14:53:11 * antonela https://dip.torproject.org/torproject/web/tpo/issues/27 14:53:17 that is the one i made for the website 14:53:32 win 3 14:53:38 :( 14:53:57 ha! 14:54:24 oh sysrqb i didnt ha at you, but at antonela 14:54:33 let me add it for February... 14:54:45 hi sysrqb /o 14:54:47 haha 14:55:06 :) *disappears* 14:55:13 oki, for next week we have 1. the last meeting of the year, 2. the kanban update and we want to discuss letterboxing related stuff 14:55:35 pili, could you review the kanban and update our roadmap so we have a better reflection of the reality? 14:56:09 yup! might not get around to it today though, still have a few reports to finish off :( 14:57:39 yes, i mean for next week 14:57:46 ok, i think that is all folks 14:57:52 thank you! 14:58:19 thanks! 14:58:51 #endmeeting