17:00:08 #startmeeting 17:00:08 Meeting started Mon Nov 16 17:00:08 2015 UTC. The chair is hellais. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:08 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:01:17 ok let's start with this thing 17:01:19 who is here? 17:01:55 ich 17:01:57 hey! 17:02:22 hi 17:02:38 hi! 17:02:54 hi 17:03:25 oi 17:03:51 hi 17:04:08 most excellent! The OONI boat is rocking today! 17:05:32 so what took up your time last week? 17:06:52 spent a night digging through the ooni-sysadmin and ooni-backend repos; thinking of ways to reduce the ansible-installing-docker-installing-ansible stuff going on. will do more this week. EOF 17:09:14 I spent time coordinating a variety of different things: including talking with joe about restoring the pipeline, with brennan about the API and thinking about what to do of the future of OONI. 17:09:26 the future is good and there are also free cookies /me thinks 17:09:34 EOF 17:09:51 as regards me 17:10:00 - measurement-kit: 17:10:09 - merged: https://github.com/measurement-kit/measurement-kit-app-ios/pull/20 17:10:17 - studied lambdas https://github.com/bassosimone/relight 17:10:32 - OONI: 17:10:33 - merged: 17:10:33 - https://github.com/TheTorProject/ooni-probe/pull/424 17:10:33 - opened: 17:10:33 - https://github.com/TheTorProject/ooni-probe/pull/426 17:10:36 - https://github.com/TheTorProject/ooni-probe/pull/425 17:10:50 EOF 17:11:31 I'll go next - I also looked through the ooni-sysadmin/ooni-backend repos in order to determine which components are involved in an oonib deployment - afterwards, I looked into what MLab has in terms of open datasets, and how data hosted by them, and related parties can be correlated to data that OONI is collecting. 17:11:32 EOF 17:11:43 ah yes I also did some code review and merging, but I have no browser to prove it 17:12:20 podgesomehodge: good stuff! 17:12:37 podgesomehodge: landers and you should speak. He is now on the pipeline/sysadmin train 17:12:47 * landers pulls horn 17:13:02 There was someone else who was interested in working on API improvements, apart from brennan wasn't there? 17:13:07 bnvk? 17:13:15 bnvk == Brennan 17:13:23 Okay, great. Thanks! 17:13:25 the full extension of that nick is brennan novak 17:13:39 Gotcha. 17:13:55 I will now ask something to isabela, but don't let me stop you from reporting if you wish to report 17:14:18 isabela: is there somebody you would need from our side (like share with you the proposal before it's submitted) to make sure Tor is happy with the fellowship proposal? 17:15:00 isabela: since it will be me and sbs (Simone Basso from Nexa Center) handling it I think it should not entail any overhead from Tor's side, but we need your approval for the dates (2015-01-01 to 2015-12-31) 17:15:07 err 17:15:18 2016-01-01 to 2016-12-31 17:15:24 the future! 17:15:59 hellais: when are you submitting it? 17:16:19 nuke-: when is the deadline? 17:16:39 The deadline is this Friday 17:17:22 I received the acceptance of submitting a full proposal only five days ago 17:18:00 oh I see, so you are like in phase 2 or something 17:18:15 I think share it with me and roger? 17:18:25 isabela: correct. We submitted the application a LONG time ago and now we are in the advanced stage (the final boss) 17:18:26 I'm gonna work on it today and tomorow full time, to have a full draft by Wed and submitting it on Thu 17:18:28 he probably does not have the time but just to keep him in the loop 17:18:44 isabela: ok we shall do. Can you PM nuke- some emails to share the doc with? 17:18:53 yes 17:19:10 is it a gdoc? 17:19:16 yes 17:19:19 isabela: thanks a lot! 17:19:19 ok 17:19:36 np 17:19:37 Ok so I will share it on Tuesday or Wednesday. Thanks isabela 17:20:01 so from my side: 17:20:02 np! 17:20:40 setup (WIP) the hardware components (bare metal) for OONI API DB 17:20:41 provide support to a number of lepidopter installations deployed in several geographical locations 17:20:44 deployed some manages lepidopters 17:20:45 fixed/improved lepidopter core functionalities scripts and cronjobs 17:20:48 helped juga__ on the psiphon install script 17:20:49 finalized the ansible ooniprobe role on a system without docker: https://github.com/TheTorProject/ooni-sysadmin/pull/15 17:23:07 EOF 17:23:17 sorry forgot that ^ 17:24:44 anadahz: epic! thanks for the report back! 17:27:00 there are some admin PRs that are pending for review: https://github.com/thetorproject/ooni-sysadmin/pulls 17:28:14 anadahz: can you point to the numbers in prioritised order? 17:28:41 we should also update the roadmap since we have not done that yet 17:28:49 I will be in Berlin tomorrow so we can discuss this IRL 17:29:19 hellais: https://github.com/TheTorProject/ooni-sysadmin/pull/14 https://github.com/TheTorProject/ooni-sysadmin/pull/15 https://github.com/TheTorProject/ooni-sysadmin/pull/11 17:29:26 arg 17:29:33 anadahz: if you paste them one per line the bot will reply 17:29:38 #14 17:29:45 https://github.com/TheTorProject/ooni-sysadmin/pull/14 17:29:52 no bot love today? 17:29:59 aah, it's on a non monitored repo 17:30:12 The future is weird. :/ 17:30:17 I will get the weasel to do it 17:30:25 podgesomehodge: #agreed 17:30:48 uncertain for sure, but given recent events also very weird. 17:31:00 though we are not in the business of politics at the moment :P 17:31:54 are there any other topics you think we should put on the table for discussion now? 17:32:53 yes, how are annotations work in ooniprone? 17:33:31 anadahz: ooniprobe --help 17:33:46 tried to add the -a (annotate) parameter with a key in this format blah:000 but wasn't added to the report 17:34:11 anadahz: weird. Then I can only point you to the source luke 17:34:24 it should, in theory, end up in the report header 17:34:35 I didn't develop that feature though so I don't remember how it was 17:35:31 there is too less documentation regarding annotations 17:35:55 and it's a feauture that has been asked for some time.. 17:38:18 anadahz: pull requests are always nice for documentation ^_^ 17:39:12 hellais: agree! 17:39:13 are there any other topics to discuss? 17:39:54 pull requests for documentations are the best actually! Since they require a long time to write and not that much though to merge. I love them so much you peeps can't even imagine! 17:43:14 isabela: any news regarding OTF? 17:44:15 anadahz: about what exactly 17:44:58 isabela: OONI's project proposal 17:45:32 ah, no not yet, but I am trying to have a call with them soon and I will ask about it 17:45:59 because we are starting our second year with them on the TBB/core tor project 17:46:45 I should also ping them about this tbh 17:46:50 I just have been overworked 17:47:07 if somebody helped out more with the sysadmin tasks and there was more communication on IRC this could happen 17:51:41 anyways I guess we should do the next steps 17:51:51 I will try to touch base with OTF about the proposal state 17:52:15 then I will continue helping out landers and bnvk to work on the backend stuff 17:52:40 also I will be busy doing a lot of meetings in Berlin to futurise the future of the Open Observatory 17:56:35 other people want to share theirs? 17:58:21 I 'll be working again on the hardware components this week 17:59:01 Determine a nice way to remove the older uploaded reports from lepidopter 18:00:17 Continue enhancing/cleaning ooniprobe documentation 18:00:29 EOF 18:00:30 i think i'll try to get the ooni-api up on ec2 instead of heroku, and streamline the -backend and -sysadmin repos also, as it seems someone a few pages up ^ was trying to get that running 18:01:52 eof 18:02:13 I need to study more of JNI to make sure the JNI api I've sketched out is correct EOF 18:02:24 I'm working on the fellowship proposal, to be submitted in three days. After this I will have more clear the objectives for the next year. That will not be only finishing iOS and Android app but also to make one or two frameworks to be easily integrated by any developer. 18:02:41 purrfect :) 18:02:48 Will keep you updated about the proposal. 18:02:49 EOF 18:02:56 thank you all for your time 18:03:10 unless somebody else snipers this I am going to close the meeting just 3 minutes overtime 18:03:32 4 - 3 - 2 - 1 18:03:35 #endmeeting