[15:50:13] isaacj: o/ [15:50:22] leila: yep [15:51:01] isaacj: I don't see Diego's calendar. It seems it's set to wmf being able to see it. can you double-check to see if you can check his? (he looked into it today and couldn't see a change on his end that's why I'm checking with you to see if it's me or you have the same problem;) [15:51:30] leila: i can see busy/free [15:51:44] isaacj: ok. you can see those. I can't. :) [15:51:54] isaacj: so it's me. I'll look into it on my end. [15:52:00] isaacj: thanks for checkign. [15:52:04] checking* [15:52:18] well probably not you so much as browser cache mess :) [20:43:00] J-Mo: I'm reading your notes from your email with Stephen. not-perhaps-surprisingly, some of the pain points are shared with existing research. for example, translation and the fact that you need guarantee on the quality of it reminds me of a similar issue we face in why the world reads wikipedia. and getting it right will require, at the moment significant volunteer time (one person, but a lot of it) [20:43:11] J-Mo: interesting. looking forward to read your excerpt. [20:43:44] email -> meeting [20:44:50] leila: yeah, the conversation reminded me of when abbey and I were trying to figure out how to do remote user testing in a cost-effective way. Use UserZoom? Use Usertesting.com? Do we need a CRM for participants? Should we build our own tool? Lot of the same issues. [20:46:11] J-Mo: oooof. yeah. and the analysis of it is a pain, too, in these cases. bringing these closer to our infrastructure make sense to me (if it's something that is becoming more and more integral to what we do) [20:46:54] makes more sense to me too. but I suspect even scoping an MVP will be a good chunk of work. [20:47:26] J-Mo: totally. I should stop reading the full thing. :D [20:56:16] quiddity: o/ [20:56:41] quiddity: do you by any chance know that if we have a request for CL support whether we should create a task in the backlog of https://phabricator.wikimedia.org/project/view/3885/ or not? [20:57:16] quiddity: I was looking for community-relations-support but it seems that project/board/tag is closed now. [20:57:22] leila, [in/de]structions at https://office.wikimedia.org/wiki/Community_Relations#Support :-) [20:58:08] quiddity: I swear I checked officewiki. [20:58:21] * leila feels one more time unable to use the search function [20:58:30] All good! E_TOOMANYLOCATIONS [20:58:31] quiddity: thanks. [20:59:08] J-Mo: soooo, I had a follow up to tell you how to request for CL support. I just learned via https://office.wikimedia.org/wiki/Community_Relations#Standard_/_public_requests [20:59:31] excellent! Thank you for that, leila [20:59:39] np [21:18:28] isaacj: I'm blanking. what is the complexity for adding a few form text option in quicksurvey? is it design and engineering challenges or just engineering? [21:19:22] isaacj: fwiw, and I'll update you once the conversation converges, it seems by offering man, woman, nonbinary, and prefer not to say options we will exclude the case of transgender users. There are currently two approaches being discussed. [21:19:36] isaacj: well 3. 0) fix the free form text option. ;) [21:20:04] isaacj: 1) ask a second question upon completion of the first question which asks whether the person identifies as transgender. [21:20:37] isaacj: 2) turn radio buttons to checkboxes (is this currently possible in quicksurveys?) [21:21:44] :( yeah, none of those are straightforward. the first (fix for free-form) is in my opinion the most generally useful [21:22:01] isaacj: agreed re 0. [21:23:04] isaacj: are you sure choose multiple options is not possible? back in the day where QS was used for collecting contributions for a short period of time, the user could choose multiple tags which is, perhaps, equivalent to being able to choose multiple choices. [21:24:01] isaacj: (as a side-note: I'm all up for time-boxing this and finding a solution that can unblock us. after hearing the point about some of these points raised I'm thinking "how hard is it to fix the free form text really?") [21:28:03] leila: i'll look but i'm pretty sure that radio is the only possible answer style. [21:29:15] isaacj: got it. [21:31:08] i don't know about the design side of things re open-text but i could see it being trickier w/ how the data is sent to the server (as an encoded URL, which has length restrictions). but yeah, the engineers would have to answer that probably [21:32:48] isaacj: yeah. I'll ask Olga on Monday/Tuesday. I don't want to make her very sad in the weekend. [21:33:54] :) couldn't agree more. this might be part of the larger conversation of whether this should instead be energy injected into an annual revised Community Engagement survey [21:40:16] * leila takes a note of "energy injected" [21:52:17] leila: done with tweaks, so you can do a full pass wheneer [21:52:20] *whenever [21:53:08] J-Mo: I left one question for you on page 1. and I'll do a pass over it soon, but I think besides that one question, the rest gives me/us enough to discuss it on Tuesday. Thank you! [21:53:40] perfect!