17:00:36 #startmeeting ux weekly sync 17:00:36 Meeting started Tue Feb 22 17:00:36 2022 UTC. The chair is donuts. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:36 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:41 o/ 17:00:48 hello 17:00:54 \o 17:00:58 hi everyone 😂 17:01:07 pad is here, as always: https://pad.riseup.net/p/tor-ux-team-2022-keep 17:01:39 welcome to a new week 17:02:15 just one quick announcement today: a new alpha was released for desktop on friday(?) 17:02:55 the next release should be 11.0.7 stable in a couple of weeks' time 17:03:09 okay, let's update the weekly planning section of the pad 17:03:20 reminder to please highlight anything you'd like to discuss in bold 17:03:32 and also review and update the team kanban too 17:03:40 https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&label_name[]=UX%20Team 17:07:31 how are we doing nah/nicob/ 17:07:33 *? 17:08:00 good! 17:08:03 and done 17:08:14 done! also good lol 17:08:36 great, looks like your item's the only thing to discuss nicob :) 17:08:41 "Onion sticker re-design sketching" 17:08:53 o/ 17:08:59 :D 17:09:24 oh ok! Just a quick question really donuts, did you have any suggestions for next steps? It seems like we were at a stand-still for processes at this point 17:09:32 https://gitlab.torproject.org/tpo/operations/fundraising/-/issues/84 17:09:41 by the sounds of things I think fundraising are open to new ideas 17:09:54 okay so I should keep exploring 17:10:07 yeah, without the restrictions we previously discussed 17:10:15 I guess we could wrap this up with 3 options 17:10:24 the original sticket, a revised version, and a totally new version 17:10:31 if that sounds good? 17:10:32 that sounds great to me 17:10:34 thanks! 17:10:38 awesome! 17:10:57 also congrats on launching the CfP nah! 17:11:01 \o/ 17:11:10 hope we get many volunteers 17:11:18 I need to follow you're lead and do the same with the tor-qa survey 😂 17:11:29 I think it's good to go though, just needs activated and emailed 17:11:43 me too nah 🤞 17:12:09 it looks like we haven't received a lot of feedback on the user stories, let's chat next steps after the meeting tomorrow on that front 17:12:17 I'll send around a reminder shortly 17:12:28 i was going to suggest a reminder as well :) 17:13:00 our survey for feedback on digital security needs didn't get answers, so i sent a reminder today 17:13:06 and some ppl already replied 17:13:16 I'll do that -> then meeting minutes -> then tor-qa after lunch 17:13:20 I saw that too, that's great! 17:14:01 okay I added a new evergreen item to our agenda either last week or the week before 17:14:04 and that is... 17:14:10 yes! 17:14:17 💃 3. Check-in with user support 🕺 17:14:25 haha 17:14:31 :D 17:14:34 how's it going championquizzer? :D 17:15:23 nothing major to highlight this week, i think most q's we got was around verifying tor (little-t) signature.. 17:15:41 https://forum.torproject.net/t/release-0-4-5-12-and-0-4-6-10/2024/6 17:15:53 https://gitlab.torproject.org/tpo/web/support/-/issues/286 17:15:59 (is fixed now) 17:16:19 aha, good! 17:16:33 looks like there's an MR for the Android downloads issue in the works too? 17:16:41 yep! 17:16:41 https://gitlab.torproject.org/tpo/applications/android-components/-/merge_requests/80 17:17:24 ah, in fact it looks like there's some reading I need to catch up on on that subject too 17:17:30 * donuts is looking at https://gitlab.torproject.org/tpo/applications/android-components/-/issues/40075 17:17:48 okay, I'll catch up on that this afternoon too 17:17:56 one quick note regarding surveys, we are using the tag 'research' for all survey related posts on the forum now: 17:18:01 https://forum.torproject.net/tag/research 17:18:21 oh great to know, ty 17:18:24 so if you publish a new survey feel free to use that tag :) 17:18:34 I think our current surveys will be private initially 17:18:40 yep 17:18:44 (the S101 call for participation and the tor-qa survey) 17:18:51 right! 17:18:58 but we'll use it for the features survey if we distribute that publicly 17:19:16 just wanted to note since we have been discussing in the past few weeks 17:19:26 for sure, thanks championquizzer! 17:19:40 yw! 17:19:54 is that everything from the user support department for today? :D 17:20:11 i have a feedback 17:20:17 go for it emmapeel! 17:20:24 donuts: yes, lemme know if you have any questions 17:20:36 i pasted it before on tor-ux 17:20:42 let me repaste 17:21:18 ah yep I see it 17:21:20 i think we should say to users not to add more than 3 bridges when running Tor or Tor Browser. sometimes users may add like 30 bridges in the hope that one of them will work, but i think that makes tor take long to connect because it has to time out on a lot of offline bridges 17:22:00 if that is the case a warning in the provide a bridge modal also be appropriate 17:22:04 i am not sure where to report this. in tor, in Tor Browser? 17:22:27 we also discussed the possibility of soft errors during bootstrapping too, I could imagine this being one of them 17:22:39 yes 17:22:47 it would be useful to warn the user which one of the bridges are offline as well 17:23:10 emmapeel: yeah it kind of depends on what approach we want to take 17:23:14 hrm 17:24:14 you could add it as a comment to the open ticket for the bridge modal maybe emmapeel 17:24:20 * donuts goes searching... 17:25:05 https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40552 17:25:29 actually that's maybe not suitable 17:25:52 okay, feel free to open a ticket in applications and someone can move it to Tor later if they want :) 17:28:01 * donuts has just sent the reminder to the vpn list 17:28:36 nah: yeah, I wonder if/how we can do that 17:28:49 the current designs only display the bridges that actively get used 17:28:57 during bootstrapping, maybe?! 17:29:33 one other thing to consider is it'll only log the bridges that fail, presumably 17:29:53 nah: I was actually thinking in the redesigned settings modal 17:30:07 but also maybe with soft errors during bootstrapping too 17:31:33 hmm 17:32:32 okay, let's have a think about this :3 17:32:40 anything else for today or shall I adjourn the meeting? 17:33:07 all good for me personally 17:33:57 closing in 3... 17:33:59 2... 17:34:01 1... 17:34:01 thanks all! o/ 17:34:04 #endmeeting