14:29:39 #startmeeting metrics team 14:29:39 Meeting started Thu Jun 29 14:29:39 2017 UTC. The chair is karsten. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:29:39 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:29:51 https://pad.riseup.net/p/3M7VyrTVgjlF <- agenda pad 14:30:03 hi there! 14:30:06 hi! 14:30:14 mornin’ 14:30:17 * karsten just found a bug in the latest metrics-web patch.. 14:30:21 hi t0mmy! 14:30:23 cool. 14:30:45 Ticket? 14:30:46 that is already in master. oh well. 14:30:54 testing :-) 14:30:56 nah, too trivial. 14:31:18 converting a List into a File[] just doesn't work. 14:31:33 oh, well. 14:31:44 anyway! 14:34:53 okay, shall we start? 14:34:58 I think we have a good list of topics. 14:35:06 yep. 14:35:56 * fine tuned release planning for (insert code base(s) here), if necessary? 14:36:12 so, I'm testing, testing, testing here. 14:36:22 and I have to admit, I'm also testing on the servers. 14:36:31 all? 14:36:36 no, step by step. 14:36:41 ah. 14:36:50 the reason is that I'm worried about postponing deployment by two or three weeks. 14:37:00 why that? 14:37:02 it's much easier to fix things now, with a fresh memory of code changes. 14:37:15 I also need to cross these things off my list before starting something new. 14:37:16 * iwakeh not implying that such a wait was necessary. 14:37:41 ok. so, I ran tests locally yesterday. 14:37:46 which looked okay. 14:37:55 and I deployed exonerator and onionoo on the servers. 14:38:03 plus metrics-web, where I just found this bug. 14:38:19 the reason for not finding it locally was that this part of the legacy module was disabled here.... 14:38:19 ok 14:38:27 which is just annoying. 14:38:38 so things are already deployed ;-) 14:38:55 not on collector. 14:39:00 and we have in-deployment testing. 14:39:20 did you not say that the 14:39:23 testing under real conditions! 14:39:31 backup instance of collector 14:39:39 is on ml2? 14:39:45 no. 14:39:49 I didn't touch collector. 14:39:56 ok. 14:39:57 it's on a collector release. 14:40:03 and the primary is on collector latest. 14:40:17 uh,'latest' 14:40:19 ? 14:40:28 -dev. 14:40:34 I can look. 14:40:57 would be important to have that on a definite release, in future. 14:41:44 no, we said we wouldn't put out a release yet, but we do need to run the onionperf stuff. 14:41:53 commit 67aea3dfac326a77163cb0cd1b3505195779bf0a 14:41:53 Author: iwakeh 14:41:53 Date: Thu Apr 27 09:49:31 2017 +0000 14:41:59 ok. 14:42:16 releases next week? 14:42:17 so, not latest. 14:42:51 this only affects onionoo and collector. 14:42:56 hmm, or maybe we are not running that commit but a later one. 14:43:12 that's why we should use releases. or 14:43:18 tags at least. 14:43:35 there should be the commit no in the jar. 14:43:37 we're using a tarball from june 17. 14:43:46 ah, I can look. 14:43:53 I can chakc later, too. 14:43:58 check 14:44:15 not so urgent. 14:44:46 ah, so we are running master there. 14:44:57 but the 1.9.0/2.0.0 change is not yet in master. 14:45:08 we're not building on the server anymore. 14:45:27 anyway. :) 14:45:29 good to know 14:45:48 I can suggest a new structure there. 14:45:58 for shared operation. 14:46:04 :-) 14:46:06 yes! 14:46:25 we should move forward with that after this june is over. 14:46:31 true. 14:46:35 so many metrics-lib releases... 14:46:43 oh yes. 14:46:59 I just wonder if this is something that is better done in person. 14:47:20 the operation structure? 14:47:27 sharing operation, yes. 14:47:42 though, no, 14:47:47 It's not too complicated. 14:47:48 let's start with that next week. 14:47:54 otherwise it'll take longer. 14:48:00 true. 14:48:07 okay, so, regarding the testing, 14:48:18 I think I can move this forward for everything except collector. 14:48:32 I haven't looked at the necessary collector changes yet. 14:48:44 You coded them? 14:48:45 but maybe we can do this update next week together? 14:48:51 all of them? 14:48:52 sure. 14:49:15 * iwakeh might mix that up with other code-bases 14:49:37 sync changes. 14:49:53 let's discuss that next week. 14:50:06 next topic? 14:50:09 we both coded a share there. 14:50:12 yes. 14:50:12 yep. 14:50:19 * blog post 14:50:23 good to go, right? 14:50:34 I checked all links. 14:50:39 Yes, no changes since yesterday I suppose? 14:50:47 not from me. 14:50:49 Sounds good. 14:51:10 t0mmy: what do you think about publishing now/in 15 minutes? 14:51:43 (just in case you're still around) 14:51:47 not from us either, as far as I know 14:51:54 * iwakeh now is aware of t0mmy=tc :-) 14:52:08 ha, sorry, I keep meaning to change my OFTC username 14:52:11 stephw 14:52:14 ping 14:52:18 blogpost good to go? 14:52:22 no stephw in this room. 14:52:27 oh, whoops 14:53:00 just pinged her but publishing in 15 sounds good to me 14:53:06 I don’t believe she’s made any new changes either 14:53:30 * karsten pinged her, too, and she says it can go online. 14:53:40 beans 14:53:44 hi stephw! 14:53:45 sounds good! 14:53:49 hi hi! 14:53:54 hi 14:54:06 okay, I'll hit submit after this meeting. thanks again for all your help! 14:54:17 great! 14:54:19 =) 14:54:27 awesome! thanks for working through this with us : ) 14:54:32 by the way, we'll need to babysit this blog post for a week or so. 14:54:39 regarding comments. 14:54:44 ah, ok. 14:54:54 will do 14:54:55 I'll look for comments at least once per day. 14:55:08 at least the old blog received a bit of spam. 14:55:20 that's true 14:55:36 is there a 'delete'-policy? 14:55:40 for comments? 14:55:46 speaking of announcements, did we announce 2.0.0 on tor-dev? 14:56:00 no, I'm waiting to point to the blog. 14:56:16 ok. regarding the policy, 14:56:27 do you mean deleting non-spam messages? 14:56:46 of course, any bland ads are easy to remove, but 14:56:55 trolling like questions... 14:57:07 fine question! 14:57:28 and, totally off-topic stuff. 14:57:44 there were not as many such comments on blog posts I wrote, but I'm not writing many posts and not on topics that everybody has an opinion on. 14:57:57 maybe defer to stephw in such cases? 14:57:59 heh 14:58:07 hehe 14:58:18 let's see what comes up. 14:58:22 and decide then. 14:58:27 not deleting immediately sounds like a good start. 14:58:41 after all, these comments can sit in the moderation queue for a day or two. 14:58:49 delete all except total praise. 14:58:54 yes, let's see what happens. 14:58:56 If I see a non-spam weird comment, I’ll just email tor-metrics 14:59:11 well, metrics-team@ is a public list. 14:59:56 anyway, there will only be good comments. 15:00:12 so, that will conclude Q2. 15:00:16 next topic? 15:00:21 right! 15:00:26 * Q3 planning 15:00:27 ah, k, just you two then 15:00:30 but carry on 15:00:42 yes, sounds good, t0mmy! 15:01:06 so, I didn't indent to make plans for Q3 today. 15:01:13 I just thought we should make a plan to make a plan. 15:01:37 next steps before bigger projects start. 15:01:39 for example, we could collect useful things to do in the next quarter and discuss them next week. 15:01:43 right! 15:01:46 that's the challenge. 15:02:03 nothing new? 15:02:13 we need to find things that we can pause and resume later. 15:02:15 no news. 15:02:34 I think there is a good small list now. 15:02:47 what we could do is a 2-week sprint to fix onionoo bugs. 15:02:54 which piled up over the last weeks. 15:03:02 just to give an example. 15:03:16 the three things on the pad all sound good. 15:03:16 the fourth item, fine 15:03:43 we could collect until next week and prioritize/filter at the next meeting. 15:04:02 I would start working on 1 and 3 15:04:06 already. 15:04:11 sure! 15:04:32 oh, report writing. 15:04:40 true, choosing the sprint items needs some time. 15:05:12 yes, I think so, too. 15:05:46 alright. how about we collect more thoughts on this pad until next week? 15:05:57 fine. 15:06:15 for a two-week timeframe? 15:06:38 the onionoo sprint? 15:06:41 that was just a suggestion. 15:07:05 no, collecting items for about the next two weeks. 15:07:16 before bigger tasks need to be started. 15:07:29 we don't know whether that will be in two or twelve weeks. 15:07:39 true. 15:07:47 then just collect. 15:07:48 it could be that we'll need a list for all of Q3. 15:07:57 also fine. 15:08:03 including an item "find different funding". 15:08:16 these things we need to list and think about anyway. 15:08:24 yep. 15:08:27 oh, yes. 15:08:30 should we evaluate our OKRs? 15:08:39 next week? 15:08:45 yes, for example. 15:09:02 is that due? 15:09:04 and write down our list as new OKRs if that was a useful exercise? 15:09:20 it's mostly for ourselves, I think. 15:09:26 and isabela will likely be curious. 15:09:28 oh, well ... 15:09:42 we could evaluate and then decide whether to do it again. 15:09:51 true. 15:10:54 okay. 15:11:02 a long list already, 15:11:05 done for today's meeting? 15:11:23 maybe move that to a different planning pad for the new year start? 15:11:24 heh, I'm not worried that we'll run out of ideas what to add. 15:11:51 new year as in new fiscal year? or new project year? 15:11:58 right! 15:12:11 sure. 15:12:17 the pad is pretty full 15:12:43 yep. 15:12:50 seems all is set now. 15:13:07 yes, I think we're done. 15:13:11 I'll publish the blog post now. 15:13:36 when it is published I'll announce. 15:13:48 I’ll schedule social media posts 15:14:48 done. 15:15:02 yay!! 15:15:09 https://blog.torproject.org/blog/tor-descriptors-la-carte-tor-metrics-library-2 15:15:15 yes, thanks. :) 15:15:26 okay, I'll end this meeting unless there's anything else... 15:15:28 yes, thanks to everyone 15:15:33 all fine. 15:16:07 great! :) 15:16:10 #endmeeting