17:06:12 #startmeeting ux team biweekly sync 17:06:12 Meeting started Wed Oct 12 17:06:12 2016 UTC. The chair is isabela. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:06:12 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:06:27 alright! 17:07:22 1. recap of dev meeting 2. next steps 3. update from other fronts (me and linda are working on a project - more on that latter) 17:07:32 anything else ppl want to add? 17:07:43 2. is about guidelines btw 17:07:46 :) 17:07:59 * linda has nothing to add 17:08:24 Me neither. CUrious to hear about dev meeting. Happy to represent Scout (best I can) and follow up on her email. 17:09:01 ok we can start with that 17:09:32 scout actually sent her notes to the list which covers all feedback/changes we should review 17:10:02 we printed out the guidelines and hosted 2 sessions to chat about it but the turn around was not that big 17:10:18 which does not mean we didn't had good discussions :) as you can see on her notes 17:11:17 since simply secure grant to get us to this phase is pretty much over / me and scout thought a next step would be to report back on the work done and how we could use more $ to do more work 17:11:59 we thought of doing a blog post - before next week when we meet with otf - but she is super busy so this might stay for now as a report on otf email list only 17:12:06 but we should do the blog post eventually 17:12:29 as next steps (which is point two already, please interrompt me if you have questions) 17:12:50 would it be possible to fwd that otf email to ux team afterwards? 17:13:10 yes 17:14:00 thanks! +10k on blog post. it's important to let the community know how we got here and what's next. 17:14:27 we thought of: 1. update the guidelines with the feedback collected 2. work with tor browser team to bring tor browser desktop to comply with the guidelines 3. do that with our site / not redesign it just update css to compy with guidelines (we still dont have resource to do more work than that) 3. since metrics team will be working on their side we could do the same with that as well (fix font, colors etc) 17:14:44 but for all that we would need more $ and that is kind of step 0 17:14:48 Very vool. 17:15:18 I know it's frustrating not to do all the things now, but it really is a solid piece of work. So Fist bump emoji, and yes to writing it up. 17:15:46 should 2 or 3 happen first? 17:15:56 and do we know if the tbb team is on board? 17:15:59 i think could work in paralel 17:16:20 sorry tbb is tor browser bundle? or? 17:16:21 linda: yes in informal chat not in formal 'ask' but it should be ok 17:16:27 ame_e: is tor browser yes 17:16:40 isabela: (★‿★) 17:16:49 linda: we should formally present this intent tho 17:17:07 but i think do the blog post and look for more resoure etc is priority right now 17:17:15 agreed. 17:17:49 +1 17:17:58 we would have a ticket for the task and work with devs to find where in the code we have things to fix 17:18:08 once we know what we need to fix work with design on those fixes 17:18:39 then they would push it on a new version and we should have a note on the release blog post of the version it comes out linking back to our blog post on guidelines and explaining is adopting it etc 17:18:52 something like that can be a way to do it 17:19:22 ヽ(•◡•)ﾉ 17:19:31 i think eventually the ux team should be able to offer the patches. 17:19:32 website is the same thing - map css that needs to change etc 17:19:41 totally 17:20:23 so if we go through a path where tb team mentors us for a while to get familiar with the codebase and then we can fix things independently, would be awesome 17:20:49 mrphs: +1 17:20:50 (just as something to have in mind) 17:21:01 totally, i agree 17:21:10 I think that css/styling is independent enough/simple enough that it should be doable. 17:21:28 i can do the website stuff for sure 17:21:38 linda: you hacked tbb on your research right? 17:22:29 isabela: yep~ 17:22:39 i hacked the css file too. 17:22:59 *hacked on 17:23:03 quite different. haha. 17:23:13 (~˘▾˘)~ 17:23:15 hehehehe 17:23:44 alright! scout said she would sent that email this week / either way whenever it goes out i can fwd to the ux list 17:24:06 any questions or comments or ideas or ... for points 1 and/or 2 ? 17:24:18 Clarifying question .... 17:24:39 Scout's email - I want to be sure I capture that to do. How is that different than what she sent? 17:24:49 #item update wiki with feedback ( PhilipL sent some to the list from before the seattle meeting and scout too) 17:25:36 ame_e: she sent notes from seattle to the ux list 17:25:52 what i am saying is that she will send a report about the guidelines project to the otf list 17:26:01 Thank you. I got it. 17:26:12 np! 17:26:46 btw - i recommend reading the notes from seattle 17:27:04 Lots of good details in that email. 17:27:12 yes 17:27:25 and cool ideas like 17:27:28 + A CSS bootstrap with all these things would be very helpful! 17:27:51 ok 17:28:08 if ppl dont have anything on these points we could move to point 3 17:28:41 ok 17:28:45 point 3! 17:30:01 tor got a small grant to work on orfox / the strategy here is that eventually orfox is just tor browser for android :) and that development becomes part of tbb team routine (orfox devs start to participate on tbb meetings on monday and so on) 17:31:30 Currently, the mobile tor browser (Orfox) does not have all the features that the desktop tor browser has. We are in the process of migrating features from the desktop to the mobile. The first thing we are doing is to give our mobile users the option to adjust their security settings. 17:31:35 this small grant is about adding tor button (entry point, not all the features) and the security slider (other features will come in other proposals and we are aiming to have orfox in parity on all tat with tor browser for desktop) 17:31:53 :) oops 17:32:03 go ahead, isa~ 17:32:26 nah is cool, i was just going to say that during tor meeting in seattle we started wireframes of how that will look like 17:32:38 linda: do you want to explain what we are doing and what help we could use? 17:33:51 isabela: sure! 17:34:03 We want your help in wording the interface text that accompanies the security slider, so that we accurately communicate the changes in browser functionality and security benefits to the user. 17:34:20 https://docs.google.com/document/d/1U_tbrC1lpuKHZg_QKD_TUVd6ImjTJ3jWZkSxjXgceZI/edit?usp=sharing 17:34:28 Anyone with the link can comment on the document, so feel free to share the link around to anyone you think that can help! 17:34:43 I will also send out an email to the list, so you will have this information again. 17:35:24 I think there is a lot of information on the google doc, so that's all I have to say. 17:35:44 (information includes what we want to accomplish and a clickable prototpye so you can see what we are talking about). 17:36:25 We want to have the text finalized soon (at the end of the month at the latest). We have a developer who will work on coding the interface in parallel. 17:36:40 (also this is the ticket explaining background and what was done with the UI and why (so far) https://trac.torproject.org/projects/tor/ticket/20291) 17:36:54 \(◕‿◕)/ 17:37:01 Thanks, Isa. 17:37:14 That's all I have to add on that front. 17:37:41 this is very exciting 17:37:43 * isabela thinks 17:38:02 since is us starting to work with devs on new uis etc 17:38:22 (≧◡≦) 17:40:25 * isabela gives some min for folks to look around and digest stuff :) 17:41:26 ah and btw some of the things we are modifying like having one medium / that will be done for the desktop version as well to be consistent) 17:43:02 This information is also on the doc~ 17:43:28 But ..what isn't is the question of if we should have different settings than the ones on the doc. 17:43:47 I'll add this to the list of things you can comment on ("Additional Feedback" section in the google doc). 17:44:14 When I look through these docs, I keep looping back to Scout's email to the UX list. I keep coming back to new recommendations for Subbrands & Icons. That's the thing that feels the most different. 17:44:17 ok, done. 17:44:46 So let me just say: that's important and let's make sure that comes through in our first pieces of work 17:44:48 ame_e: those are wireframes not the real design / just placements of things 17:45:03 ame_e: I agree. The best way to merge the two is for them to look alike. 17:45:06 this is a very small grant 17k 17:45:30 ame_e: some stateful information is that there is a grant specifically to add this security feature, and not necesarily the design. 17:45:34 so i am not sure how much more we can do beyond the original scope but we will try to always move towards that direction 17:45:42 I'm not in the wireframes - point me there please? 17:45:52 ame_e: which is I think why we are personally focused on this even though having the same options isn't as helpful as having the same look. 17:46:02 https://trac.torproject.org/projects/tor/attachment/ticket/20291/orfox-security-slider-wireframes.pdf 17:46:08 Ok I found it 17:46:13 ame_e: https://marvelapp.com/111c9jh/screen/15851576 (clickable version) 17:46:16 oh, good. 17:46:22 Thanks. Tooooooo many tabs 17:46:38 That was half a sec slow to load and I moved on. 17:46:43 But looking now 17:47:19 cool 17:47:26 the link from linda might be easier 17:47:34 since no download is needed 17:50:06 we will get back to this stuff too - like linda said, we will be working on it and our goal is to have it done by eom 17:50:24 she is sending an email with more detailed info if you want to help with it 17:50:39 we just wanted to give a heads up since we had this meeting 17:51:08 we are 10 min till the hour - if folks has comments now about it or other points we still have some time 17:51:30 if you want time to digest and pick it up later is fine too :) we can end the bot and continue via email list 17:51:52 In terms of declaring victory on Style Guide v1 or 0.5 or however it's numbered... Is there a final to do list? 17:52:13 Final isn't the right word. I expect it to be better in 2 months than now. Better in 6. Better in 1 year, you get the idea. 17:52:42 I know we have report out/blog, but don't know what agreements are on immediate next steps 17:52:43 ame_e: we need to incorporate that feedback / but we would need more $ to do so 17:53:33 ame_e: you - specifically how to apply that feedback? 17:53:36 Got it 17:54:01 I had just hoped Elio would be on here for this. Wasn't sure if the loop was already closed or not. 17:54:05 i think we will try to get $ to have design resource around to do that 17:54:09 But understood on need more money for more. 17:54:20 yes 17:54:26 #grantlifehell 17:54:48 #OneStepAtATime 17:54:50 :0 17:54:53 I mean :) 17:54:54 hehehe 17:55:05 indeed 17:55:19 buenas people! 17:55:32 anything else or we are all good? :) 17:55:40 * linda is good 17:55:48 good here 17:56:19 poor PhilipL is probably not good cuz of the cold 17:56:41 ok i will end the bot then 17:56:42 Indeed. Soup and tissues for PhilipL 17:56:51 lets keep it up on the email list 17:56:56 #endmeeting