17:00:47 #startmeeting 17:00:47 Meeting started Mon Apr 27 17:00:47 2015 UTC. The chair is hellais. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:47 Useful Commands: #action #agreed #help #info #idea #link #topic. 17:00:55 ok so here we go 17:01:34 so who is here? 17:01:39 here 17:01:45 here 17:02:02 #help 17:02:35 here 17:02:53 so for this meeting arturo and I proposed we update and delegate tickets related to our open data hackfest in rome 17:03:06 I created tickets based on some points from arturo: https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~ooni-odhf 17:03:25 this is likely not a complete set of tasks 17:04:42 a few tasks may block on deploying the new ooni website, but I'm not sure what the status/timeline of that task is 17:04:45 yes true 17:05:04 I think most of those tasks have a predictable amount of time they will require except the pipeline migration stuff 17:05:40 but I would say that before we digg into that perhaps it's useful for us all to do a round of what has happenned in the last couple of week? 17:08:35 I will interpret such silence as "please do begin with yourself" :P 17:08:52 I can go. I have not done much OONI related tasks in the past week other than to reach out to some big data contacts and discuss with arturo our plans for the hackfest and data architecture 17:09:01 ah ok 17:09:35 aagbsn: anything else? 17:10:06 possibly but nothing off the top of my head 17:10:14 on my side what went on from the 14th-today is: 17:10:46 * We had a call with some people from MLAB to discuss having libight be a library for all MLAB tests and completed the prototype of the iOS app with nuke 17:11:15 * Reviewed the pull requests from vasilis and you on the censorship tool tests and specs 17:11:35 * Had to update the bouncer ooni-sysadmin script to work with the production mlab-ns. 17:11:52 * Then a lot of work was done on organising this OONI Hackfest 17:14:16 from my side I have finished the lepidopter image script 17:14:32 https://twitter.com/OpenObservatory/status/592738610778120192 17:14:43 this is what some designers have come up for the banner of it 17:15:16 hellais: oh sorry I thought you 've finished (long pause ;)) 17:15:36 yeah sorry I thought it would take me less to upload that image 17:15:51 anyways we have some possible dates for the hackathon: 17:16:20 60% 5-6%, 40% 19-20, 10% 26-27 June 17:16:27 err 5-6 17:16:42 the other work we did this past week was related to the OTF proposal, reviewing our budget estimates and looping in isabela and tom for feedback. I believe art has been reaching out to otf for early feedback, as well 17:16:45 the probability is there because we have so far only confirmed the first of juen and last of june 17:17:03 hellais: that image rocks! 17:17:05 aagbsn: yes true 17:17:08 love it 17:17:15 aagbsn: :) 17:17:29 they also made a mockup of the announcement page 17:17:48 I think we can manage to launch it by end of week 17:17:51 (though I dont know why the octopus needs a scuba mask, maybe the water is quite polluted ;) ) 17:18:26 aagbsn: it's more of a special optic to see censorship better 17:18:27 it would be quite good to lock in our dates for the hackathon so people can plan around it; it's a bit bleh to block out all of june 17:18:51 yeah well when we make the announcement the dates shall be fixed :P 17:18:55 so end of week we will know for sure 17:18:57 but as hellais points out, we need a good estimate for how long these tasks will take 17:19:09 I am waiting on the parliament to call me back and tell me what dates are good 17:19:11 and who can commit to working on them, so we can complete everything before jun 17:19:53 is ADINA15 the official name of the event? 17:20:14 anadahz: do you like it? 17:20:23 it doesn't have to be, but I like how it sounds 17:20:30 it's quite pronounceable in any language 17:20:55 ADNA was another contender, but ADNA is actually a thing 17:21:02 is it just a random or implies a meaning as well? 17:21:15 the elephant is that our data architecture must be available for the event 17:21:15 A Dive into Net Aonomalies 17:21:22 aagbsn: yes correct 17:21:31 let's return to the main points 17:21:32 and be something that we are going to stick with for a while 17:21:55 hellais: i like it ;) 17:22:02 so another passtime of mine in the past week has been to explore the big data subculture 17:22:32 it's a pretty intersting field and there are some solutions to our data storage and querying needs 17:22:40 much better than mongodb as a matter of fact 17:23:24 though I fear this to be a big rabbit hole so I would advise if we first go through the tickets you created 17:23:34 and perhaps start assigning some names to the easy tasks 17:23:51 #link ooni hackathon tickets: https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~ooni-odhf 17:24:23 so this I think is easy: https://trac.torproject.org/projects/tor/ticket/15833 17:24:32 as a matter of fact it already is happening here: ooni.io 17:24:49 I just have to update my script to push it also to the torproject server 17:25:52 this is fun code to write perhaps: https://trac.torproject.org/projects/tor/ticket/15829 17:26:13 I sort of question whether that task is a good use of time 17:26:40 can we just ask particpants to send an email to {the list, a point of contact} ? 17:28:44 I added the google doc where the announcement page resides: https://trac.torproject.org/projects/tor/ticket/15828#comment:1 17:28:50 it needs more work, but the structure is there 17:29:29 aagbsn: it's that it requires manual labor to fill in the project descriptions with $number_of_members_in_team 17:29:40 to be honest it's a quite trivial thing to do 17:30:01 otherwise if somebody volunteers to daily spooling the emails and updating the website we can do it the manual way 17:30:18 there probably is some service that already does this 17:30:21 did we intend on adding all applicants to the page? or all accepted applicants? 17:30:29 all applicants 17:30:34 we don't do selection of applicants 17:30:41 you just have to preregister and then you can show up 17:30:56 if you can't afford to come to Rome, there is a stipend program 17:30:59 oh, I was under the impression we had finite travel stipend funding :) 17:31:02 that require you to be approved 17:31:05 but I see what you mean 17:31:15 well the travel stipend is not for general attendance 17:31:19 so perhaps, if we expect quite a number of attendees, that this is indeed a useful task 17:31:24 it's a special thing for people in need of travel support 17:31:38 we have a limit of 100 people 17:32:09 is that a hard limit? 17:32:20 if we do FCFS we might expect that some people will not make it 17:32:21 but still I would expect we get around 100 registrations, probably not all will show up though so we should factor that into the algorithm 17:32:58 yes +1 17:33:03 tricky. 17:33:12 there are a few missing things there 17:33:13 (are we an airline now or something?) 17:33:17 in the ticket list I mean 17:33:29 for example that we neewd to make a list of OONI proposed teams 17:33:37 that can work on some project we consider interesting 17:33:58 this is crucial because it will set the themes of the sort of projects people will be proposing 17:34:50 this is a good point; though I think we should be careful to have fairly vague categories as we ideally wont have thought of all the ideas people are proposing :) 17:35:16 such as, "interactive visualization" 17:35:23 I don't plan on having categories 17:35:34 hm, what is your thought? 17:35:38 I think people should be able to propose anything 17:35:50 even say, make a painting that is inspired by internet freedom 17:36:05 agree, though we may want some suggestive ideas 17:36:22 well the ideas are to be very concrete and detailed 17:37:17 and I think that if we summarise well what is in #13731 we have already a good starting point 17:39:10 #15838 17:39:50 we also need to come up with the rules for the hackathon and come up with what prizes we want to give out 17:40:28 I was also thinking that since we don't know how much bandwidth we will have there it may be good to bring a computer with the OONI data in various formats and people can plug in their own hard drive and get the dump of ooni data 17:40:46 yes, we should have some local copy of the infrastructure 17:41:06 so many events i have been to with internet or wifi that falls over... 17:41:08 if we want to be super pro we can buy some cheap USB drives (they must have 100s of GB) and prepare them in advance with a copy of the ooni data 17:41:13 and we can have people pass them around 17:41:28 ... ha, lets just put this on a http server on the network :) 17:41:42 well if the wifi goe's down it's crap 17:41:48 we can just do this with a cheap gbit ethernet switch 17:41:53 also if everybody is downloading via wifi it's super slow 17:41:59 USB 3.0 is very fast 17:42:11 much faster than any consumer networking card 17:42:16 even GBIT 17:42:30 most flashdisks are shit or expensive. show me a usb drive that can push > 60MB/s :) 17:42:31 (and who even has ethernet these days) 17:43:02 aagbsn: I am not talking about flash disks I am talking about hard disk 17:43:06 2.5" USB 3.0 17:43:23 the WD 1 TB drive costs about 70 EUR 17:43:30 ok 17:43:46 we can do both, I assume 17:44:01 we could even do something crazy like emulating a USB drive from a computer 17:44:07 I should have a spare switch or we can acquire one 17:44:18 so you actually read the data off the hard drive of the computer 17:44:27 we should also find out what kind of network infrastructure is available to us 17:44:43 will we have wired ethernet uplink, can we deploy our own AP, etc 17:44:47 yes, when I have the confirmed dates I will go and scout the venue 17:44:53 ok right on 17:44:58 I haven't actually seen it yet, but people have told me good things of it 17:45:10 I can probably borrow some ubiquiti networks AP 17:45:14 I also have a few myself 17:45:24 (3) 17:45:30 http://dati.camera.it/it/hackathon/ 17:45:34 they did this thing in the past 17:47:26 I also have various wifi gear 17:47:36 a routerboard with 2 wifi cards 17:47:49 2-3 APs of misc types 17:48:06 1 ubquity picostation 17:48:21 or nano don't recall 17:48:22 i have a few nanostation loco m2 17:48:26 2.4 band 17:48:49 anyways we shall discuss this once we have an idea of the venue 17:48:57 but no worries for now, we can update the relevant ticket 17:49:02 so these tickets? 17:49:08 who wants them :P 17:49:10 ? 17:49:35 (did we lose everyone or is anyone still around :) )? 17:50:49 we could maybe go a day before the event and setup the infrastructure 17:51:01 there is some serialization to these tasks. I could potentially look at #15829 though I might not be the ideal person as I am not familiar with the new site design yet 17:51:19 #15831 I can take 17:51:35 anadahz: yes, with aagbsn we were discussing even perhaps 2-3 days before 17:51:46 arturo or another local italian might be best for #15835 17:51:48 anadahz: so arriving on tuesday or wednesday 17:52:23 aagbsn: yeah I will take care of that. I think had already prepared some it it somewhere 17:52:32 I can also look at #15838 17:52:41 I can take #15835 17:54:01 ok I have taken those 2 tickets. what is your username on trac anadahz ? 17:54:16 aagbsn: yes 17:54:21 anadahz: I think it's ideal I do #15835 :P 17:54:32 * irl arrives late 17:54:35 hellais: OK 17:54:39 I tend to agree since I suspect a lot of this travel stuff will be in italian 17:54:46 unless you are very familiar with the roman transport system 17:54:47 ? 17:54:48 :P 17:54:52 so what's about #15834 17:55:04 so I am not sure what that means, exactly :) 17:55:06 hellais: not really ;) 17:55:21 #15834 is actually probably already done 17:55:38 we can just use the machine on which ooni-app resides and implement it as part of ooni-app? 17:55:39 aagbsn: 'dynamic aspect' 17:55:54 or find a service type solution for it 17:56:46 I'd like whatever we roll out to be the thing we deploy longer term 17:57:01 so that is the biggest unknown in terms of time, with regard to our schedule 17:57:21 or am I misunderstanding what this ticket is about? 17:57:40 that ticket could do with some details on it :/ 17:57:53 yes, they are just placeholders 17:58:02 aagbsn: what is "the biggest unknown in terms of time"? 17:58:18 we have about a month if we select the earliest dates for the event 17:58:56 I think that is doable if we pick something simple and extensible 17:59:39 well I was thinking that this would be a simple bit of javascript that does a query to some REST API and it either POST a proposal or GETs the existing ones 17:59:54 we could easily implement this as part of the ooni-app api 17:59:56 ah, yes, I was misunderstanding this ticket 18:00:01 it's sort of ghetto to put it there 18:00:03 but whatever 18:00:15 it will take 1 hour to implement and be deployed with 1 command 18:01:05 so, #15830 is the big item, I think 18:01:34 aagbsn: yes that is the biggest one 18:02:00 which is actually a few subtasks. I think arturo and I can collaborate on slicing that up 18:02:11 (I looked at the hugo documentation and it looks like we can do this without even using javascript with it's "Dynamic Content" feature) 18:02:38 yes #15830 is quite a task 18:02:45 but some progress is being made 18:03:21 we also exploring the possibility of getting some big cloud big data provider to sponsor us 18:03:40 I was supposed to hear back from one of them today, but so far nothing. I will call them tomorrow at this point. 18:04:17 I am currently experimenting with the rackspace cloud and I am putting all the reports into hadoop 18:04:18 does someone want to own #15828 and #15832 ? 18:04:53 hellais: did greenhost offer any resources? 18:05:21 (or OTF?) 18:05:32 i vaguely recall they were collaborating 18:06:16 aagbsn: they don't offer big data solutions 18:06:27 at least they don't advertise them and I don't think they have anybody expert in that field 18:06:36 we want a solution that is as managed as possible I think 18:06:55 well, 'big data solutions' is a couple machines in some racks, right ;)? 18:07:04 the nice thing of all these cloud type providers is that you can go to a graphical dashboard and click the resize bar to scale 18:07:13 and you don't have to edit any code or anything 18:07:34 i would hope that hadoop or w/e isn't so cumbersome to use that we cant add a new node easily 18:09:05 well there is a little bit of things to tweak there 18:09:13 and it's much better to have a manager for it 18:09:20 there are also free software solutions for that 18:09:32 but really, do we want to be doing maintainance on this stuff? 18:09:49 i have reached out to a few friends who may be able to help us with this task 18:09:59 who do this sort of thing professionally 18:10:06 so lets get feedbck from them and see what we think 18:10:11 ok 18:10:27 well I will continue doing work on this and seeing if I can get the pipeline running in hadoop 18:10:46 if the maintainence wasn't massive and we had the boxes, i can supply free rack space, electricity and and gig/gig internet if finding a place is a problem 18:10:48 I will help with this task, I am quite interested in this aspect as well 18:11:25 it would be ideal if a provider or donor could supply this infrastructure 18:12:57 I am against a solution where we have our own machines to maintain 18:13:14 especially if that means that I have to do all the sysadmin work to maintain it 18:13:27 that is why I think the cloud solution is advantageous 18:13:48 I am open to that solution so long as the underlying components are open source 18:14:02 they arew 18:14:02 and the cost estimates are reasonable for the resources provided 18:14:06 * irl agrees with aagbsn 18:14:28 I don't know about the later 18:14:36 free is good, but we should be able to migrate if a donor isn't able to continue 18:14:43 but that's why I am looking into this sponsorship opportunities 18:14:58 well the technologies that would be used are: 18:15:14 i'd be concerned if one sponsor pulling out would cause the system to vanish 18:15:23 hadoop (HDFS), HBase and/or elasticsearch, luigi, all of which are free software 18:16:02 irl: well it's important to always have an offline backup and design it so that it's simple to restore from the offline backup 18:16:19 yep 18:16:32 should we defer this discussion and proceed with any other items? 18:16:40 anyways if you consider the amount of stuff that these cloud platforms automate for you, the cost is really low compared to bare metal 18:16:47 aagbsn: yeah sure 18:17:23 if anyone feels like working on the above tasks, please comment or add yourself to the ticket 18:18:28 perhaps we can schedule a meeting later this week to collaborate on #15828 18:18:33 poly: are you still here? 18:18:48 (the hackfest announcement text) 18:18:59 poly: would you like to say something about what you have been hacking on these days? 18:19:19 aagbsn: yes, let's do something ad-hoc perhaps with voice support on the hackathon stuff tomorrow 18:19:35 tomorrow is ok, wednesday might be better for me 18:20:05 aagbsn: tomorrow would be ideal, since we don't have much time 18:20:12 or later today even 18:20:23 Lunar^, irl: any idea what "ooniprobe 1.2.2-1 MIGRATED to testing" means? 18:20:36 jessie was just released (yesterday) 18:20:39 it's from the "Debian testing watch" 18:20:47 hellais: both days are good for me 18:20:49 which means that uploads are now migrating from unstable into the new testing distribution 18:20:54 freeze is over 18:20:57 ah nice 18:21:00 i have questions for you regarding this hellais 18:21:03 so we should get that package cracking 18:21:04 when we get to that 18:21:15 * poly is here 18:21:20 poly can go first 18:21:28 * anadahz afk 18:21:34 thanks 18:21:46 hellais: ok we can chat a bit more tonight and lets plan on collaborating tomorrow, let's say 1600 UTC? 18:22:14 (i can also be available for discussing hackfest related things if that would be useful) 18:22:22 I've been looking at implementing a censorship analyzer for tor per https://trac.torproject.org/projects/tor/wiki/doc/OONI/censorshipwiki/TorCensorshipAnalyzer 18:22:27 aagbsn: can we do it earlier? Like 14-15 CEST? 18:22:43 isn't that the same? 18:22:48 I was thinking 1400 CEST 18:23:21 aagbsn: 16:00 UTC is 18:00 CEST. 18:23:21 I'm a bit new to the OONI thing, but so far I've implemented a parser for the directory authority list 18:23:31 hellais: oops tz fail. yes. 18:24:02 poly: do you have the link to the screenshots? I think that explains what you are doing quite well. 18:24:29 right here: 18:24:31 https://trac.torproject.org/projects/tor/attachment/wiki/doc/OONI/censorshipwiki/TorCensorshipAnalyzer/1.png 18:24:36 https://trac.torproject.org/projects/tor/attachment/wiki/doc/OONI/censorshipwiki/TorCensorshipAnalyzer/2.png 18:24:43 https://trac.torproject.org/projects/tor/attachment/wiki/doc/OONI/censorshipwiki/TorCensorshipAnalyzer/3.png 18:24:46 https://trac.torproject.org/projects/tor/attachment/wiki/doc/OONI/censorshipwiki/TorCensorshipAnalyzer/4.png 18:24:55 excellent 18:25:06 (all inkscape mockups) 18:25:29 poly: awesome! 18:26:12 currently working on the first part, which is diagnosing the connection to the tor directory authorities 18:27:02 hellais also mentioned that I could contribute to this (https://github.com/TheTorProject/ooni-probe/blob/master/docs/source/tutorial.rst) while implementing some of my tests since they are quite similiar 18:27:37 yes and also see if the writing_tests document makes sense to you and if not how to improve it 18:28:45 I just wanted to say thanks to everyone (and hellais in particular) for being so nice and helpful towards a noobie 18:29:10 hellais is indeed lovely 18:29:42 poly: :) 18:30:30 poly: also if you think it's ok to do so, I would send an email to ooni-dev about that interesting filtering equipment discovery 18:30:42 maybe somebody has seen it before 18:31:33 also if you could pastebin the ooni report for ooniprobe blocking/http_requests -u http://www.torproject.org/ 18:31:45 hellais: poly in which country? 18:31:53 anadahz: UAE 18:32:19 hellais: think it's safe to submit to ooni-dev@? 18:32:55 poly: that's a very fine question indeed and I don't think I have the definitive answer 18:32:55 poly: did you collect the reports by yourself? 18:33:11 I don't know if how aggressive they are towards these sorts of things 18:33:29 anadahz: yup. I just noticed my ISP changed filtering equipment 18:33:30 probably the risk is very low, but I don't really know 18:33:41 they're using a local made solution instead of the bluecoat stuff 18:34:02 hellais: I don't think they're agressive about it, no 18:34:13 but I'll do my research first 18:35:08 ok, some lawyers are looking into the legal situation of running ooniprobe in UAE and I can give you their memo when they are done 18:35:31 do you have my email? 18:35:48 I don't think so. Send it to me on jabber. 18:36:14 #help 18:36:33 done 18:36:59 cool 18:37:06 so it looks like we are quite overtime 18:37:07 re: https://trac.torproject.org/projects/tor/attachment/wiki/doc/OONI/censorshipwiki/TorCensorshipAnalyzer/3.png I think it would be good to b ea bit more explicit about what is going on at each level of the slider 18:37:25 irl: what was your thing? 18:37:47 so, i was wondering about translations and whether you'd made progress there. 18:38:06 i was thinking i might do the first set via debian and do updates via external people if that would speed it up. 18:38:09 irl: no I didn't manage to do any progress there 18:38:12 turnaround will be 12 days via debian. 18:38:22 ah that is pretty good 18:38:36 it is. those teams need more credit. 18:38:39 well if I am blocking you I can't guarantee that I will manage to tend to it before 12 days 18:38:48 ok, i'll get that done via debian then. 18:39:01 the other thing left to do is make sure failed uploads are reuploaded as part of the cron job. 18:39:08 then i believe it is ready for upload. 18:39:39 irl: I think in this first iteration we can even just avoid putting that there 18:40:06 I think that logic can be improved a bit on the ooni side and then have it be just 1 command that you run periodically 18:40:17 and it handles cleanup and such 18:40:24 hmm. ok. 18:40:27 this makes sense. 18:40:29 oh 18:40:36 does ooni detect whether or not there's a network connection? 18:40:43 there was a bug, but i didn't check it was closed. 18:41:06 or maybe there wasn't a bug, it's not in my history 18:41:18 irl: yes, it does and now the oonireport and oonideckgen don't hang when it's missing 18:41:26 awesome! 18:41:40 I confirm that this bug did exist 18:41:46 btw re: debian packages, are we able to depend on geoip-database-extra (the AS databases are packaged now, thanks to Patrick Matth�i 18:41:46 ok, so that's basically done then. 18:42:14 aagbsn: yes, this is something that could be done. 18:42:24 well, now you've told me it's packaged i have to do that, debian policy. 18:42:36 https://github.com/TheTorProject/ooni-probe/commit/9c2802dc85d14e9a4e03b61bbf61abfd0e88c25f 18:42:39 here it is 18:43:01 irl: oh, interesting. it is in wheezy-backports and testing/unstable 18:43:30 but not in jessie backports because that only came into existence yesterday 18:43:35 I think that means it is in jessie too? 18:43:39 < goes to look 18:44:08 yes! 18:44:15 https://packages.debian.org/jessie/geoip-database-extra 18:44:44 awesome 18:44:54 oh hm, now i am confused because that page says "Packages providing..." "geoip-database-contrib" 18:45:06 the -contrib package contains the downloader script, I think 18:45:15 hmm 18:45:20 is the database non-free? 18:45:24 https://packages.debian.org/jessie/all/geoip-database-extra/filelist though it appears to be here 18:45:43 irl: no, I wrote software to take csv formatted data and package it in the libgeoip compatible format 18:45:52 in the same manner that is done for the country-code databases, more or less 18:46:52 (I also extended blockfinder to produce compatible csv data from open data sources) https://github.com/ioerror/blockfinder 18:46:53 it looks like you can install the package or install the downloader to get more frequent updates which also provides the package 18:47:05 so dependencies work 18:47:23 although i still haven't got my head round metapackages that are also packages yet 18:47:28 we currently do something similar via ooniresources, but maxmind doesn't version these things and it is a binary format 18:48:19 https://sources.debian.net/src/geoip-database-contrib/1.8/debian/control/ 18:48:27 yep, they are conflicting and do the same thing 18:48:29 I would for the moment keep the ooniresources download strategy 18:48:43 then perhaps in the future we can use geoip-database-extra 18:48:50 hellais: where does that try to put the downloaded files? 18:48:59 but changing something so crucial like this can lead to badness 18:49:34 irl: I forget where Lunar^ set it to download it, but it's set inside of ooniprobe.conf and then ooniprobe knows where to get it locally from 18:49:35 however, ooniresources is suggested to be run as root, which is A Terrible Idea, IMO 18:50:09 nor does it get updated unless the user chooses to update it 18:50:28 well you need to be root to install a package so I don't see how this is a problem 18:50:39 whereas apt-get update will update the geoip-databases. perhaps we should work with Patrick to ensure that the packages are updated often? 18:50:52 aagbsn: it would get updated if a new version of ooniprobe is released, because it would rerun the postinstall script, I think 18:51:01 well, apt-get at least verifies the packages, and they are signed, etc, and we also provide ooni-probe updates via apt 18:51:23 it will re-run the postinstall script yes 18:51:24 I spent a fair bit of time on this as well, so I am motivated to force the change :) 18:51:25 aagbsn: we still need to use ooniresources to download the citizenlab test lists 18:51:48 this is anyways something that has caused us lot's of pain in the past and I don't think will be solved before the next ooniprobe debian release 18:51:55 ok, there are bugs here, but none that *need* to be fixed before we can do an upload 18:52:05 that is we should make it so what is well tested and we know works well is packaged ASAP 18:52:14 i could package the citizenlab test lists? 18:52:21 (in the future) 18:52:38 that would be ideal, or perhaps citizenlab would like to contribute/help? 18:52:46 irl: I think the future is for having a service that we run that you query to get your inputs 18:53:14 there is also the list of open DNS resolvers that is quite large 18:53:18 hellais: afaik all we have to do is make the debian package depend on geoip-database-extra and drop the postinstall for the geoip data 18:53:57 aagbsn: yes in future debian packages we could 18:54:27 so, is there something I should do to convince you? 18:54:31 irl: so are you or Lunar^ doing the packages? 18:54:34 ok, there are two weeks between now and the translations being finished. i'll look at testing the cron job stuff and porting the packages to ubuntu first. 18:54:56 if there's time i'll do the geoip stuff but won't include it unless i've tested it to a decent level. 18:55:03 I don't really understand this story with translatiosn 18:55:05 translations 18:55:18 hellais: Lunar^ did a lot of work, which looks good, just needs some tidying up. 18:55:35 irl: let me know how I can help you test it to a decent level ;) 18:55:36 Lunar^: it is debian policy that debconf options are translated and you give the translation teams an oppertunity to do this. 18:55:44 aagbsn: i will do this. 18:56:21 we were going to use OTF translators, but hellais has not had time to make progress there. 18:56:32 I could write a simple tool to compare the AS to /24 mappings for the maxmind and debian packaged datasets though they might not be congruent if we use say, the latest maxmind data and an older package 18:56:40 the reasoning for this is we may change the text as upadates are made from the lawyer people. 18:56:48