16:59:27 #startmeeting ux weekly sync 16:59:27 Meeting started Tue Feb 8 16:59:27 2022 UTC. The chair is donuts. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:59:27 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:59:33 perfect timing nicob! 16:59:33 hello o/ 16:59:38 hiii 16:59:43 hi championquizzer! 16:59:59 welcome to this week's UX Team meeting everyone 17:00:06 heya 17:00:10 as usual, the pad is here: https://pad.riseup.net/p/tor-ux-team-2022-keep 17:00:28 please take a minute to add anything you may want to discuss to the agenda 17:00:42 otherwise, there's just one announcement this week 17:01:04 our first release of the year for Android is sort of released, but not really 17:01:37 meaning there's a release post up, but it's not available anywhere yet :P 17:01:54 I see championquizzer has already posted a ticket about the APKs 17:02:02 yep :) 17:02:07 ty :) 17:02:13 np! 17:02:15 when will it available? 17:03:00 well the APKs should be up asap, but there's a slight delay between the "release" and when it's updated on other distribution channels (i.e. Google Play, F-Droid etc.) 17:03:12 this is inevitably causing confusion though 17:03:42 and I'm going to chat to the android team(?) about whether we can tighten this up a little in future 17:04:34 got it 17:04:35 ty donuts 17:04:39 okay, let's take 5 minutes to update the weekly planning section of the pad next 17:05:01 remember to please highlight anything you'd like to discuss (that's not already on the agenda) in **bold** 17:05:24 and lastly, make sure your tickets are in the right columns and assigned to the right people in the team kanban :) 17:05:26 https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&label_name[]=UX%20Team 17:10:03 okay, I'm done 17:10:06 how's everyone doing? 17:10:16 also done 17:10:46 ok 17:11:06 great 17:11:34 looks like both of the items in bold relate to the S101 (VPN) project 17:11:43 mind if I go first nah? 17:12:10 go ahead 17:12:11 :) 17:12:19 aha ty 17:12:39 so at the VPN meeting tomorrow I'm planning on presenting the work so far on both the non-empirical user stories 17:12:54 (wip found here: https://www.figma.com/file/pN5u676dfXI6Qk1wyXD7XG/VPN-UX-planning-board?node-id=0%3A1) 17:13:08 and the screenshots I've been collecting for the ecosystem evaluation 17:13:26 (not sharing the link in here because there are some IP leaks I need to tidy up first) 17:13:36 I need to finalize both this afternoon and then structure the session 17:14:14 but the plan is to encourage feedback from the project committees and development teams over the next couple of weeks, so we can validate the user stories in interviews and the next survey 17:14:20 and get started on the wireframes 17:14:35 I'll also give everyone a short update on what nah's been up to 17:14:44 which is the perfect segue... 17:14:53 (go ahead nah hehe) 17:14:56 haha 17:15:46 yep, so, while the interviews are on hold for a little bit (so we can gather feedback to create better questions) 17:16:06 i worked on a screening questionnaire for the interviews 17:16:37 so we can share the call for participation for the interviews with tor communities 17:16:54 we plan to interview at least 10 ppl in this round 17:16:54 it's looking great nah! 17:17:04 from various locations, gender, ages 17:17:14 we are looking for vpn power users and tor power users 17:17:39 i brought this up so we could discuss ~localization~ for this call for participation 17:17:55 ohhh yes good idea 17:18:00 what are you thinking? 17:18:19 well, i thought about english, portuguese and spanish 17:18:27 (languages that i'm able to interview) 17:19:10 what do you think? 17:19:21 yep, that makes sense – I'm assuming you want to localize the screening survey itself? 17:19:25 yes! 17:19:40 can we do that with a single survey in limesurvey, or does it need split in three? 17:19:56 we can do it with a single survey 17:20:00 oh amazing 17:20:15 I spotted it has an autotranslate feature, but I wasn't sure if you could do it manually 17:20:27 that are options on 'general settings' for 'additional languages' 17:20:34 ahhh I see 17:20:43 well, I think it's a great idea – go for it! 17:20:54 I'm guessing a graphic would be nice too :) 17:21:06 yes! it would be amazing 17:21:13 happy to make one! 17:21:13 now i want a graphic for all surveys 17:21:14 hahaha 17:21:17 hehehe 17:21:27 <3 17:21:28 awesome, yep just throw a ticket in ux/research for nicob ^^ 17:21:34 haha! 17:21:41 is there anything else we can help with here nah? 17:22:01 i know we can add a css to limesurvey 17:22:06 like 'additional css' 17:22:22 i'm still trying to find out where it is supposed to be 17:22:29 mmmmmmmmmmmmm 17:22:34 or if i need to ask access to it 17:22:37 access/privileges 17:23:11 anyway, i'll take sometime to look for it 17:23:21 and then i'll bring it back, probably today on tor-ux 17:23:50 I think we should just use the vanilla theme tbh 17:23:55 I know it's not great 17:23:58 but it also works 17:24:02 it's not to change the theme 17:24:07 oh 17:24:31 it's just for additional small fixes/changes 17:24:43 gotcha, in that case good hunting :) 17:25:21 not gonna spend too much time on that anyway 17:25:39 if i don't find it, we work with what we got hehe 17:25:46 no worries, sounds like it would be good to suss out anyway 17:25:49 ha! 17:26:05 * donuts checks the agenda... 17:26:21 I put "3. UX Team Q1 roadmap review" in here but I've not finished it yet 17:26:40 I still need to add things to sponsors 9, 30 and 96 17:27:03 but given you've already added everything that's on your plate nah, I don't think we need to review it before together really 17:27:13 I'm adding both my and nicob's work 17:27:45 for ref: I'll be presenting the team roadmap for Q1 super quickly at the all hands tomorrow 17:27:47 along with the other teams who haven't gone yet 17:28:02 https://www.figma.com/file/n4ETd0cUkcfj3KyclJQnt3/UX-Team-Planning?node-id=0%3A1 17:28:27 any Qs on that subject? 17:28:55 I don't think so. Is there anything you need from me? 17:29:06 nope, you're all good nicob :) 17:29:17 our work kind of blends together so it's easy for me to add 17:29:24 gotcha 17:29:30 question o/ 17:29:34 go for it nah 17:30:24 there are some ur activities planned for tor:connect this quarter on s96, i think? 17:30:49 ah yep, I was in the middle of fixing S96 when this meeting started 17:31:02 I repurposed the blocks you added for onionshare 17:31:08 and was about to duplicate them for the browser 17:31:09 ah ok 17:31:10 :) 17:31:18 but I need to check in to see if the timeline's still accurate there 17:31:33 S9/30/96 are still missing a bunch of stuff 17:31:42 not too much though, hopefully :) 17:32:06 :o 17:32:15 (mostly product stuff ha_ 17:32:19 *) 17:32:52 are you still around championquizzer? 17:32:56 yep 17:32:59 woohoo! 17:33:04 I see the next agenda item's yours 17:33:13 somehow though I _completely_ missed your report on friday 17:33:14 yes, that's me! 17:33:20 so I haven't looked it over yet 17:33:23 :( 17:33:44 no worries.. 17:33:46 did you get the chance nah? 17:33:50 https://lists.torproject.org/pipermail/tor-project/2022-February/003283.html 17:34:16 wow, those kazakhstan tickets are climbing 17:34:31 yep!!! 17:34:39 it was fortunate in a way that the community team already had RU language resources ready 17:34:46 donuts: no, i was reading right now as well 17:34:53 agreed, donuts 17:35:10 I can't wait until the missing features bug is fixed 17:35:25 ok ...before diving into the report i think i should give a quick overview what our work is actually ... 17:35:34 go for it, sorry championquizzer :) 17:35:39 since we have nicob now! :) 17:35:55 yes I'd love to hear!! 17:35:57 donuts: nah, championquizzer maybe we could discuss about the user feedback monthly report - format, period, etc? 17:36:39 sure, happy to do that too ^^ 17:36:57 we (the community team) coordinate user support activities at Tor. our work encompasses helping folks with software in the Tor ecosystem, collaborating on bug reports with dev teams, collaborating on user feedback with the UX team.. 17:37:21 helping users during censorship events and collaborating with ACT when required, write/maintain user facing docs 17:37:54 currently we actively monitor frontdesk@tpo (email, using RT https://bestpractical.com/request-tracker/) 17:38:05 forum (forum.torproject.net) 17:38:15 and IRC/matrix channels 17:38:18 what is ACT? 17:38:22 sorry 17:38:30 anti-censorship team 17:38:33 ah, ty 17:38:52 so that's about it 17:39:28 you can find us lurking on r/tor reddit, twitter, tor stack exchange ..but we don't monitor those support channels :D 17:39:45 <3 17:39:58 back to the report.. 17:39:59 ty for all the work the community team does 17:40:11 <3 17:40:25 thanks for the overview! 17:40:47 :) 17:41:32 .ru Tor censorship and .kz internet shutdown has been keeping us busy last month 17:41:48 we now have a telegram support channel for users in .ru! 17:42:00 \o/ 17:42:57 re. missing feature on mac/windows. we got a number of tickets for that issue ..but i see the bug is fixed and might make into 11.0.6? 17:43:28 richard has just confirmed that in #tor-dev, yep! 17:43:36 awesome 17:43:47 * donuts is looking forward to it 17:44:06 and we saw an uptick in the reports for https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40192 17:44:28 o/ 17:44:32 hrm, any leads as to why? 17:45:10 i am not entirely sure ..but I can confirm i could reproduce the bug 17:45:16 once aguestuser is fully settled in and TBA releases have been smoothed out, I'm going to review the open bugs for Android and see what we can prioritize now it has dedicated dev resource 17:45:31 hopefully in march-ish 17:45:47 apologies for the wait :/ 17:45:59 no worries 17:46:06 if this one's generating a lot of tickets, we could look into it now though 17:47:10 i would not rush but report back if we see more reports of this :) 17:47:24 sounds good! 17:48:02 ggus: thanks for bringing this up! 17:48:18 i am happy to keep this monthly .. 17:48:31 but open to suggestions, feedback :) 17:48:48 I'm more than happy with this format/frequency – I think it works great 17:48:53 so I have no notes :) 17:49:32 except to say thank you for doing these reports championquizzer and fielding our Qs afterwards <3 17:49:38 nah: any comments? 17:50:16 i'm happy with it too! 17:50:23 awesome 17:50:23 thank you championquizzer and community team ;) 17:50:59 was there anything in particular you wanted to bring up re: the format ggus, or were you just checking in? 17:52:13 donuts: we started using that format during Outreachy project with Pari 17:52:24 idk now with weekly meetings make sense waiting 1 month to report to devs 17:53:31 the user feedback report should help on prioritizing TB and TBA tickets 17:54:05 ah, I see! I'm happy to stick to monthly for the reports themselves – and championquizzer can let us know of anything pressing (like the downloads issue) that needs attention inbetween during regular weekly meetings 17:54:10 yep, absolutely 17:54:47 cool, that wfm 17:55:06 sounds good! 17:55:10 thanks both!! 17:55:30 okay it looks like we're at the end of today's agenda 17:55:44 is there anything else anyone would like to discuss? or are we all good? 17:55:52 i'm good 17:56:11 thanks all o/ 17:56:35 great, thanks very much everyone! catch you on IRC :D 17:56:38 thanks! o/ 17:56:40 #endmeeting