13:59:44 #startmeeting ux team meeting 13:59:44 Meeting started Tue Oct 16 13:59:44 2018 UTC. The chair is antonela. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:59:44 Useful Commands: #action #agreed #help #info #idea #link #topic. 13:59:50 hello people! 14:00:17 a shared link for this meeting pad https://storm.torproject.org/shared/8PePYJhTurnYMDKyYoywZn31EZgiIqktvnUJH7uwmBn 14:00:35 please, fill your updates and add topics into discussion (if you have them) 14:01:28 at the top of that pad there is a semi ended roadmap - please check if your items are there, if not lets talk about them 14:02:53 Hola! 14:03:07 hey 👋 14:04:30 elioqoshi : i saw the announcement for your talk at the moz festival, i added you at the ux team page and let me know if you need slides or anything :) 14:05:27 Perfect, thanks antonela 14:05:45 nyinz: emmapeel: please add your updates 14:06:06 emmapeel: tomorrow during the sync meeting with the tbb team i'll ping about tba translations 14:06:11 I think I still need to do some OONI branded slides but it would be good to have Tor slides as well 14:06:27 oh will be an ooni talk? they announced a tor one 14:07:30 anw, you can do the convo ;) 14:07:45 and you can kill that emoji lol 14:08:05 Yeah blame their social media coordinator. It was an OONI Probe workshop. 14:08:09 haha gracias 14:08:33 "Begin outreach material for community portal with UX ( from community roadmap, needs designer )" Can I help with this? 14:08:43 that could be great 14:08:53 It might be good to assign me something Tor related to start working on 14:09:20 Just might need a bit more time to get started so I hope it's not something too urgent 14:09:39 i mean, the community team has that item in their roadmap and i'm overloaded, so could be great if you take it 14:09:50 i'll meet flexlibris/ggus and define some scope for it 14:10:03 Sounds good, perfect 14:10:09 gracias 14:10:11 pili: you go 14:10:14 I hope it's fine that I might use some different tools? 14:10:22 (Figma + Presentator for example?) 14:10:23 ye sure, you can use whatever you want 14:10:46 hey cool :) 14:10:52 hi everyone, I was looking through the items we have to do on TPO.org and I was just wondering if anyone is reviewing the content or if that's something I should take on 14:11:02 also fyi it will probably take us into november to get the community portal materials worked on anyway, so there is time 14:11:12 what has the workflow on that been so far? 14:11:20 tpo.org friday's meeting were isabela, stephw and me 14:11:32 stephw worked with the content and we iterated over the layout 14:11:53 this friday we will back to those meetings so we can move forward 14:11:55 oh yeah, I missed last week's 14:12:04 great! I think I have it in my calendar anyway 14:12:32 colio, we are trying to finish tpo.org - tpo.org/download and tpo.org/about (and inner pages) 14:13:33 ok, that's me done on that then :) 14:13:36 flexlibris cool that gives me some breathing space as right now I'm all into OONI Probe mockups 14:13:51 pili, about s17 14:14:08 we have debriefes from uganda, colombia and kenia 14:14:17 could be cool if we can setup a framework for reporting those 14:14:39 yup, that's part of the user testing stuff I need to look at soon... :/ 14:15:05 this is something i'm personally struggling with because I'm not sure how to make it useful 14:15:09 does it need to be a public framework or just a way for peeps to look and write about them? 14:15:21 idk - what do you think? 14:15:34 idk what are the requirements? 14:15:39 I need to do my homework first and come up with some ideas i think :D 14:16:04 that's cool 14:16:04 e.g what is the format, what is the content, can we standardize? any common themes? any good conclusions we can draw from them? 14:16:13 exactly 14:16:25 (this is me thinking out loud without having looked at them yet... sorry nyinz :( ) 14:16:27 ok no fancy visualisations then? that's good 14:16:33 nono 14:16:34 it feels similar to what wayward is gathering too 14:16:45 yes, wayward work should be part of that for sure 14:16:56 s17 is community+ux work so we overlap 14:17:11 yup, i have it on my notes to work with both nyinz and wayward on this 14:17:31 cool 14:18:00 maybe sajolida has some ideas 14:18:15 i suggest you ping him 14:18:19 emmapeel: good point, I'll reach out, thanks! 14:18:30 about reporting to s17? 14:18:48 no, about gathering user input 14:18:54 sorry for noise 14:18:58 oh yes 14:21:32 * antonela updates the pad 14:21:33 any other item to be discussed? 14:22:15 not from me 14:22:40 oh, sorry, one thing 14:22:49 gogo :) 14:22:49 antonela: let me know about how I can help with the wiki content :) 14:22:56 oh yes that 14:23:31 i need to work on it - i have notes in several places and i need to put them together 14:23:49 * emmapeel dont like documentation in the wiki because is hard to localize and keep the translations updated 14:23:52 not sure if they fit on s19 reports or what but i need to finish YE campaign things to get back to work 14:23:59 emmapeel: <3 14:24:18 but i hope we will move this stuff to the community portal or something 14:25:33 how should i document our work so? i feel like there is a leak of reporting on the last changes we made, specially in tor browser and we had a design process behind those and I should report that 14:25:54 ok, let me know, hopefully we're done with S19 and YE campaign soon :) 14:25:59 and we are going to iterate over the new changes, and not sure if tickets are enough, idk 14:26:14 tickets get lost too 14:26:18 yes 14:26:24 also I am not sure we need to localise everything 14:26:25 i was talking about user-facing docs, for example the tor relay guide, is hard to keep updated and check if the translations are in line withthe english original 14:26:43 yes, this is more internal-docs? 14:26:58 yeah i dont think we need to localize internal docs, sorry 14:26:59 internal docs go on the wiki imp 14:27:05 imo 14:27:11 sure 14:27:24 the relay guide will need to be moved to community or dev portals 14:27:29 imo 14:27:32 hiro: +1 14:27:38 ye, at some point we can have those resources also in lektor 14:27:41 I think probably community 14:27:47 user-facing ones 14:27:56 (although you do need some technical knowledge for it...) 14:28:18 depends also because we need and there will be an effort in documenting tor network infra 14:28:35 so that people can know why running something is better than running something else 14:28:54 and they can make informed decisions on how they want to contribute in that sense 14:28:56 si 14:28:57 antonela: so, to clarify, these wiki items that we're talking about are for the internal wiki, reporting on the work we have done in those areas? 14:29:05 pilie: si 14:29:08 pili: si 14:29:28 pili: cool, because we went off on a tangent and I just wanted to make sure :D 14:29:45 yes, is the same thing we talked about in our 1:1 last week 14:29:50 antonela: rather... :P 14:30:11 yep 14:30:30 ok 14:31:06 this week i talked with kevun, he is a researcher and he wrote a cool paper about tor browser ux https://lists.torproject.org/pipermail/ux/2018-September/000427.html 14:31:20 not sure if he is around, but you can read it! 14:32:48 Awesome, thanks for sharing the link 14:32:54 another thing is that we will launch a tor browser icon survey soon 14:33:06 we have a couple of options and the community will pick 14:33:27 elioqoshi, i'd like to include your https://dribbble.com/shots/4464564-Tor-New-Onion-Logo-Explorations there 14:33:35 i'll send you an email before this week end about this 14:33:36 Let's just ensure this won't happen: https://en.wikipedia.org/wiki/Boaty_McBoatface :P 14:33:48 Sure, cool 14:34:08 haha 14:34:20 anything could happen 14:35:04 hiro, do you want to talk about #28065? 14:35:37 yep sure, so put everything in this ticket in the hope that we can discuss and start planning 14:35:52 there are I think 2/3 things to consider 14:36:15 1. the frontend part of things. Like all the lil css tricks we use to avoid that something doesn't work with js disabled 14:36:26 that can easily be included in the styleguide 14:36:52 yep 14:36:55 2. there is the friendliness scanner Kevin is working on, that could tell how well does a website render on tor browser 14:37:31 that sounds really cool 14:37:39 and finally 3. In tor-onions and other of our lists there are people sharing best practices and tips for onion services - apache configs - how not to leak info and so 14:37:49 these things are sometimes documented 14:38:02 sometimes "are lost in time like tears in the rain" 14:38:09 haha 14:38:23 it would be cool if we could document these best practices 14:39:00 ex: https://riseup.net/en/security/network-security/tor/onionservices-best-practices 14:39:07 definitely and also was something that came up during the tb+ux meeting in mexico by a lot of people 14:39:19 yeah, how to prevent your MTA becomes a spambot 14:39:29 :) 14:40:07 * hiro wonders if gman999 has a notification every time someone says MTA 14:40:11 ;) 14:40:26 i think he also highlights 'spambot' 14:40:28 lol 14:40:36 * gman999 shhhhh hiro 14:40:41 hehehehe 14:40:57 haha 14:40:58 best practices i caught.. and it's a general issue 14:40:58 COOL 14:41:10 so yeah if we document all this, maybe the styleguide is not the best place 14:41:26 maybe we should start in the wiki and then decide where to put this content once we have enough of it 14:41:30 lets start with the content and them we can decide 14:41:31 yee 14:41:36 *tehn 14:41:41 grr *then 14:42:00 anything else? are we groot? am i missing something? 14:42:12 groot 14:42:36 groot 14:42:36 hiro: I'm going to add some of these comments to the ticket 14:43:03 pili: groot 14:43:40 I guess I'm groot :D (I need to find out what that means, but I'll follow the crowd :P) 14:44:18 cool! it's a wrap! 14:44:21 #endmeeting