17:00:00 <hellais> #startmeeting
17:00:00 <MeetBot> Meeting started Mon Jul 13 17:00:00 2015 UTC.  The chair is hellais. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:00 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
17:00:02 <hellais> who is here?
17:13:55 <hellais> nobody?
17:29:21 * sbs is here
17:29:49 <hellais> I will at this point to a brain dump of what happenned last week for log sake.
17:29:50 <hellais> What I did this week:
17:29:50 <hellais> * Hacked on the OONI hackathon website. A large portion of it is done and I shall speak again with the designers this week to sort out some aspects of the design. The plan is to publish it this week or the next.
17:29:53 <hellais> * Met with a probe operator and gave them a raspberry pi
17:29:56 <hellais> * Worked on lepidopter build script to automate building of the image on AWS
17:29:58 <hellais> * Discuss options for the OONI OTF proposal
17:30:46 <hellais> if  you have questions, comments, things to talk about, don't be shy :)
17:33:44 <sbs> I started to help people at the University of Pisa to integrate measurement-kit into their network measurement tool, Portolan
17:34:08 <sbs> This is a follow up of when Portolan code for doing traceroute was contributed to measurement-kit
17:34:24 <sbs> and is a good use case for the porting on Android of mkit
17:44:06 <hellais> excellent!
17:44:22 <hellais> so I think for me the next steps are to finish implementing the website
17:44:46 <hellais> the biggest potential blocker I see is implementing the dynamic team/project registration form
17:46:22 <sbs> hellais: how do you plan to implement it?
17:47:30 <hellais> sbs: I think I will make a node.js app running on heroku
17:47:37 <hellais> most probably based on strongloop
17:48:04 <hellais> the static ooni.tpo website will then communicate via REST to the heroku app to POST the data and load the content
17:48:24 <hellais> CORS will ensure this is possible across different hosts
17:48:38 <hellais> the data will end up inside of a postgres database
17:48:51 <hellais> I am not yet sure if it is to be also integrated into eventbrite
17:48:57 <hellais> but perhaps also tghat
17:49:51 <hellais> thoughts?
17:52:08 <sbs> hellais: what do you mean by integration with eventbrite? that one could use eventbrite to register?
17:53:23 <hellais> sbs: yes, if we want to use eventbrite to collect participation and potentially have people donate when they join the event or something
17:54:41 <sbs> hellais: if the answer to the latter question is yes, wouldn't it be easier to just use eventbrite?
17:56:04 <hellais> sbs: the problem is that we need to also get information about 1) What team they want to join 2) Support creation of a new team 3) Show the existing teams, etc.
17:56:19 <hellais> looking at the eventbrite API it seems like it's too limited to support this sort of features
17:59:37 <sbs> hellais: ah, I understand... ok, so probably it's the other way round and supporting also eventbrite with limited features could be confusing?
18:03:27 <hellais> perhaps
18:03:36 <hellais> I guess we could also not collect donations
18:04:12 <sbs> sbs: well, we could eventually discuss this further in the coming days!
18:08:14 <hellais> indeed
18:08:25 <hellais> I can share some code with who is interested
18:12:40 <sbs> sbs: great!
18:12:53 <hellais> I guess this gathering is over
18:12:57 <hellais> sbs: thanks for attending :)
18:14:02 <hellais> #endmeeting