--- layout: post title: Logs for the Kovri Dev Meeting Held on 2016-06-19 summary: Brief review of what has been completed since last meeting, C++ specific discussion, closed and open issues tags: [dev diaries, i2p, crypto] author: dEBRUYNE / fluffypony --- ### Logs **\** ok I guess we move on to Kovri - anonimal, the floor is yours **\ [anominal]** From agenda https://github.com/monero-project/kovri/issues/192 **\ [anominal]** 17:00 (UTC) **\ [anominal]** 1. Greetings **\ [anominal]** 2. Brief review of what's been completed since the previous meeting **\ [anominal]** 3. C++ specific discussion (carried over from June 5th meeting) **\ [anominal]** 4. Review open tickets (assigned and/or unassigned): status, code ideas (if applicable), etc. **\ [anominal]** 5. Discuss any pertinent TODO's **\ [anominal]** 6. Any additional meeting items **\ [anominal]** 7. Confirm next meeting date/time **\ [anominal]** 1. Greetings **\ [anominal]** Hi **\ [anominal]** EinMByte: present? **\** there's 2x greetings? **\** best meeting ever **\ [anominal]** lol **\ [anominal]** Well, EinMByte is here but not present. **\** k **\ [anominal]** Moving on, **\ [anominal]** 2. Brief review of what's been completed since the previous meeting **\ [anominal]** A somewhat productive two weeks in contrasting areas. Highlights include: **\ [anominal]** - New --log-levels runtime feature **\ [anominal]** - Security fix in Garlic/ElGamal **\ [anominal]** - New user-agent scrubber **\ [anominal]** - Bump to 0.9.26 **\ [anominal]** - Coverity coverage via travis-ci (though problematic, see #209) **\ [anominal]** - Design refactoring, misc. refactoring, code documentation **\ [anominal]** 6 closed issues **\ [anominal]** 2 new standing issues **\ [anominal]** fluffypony: have you had a chance to complete anything since previous meeting? **\** anonimal: like 80%-ish done with the Kovri page on the site, per the info you gave me + the docs **\** s/page/section **\ [anominal]** Great, I'm looking forward to it. **\ [anominal]** Do you think it will be finished before next meeting? **\** yes definitely **\ [anominal]** Yay, sounds exciting. **\ [anominal]** Anything else on 2.? **\ [anominal]** Going once... going twice... **\ [anominal]** 3. C++ specific discussion (carried over from June 5th meeting) **\ [anominal]** Well, I was hoping to merge this in with 4. and chat with EinMByte since he said he'd be here. **\** is this wrt the C++ standard ? **\** or the style guide stuff? **\ [anominal]** Anything C++, I imagined. **\ [anominal]** I was hoping to focus on C++ related to #187, but I haven't looked at #187 since it was opened. **\ [anominal]** Have any bitmonero devs taken an interest in Kovri yet? **\ [anominal]** Its quite the beast, and needs much taming. **\** I don't think anyone has yet **\** anonimal: passing interest at best for me **\ [anominal]** Ok, good to know. **\** I more or less know what it is, but I haven't looked into tinkering with it yet. **\** I think the problem is that the time I'd spend hacking on anything, I wouldn't spend on monero anymore :) **\** s'true **\ [anominal]** I totally understand. **\** there will be a bleed area between the two when integration happens **\ [anominal]** That makes, so patience and persistence seems to be the key. **\ [anominal]** \*makes sense **\ [anominal]** Well, anonymity has a certain taste too. Maybe I'm one of the few fanatics who enjoy working on it ;) **\** I think most of us are here because we're pro-privacy **\ [anominal]** Anyway, I look forward to the meeting of the minds, I like what I've seen in bitmonero dev. **\ [anominal]** Yes, good point. **\** which is awesome :) **\ [anominal]** Anything else on 3.? Any questions? **\ [anominal]** Alrighty, moving on, **\ [anominal]** 4. Review open tickets (assigned and/or unassigned): status, code ideas (if applicable), etc. **\ [anominal]** Let's see, **\** anonimal, also, if EinMbyte can't make the meeting maybe we must collate stuff and raise it on his behalf ? **\ [anominal]** How so? **\** like if he just adds to the agenda then we can discuss it without him needing to be here **\ [anominal]** Ok, well he's welcome to do that. **\ [anominal]** But he and I are great at bouncing ideas off each other and getting to core issues, so I wish he would be present more often. **\ [anominal]** I see, so we'll send him a note to add to the agenda regardless of his attending? **\** yes I think that would help, he lacks time at the moment **\ [anominal]** Ok. **\ * anonimal** back to 4. **\ [anominal]** #210 might be an easy fix, if any bitmonero devs want to take a peek. **\** once you go Kovri you never go...uh...something that rhymes with Kovri **\ [anominal]** lol **\ [anominal]** That's a tough one.... **\** https://github.com/monero-project/kovri/issues/210 <- for reference **\ [anominal]** Remaining tickets are mostly all hard-core. I'll see what I can get into before the next meeting. Obviously the big ones would be nice if I can make the time. **\ [anominal]** I may pick at #191 or #187 because I get irritated with severely broken things. **\ [anominal]** Or who knows what, the world is full of mysterious and discovery. **\** lol **\ [anominal]** *mystery **\ [anominal]** lol **\** invent a time machine ! **\ [anominal]** pffffffffff **\ [anominal]** That would be fun. **\** :-P **\ [anominal]** Does anyone here work with Debian Jessie often? **\** tewinget is an Arch user **\** moneromooo wrote his own OS from scratch I'm sure **\** osensei maybe **\** but he's not around atm **\** I use a pretty common one nowdays actually. **\ [anominal]** Ok just curious. Arch here so #210 will probably take more than a few moments. **\** moneromooo: Windows XP ? **\ [anominal]** ^ Windows 98 **\** Good point. I guess it's not that common. I forgot about windows. **\ [anominal]** 95 was better at breaking. **\ [anominal]** Ok, well re: 4., fluffypony have you see #209? **\** probably **\ [anominal]** 50% yay because we solved the coverity/travis issue! **\** oh yes the Coverity thing **\** ok so plz update me - Travis builds are now work **\** *working **\** but Coverity isn't triggering ? **\ [anominal]** No, we are \*finally\* triggering, but now coverity says build is failing on their end. **\ [anominal]** So, travis says "we're fine", coverity says "you're not fine but neither is most of my site". **\ [anominal]** Because they really do have some issues there and support is... meh. **\** LOL **\** considering how long it took for their site to pick Travis up I'm not even surprised **\** do we wait until they've fixed it, or keep pushing **\ [anominal]** Seriously, and their "community" site is still offline despite "we'll be back in early 2016!". **\ [anominal]** It's June already... **\ [anominal]** Good question, **\ [anominal]** I can review \*why\* they think our build failed, I could even try to do it manually. **\ [anominal]** I may have to do it manually just to get things going \*or\*, it could be another travis/coverity issue (or just pure coverity). **\** maybe we must switch to manual Coverity **\** and just do it once every two weeks **\ [anominal]** Sounds fair, I'll give it shot before next meeting. **\ * anonimal** before I forget, opens https://github.com/monero-project/kovri/issues/assigned/fluffypony **\ [anominal]** fluffypony: Any updates on #27? **\ * anonimal** knows you've been busy, simply curious **\** anonimal: no - also, we're switching providers **\ [anominal]** Ok. **\** debating Zoho vs. FastMail **\** ProtonMail doesn't do multiple users on a domain, unfortunately **\ [anominal]** Hmmm... **\ [anominal]** Pros/Cons so far re: providers? **\** well they're mostly doing forwarding and SMTP, so it's pretty open **\** part of the decision making is cost, part is also reliability and if they feature reasonable web interfaces for those inevitable users that don't want to use a mail client **\** will wrap that up soon, it's on my short list **\ [anominal]** Ok, good to know. **\ [anominal]** I don't have an opionion so far. If I do I'll be sure to chip in. **\ [anominal]** Is xmrpromotions there? re: #105 **\** no not online atm **\** I'll prod them for that when I see them next **\ [anominal]** K. **\ * anonimal** typing **\ [anominal]** I'll most likely take a look at bitmonero's 0MQ work too before next meeting (thinking of #53). **\ [anominal]** Other than that, I may just grab some low hanging fruit before next meeting and work on the mingw build and other smaller tickets. **\** anonimal, feel free to direct any 0mq questions at ~~fluffypony~~ me **\ [anominal]** Thanks tewinget. **\** oh yeah speaking of **\** sad that my IRC client doesn't support strikeout...hoping someone else's does **\** the Windows test box is borked **\** msys2 decided to give up the ghost **\** so doing a complete reinstall of it **\ [anominal]** Yeah, so what happened? Any idea? **\** no clue **\ [anominal]** (very strange) **\** On a scale from 1 to I hate compiling anything on Windows: I hate compiling anything on Windows. **\** it's a binary scale. **\ [anominal]** Oh windows, you never cease to disappoint me. **\ [anominal]** Anything else on 4.? **\ * anonimal** quick reviewing **\ [EinMByte]** Hi, I'm late sorry **\ [anominal]** EinMByte! Welcome back. **\** wb EinMByte **\** still 15 minutes left :) **\ [anominal]** With 15 minutes or so to spare, any input? (much backlog) **\ [EinMByte]** Something about #210 maybe: I'll provide some more information **\ [anominal]** EinMByte: before I forget and while you're here: what is your preferred/most-reliable public contact method? **\ [EinMByte]** public as in to put on a website or so, or as in where you guys can contact me **\ [anominal]** So we can contact you. **\ [anominal]** And would you be interested in leaving agenda TODO's/notes in meeting tickets in case you can't make a meeting that you'd hope to make? **\ [EinMByte]** Well I'll be on IRC, or else einmbyte@mail.i2p or github **\ [anominal]** Ok. **\ [EinMByte]** sure **\ [anominal]** fluffypony: did I word that correctly? **\ [anominal]** EinMByte: we're still on point 4. "reviewing tickets", etc. **\ [anominal]** Is there anything you wanted to add re: SSU? **\ * anonimal** knows you just got back to working on it **\** yes I think so **\ [EinMByte]** Well I can give you a quick status update **\ [anominal]** Awesome. **\ [EinMByte]** So SSUSession.cpp is now using the new parsing code, except for the fragments **\ [EinMByte]** (I have the code to parse data packets, just not using it yet) **\ [EinMByte]** I am slowed down right now due to a bug, with the header I suspect **\ [anominal]** Grrr... bugs... **\ [EinMByte]** (Rekey options being set etc when this shouldn't happen, I think it's all related) **\ [EinMByte]** Well, I'll try to fix it in the next days **\ [anominal]** bitmonero devs: FYI, SSU is the ugly High School girl standing in the corner of the dance hall that no one will dance with because she is awkward and is a very mean person. **\** lol **\ [anominal]** In other words, SSU has needed much love and I'm glad EinMByte has tackled the challenge. **\ [EinMByte]** Hah, nice comparison - although it does make me seem quite desperate :P **\ [anominal]** lol, oops. Sorry EinMByte, I didn't mean it that way :( **\ [EinMByte]** Once the parsing part is done, I'll do something similar to build the packets **\ [anominal]** Sounds great. **\ [anominal]** How about, EinMByte dances with her because he is a leader and willing to show great sympathy to those who need it most. **\ [EinMByte]** I'll write some tests, but don't expect full coverage just yet. I don't think that's a priority right now. **\ [anominal]** And turns down the more promising dancers to make SSU work well. **\ [EinMByte]** (I want to get the API started too) **\ * anonimal** sorry, I'm getting carried away **\ [anominal]** Ok. **\ [anominal]** Do you have an idea of schedule coming up? **\ [anominal]** (as in availability) **\ [EinMByte]** anonimal: You're making a lot of assumptions about my gender here :). But let's see how well that dance turns out **\ [anominal]** I know, again my apologies. **\ [EinMByte]** Yes, next week I'll be mostly available (several hours per day) **\ [anominal]** Ok. I'll check my IRC more frequently then. **\ [anominal]** Anything else on 4.? **\ [EinMByte]** Well as I said I'll put up more info for #210 **\ [anominal]** Ok. **\ [EinMByte]** Seems like 2 tests are failing **\ [anominal]** Since we're out of time, I don't see much on 5. except for a couple of quirky core ones that I may get to before next meeting. **\ [anominal]** Any comments on 5.? **\** EinMByte: well you can dance with SSUzy regardless of your gender **\ [anominal]** SSUzy, lol. **\ [EinMByte]** fluffypony: or my ability to dance :p **\** everyone can dance, it's just a matter of how badly (or well) **\ [anominal]** Paraplegics? **\ * anonimal** doesn't do off-topic very often, quite the release. **\ [anominal]** Ok so if no thoughts on 5., **\** LOL **\** nobody is going to attend the Kovri meeting in future :-P **\ [anominal]** LMAO **\ * anonimal** watches ship sailing away, burning in the distance **\ [EinMByte]** See you all next time in #dancing **\ [anominal]** Ok, last call for 5. Discuss any pertinent TODO's **\** I think that's it from my side **\** lol EinMByte **\ [anominal]** lol, or #dancing-dev **\ [EinMByte]** Well, for 5: If anyone wants to start on the API, you're welcome **\ [EinMByte]** This also applies to all (any?) monero people reading this **\ [anominal]** Good point, that's another big item to tackle. **\ [EinMByte]** Since you're going to be the people using the API, making up a list of requirements would be nice ***\** kk **\ [anominal]** 6. Any additional meeting items **\ [anominal]** Just one from me, briefly, **\** I think we've already discussed EinMByte's dancing enough, so nothing more from me on 6 **\ [anominal]** Forum Funding. I plan on writing up some proposals within the next month or so. **\** kk **\ [anominal]** EinMByte: if you were crowdfunded on FFS, would you be able to devote any more dev time? **\ [EinMByte]** I've already told fluffypony, not really **\ [anominal]** Ok. **\ [EinMByte]** If you can build me a time machine, yes **\ * anonimal** was planning proposals to fund my work **\ [anominal]** Funny, fluffypony mentioned that earlier (time machine). **\** lol **\ [anominal]** We should invest in one. The writing is on the wall. **\ [anominal]** Last call for 6. **\** new project for the Monero Research Lab to tackle **\ [EinMByte]** But, as I've also told fluffypony, please do fund other programmers **\ [anominal]** Agreed. **\ [EinMByte]** Apparently you first need the programmer (before getting the money) so let's go find some C++ programmers **\ [anominal]** fluffypony: ^ we should devote an entire meeting to that IMHO sometime within the next few months. **\** yeah definitely **\** would love to see a FFS proposal for kovri/i2p dev **\** grimpants: we've had open-ended stuff before, the funds just sit there and no dev comes along - we need to first find someone interested that can price in their work, even if it's on a full time commitment for X long **\ [EinMByte]** By the way, we don't need only expert C++ programmers **\** and then we can raise funds accordingly **\** i see **\** been a while since ive check tbh **\ [EinMByte]** We can use people who just write documentation / tests too **\ [anominal]** ^ which is a great way for newcomers to learn the codebase. **\** this may not be an honourable line of thought, but I've been wondering if there's any fall-out from the issues Tor are facing that might lead to some new contributors looking at Kovri **\ [anominal]** Good concern, I think that's very plausible. **\ [anominal]** But the devoted C person usually scoffs at C++ and turn their nose at Java. **\** like hyc :-P **\ [anominal]** I've become spoiled with STL so, I can't vouch for C devotees on more complex apps like Kovri. **\ [anominal]** But bigger point: **\ [anominal]** The world needs more options, so if Tor starts to burn, another ship will be ready. **\ [anominal]** Some great minds there, so I'm not concerned about the near future. **\ [anominal]** But that was a hefty loss on their end with the one who shall remain nameless. **\** yeah, and the larger loss is how much emotional damage it did to people during the time it was kept hidden **\** as a community I hope we can learn from that and call people out when they're out of line **\ [anominal]** Yeah, everyone involved seems to have taken a loss. **\ [anominal]** So, regarding that in relation to ship-jumpers: I think we should continue on our track of availability, professionalism, quality, code correctness and maintainability, **\** 100% **\ [anominal]** But, **\ [EinMByte]** let's first get some people :) **\ [anominal]** devs can be strong in their ways, so being malleable is also important (but that's a given). Constant ebb and flow. **\ [anominal]** Anything else on 6.? **\** that's it from my side **\ [anominal]** 7. Confirm next meeting date/time **\ [anominal]** Same time in two weeks? **\ [EinMByte]** Nothing else from me **\** yes same time in two weeks **\ [anominal]** Alright. A million thanks to everyone. **\** taking meeting-bot down