17:02:38 <hellais> #startmeeting
17:02:38 <MeetBot> Meeting started Mon Nov  9 17:02:38 2015 UTC.  The chair is hellais. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:02:38 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:02:43 <hellais> ok sorry for the lag
17:02:44 <hellais> here we go
17:03:02 <hellais> let's get this started who is here?
17:03:26 <hellais> you can also comment on Dunbar if you want here is an informative link: https://en.wikipedia.org/wiki/Dunbar%27s_number
17:05:25 <sbs> hello again
17:06:02 <poly> heyo
17:06:07 <hodgepodge> Hello.
17:06:51 <sfh> Hello.
17:06:54 <landers> here
17:06:59 <hellais> so let's go with some report backs
17:08:42 <sbs> ok... as regards me:
17:08:49 <sbs> I have a number of pull request reviews pending. I did some progress in the revi
17:08:50 <sbs> ew of the ORG pull request ( https://github.com/TheTorProject/ooni-probe/pull/406 )
17:08:57 <sbs> (damn)
17:08:59 <sbs> EOF
17:09:13 <poly> I'll go next...
17:09:46 <poly> worked on simplifying regex parsing within network meter
17:09:49 <poly> https://github.com/measurement-kit/network-meter/pull/35
17:10:15 <poly> however, as sbs noted, the current method is still too unstable to be merged
17:10:44 <poly> it seems that the simpler approach doesn't work due to the nature of comments in javascript
17:10:56 <poly> so I will need to think of someway of handling the issue
17:10:57 <poly> EOF
17:11:40 <hodgepodge> I'll go next.
17:12:13 <hodgepodge> No updates on ooni development while ooni-api service is restored, and reports are being normalized, looking for something to do.
17:12:14 <hodgepodge> EOF
17:12:24 <hellais> I worked on:
17:12:25 <hellais> * Fixing the ooni-pipeline and defeated the angry AWS monster
17:12:25 <hellais> * Taking care of migrating the backend collector and bouncer to a new box (Greenhost is down since 48 hours or more and are not super reliable)
17:12:27 <hellais> * Prepared some documentation about the ooni-api and pipeline to run locally https://github.com/TheTorProject/ooni-pipeline/commit/29852f5360eccacbd243683546420a94a2c7ad45 https://github.com/TheTorProject/ooni-api/commit/c7007e3f9430f89100469bc946803bcd2c8ed38a
17:12:42 <hellais> also I worked on clearing my backlog of people to follow up on stuff
17:12:52 <hellais> and replied to some comments on the github
17:12:56 <hellais> EOF
17:13:04 <landers> i've been doing not so much. learning about kubernetes, thinking about sysadmin things. EOF
17:13:17 <hellais> thank you all for the nice and tight report backs as gunner would say
17:13:33 <hellais> (gunner is this guy that facilitates meetings that one day you will perhaps meet :) )
17:13:42 <landers> uwelcome
17:13:53 <hellais> so now, is there something somebody would like to talk about?
17:15:56 <hellais> since nobody replies I am going to bring out a very tedious topic
17:16:01 <hellais> the day and hour
17:16:09 <hellais> is this ok for all of you or should we change it?
17:16:22 <sbs> hellais: it's ok for me
17:16:25 <hellais> I know the legal illegal time creates issues and we should be friendly also to the canadians
17:16:28 <hellais> :)
17:16:45 <landers> no objections from me
17:17:04 <hellais> the time shall be synchronized to UTC as the universe dictates
17:17:08 * hodgepodge didn't know that legal/illegal time exists
17:17:18 <hellais> so 17:00 UTC is now 18:00 CET
17:17:22 <hellais> (notice the missing S)
17:17:25 <hellais> S == Summer
17:17:33 <hellais> CET == legal time as we say in italy
17:17:33 <hodgepodge> Oh God.
17:17:40 <murb> MEZ
17:17:45 <hodgepodge> Is DST not a universal construct?
17:17:47 * hodgepodge doesn't know
17:17:56 <hodgepodge> (i.e. daylight savings time)
17:18:07 * murb who had DST/CET/MEZ issues this morning :(
17:18:29 <hodgepodge> I think that we can all agree that using UTC is the way to go.
17:18:32 <hellais> hodgepodge: in italy we call it different, we say "legal" and "oral solare"
17:18:35 <hodgepodge> Time handling makes no sense.
17:18:35 <hellais> *legale
17:18:41 <hellais> like "legal" and "solar time"
17:18:42 <hodgepodge> Oh, gotcha.
17:18:47 <hellais> we are a bit innatively anarchist
17:18:56 <sbs> lol
17:18:57 <murb> yeah use solar time :p
17:18:58 <hodgepodge> It sounds so much more elaborate too.
17:19:09 <murb> webcam + sundial.
17:19:20 <hellais> murb: hahahah
17:19:30 <hodgepodge> We call it daylight savings time because it gives you more daylight in the morning.
17:19:35 <hellais> anyways some more ooni related topics?
17:19:46 <hellais> otherwise we move onto the next steps
17:19:47 <hodgepodge> Who needs help?
17:20:18 <hellais> hodgepodge: it would be great to have some help on the documentation and next steps of the ooni-pipeline and ooni-api
17:20:41 <hellais> since that is a thing that can be done by others and we have a contract to do some work on it to be conclude end of december 2015
17:20:53 <hellais> also I think sbs needs help reviewing pull requests
17:21:06 <hellais> reviewing pull requests is always something that is tedious and it would be good to have more eyes on
17:21:16 <hodgepodge> If you send me a pull request, and help me figure out how to test it locally, I can help with that part.
17:21:27 <hodgepodge> I don't really know how to develop oonib components.
17:21:31 <hellais> sbs: do you have some priorities for the PRs?
17:21:46 <hellais> hodgepodge: did you manage to get ooni-pipeline and ooni-api running locally or on some box?
17:22:04 <hellais> (Off topic this is an interesting time construct: https://it.wikipedia.org/wiki/Swatch_Internet_Time)
17:22:51 <hodgepodge> No, I haven't. Do I just need to run an ansible playbook to set-up a local dev environment?
17:22:57 <sbs> hellais: my top priority at the moment is the JNI API
17:22:58 <sbs> https://github.com/measurement-kit/measurement-kit/pull/200
17:23:04 <sbs> and the related android app
17:23:23 <sbs> https://github.com/measurement-kit/measurement-kit-app-android/pull/1
17:24:40 <hellais> hodgepodge: unfortunately not, that would be epic though
17:24:57 <hellais> hodgepodge: the dependencies are not many though it's basically posgresql and node
17:25:12 <hellais> sbs: ok thanks for pointing those out
17:25:24 <hellais> I will see if I can test them as soon as I get my other cruft out of the way
17:25:41 <sbs> hellais: thanks!
17:25:46 <hellais> hodgepodge: writing the ansible tasks piloted by invoke, perhaps, would be very good
17:25:51 <hodgepodge> Is there a canonical set of instructions for setting up a dev. environment for ooni-pipeline?
17:25:58 <hellais> hodgepodge: ah wait
17:26:04 <hellais> ooni-pipeline yes, it's super simple
17:26:06 <hellais> ooni-api no
17:26:25 <hellais> let me find the ooni-pipeline stuff
17:26:34 <hodgepodge> Okay, great.
17:26:54 <hellais> you need to configure it in invoke.yaml
17:27:09 <hellais> and to setup the dependencies on aws there is a invoke task called start_computer
17:27:09 <hellais> https://github.com/TheTorProject/ooni-pipeline#how-to-run-the-pipeline-tasks
17:27:28 <hellais> https://github.com/TheTorProject/ooni-pipeline/blob/master/tasks.py#L250
17:27:35 <hellais> it takes an invoke command to be run remotely
17:27:42 <hellais> instead if you want to run it on your machine
17:27:45 <hellais> you will need
17:27:56 <hellais> requirements.txt and requirements-computer.txt
17:28:19 <hellais> https://github.com/TheTorProject/ooni-pipeline/blob/master/playbook.yaml#L58
17:28:23 <hellais> as is shown in the playbook
17:28:38 <hellais> you will have to change teh playbook to work with a non aws machine
17:28:41 <hellais> but it should be minimal changes
17:29:06 <hellais> basically you just change this: https://github.com/TheTorProject/ooni-pipeline/blob/master/playbook.yaml#L45
17:29:42 <hodgepodge> Alright, thanks!
17:29:59 <anadahz> hi
17:30:00 <hellais> if you are digging this ping me when you are hacking on it and I can help you out
17:30:26 <hellais> I can also give you a AWS sub account like anadahz has
17:30:38 <hodgepodge> Alright, thanks, I'll be sure to ping you with the deets on my progress.
17:31:35 <hodgepodge> Whatever is easiest. I have access to an Ubuntu VM so it shouldn't be too difficult for me to replicate what you already have.
17:32:11 <hellais> that would be neat
17:32:18 <hellais> so we also don't just have to depend on AWS
17:32:25 <hellais> if you do this please document it in some form
17:32:39 <hellais> even if it's just a script that does what you did or a text file with some notes
17:34:18 <hodgepodge> Yeah, for sure.
17:34:44 <hodgepodge> There are a few things I've been meaning to take a look at, if there's a way to get this running locally, that'll be the first step.
17:39:14 <hellais> so now for next steps I guess
17:39:21 <hellais> I will be working on migrating the backend
17:39:30 <hellais> setting up a NAS for disaster recovery purposes
17:39:41 <hellais> and reviewing pull requests and replying to backlog of mailz
17:40:00 <anadahz> has anyone experience any issues with oonireport?
17:40:36 <hellais> anadahz: the bouncer is down
17:40:39 <anadahz> it seems that oonireport doesn't always upload the reports under some circumstances which are not yet know
17:40:54 <anadahz> hellais: this happened some weeks ago
17:41:26 <anadahz> sbs helped me debug and even provided a patch to the oonireport
17:41:35 <hodgepodge> Is oonireport used to upload the publicly facing reports on the ooni website?
17:41:46 <hodgepodge> It looks like that hasn't been updated since February?
17:42:51 <anadahz> hodgepodge: oonireport uploads the reports to the collector that haven't been uploaded for any reason
17:43:02 <hodgepodge> Oh, gotcha.
17:43:03 <hodgepodge> Thanks.
17:43:17 <anadahz> hodgepodge: https://github.com/TheTorProject/ooni-probe/blob/master/bin/oonireport
17:44:17 <anadahz> unfortunately lepidopter uses oonireport to freed up space
17:44:38 <anadahz> so in one of my tests RasPis i realized that there was no space left
17:44:39 <hellais> oonireport will not work today as I told you already on the telephone
17:44:55 <anadahz> hellais: please re-read my msgs
17:44:56 <hellais> the greenhost box is down as I said at the beginning of the meeting
17:45:39 <hellais> I have, but your question is a bit vague given that even if there were no bugs (that will always exist in software) it would not work anyways
17:45:45 <hellais> anyways now is the time for report backs
17:45:50 <sbs> hellais: oonireport uses reports.yml to decide the reports to upload, or am I wrong?
17:45:51 <hellais> you had time for discussion previously
17:45:56 <hellais> now let's move to next steps
17:46:01 <hellais> since there are only 15 minutes left
17:46:47 <sbs> Ok. My next steps: Will continue to study JNI, initiate to study CPAProxy, review pending PRs. EOF
17:47:19 <anadahz> if oonireport is not going to be fixed i 'll be force to remove it from lepidopter and just delete the reports that haven't be uploaded
17:47:39 <anadahz> ^ place this to the the discussion part
17:55:52 <hellais> ok so if nobody has anything to add
17:56:12 <hellais> I would say we can say bokraxiexie, to tomorrow humans
17:56:17 <hellais> #endmeeting