--- layout: post title: Logs for the Kovri Dev Meeting Held on 2017-07-09 summary: Brief review of what has been completed since last meeting, discussion of meta issues, and code & open tickets discussion tags: [dev diaries, i2p, crypto] author: dEBRUYNE / fluffypony --- *July 10th, 2017* # Logs **\** 1. Greetings **\** 2. Brief review of what's been completed since the previous meeting **\** 3. Contributor FFS check-in / status **\** 4. Open Meta issue review https://github.com/monero-project/meta/issues **\** 5. Code + ticket discussion / Q & A **\** 6. Any additional meeting items **\** 7. Confirm next meeting date/time **\** Hello! :) **\** hi **\** Yo **\** hi **\** Hi MoroccanMalinois rehrar ArticMine **\** fluffypony too? **\ {-fluffypony}** yes **\** Hi fluffypony **\** 2. Brief review of what's been completed since the previous meeting **\** On my end: testnet development and related collab with MoroccanMalinois and lazygravy + SSU/Ident collab/PR review with MoroccanMalinois (and related research/development), rehrar collab for his site related work, some collab with serhack/ericcion Italian translations for kovri-site, email + PR collab + R&D with rbrunner on the windows InnoSetup installers, Monero project work (monero svn to git for **\** unbound), work with pigeons on setting up kovri.i2p (now online!), answer various IRC/reddit Q&A + related collab. **\** This past week was launching the Monero website. Now that's basically done. **\** Some various things here and there, I2P/Tor family node research and more. **\** Some French + Russian kovri-site translations are in the works, they are in the PR pit. **\** Same with kovri repo, I have yet to review the new MM PR's. **\** Did we miss anything else? **\** 3. Contributor FFS check-in / status **\** I'm here, checked-in! MoroccanMalinois is here. Yay! **\** i will be ok with a milestone in next meeting if last PR's get merged :) **\** Excellent, I'm sure they will. **\** re: FFS check-in, MoroccanMalinois is doing great. I can't review myself, anyone else on point 3.? **\** Well, I *can* review myself, but that wouldn't be fair now would it? ;) **\** lol **\ {-fluffypony}** lol **\ {-fluffypony}** leave it to the community to review **\** With the exception of this intermittent week, point 2 shows that I've been active and busy, that I can say the least. **\** Alright, moving on. 4. Open Meta issue review https://github.com/monero-project/meta/issues **\** Starting from the top down, #80 **\** rehrar, any news on that front? **\** #77 and #78, fluffypony what do you think? **\ {-fluffypony}** checking **\** Sorry. Afk 2 min **\ {-fluffypony}** what's a topic **\ {-fluffypony}** lol **\ {-fluffypony}** anonimal: won't web hooks for -site and -docs be too distracting? **\** This week is all Kovri for me. **\** I'll be writing the brief tomorrow and presenting it **\** fluffypony: well, not for me: it would be helpful because of the sometimes very large notification lists I get in github. **\** I'll also be importing the tech from the new Monero website to Kovri. That which is applicable. **\** Awesome rehrar **\** fluffypony: is it too much? **\ {-fluffypony}** I don't mind activating it, it's your call :) **\** Can we give it a trial run? **\** (e.g., do it until too many people complain) **\** Hey anonimal **\** How are you? **\** fluffypony: re: topics, quick link https://help.github.com/articles/classifying-your-repository-with-topics/ **\** Hi serhack **\ {-fluffypony}** tks **\** serhack: sono stanco, ma we can chat more after the meeting **\** On 4 there is Project licensing #85 impacts kovri **\** Oh okay **\** Was opened to get feedback **\** Kovri doesn't have to have the same license as Monero, right? **\** ArticMine: I took a quick look at that earlier this week, will look again now. **\ {-fluffypony}** rehrar not necessarily, but might be better if we did **\** kovri's library part will be used by monero at some point. **\ {-fluffypony}** I don't see a reason to have different licenses **\** BSD-3, yes I believe so. **\** re: licensing, no matter what, we'd need to adhere to the licenses of all bundled dependencies, right? **\** Yes **\** That is part of the issue in 85 **\** I2P is effectively GPL v2 **\** "I2P" ? The Java router ? **\** Yes java **\** Huh? Java I2P? **\** java makes I2P GPL v2 **\** I don't see how that applies to us as we're not using any of their code. **\** And most of the important bits are "free (adj.): unencumbered; not under the control of others", whichever license that equates to. **\** Not directly to kovri **\** Open specification is different than implementation in terms of licensing, right? **\** but that is why 5 was opened to deal with this discussion **\** 85 **\** If monero goes dual-license, then we must? **\** Not necessarily **\** Ok. I'll need more thought on this. I can add to the next agenda too. Does anyone have any strong feelings on this now? **\** I think it is best if we discuss it on Github under 85 **\** Then we can look at it in the next meeting **\** I have strong feelings to go proprietary. **\** er, we would not do that. **\** But aside from that let's move on. **\** I kid. **\** ArticMine: ok. **\** re: #63, rehrar did you figure out your git branching issue? **\** Web launch took priority. **\** We've been feverishly working on it and it is done for now. I've been reading into branches yes. **\** Sorry, also headed to Mexico atm. :/ So my replies will be intermittent. **\** Should be resolved in the next two days. **\** I haven't made any new contributions to it yet so I don't think it's done for now ;) **\** No, I meant the website **\** Working in the website and the site is done for now. **\** Ok **\** re: #46, fluffypony are we still scheduled for the 20th? **\ {-fluffypony}** I have no idea - I don't have it in my calendar, has someone checked with Shay? **\** Eek, I thought he sent an email after he posted in #46 **\* anonimal** will ping him right now **\ {-fluffypony}** tks **\** I have a feeling he may have been waiting for more responses. **\** #43, hmm **\** This week. ;) **\** First step is to nail down #80 imo **\** Because then I can start producing some material. **\** I think rehrar had thoughts on that area. Sounds like everyone is at max capacity at the moment though. **\** Ok **\** fluffypony, is #12 still applicable? **\ {-fluffypony}** checking **\ {-fluffypony}** yes - label bot took precedence **\ {-fluffypony}** but we'll pick that up after it's deployed **\** Spoke to @fluffypony, could be resolved as early as next week **\** Over one year ago. :P **\ {-fluffypony}** lol **\ {-fluffypony}** we had to choose a mail provider **\ {-fluffypony}** that took multiple face-to-face meetings **\** Oh neat, label bot is online **\** Can we give him a better name? **\ {-fluffypony}** only in meta right now **\** Oooh, where is the documentation ? **\** Oh lol, I see, rehrar quoted my kovri comment from March 16th, 2016, heh X) **\** fluffypony: so #12 is applicable but not finished? **\ {-fluffypony}** yes **\** Ok **\ {-fluffypony}** @rehrar ask pigeons **\** Will do. **\** #9 #19 #29 #30 are pigeons territory I believe. **\** Anything else on this point (meta issue review)? **\** #24 #26 #27 will be useful. ajs waits patiently on #27. We can eventually make a big move on #27 when the time comes. That should be fun. **\** Out of time, 5. Code + ticket discussion / Q & A **\** Nothing pressing at the moment aside from the open PR's which will be reviewed. **\** Anything else on 5.? **\** 6. Any additional meeting items **\** Nothing from me at the moment. ArticMine how urgent was meta #85 in terms of coming to a resolution? **\** I think we gucci. **\** I would give it at least two weeks **\** Once we see discussion / comments **\** K. Going to be crossing soon, so I'm out for now. Cya all Kovri Peeps. **\** It was promoted by a Monero dependency going to a copyleft **\** Ok **\** 7. Confirm next meeting date/time **\** Same time, two weeks from now? **\** rehrar will you be back by then? **\** It's a day trip. **\** I live like right next to the border. **\** Ill be back before my day is over, and right to work tomorrow. **\** Oh, alright, then we'll keep the usual meeting date/time. **\** Thanks everyone :) **\** thanks anonimal :)