15:58:24 #startmeeting UX Team Weekly Meeting, 11 April 2023 15:58:24 Meeting started Tue Apr 11 15:58:24 2023 UTC. The chair is donuts. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:58:24 Useful Commands: #action #agreed #help #info #idea #link #topic. 15:58:29 hello! o/ 15:58:29 hello ux team 15:58:34 pad is here: https://pad.riseup.net/p/tor-ux-team-keep 15:58:40 I think nah will be a little late 15:58:46 o/ 15:59:08 I don't have any agenda or announcements today, so please add anything you'd like to discuss to the pad 15:59:12 otherwise this is gonna be a short one 15:59:25 (which isn't a bad thing, everyone's busy) 15:59:56 yeah, just added the user support report for last month to the agenda 16:00:06 but don't think there's a lot to discuss :) 16:01:45 cool! let's take 5 to update our sections atm anyway 16:04:16 o/ 16:04:41 hi nah :) 16:04:44 we're just filling out the pad 16:04:48 https://pad.riseup.net/p/tor-ux-team-keep 16:04:54 * nicob is done 16:05:42 * championquizzer too 16:05:59 okay so I know everyone's waiting on me to review various things 16:06:05 I'm sorry that's holding stuff up 16:06:23 Once I get past tomorrow I'll be back on the review train 😅 16:06:34 no worries! 16:06:46 i'm done! 16:07:16 right now I'm in a weird place where we're still recovering from S131, working on quarterly reports, and trying to support the developers for our looming S30 dev deadline 16:07:56 on that subject nah, we should have a clearer picture for what will get shipped as part of S30 by the end of the week 16:08:07 (including what fixes will be available in the next Nightly for Mx) 16:08:07 on that matter, next week i'll be in MX to the usability testings 16:08:14 great! :) 16:08:25 is it still planned to be up on the 17th? 16:08:42 yep! but some of the issue may not make it 16:08:49 i'm planning to run the activities on...friday 21st 16:08:58 FYI any issues that are still open have been moved from the 3.5 to 3.7 milestone 16:09:00 so are here instead: https://gitlab.torproject.org/groups/tpo/-/milestones/31 16:09:06 although the closed issues are still in 3.5 16:09:12 nah: okay, that's fantastic 16:09:26 how sure are you about the 21st? I'm wondering if I can give the devs a few more days 16:09:37 completely sure 16:09:49 okay that's good to know! 16:09:51 we are holding the whole 21st only for usability testings 16:09:51 gaba, are you around? 16:10:18 I'm not actually sure if I _can_ give the devs a few more days because of the code audit though, will need to check in with gaba first 16:11:04 got it -- i'll keep checking with you about it 16:11:06 the issue I'm most doubtful about being completed in time is this one: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/41617 16:11:26 but I can ask that the devs prioritize the string changes first, which should be easy compared to the rest 16:11:49 it would be good to test it on MX, but we would need them to be localized too 16:11:57 right, that definitely won't happen 16:12:02 it'll just be in EN 16:12:12 this is another thing we should figure out as part of our new process 16:12:45 yep, particularly on s30, where all countries don't have english as their mother tongue 16:13:25 yep yep 16:13:29 same goes for S96 too 16:13:41 although that should be mostly localized by now 16:14:06 okay I think we're good to hand over to championquizzer for their updates? 16:14:14 thanks 16:14:34 published the user support report for march last week: https://lists.torproject.org/pipermail/tor-project/2023-April/003599.html 16:14:48 this was our first complete month of whatsapp user support 16:14:58 the engagement looks promising 16:15:25 telegram still reigns supreme! 16:15:32 but 67 tickets from whatsapp is great :D 16:15:33 yeah! 16:15:58 nice! 16:16:33 most of our work is focussed on user support for users in countries where Tor is censored (as is reflected in the numbers) 16:16:40 how are our private bridge requests trending for CN? are they about the same as usual? 16:16:42 a lot of private bridge requests from china yet 16:16:59 yeah, I can't remember if that number was about as high last time 16:17:11 donuts: the numbers seem to be high but the fdeedback is very positive 16:17:38 okay good to know 16:19:28 i think that's about it for the updates 16:20:05 thanks championquizzer! 16:20:13 thank you championquizzer! 16:20:29 one quick thing, i will be afk next tuesday so won't make it to the meeting 16:20:45 me too! 16:20:57 no prob, thanks for the heads up :) 16:20:57 nicob I noticed you have the annual report back on your todo list, what are the timelines like for that now? 16:20:58 oh of course 16:21:03 let's just cancel next week then :) 16:21:21 next ux-community sync in CR i guess ;) 16:21:31 🙌 16:21:53 so the next IRC meeting will be May 2nd 16:22:35 there we go, looks like we had an announcement after all :) 16:22:48 hehe 16:23:15 donuts yeah! I've been working on some cover art, but am waiting for content - in our last comms meeting it sounded like pavel might take some creative liberty in copy formatting - iirc they were trying to have content complete before CR. i'm estimating mid-late may right now factoring in CR but i'd like to check in with al to determine a more accurate goal date 16:23:35 nicob: ack, thanks for the update! 16:23:56 let's call it a day here then :) 16:24:12 thanks everyone, have a good week o/ 16:24:14 thanks all :) 16:24:16 thank you! 16:24:18 #endmeeting