17:02:56 #startmeeting support.tpo sync: ux, community and comms teams 17:02:56 Meeting started Wed Jan 10 17:02:56 2018 UTC. The chair is isabela. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:02:56 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:03:02 hello pari ! 17:03:04 welcome! 17:03:16 does everyone know Pari? 17:03:17 give me one min to get the pad 17:03:21 * isabela does 17:03:49 hi Pari! 17:04:08 Back in a moment, terminal is messing up 17:05:11 Back 17:05:37 sorry 17:05:42 getting things together :) 17:06:03 https://trac.torproject.org/projects/tor/ticket/24129 17:06:14 our main ticket has a list of things we need to do to launch this site 17:07:30 i pasted it here 17:07:31 https://pad.riseup.net/p/support-tpo 17:07:39 for us to interact with 17:08:03 ok 17:08:12 can anyone give an update on the state of the articles? 17:08:28 isabela: those are edited and pretty much ready to be incorporated 17:08:32 let me get the link to that doc 17:08:50 https://docs.google.com/document/d/1bOX9KSTFrc7rkMbw-QgKG9jAu6JIGMA83bvz7TMsaLE/edit?usp=sharing 17:09:10 now, I think we will continue writing more, since we're getting a lot of great ideas from Pari's user issues research 17:09:25 :) 17:09:31 so let me know how we could best incorporate new articles 17:09:57 we can add them to this doc as we have them, or we can make a new doc, or we can wait until the site is launched and just add them there 17:10:24 flexlibris: i think that we will build the site with what you have on that doc 17:10:30 create a new one with new articles 17:10:30 cool 17:10:38 and then we roll them out later 17:10:41 what about that? 17:10:42 sounds great 17:10:53 awesome 17:11:02 and then 17:11:30 a think one thing to build is for the team who will keep support updated (that is community team or will this be tor browser team?) 17:11:44 that's something we never came to consensus on 17:11:46 should have a process for adding new articles 17:11:49 I agree 17:11:58 which includes, revision, translations etc 17:12:01 ok 17:12:05 maybe we do that in rome! 17:12:10 sure 17:12:14 is a good timing 17:12:25 I personally think some combination of the two teams would be best 17:12:28 but please, keep wwriting new ones in a new doc, more the better :) 17:12:29 like a support sub-team 17:12:30 I'd imagine it will be maintained by the community team, kinda like the tb manual is. But hoppefully with assistance from tb team? 17:12:30 great 17:12:42 wow.. sorry, my terminal is replacing lines again. Going to reconnect. 17:12:56 I think it's ideal to have some TB people working on it too, because it's a prompt for them to interact with the content 17:12:59 poor phoul ;( 17:13:08 and that can give them a better sense of what issues users are facing and all that 17:13:22 yes, maybe this process includes tb as reviewers or someething 17:13:28 yes totally 17:13:52 great! so as for adding those to the site 17:14:02 hiro will add them at first, as she is building it 17:14:15 but for after launch, y'all should know how to do it yourselves with leckotr 17:14:29 *lecktor and hiro would just 'merge and push' 17:14:57 yes, should be simple, I already familiarized myself with using Lektor 17:15:15 cool! 17:15:17 moving on 17:15:20 I have as well 17:15:52 antonela: for support site, do you think we need this? update high definition mockups with real content 17:16:02 not really 17:16:03 i dont think so, because we did for the UI strings 17:16:08 and the rest is articles 17:16:14 we have all the styles ready with the styleguide 17:16:20 ok 17:16:23 will cross it then :) 17:16:25 yes, we are good to go there 17:16:58 alright! let me explain this: 6) guerrilla user testing #1 17:17:23 yes I was wondering how that will be done 17:17:36 i will create a quiz, stating problems and asking for people to type words they would use to search our site for articles to solve this problem 17:17:58 sukhe and antonela will apply this to folks in India when they do their user testing 17:18:17 goal here is to latter figure out how well we are doing with our search indexing etc 17:18:35 i think this is the main functionality to test in this site 17:18:44 pari: user testing will be happening on Mumbai, Saturday 20th 17:18:48 and with what will have by the time antonela and sukhe will be there in india 17:18:59 the quiz is the best input for test that we can do 17:18:59 hey I think I am going to be in Mumbai that tme 17:19:00 time 17:19:07 pari: nice! 17:19:20 pari: awesome, you should join us there 17:19:25 so, i will share the quiz with you all too 17:19:28 cool! 17:19:38 Yes would love to join! 17:19:42 :) 17:19:50 because i think your input on the issues we will state for folks to think of keywords will be importatn 17:20:26 pari: btw your spreadsheet is something i plan to use for inspiration :) 17:20:30 If you need anything translated before that, let me know and I can try and make that happen. 17:20:31 yes exactly, it is important we simulate it to be as close to real issues as possible 17:20:33 very useful 17:20:41 pari: I'll share with you the details about the event next week 17:20:47 great 17:20:47 thank you so much 17:20:58 I'm glad it was useful 17:20:58 yessss I'm so glad you're incorporating Pari's research here 17:21:07 so that is that :) we can coordinate more off meeting just want to make sure everyone understands what we will do here 17:21:16 do share. I will email you my PGP signature 17:21:41 awesome! next one 17:21:58 pari: super, thanks! 17:22:41 antonela: :) 17:22:41 7) start coding the pages 17:22:49 hiro: said she would be a bit late i think 17:22:51 hiro: ping 17:23:05 but i know she started this and i know she needs the sitemap to know if she is done hehe 17:23:22 I am here 17:23:26 i think now with the articles will be good for her 17:23:27 aha! 17:23:47 hiro: you also wanted Phoul to review how you internationalizing stuff right/ 17:23:50 ? 17:23:51 yes 17:24:17 Phoul have you had time to look at my email? would that be ok? 17:24:28 I know it's from a while ago 17:25:02 but basically: https://oniongit.eu/infra/portal/blob/master/databags/menu.ini 17:25:12 for localising the menus 17:25:35 did Phoul have another terminal issue? 17:25:54 Sorry, was just checking for the email. 17:26:07 ah it's okay, just checking on you :) 17:26:09 and in https://oniongit.eu/infra/portal/tree/master/content there is a contents.lr for english and contents+es.lr for spanish 17:26:20 That should work as expected, however right after this I will throw up a test version on Transifex to make sure and respond to that email. 17:26:26 I'm sorry, somehow I missed this email entirely. 17:26:31 sure no worries 17:26:44 Phoul: oh that would be super to test it 17:26:52 also how do we want to do the url structure? this is not urgent but good to have it in mind 17:27:00 flexlibris: appreciated, the buffer seems to randomly decide to stop scrolling and just replace the last line. Annoying. 17:27:07 ugh annoying 17:27:51 hiro: Hrm, Ill put some thought into that. I imagine what we decide for this we will want to carry over to other portals once they are up. 17:27:51 hiro: yes, i will think about it. i need to refresh my brain on what is better for search etc 17:28:11 yes also we can easily localise the urls or not 17:28:17 yes, namespace continuity for the other portals definitely 17:28:18 i mean 17:28:20 I'll think on it some too 17:28:53 if we dont use /en/p918230139 but .html&=title.blah.dlasl.dlas 17:29:21 I mean we could have /about and /es/about or we could have /acerca 17:29:27 yes 17:29:44 with lang define on url or just the title 17:29:48 ok 17:29:49 i will think 17:29:50 or /es/acerca ... not sure... just think about it this can be easily changed 17:29:50 :) 17:31:23 ok i added it to the pad 17:31:32 next one is : 8) once content is finished we upload them on transifex for translation to start 17:31:45 Phoul: i added you will test the internationalization 17:31:55 Great! :) 17:31:58 about the onboarding doc we start chatting over email 17:32:33 I will go ahead and expand the wiki page to include onboarding information, and some more specific information for users. 17:32:34 how folks feels about that? organizing the process end to end and document it, then update the wiki to include screenshots and have a full onboarding for translators 17:32:58 s/users/translators, oops. 17:33:19 Phoul: thanks! i think we should have one document with the whole end to end process and who does what (which includes the translators steps but ours too) 17:33:31 and one for the translators only 17:33:45 the first one is more for internal use 17:35:55 I'm happy to make a translator-only document, however aside from the approval process, I'm not sure if it would be significantly different from the guide Transifex puts out. 17:36:27 Phoul: maybe i can draft in a pad the steps i am thinking for this internal doc 17:36:40 isabela: I think that would help :) 17:36:53 i was thinking of including ssteps like 'push to stage for review' 17:37:23 ok i will do that 17:37:25 :) 17:37:29 let me write this down 17:37:49 Phoul: btw t0mmy offered to help with the translator doc too if you need any help :) 17:37:53 maybe ping him later 17:38:05 * t0mmy is lurking =) 17:38:31 t0mmy: I will likely take you up on that. Will get the basic content together, and then we can figure out making it look / read nicer for translators. 17:39:09 t0mmy: o/ 17:39:15 ok 17:39:32 so this is it :) is where we are with the project and what we need to do next 17:39:49 i think we could try to launch this by end of jan or early feb 17:40:01 depending on how long translations take 17:40:26 For that, are we wanting to wait for all major languages to be complete before launching? Or launch with what we have and add to it? 17:40:37 Phoul: we are doing just the tier 1 langs 17:40:49 Sorry, thats what I meant by major in this case. Should be more specific. 17:40:59 aha 17:41:02 yes 17:41:04 you right 17:41:06 https://trac.torproject.org/projects/tor/ticket/21222 17:41:08 the ones listed here 17:41:17 at the 'what about translation?' section 17:41:18 hehe 17:41:44 My only concern is if one language lags on translation, it could delay us if we are waiting on all of them. 17:41:57 Will try and be sure that doesn't happen. 17:42:11 yeah, if it does we can make a call at the time 17:42:19 Sounds good 17:42:21 we can always leave one behind if we think is ok to do so 17:42:28 and then release it 17:42:41 but lets think of that if we need to think of that :) 17:42:46 hehe 17:42:50 Phoul Sounds good, we'll be in touch. 17:43:15 Phoul: i would say to prepare the reviewers too 17:43:22 like give them a heads up that this load will come 17:43:55 isabela: Good idea, will send an announcement out this week with that information. 17:44:32 cool! 17:44:49 i think we good for this sync, catching up after the holidays etc 17:44:55 how folks feel? 17:45:07 i also want to keept his every wed 17:45:10 till we launch 17:45:18 That works for me. 17:45:27 even if its just a 10in update sync 17:45:34 +1 17:45:38 but will be godo to keep the mojo 17:45:39 hehe 17:45:58 fantastic! 17:46:14 feeling good 17:46:15 does anyone has anything ? questions, comments, worries, blockers 17:46:26 excited to see this really taking shape 17:46:30 +1 ^ 17:46:31 :) 17:46:35 :) 17:46:45 sounds exciting :) 17:46:55 indeed 17:47:03 alright people! I will end the bot then 17:47:09 #endmeeting