16:01:07 #startmeeting 16:01:07 Meeting started Tue May 8 16:01:07 2018 UTC. The chair is hiro. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:01:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:01:18 aaalright I am the chair 16:01:25 great 16:01:53 I think we can start with our updates? 16:01:57 yes! 16:01:59 go for it 16:02:13 this week I am cleaning up issues in the deb package for lektor according to feedback from irl 16:02:31 I am also doing some service docs and waiting on complete translations for portal 16:02:51 also doing some backend work for search 16:03:07 great 16:03:26 last week I was at a seminar so I basically cleaned up a few tickets and replied to issues 16:03:49 so this is my update. left to do is add this month recap to the ux updated to tor-project 16:03:55 we already have the job post ready for the localization services coord, i'll ask erin when we will launch it 16:04:01 yee 16:04:05 and maybe make a separate service recap 16:04:11 feel free to remove/add/whatever items there 16:04:12 for things that are only services related 16:04:14 i like it :) 16:04:22 https://pad.riseup.net/p/ux-report-april 16:04:30 yep as soon as the job post is ready we should add it to the jobs page 16:04:36 yep 16:04:39 on my side 16:04:51 i worked with #25695 16:05:00 and #25658 16:05:27 for security settings, seems like the shield icon is the favourite, so we will move forward it version for user testing 16:05:41 i have been reading/working with #25694 16:05:53 i'd like to update it before our sync with TTB tomorrow 16:06:27 i drafted the april report, feel free to edit it 16:06:45 we did Community Liaison Interviews, i have been in cryptorave last weekend 16:07:07 im writing a blogpost about Tails+Tor Users session there 16:07:14 nice 16:07:58 i think i can have something readable to share with Intrigeri tomorrow :) 16:09:01 alison and me we were working on S9 things, defining our activities in Uganda 16:09:40 that's happening in 2 weeks right? 16:09:46 and i already sent the demographic questionnaire to our partners 16:09:58 yep that turned out nice with survey.tpo 16:10:14 yes is happening in 2 weeks 16:10:16 :) 16:10:21 lets see how it works 16:11:24 * flexlibris is here if you need her 16:11:51 one thing we should discuss is how we could reach out to the mozilla people reg their loc platform 16:12:20 we still need to define the ux activities for Uganda, but i have in mind: TTB user testing for OTF improvements, update our Persona documentation, work with the community to define threat models and collect user needs 16:12:34 oh yes 16:12:37 since we are BFF 16:12:43 haha 16:12:55 we can actually 16:13:15 do you want to ask to the list first? seems like it is a group move 16:13:21 maybe I can start an email thread 16:13:40 we should see if it could work for us and if we could test it a bit 16:13:40 cool, what is the list? localization? 16:13:44 yep 16:13:49 I was thinking first ux 16:13:53 oh okey 16:13:54 yes 16:13:55 go for it 16:14:53 not sure if we have any other thing? 16:15:53 i dont think so 16:16:05 can i add agenda items? 16:16:08 yes 16:16:09 sure 16:16:18 hi irl! 16:16:20 #24422 16:16:29 https://trac.torproject.org/projects/tor/attachment/ticket/24422/map.png 16:16:45 some work in progress that is ux related 16:17:05 wow! 16:17:16 lovely ticket :) 16:17:19 * dmr lurks and glances through updates occasionally :) 16:17:29 once the bootstrap is mature enough to start integration, i'm planning to shuffle around some of the content on the metrics website 16:17:49 this is my map of the content that we have, or should have, so far 16:18:02 it's probably not complete and currently this is only a hierachical view, there will be more interlinking 16:18:35 it's probably a good idea at this point to share this with you, as there may be other portals that might want to link to metrics content, and also we might want to link metrics content to other portals 16:18:42 and i guess ux are the people that know about all the portals 16:18:48 yes, that is useful for sure 16:19:26 did you run it automagically? or which tool are you using to map it? 16:19:40 hey irl maybe this is loosely related but maybe one thing to include in the scope of this work could be how information in the data is also related and structured? 16:19:53 antonela: http://www.insilmaril.de/vym/ 16:19:55 oh yes 16:20:13 so that it is easy for people to search for things that can be correlated or easy for them to run their analysis on raw data 16:20:35 and also related with the terminology source-of-trust we talked about last week 16:20:59 yep, so we're currently (for Sponsor13 i think) producing a lot of documentation around how to process the data, and i want to make sure that any graphs always link back to the data and processes that made them 16:21:20 ah yes, for the terminology, we have decided to try a new policy for the metrics glossary 16:21:39 tell me more 16:21:40 i will be making a patch for torspec to include all our current terms in the torspec glossary, and that will be the source of truth 16:21:47 yess 16:21:55 but we will not be using the definitions word for word 16:22:05 karsten rightly points out that these glossaries have different audiences 16:22:09 yes 16:22:20 so the metrics glossary will probably be less technical whereas the torspec glossary would be more technical 16:22:35 the important thing is that the definitions do not directly conflict, even if they are described differently 16:22:40 and then we can create a human-based one ha 16:22:56 yep 16:23:23 perfect, thanks for jumping here and working on it! 16:23:25 we can see how well it goes integrating metrics terms into torspec, i'm guessing that it's probable that we don't want to have all the community terms in 16:23:26 but 16:23:27 irl: cool to hear the glossary work - sounds like good direction to have a few glossaries! 16:23:43 maybe there is another organisation that maintains a glossary of useful terms, maybe eff? 16:24:09 community could then reference the eff glossary or the tor glossary depending on whether or not it's a specific tor term 16:24:17 (i don't know if they have one or not, just an example) 16:24:35 generally speaking there is a lot of things that we and the eff do and somehow might overlap 16:24:47 we talked in rome about how to share more of our work mutually 16:24:53 yes, not just eff 16:24:56 exactly 16:25:07 maybe we all just start contributing to wikipedia's dictionary 16:25:18 on thing that we mentioned was maybe start with a repository on the gitlab that riseup maintain and use that 16:25:32 that sounds like a good idea 16:25:49 it would be good to have reusable content for this 16:25:50 the idea in the case was less of a glossary but mre in terms of "things" that we might share 16:26:04 so the glossary would fall under that :) 16:26:07 yep 16:26:09 sounds good (: 16:26:18 yes, is awesome 16:26:20 also that has also a wiki 16:26:35 so we might have common documentation that we want to sahre and maintain 16:26:38 I don't know 16:26:48 one thing I could do is start that repository and invite people to it 16:26:50 im thinking how we can work with metaphors/technical explanation, like maybe depends on user suggest a definition? 16:27:13 i think there would definitely be a benefit to everyone working in the same space using the same terminology 16:27:26 if we think end-to-end encryption means one thing while eff think it means something else 16:27:32 that's going to be a disaster for users 16:27:35 yes 16:27:50 so it's like a shared style guide for writing i guess 16:27:59 this is why we should join forces, not just with EFF, but Tails, SecureDrop floks, for sure 16:28:01 yes 16:28:21 yes also one thing that I was discussing with antonela is that going forward if org like mozilla and brave start integrating tor, having common terminology is one thing that will help the integration process and adoption too 16:28:49 also maybe commond docs (ex: the mozilla dev network) 16:28:56 and this tool might help us on it 16:28:57 definitely 16:28:59 but that's maybe too far away in the future 16:29:28 anw, is good to have a vision about what we want to build :) 16:29:45 ok, well, i will let you know how i get on with the metrics glossary 16:30:01 great! thanks a lot irl! 16:30:02 and I will share the repository 16:30:05 :) 16:30:07 ok cool (: 16:30:12 iujuu 16:30:16 i owe you/everybody a lot of styleguide related tickets. I'm working with apps (TTB desktop/android) this month, but next one i'll back to website/styleguide related tasks 16:30:24 irl, something there is blocking you in any way? 16:30:44 if you spot anything where you think things could have linkage in the information architecture for metrics, send me a mail, that would be good 16:30:56 nothing is currently blocking me, but i maybe have one more agenda item 16:31:03 yes sure 16:31:07 https://people.torproject.org/~irl/snowflake/ 16:31:32 i have no idea when these meetings happen, but did anyone want me to do anything with this? 16:32:29 "these" being the snowflake meetings 16:32:40 oh, i have a backlog item to design a landing for it. But your help and implementation there was perfect! 16:32:48 is the same content we had before, so i think is ok for now 16:32:57 exactly the same content 16:33:11 i literally stuck the header and footer on it and uploaded the css 16:33:39 i know, thanks for it :) 16:34:04 ok cool, so there's nothing you need from me on that and it's under control? 16:34:28 it was definitely useful to do as i discovered the x-frame-options header preventing anyone from actually being a snowflake bridge 16:34:43 but it's also probably easy enough (and you'd do a better job) to do the integration again 16:36:05 i'm not sure which sponsor we have (if we have) for snowflake, so if we are going to improve it is out of my hands for now 16:36:16 ok 16:36:25 that's all my agenda items then (: 16:36:28 thanks 16:36:29 but i'll ping people to know more about it 16:36:42 cool (: 16:36:42 shall i kill the bot? 16:36:42 thanks youuu, thanks for joining us :) 16:36:43 i think so 16:36:47 #endmeeting