18:33:01 #startmeeting gettor 02/28 18:33:01 Meeting started Thu Feb 28 18:33:01 2019 UTC. The chair is pili. Information about MeetBot at http://wiki.debian.org/MeetBot. 18:33:01 Useful Commands: #action #agreed #help #info #idea #link #topic. 18:33:11 ok, go! :) 18:33:57 ok so I have been refactoring the code here: https://gitweb.torproject.org/user/hiro/gettor.git/tree/?h=refactoring 18:34:04 and I need to test it on the gettor vm 18:34:24 locally it works... :) "it works on my machine" 18:34:39 and I have also installed a vm with prometheus yesterday 18:34:46 to have a test of the monitoring that we should do 18:35:31 I think now the repository has more of a structure and I am also adding tests 18:35:36 those are almost finished 18:35:40 but not quite 18:35:55 I think I can be ready to review everything next week 18:35:55 \ 18:35:56 sounds great so far :) 18:36:05 with prometheus and all 18:36:14 who do we want to ask for review? 18:36:16 any ideas? 18:36:49 I think I could ask maybe ahf? but haven't asked yet so not sure he is up for that 18:36:58 ;) 18:37:40 cohosh maybe? 18:37:56 yeah too 18:38:04 i think getting at least one of us to look at it sounds like a good idea 18:38:23 hey ahf ! 18:38:31 hey hey 18:38:31 that would be great 18:39:10 (i'm sitting and eating so a bit show response time) 18:39:15 slow* 18:39:36 so when the tests are finished and we get a review we can start thinking about replacing existing gettor service? 18:39:48 or do we want to have both up and running for a time? 18:39:54 (ahf: I have a toddler on me :D) 18:40:20 I think we shouldn't have two gettor up and running 18:40:43 if we like how refactored gettor works then what would be the advantage of keeping the old one there? 18:40:52 pili: :-D 18:41:09 just in case of any issues with the new one :) 18:41:32 but I'm happy to just run with the new one once we're happy 18:41:46 If we test it and we are happy then we should be able to fix issues 18:43:19 so, just to be clear, the re-factored gettor has the same functionality as the existing one? or is there more/less functionality? 18:43:47 because we've been talking for a while about writing a product requirements document to define the functionality but we've not managed to get around to it 18:43:56 same functionality - twitter 18:44:05 we can re-add twitter easily 18:44:15 and it would be good to explicitly outline what it does now 18:44:16 so we can think of potential enhancements in the PRD 18:44:23 we need first to ask twtiter for api access with the gettor twitter account 18:44:41 who owns that gettor twitter account? 18:44:42 and then we just adjust the old code to work with the new one 18:44:46 I have no idea! 18:44:47 i assume we have access to it? 18:44:53 I was aout to ask ilv 18:44:59 s/aout/about 18:45:26 hehe ok 18:45:27 yes it’s ilv 18:45:33 hey there stephw :) 18:45:39 hi :) 18:45:50 * pili wonders if stephw has an alert for "twitter" ;) 18:45:55 haha indeed 18:46:14 :D 18:46:16 thanks for confirming :) 18:46:23 ok, so we should get that transferred probably 18:46:41 yes 18:46:57 I think someone in tor besides ilv has access to that account 18:47:00 but I don't think twitter is a deal breaker to go live, i would still love to know how many requests we were getting before it stopped working 18:47:04 but I wouldn't know 18:47:13 so we can figure out how useful/important it is to users 18:47:38 but pili the code is quite probably the same, and it will work again as soon as we apply again for dev access 18:47:43 I think before you didn't need this 18:47:52 yup 18:47:53 and now you have to go through a quick process 18:48:04 in which you tell them what you want to do with api access 18:48:32 so even if this is for only a few people a month I think it would be cool to have it back 18:48:35 we can play it by ear, let's see about getting twitter access back and in parallel work towards deploying the new gettor 18:48:41 if it doesn't require too much effort 18:48:50 hiro: yup, agreed, I'm just always interested in numbers :D 18:49:14 I would really love to know how many people use gettor and the different channels, etc... :) 18:49:46 sure 18:50:03 one thing that we can do is sending that info to the logs 18:50:13 and do some log rotation and store it somewhere 18:50:17 but it's just curiosity, I don't _need_ to know 18:50:26 I wonder if metrics would be interested at all also 18:50:30 but we should have a way to know 18:50:32 if we wanted 18:50:32 or anti-censorship team 18:50:37 we just need aggregated numbers 18:50:40 we should push that info to metrics 18:50:46 antonela:+1 18:50:49 like something we compile at the end of the day 18:50:56 or weekly, or monthly 18:51:01 yeah and if we use a format metrics can easily crunch 18:51:07 they can import it with collector 18:51:12 yes 18:51:33 notirl will be happy to play with it 18:52:16 that should go in the PRD ;) 18:52:23 I think that's all for my side... finish testing then review 18:52:34 ok, thanks for your work on this hiro!!! :) 18:52:40 oops 18:52:51 I was still in the other meeting 18:52:52 sorry 18:53:06 ok, I have about 5 more minutes 18:53:12 so, what is needed on my side? lets wait for hiro, update gettor.tpo.org? 18:53:14 * antonela too 18:53:25 yes I think that's it 18:53:32 antonela: I think so 18:53:54 I was also going to say if anyone else wants to stay on then gaba could take over for the second half of the meeting 18:54:10 * gaba going to read the backlog after it 18:54:15 and we really need to meet at some other point to discuss the PRD 18:54:44 okey, once hiro has it working we can try it and walk through the different escenarios and think how we can improve that webpage 18:55:11 that is the scope? 18:55:18 ok 18:55:44 ok thank you everyone I think I'll walk the dogs 18:55:44 antonela: I think so 18:55:50 pili great 18:55:54 do we have deadlines? 18:56:01 for hiro and for final version? 18:56:16 before I go on vacation I want to have the review 18:56:30 when is that? 18:56:32 hiro 18:56:39 15th of match 18:56:41 march 18:56:55 I wanted to have it running with gettor+test@tp.o today 18:57:01 but got slowed down w other things 18:57:25 I think we have time 18:57:35 so the ux team can work on that the last two weeks of march? and talk about the improvements implementations at the webpage when hiro is back 18:57:50 it sounds good to me 18:57:51 yes 18:58:16 the first thing that comes to my mind is removing all those hard requirements for send that email and make some kind of natural language form, but i need to think more about that 18:58:36 ok 18:58:43 Can we setup a next gettor checkin at the beginning of the march 15th week? 18:58:57 can that be the week before that? 18:59:03 the thursday before 18:59:14 I mean 15th is a friday I think 18:59:26 yup, I think so too 18:59:29 14th 18:59:31 so 18:59:31 ? 18:59:38 so between the 10th and that friday more or less 18:59:52 same time same channel? 18:59:56 14th I'm traveling but I can meet the 13th or you can all do for next steps 19:00:24 13th works for me 19:01:00 I need to double check about the time 19:01:08 can I follow up tomorrow by email? :) 19:01:14 (I really have to run soon) 19:01:14 1700 UTC ? 19:01:18 ok 19:01:20 bye pili! 19:01:21 ok 19:01:26 me too 19:01:28 yeah 19:01:29 me too 19:01:30 thanks people! 19:01:31 are we still logging the meeting? 19:01:34 one of the dog is bumping me with the nose 19:01:38 pili close the bot haha 19:01:38 :P 19:01:40 yup, still logging 19:01:41 ok 19:01:44 please 19:01:45 thanks! 19:01:46 #endmeeting