14:59:57 <karsten> #startmeeting metrics team
14:59:57 <MeetBot> Meeting started Thu Jan  5 14:59:57 2017 UTC.  The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:59:57 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
15:00:01 <karsten> okay, let's start.
15:00:08 <karsten> thanks, linda, for putting the pads on the, err, pad.
15:00:20 <karsten> shall we go through the suggestions?
15:00:23 <linda> karsten ... lol is that not what I should have done?
15:00:26 <linda> sure.
15:00:42 <karsten> ah, sure, putting them there was fine.
15:00:54 <karsten> starting with the general feedback pad?
15:00:57 <linda> Sure.
15:01:18 <hiro> hello
15:01:23 <karsten> hi hiro!
15:01:23 <iwakeh> Mostly positive feedback or productive hints.
15:01:32 <iwakeh> on the public pad.
15:02:05 <iwakeh> The cvs link is useful.
15:02:33 <iwakeh> referring to (5)
15:03:16 <linda> I lost connection for a sec, but I'm back (and I have a log).
15:03:16 <karsten> yes, lots of good ideas.
15:03:39 <linda> I agree that the overall message of the feedback is that 1) we didn't make it worse and 2) there is nothing very obviously wrong to the user.
15:03:41 <karsten> so, I think we should decide which of them we fix before going live, which we're saving for later, and which we're dropping.
15:03:48 <karsten> linda: agreed.
15:03:56 <linda> karsten: that sounds like a good strategy.
15:04:33 <linda> I agree with iwakeh that the csv link would be really useful.
15:04:43 <karsten> okay, let's discuss that more then.
15:04:47 <linda> But that sounds like work? :P
15:04:59 <iwakeh> no, at first just to all data.
15:05:00 <linda> *work == more than just front-end work
15:05:10 <karsten> right, link to all data is easy.
15:05:13 <iwakeh> that's just a link.
15:05:18 <linda> OH
15:05:37 <linda> oh oh oops I was thinking of another suggestion (current graph to csv)
15:05:38 <karsten> I guess I just need to now what exactly to write and how to format it.
15:05:38 <linda> sorry
15:05:46 <karsten> right, that's work.
15:05:59 <karsten> [we could do two things: a) provide two links to full .csv file and to .csv file spec, b) provide link to .csv file of displayed data only. needs discussion -karsten]
15:06:03 <iwakeh> I'm not sure , if the partial data is really worth it?
15:06:11 <karsten> a) is easy, b) is work.
15:06:48 <linda> I think we should definitely do a, unless people see otherwise.
15:06:51 <karsten> maybe we do a) now and save b) for later?
15:06:56 <iwakeh> a) should be done and b) might not be that necessary.
15:06:59 <linda> I think b) would save some users time filtering their own data.
15:07:19 <linda> Which might be good for people who aren't technical, and want to use excel or something less intensive.
15:07:28 <karsten> yes, I see the value in that.
15:07:39 <linda> Wait, but you can also set filters in excel.
15:07:40 <iwakeh> But, if you're really into data stuff you'd like all and filter by yourself ;-)
15:07:41 <karsten> (and the required effort on our side.)
15:08:04 <linda> As someone who is fine with writing scripts and uses R easily I fail to see it.
15:08:07 <iwakeh> All the edge cases ....
15:08:21 <iwakeh> if we programmed b).
15:08:23 <linda> But people want it? and I think it could help people not like us (newspeople? er..?)
15:08:36 <linda> iwakeh: oh boy, you're right.
15:08:56 <karsten> I don't mind putting it on the list to consider later.
15:09:02 <linda> karsten: that sounds like a good plan
15:09:06 <iwakeh> filtering data is real easy and if people can't do that they could not really make use of the given data.
15:09:18 <iwakeh> yeah, the backlog is fine :-)
15:09:58 <karsten> what about 3?
15:10:07 <karsten> RaBe: any clue what to do?
15:10:29 <RaBe> i'm not sure what "3" you are referring to, sorry
15:10:32 <iwakeh> accessibility.
15:10:36 <karsten> on https://pad.riseup.net/p/esVoPphdMGnU
15:10:44 <iwakeh> for screenreaders or the like.
15:11:00 <iwakeh> and icons don't translate to text easily.
15:11:16 <karsten> so, I installed ChromeVox, and the page reads okay to me.
15:11:35 <linda> I didn't manage to replicate the issue either? 乁(՞︿՞)ㄏ
15:11:39 <karsten> but I only tried a page or two.
15:11:50 <linda> I was also not toooo thorough.
15:12:07 <RaBe> perhaps we should rename just the aria part, so the "performance" icon does not say "dashboard" any more...
15:12:09 <iwakeh> what did the icons "say"?
15:12:28 <linda> I think the names of the icons clash with the titles?
15:12:37 <linda> or something?
15:12:40 <linda> 乁(՞︿՞)ㄏ 乁(՞︿՞)ㄏ 乁(՞︿՞)ㄏ
15:12:57 <RaBe> I was not aware that any reader would read a class name?
15:13:06 <iwakeh> linda: How do you type the ascii art?
15:13:26 <karsten> I don't hear icon names, either.
15:13:29 <hiro> linda: I have been wondering that too
15:13:31 <hiro> :)
15:13:34 <linda> iwakeh: I went to a website and copied all the ones I wanted to use frequently onto a pad.
15:13:47 <linda> And then I copy and past it in. It's not that exciting, but I like the pizzaz it adds.
15:13:54 <linda> If you want to collect your own set: http://japaneseemoticons.me/
15:14:06 <linda> I have about ~20 smileys and that's enough for me, but they have 1000_
15:14:06 <iwakeh> thanks :-)
15:14:15 <karsten> okay, does that mean there's no issue with 3?
15:14:17 <linda> (≧◡≦)
15:14:21 <linda> karsten: I think so?
15:14:38 <iwakeh> well, we culd ask again after rollout?
15:14:42 <linda> maybe we should rename the confusing stuff? (ಠ_ಠ)
15:14:43 <iwakeh> could
15:14:51 <linda> But I can't even see why it's confusing, to be honest. still a bit confused.
15:15:01 <karsten> are we naming them at all?
15:15:17 <RaBe> i think if they're aria hidden, they should not be read at all
15:15:21 <linda> *can't see == literally cannot replicate and see, not that I can't understand why it would be confusing if what they said happened
15:15:22 <iwakeh> well, there are the links themselves and the icons and the text.
15:15:40 <karsten> <a href="userstats-relay-country.html"><i class="fa fa-users fa-fw fa-4x" aria-hidden="true"></i> <h2>Users</h2>
15:15:58 <karsten> there's no icon name in there. it's just "fa-users" which identifies the icon.
15:15:58 <iwakeh> maybe, screenreader in blocked objects mode?
15:16:01 <RaBe> this should just read as "Users"
15:16:06 <linda> (◕o◕)
15:16:08 <karsten> RaBe: it does here.
15:16:15 <linda> (•₃•)...
15:16:33 <karsten> alright, before linda shows us the other 17 smileys, let's move on.
15:16:34 <karsten> ;)
15:16:36 <RaBe> perhaps there was one icon where we missed the aria-hidden="true"?
15:16:44 <karsten> RaBe: plausible.
15:17:35 <karsten> so, 4 and 9 are left.
15:18:03 * karsten didn't mean to offend linda.. you still here?
15:18:08 <linda> 4): I agree and disagree.
15:18:17 <linda> oh I am not offended!
15:18:18 <linda> hehehehe
15:18:23 <karsten> hehe phew!
15:18:39 <linda> 4) I think that it is good to have all the names out in the open before the user clicks a dropdown.
15:18:48 <karsten> right.
15:18:50 <linda> 4) I don't know if the tabs are the best way
15:18:56 <RaBe> 4) i suggested a dropdown box there some time ago ... on mobile phones, theres a full screen just filled with tabs...
15:19:06 <RaBe> however, i like the tabs on the desktop
15:19:07 <iwakeh> the tabs are unusual, but work, I think.
15:19:10 <linda> RaBe: ah, I see.
15:19:17 <linda> iwakeh: that's how I felt, too.
15:19:20 <karsten> I hope that we'll get rid of some tabs in the future when we merge graphs.
15:19:38 <linda> I think isa suggested radio style buttons?
15:19:48 <linda> karsten: that could do it.
15:19:55 <iwakeh> and, with the dropdown we'd loose immediate bookmarkability (if that exists)
15:20:02 <linda> this isn't the final forever version.
15:20:10 <linda> iwakeh: that's a great point. I don't wanna lose that.
15:20:12 <iwakeh> true.
15:20:19 <karsten> okay, how about we defer then?
15:20:24 <iwakeh> yes.
15:20:25 <linda> karsten: +1
15:20:32 <linda> ٩(^‿^)۶
15:20:46 * linda is a little smiley-enthusiastic right now
15:20:57 <karsten> hehe
15:21:00 <karsten> 9.
15:21:03 <karsten> search.
15:21:26 <karsten> preference is drop or defer.
15:21:29 * linda cringes at the notion of adding user inputs
15:21:36 <iwakeh> defer.
15:21:50 * linda recalls all the horror stories in her cs securty exploits class
15:21:55 <iwakeh> the drop-down, I mean.
15:21:56 <karsten> yeah.
15:22:02 <linda> I do think it's a good idea to be able to search.
15:22:04 <RaBe> we could add a search box that just opens duckduckgo or something ...
15:22:10 <linda> Oh I was thinking of a search bar!
15:22:15 <iwakeh> rather not.
15:22:21 <linda> iwakeh: yeah, I know
15:22:25 <iwakeh> We do not have text contents.
15:22:33 <karsten> well, some.
15:22:38 <karsten> the graph descriptions.
15:22:45 <linda> RaBe: hmm, if we have to have a search bar I would rather go that route
15:22:46 <iwakeh> yes, but in one page settings, like
15:22:56 <iwakeh> glossary
15:23:28 <iwakeh> a bad search is worse than none.
15:23:30 <linda> I wouldn't mind typing "relays" into a bar and being presented with the definition, tools to manage, and graphs all in one page.
15:23:36 <karsten> +1 iwakeh
15:23:46 <linda> the idea sounds good.. but I'm tramutized.
15:23:53 <RaBe> we can't add a [any search engine] box with the launch of the page, because nothing has been indexed or would be found
15:23:56 <linda> iwakeh: +1
15:24:08 <iwakeh> RaBe: true.
15:24:08 <linda> RaBe: also good point
15:24:14 <karsten> okay. drop?
15:24:17 <iwakeh> yes.
15:24:23 <linda> :P defer?
15:24:28 <linda> to much much much much later if ever?
15:24:34 <linda> ... okay drop maybe is the correct word then
15:24:38 <karsten> hehehe
15:24:41 <karsten> sounds like the same.
15:24:51 <iwakeh> less radical :-)
15:25:02 <linda> okay. drop then!
15:25:07 <karsten> done!
15:25:08 <linda> \(•̀ᗝ•́)/
15:25:14 * linda stands up for beliefs?
15:25:15 <karsten> https://pad.riseup.net/p/Fv8A9XrSnaez
15:25:15 <linda> lol
15:25:23 <iwakeh> ٩(•̤̀ᵕ•̤́๑)ᵒᵏᵎᵎᵎᵎ
15:25:30 <iwakeh> ٩(•̤̀ᵕ•̤́๑)ᵒᵏ
15:25:32 <linda> iwakeh: hehehehhehe yes
15:26:13 <karsten> RaBe: what do you think about 11?
15:26:31 <iwakeh> 11?
15:26:36 <karsten> https://pad.riseup.net/p/Fv8A9XrSnaez
15:26:41 <karsten> I just went ahead.
15:26:41 <iwakeh> yes?
15:26:48 <karsten> line 27.
15:26:51 <RaBe> i wouldn't put both menus on top of each other, that would look like if one was the submenu...
15:27:05 <karsten> agreed.
15:27:06 <linda> RaBe: +1
15:27:12 <linda> I do think that we can make the banner skinnier.
15:27:27 <karsten> yes, I was also thinking what we can do with whitespace.
15:27:28 <linda> But I like how it looks now...
15:27:37 <linda> karsten: good point
15:27:46 <karsten> try to resize your browser vertically.
15:27:54 <karsten> the header changes at some point.
15:28:06 <RaBe> we could use the smaller header version on a bigger size of the screen (change the break point), but i felt it was ok as it is...
15:28:08 <iwakeh> I actually didn't see the top menu at first use.
15:28:20 <linda> yeah, I thought this was fine.
15:28:30 <linda> Maybe we should set the breakpoint earlier, would be the feedback?
15:28:43 <linda> (~˘▾˘)~
15:28:54 <iwakeh> Couldn't the onion logo part be less high, as linda suggested?
15:29:13 <iwakeh> The way it changes with changing width is great.
15:29:18 <karsten> and could the logo start a bit higher than it does now?
15:29:31 <linda> I like visually how it looks, to be honest.
15:29:39 <linda> Although both those things are probably true
15:29:45 <karsten> this feels a bit like bikeshedding, too. ;)
15:29:47 <RaBe> the onion logo changes with the HEIGHT of the viewport...
15:30:14 <RaBe> we could change the break point for the smaller version, or drop the big header version...
15:30:18 <iwakeh> only the text part, not the onion.
15:30:26 <linda> karsten: lol or yak-shaving
15:30:45 <linda> RaBe: no I love the big version!
15:30:46 <karsten> yes, speaking of, where is my yak......
15:31:01 <karsten> sounds like DROP?
15:31:03 * linda looked up the difference between bikeshedding and yak shaving and there is one.
15:31:08 <linda> (https://phinze.github.io/2014/05/24/useful-tech-terms-part-1.html)
15:31:27 <RaBe> drop the big header, or drop the topic? :)
15:31:39 <karsten> the topic. but I don't feel strongly.
15:31:44 <linda> header: no plz, topic: sure.
15:32:04 <linda> I feel like it's nto that important and it's good to be aware of it, but eh.
15:32:08 <iwakeh> fine, next topic.
15:32:15 <karsten> cool! we're out of suggestions.
15:32:27 <linda> ᕦ(^o^)ᕤ
15:32:40 <karsten> I'm counting 3 x should-fix.
15:32:51 <linda> So: 1) yay! and 2) those fixes aren't too laborious, I think.
15:32:56 <karsten> and 2 x defer.
15:33:03 * linda nods
15:33:14 <iwakeh> fine, sounds like done.
15:33:16 <pard> Hello
15:33:25 <karsten> the should-fixes are really easy.
15:33:33 <linda> pard: ヽ(•◡•)ﾉ
15:33:38 <pard> :)
15:33:39 <karsten> pard: in the middle of a meeting. try #tor-project maybe?
15:33:39 <iwakeh> ٩( ᐛ )و
15:33:53 <linda> iwakeh: it looks like you are dancing!
15:34:06 <RaBe> ( i have to start building my own ascii smiley library... )
15:34:06 * linda doesn't have a dancing one... hmm..
15:34:09 <pard> karsten, apologies, sure
15:34:21 <karsten> okay, what are the next steps then?
15:34:23 <iwakeh> oh, second page.
15:34:45 <linda> RaBe: it adds a lot of value and spunk, and I use IRC for EVERYTHING, so I'm a fan.
15:34:46 <karsten> assuming we have fixes by tomorrow or monday.
15:35:05 <iwakeh> when to turn it productive?
15:35:11 <karsten> yep.
15:35:22 <iwakeh> next tuesday?
15:35:32 <linda> what does "turn it productive" mean?
15:35:39 <linda> go live? :o
15:35:52 <iwakeh> put on metrics.torproject.org
15:36:06 <iwakeh> right.
15:36:07 <karsten> yes.
15:36:21 <iwakeh> is that a germanism?
15:36:22 <karsten> sounds good to me.
15:36:44 <iwakeh> should there be an announcement?
15:36:51 <linda> iwakeh: I think so!
15:36:52 <karsten> ah! blog post.
15:36:54 <iwakeh> synching it to the blog post?
15:37:00 <karsten> yes, we should sync those two.
15:37:03 <linda> :)
15:37:21 <karsten> linda: you're going to write that one?
15:37:21 <linda> I can finalize the blog post and send it to you guys in an email.
15:37:28 <linda> yep~
15:37:28 <iwakeh> (ง ͡ʘ ͜ʖ ͡ʘ)ง
15:37:42 <karsten> cool!
15:37:55 <Sebastian> you young kids and your newfangled smileys
15:37:57 <linda> When is it going to be announced?
15:38:07 * linda thinkis Sebastian is jealous (•̤̀ᵕ•̤́)
15:38:19 <iwakeh> when the post is done.
15:38:21 <karsten> hi Sebastian! :)
15:38:32 <karsten> some time next week?
15:38:35 <linda> iwakeh: oh, okay! I should get a move on then. I'll try to have it by Friday.
15:38:42 <linda> Or sure, we cna make it live next week
15:38:43 <iwakeh> ٩( ᐛ )و
15:38:49 <linda> But I'll still try to do it by friday!
15:38:54 <karsten> great!
15:39:03 <iwakeh> yes, indeed!
15:39:13 <linda> whoo
15:39:15 <karsten> okay, does that mean we're done with the UX/website topic for today?
15:39:19 <linda> ♫♩♪♫♩♪♫♩♪♫♩♪
15:39:26 <linda> ٩(^‿^)۶
15:39:27 <iwakeh> nice.
15:39:31 <karsten> whee!
15:39:33 <RaBe> great :D
15:39:35 <linda> lol only 40 minutes out of 30~
15:39:37 <karsten> hang on, RaBe
15:39:40 <linda> we're getting slightly better.
15:39:42 <linda> lol
15:39:43 <karsten> there's another website topic left.
15:39:47 <karsten> we are!
15:39:50 <iwakeh> which?
15:39:52 <karsten> - Atlas/Onionoo improvements (karsten)
15:39:56 <karsten> that other website.
15:40:10 <karsten> we should start making plans for atlas.
15:40:22 <karsten> let me find the deliverable text...
15:40:42 <karsten> 2017-05: Improve all usability issues of Atlas that are classified as High priority or above in the issue tracker as long as they are within scope and reported at least six months before the end of the award. (Sponsor X 3.3. Atlas)
15:40:52 <iwakeh> ah, yes.
15:41:02 <iwakeh> are there many?
15:41:20 <karsten> depends.
15:41:27 <karsten> I made a list of tickets that might be relevant,
15:41:33 <karsten> but we'd have to triage them.
15:41:37 <iwakeh> ok.
15:42:11 <iwakeh> is irl still working on these?
15:42:13 <karsten> there, 40 tickets.
15:42:16 <karsten> irl: ping
15:42:36 <karsten> some are onionoo tickets which would affect atlas.
15:42:46 <karsten> we'll certainly shrink that list to half or less.
15:42:54 <karsten> and some are easy.
15:43:10 <iwakeh> yes, special reluctance for cross-product tickets.
15:43:28 <karsten> well, for example, #16552.
15:43:42 <karsten> that's a usability issue in atlas but one that we can only fix in onionoo.
15:43:57 <karsten> but, let's go through the list (not now, but maybe over the week).
15:44:32 <karsten> we could assign some sort of priority for this deliverable.
15:44:40 <karsten> and then work them off by priority.
15:44:47 <karsten> until we run out of time.
15:44:54 <iwakeh> well, we said all of high prio.
15:45:05 <karsten> yes, that was smart. :)
15:45:05 <hiro> if is there anything I could help yo uguys with please let me know
15:46:03 <karsten> okay, how about we discuss this more next week?
15:46:08 <iwakeh> right.
15:46:17 <karsten> hiro: I'll have a question for you in a minute. :)
15:46:17 <hiro> ok
15:47:00 <karsten> anything else on the atlas topics?
15:47:04 <karsten> topic*
15:47:31 <iwakeh> no
15:47:35 <karsten> iwakeh: another advantage of fixing onionoo bugs that affect atlas is that we wouldn't lose that effort when switching to another atlas.
15:47:43 <iwakeh> true.
15:47:45 <karsten> whereas all atlas fixes would be lost.
15:47:51 <karsten> okay,
15:47:55 <karsten> - OnionPerf status (karsten)
15:48:02 <karsten> how did that work?
15:48:24 <karsten> that == setting up an instance
15:48:31 <karsten> iwakeh, hiro: ^
15:48:34 <iwakeh> I got some
15:48:58 <iwakeh> to work, but really not in a smooth way.
15:49:12 <iwakeh> and, didn't run it for long.
15:49:30 <karsten> okay. did you run into bugs, or out of time?
15:49:41 <iwakeh> out of time.
15:49:44 <karsten> okay.
15:49:47 <hiro> I had some issues with the instructions
15:49:58 <hiro> and will send some updates to the README this week
15:50:13 <karsten> neat!
15:50:19 <hiro> one thing that I noticed is that it is difficult to understand results. I assumed it is because I might not be familiar with the tool
15:50:42 <iwakeh> I'd still like to look at the background more.  Reliability of the measurements ...
15:51:06 <hiro> but it would help to have some more links at least to verify what is that you are obtaining
15:51:17 <iwakeh> The results and what is measured is not really explained.
15:51:26 <karsten> do the torperf explanations help, maybe?
15:51:52 <karsten> like https://collector.torproject.org/#type-torperf
15:52:11 <iwakeh> It is easy to understand what the intent is,
15:52:37 <iwakeh> but to judge or at least believe that
15:52:45 <iwakeh> the code does what it claims ...
15:52:52 <karsten> ah, you want to review the code then?
15:53:11 <iwakeh> Well, that's the most accurate documentation at the time.
15:53:18 <iwakeh> :(
15:53:27 <karsten> hehe, why at the time? isn't that always the case? ;)
15:53:43 <iwakeh> well, you're right there ;-)
15:54:02 <iwakeh> hiro: do you think that, too?
15:54:02 <karsten> alright, how do we proceed? you're looking at the code? what should hiro do, if anything?
15:54:36 <iwakeh> I think hiro points at the same issue?
15:55:00 <hiro> The way I see this is that you get a pdf w a list of graphs and measurements and it is a bit difficult to understand if those measurements make sense or if something in your setup isn't really working
15:55:18 <iwakeh> yes.
15:55:31 <karsten> so, we'll want to run this tool ourselves.
15:55:40 <iwakeh> that's lack of documentation.
15:55:45 <iwakeh> create documentation?
15:55:50 <hiro> So maybe people that are interested in the tool do not need this explanation, because it is assumed they know already
15:55:53 <karsten> that means as soon as we have reviewed the code, we'll be confident that it measures the right thing.
15:56:03 <karsten> we could create documentation, sure.
15:56:09 <iwakeh> later.
15:56:11 <karsten> for ourselves and then contribute back.
15:56:16 <iwakeh> sure.
15:56:39 <karsten> oh, and we have hiro's plan to submit README updates.
15:56:48 <iwakeh> maybe, have a list of most important topics?
15:57:11 <karsten> hmm?
15:57:18 <iwakeh> The README is already in preparation, that's great.
15:57:42 <iwakeh> q1: What is measured and is it what we need?
15:57:58 <iwakeh> q2: Is it reliably measured?
15:58:23 <iwakeh> q3: What tests would be needed for regression testing in new versions?
15:58:26 <hiro> under q1 would also help to have something like: what to expect when running the service
15:58:33 <iwakeh> sure.
15:59:01 <karsten> iwakeh: want to paste your and hiro's action items on the agenda pad?
15:59:30 <iwakeh> ok, but did we arrive at a prioritization?
16:00:12 <karsten> well, our priorities are in the deliverables.
16:00:39 <karsten> 2017-02: Replace all existing Torperf instances gathering current Tor network performance measurements with OnionPerf instances. (Sponsor X 5.1. OnionPerf)
16:00:46 <karsten> 2017-04: Develop and deploy at least one more user model in addition to the current model. (Sponsor X 5.2. OnionPerf)
16:01:15 <iwakeh> Then postpone q3.
16:01:29 <karsten> plausible.
16:01:41 <karsten> q2 seems important for the first deliverable.
16:01:43 <iwakeh> the other two are related to 5.1/2
16:01:44 <karsten> q1 for the second.
16:02:16 <karsten> but regarding prioritization,
16:02:29 <iwakeh> q2 builds on q1 :-)
16:02:30 <karsten> there's one more topic left on the agenda, and it's quite important.
16:02:46 <iwakeh> tech-rep?
16:02:51 <karsten> well, q1 is two questions. ;)
16:02:53 <karsten> yes.
16:03:22 <iwakeh> hiro: would you try to do some work on q1?
16:03:35 <hiro> ok good for me
16:03:57 <hiro> when you mean "is it what we need?" who is we?
16:04:11 <iwakeh> metrics.
16:04:15 <hiro> ok
16:04:24 <iwakeh> torperf replacement.
16:04:31 <karsten> hiro: the current torperf measurements are not as useful as they could be.
16:04:44 <karsten> they fetch static files, which is quite different from web browsing.
16:04:53 <hiro> ok
16:04:56 <karsten> there are trac tickets related to that, maybe search our trac for them.
16:05:03 <hiro> perfect
16:05:11 <karsten> cool!
16:05:34 <karsten> hiro, iwakeh: please add an action item or two to the pad.
16:05:43 <iwakeh> there are some
16:05:54 <iwakeh> or am I offline?
16:06:05 <karsten> for onionperf?
16:06:23 <karsten> not seeing any.
16:06:51 <iwakeh> 12ff
16:06:58 <iwakeh> line 12 and below
16:07:03 <karsten> yep, none here.
16:07:09 <iwakeh> oh!
16:07:42 <iwakeh> had to enable js.
16:07:57 <karsten> perfect!
16:08:08 <karsten> so, tech reports and metrics-lib release remain.
16:08:39 <karsten> I can move forward with the metrics-lib release.
16:08:41 <iwakeh> I would place highest prio on finishing the reps.
16:08:49 <karsten> reps?
16:09:10 <iwakeh> tech-reports.
16:09:11 <karsten> reports.
16:09:15 <karsten> yes.
16:09:20 <karsten> those are really important.
16:09:31 <karsten> so, works for me.
16:09:40 <karsten> I can review things and give feedback.
16:09:46 <iwakeh> good.
16:10:15 <karsten> ah, another important topic for this month: tor browser downloads/updates on metrics.
16:10:23 <karsten> so much to do.
16:10:26 <iwakeh> yes.
16:10:35 <karsten> but I think we're out of time for this meeting.
16:10:46 <iwakeh> there is plenty of work.
16:11:03 <karsten> how about we continue setting priorities next week?
16:11:13 <iwakeh> sure, good idea.
16:11:26 <karsten> yay.
16:11:36 <iwakeh> ٩( ᐛ )و
16:11:41 <karsten> productive meeting, as so often. thanks, everyone!
16:11:45 <karsten> #endmeeting