From e8a7ae0c974fa5114bb2da2444b0a9aa0cb9b95a Mon Sep 17 00:00:00 2001 From: dEBRUYNE-1 Date: Mon, 8 Aug 2016 20:05:57 +0200 Subject: [PATCH] Add logs for the last two dev and Kovri meetings --- ...he-Kovri-dev-meeting-held-on-2016-07-03.md | 248 ++++++++++++++++++ ...-for-the-dev-meeting-held-on-2016-07-03.md | 132 ++++++++++ ...he-Kovri-dev-meeting-held-on-2016-07-31.md | 127 +++++++++ ...-for-the-dev-meeting-held-on-2016-07-31.md | 79 ++++++ 4 files changed, 586 insertions(+) create mode 100644 _posts/2016-07-03-logs-for-the-Kovri-dev-meeting-held-on-2016-07-03.md create mode 100644 _posts/2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md create mode 100644 _posts/2016-07-31-logs-for-the-Kovri-dev-meeting-held-on-2016-07-31.md create mode 100644 _posts/2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md diff --git a/_posts/2016-07-03-logs-for-the-Kovri-dev-meeting-held-on-2016-07-03.md b/_posts/2016-07-03-logs-for-the-Kovri-dev-meeting-held-on-2016-07-03.md new file mode 100644 index 00000000..242cf07d --- /dev/null +++ b/_posts/2016-07-03-logs-for-the-Kovri-dev-meeting-held-on-2016-07-03.md @@ -0,0 +1,248 @@ +--- +layout: post +title: Logs for the Kovri Dev Meeting Held on 2016-07-03 +summary: Brief review of what has been completed since last meeting, SSU refactoring, closed and open issues +tags: [dev diaries, i2p, crypto]** +author: dEBRUYNE / fluffypony +--- + +*July 3th, 2016* + +# Logs + +**\** ok I guess we move on to Kovri - anonimal, the floor is yours +**\• fluffypony:** ding dings +**\ [anonimal]** Meeting Agenda: Sunday, July 3rd, 17:00 UTC +**\ [anonimal]** 1. Greetings +**\ [anonimal]** 2. Brief review of what's been completed since the previous meeting +**\ [anonimal]** 3. Discuss SSU: status of #140 and https://github.com/EinMByte/kovri/pull/1 (if applicable), ideas, problems, and solutions (note: ask if @EinMByte will allow issues tracking within his repo) +**\ [anonimal]** 4. Discuss commit message labeling, e.g., how to organize first line of commits. Touch-up on C4. +**\ [anonimal]** 5. Review open tickets (assigned and/or unassigned): status, code ideas (if applicable), etc. +**\ [anonimal]** 6. Discuss any pertinent TODO's +**\ [anonimal]** 7. Any additional meeting items +**\ [anonimal]** 8. Confirm next meeting date/time +**\ [anonimal]** -- 1. Greetings +**\ [anonimal]** Hi +**\** hi +**\** hi +**\ [anonimal]** I know Ein is irc2p side waiting for me to move on :) +**\ [anonimal]** 2. Brief review of what's been completed since the previous meeting +**\ [fluffypony]** I'm on this side too +**\ * anonimal** wishes this was automated. /pulse only does so much +**\ [anonimal]** 28 commits (not including merges), 2 new issues open, 0 issues closed +**\ [anonimal]** All new commits in https://github.com/einmbyte/kovri/tree/ssu +**\ [anonimal]** I ended up diving into SSU with EinMByte this week. Much fun. +**\ [anonimal]** Teamwork-teamwork: within the past hour, we had figured out that the HMAC digest impl was segfaulting because GetHeader->GetMAC() was not initialized, so the segfault is fixed for now. +**\ [anonimal]** But that's just a small portion of what's been completed since previous meeting, and more issues abound. More to discuss in 3. +**\ [anonimal]** Anyone else re: completed work since previous meeting? +**\ [fluffypony]** I've been focused on the OTF funding stuff, so I haven't had a chance to finish the website work +**\ [fluffypony]** pushing that out till the next meeting, unless we have to prepare more stuff for the OTF +**\ [anonimal]** Ok. Any new issues re: OTF? +**\ [anonimal]** Seems like they've had a few lately. +**\ [anonimal]** i.e., did we get confirmation that they received our request? +**\ [fluffypony]** no I think the next step is we'll receive a pass / fail on the concept note +**\ [fluffypony]** yes we did +**\ [_trump2016]** OTF will make kovri great again! +**\ [anonimal]** Confirmation, good. +**\ [anonimal]** Anyone freenode-side? Is xmrpromotions there? +**\ [fluffypony]** so if we receive a pass we have to prepare an actual proposal +**\ [fluffypony]** but let's see when we get there +**\ [fluffypony]** (if) +**\ [fluffypony]** they were on Reddit the other day, they seem to be busy at the moment +**\ [fluffypony]** they've asked for assistance on the gnu-social thing +**\ [anonimal]** Link? What kind of assistance? I'd be happy to help. +**\ [fluffypony]** I'll have to find it and send it to you post-meeting +**\ [anonimal]** Ok. Anything else on 2.? +**\ [fluffypony]** oh found it, nevermind: https://www.reddit.com/r/Monero/comments/4qywbx/what_are_moneros_pain_points_marketing_design/d4x34p3 +**\ [fluffypony]** nein +**\ [anonimal]** fluffypony: Thanks, I'll look into it later. +**\ [anonimal]** Moving on, +**\ [anonimal]** 3. Discuss SSU: status of #140 and https://github.com/EinMByte/kovri/pull/1 (if applicable), ideas, problems, and solutions (note: ask if @EinMByte will allow issues tracking within his repo) +**\ [anonimal]** So, https://github.com/EinMByte/kovri/pull/1 has been merged +**\ [anonimal]** EinMByte: will you allow issues tracking within your repo? It would help with this bug we're hunting. +**\ [anonimal]** Oops, old paste, we fixed the bug, +**\ [anonimal]** but are still dealing with related issues. +**\ * anonimal** knows Ein is somewhere, we were chatting elsewhere during the bitmonero meeting +**\ [EinMByte]** Hi +**\ [anonimal]** Maybe he still thinks its the previous meeting... +**\ [anonimal]** Hi +**\ [EinMByte]** Yes, I will allow all contributions to my repo +**\ [EinMByte]** Latest issue is: we are sending out broken packets +**\ [fluffypony]** issue tracking has to be explicitly enabled for the repo, EinMByte +**\ [EinMByte]** (but at least the segfault is fixed) +**\ [fluffypony]** it's a setting in github somewhere +**\ [anonimal]** ^ what fluffypony said +**\ [anonimal]** EinMByte: are we in a committable stage for the segfault fix? So I can see where we stand? +**\ [EinMByte]** anonimal: Already committed +**\ [EinMByte]** fluffypony: somewhere where +**\ [anonimal]** I imagine we're sending bogus packets in SessionRequest +**\ [fluffypony]** I'll check +**\ * anonimal** fetching +**\ [EinMByte]** fluffypony: Never mind, I think I got it +**\ [fluffypony]** if there's time, anonimal, can you please explain what SSU is for those who are observing the meeting ? +**\ [anonimal]** Ok, latest commit makes sense. +**\ [anonimal]** Yes, +**\ [anonimal]** tl;dr, in plain english, +**\ [anonimal]** it is one of two transport mechanisms closest to the IP layer: +**\ [anonimal]** NTCP is for TCP, SSU is for UDP. +**\ [anonimal]** SSU essentially takes care of encryption and negotiation with peers at the UDP level. +**\ [anonimal]** Does that make sense, or should I explain more? +**\ * anonimal** fetches link +**\ [anonimal]** Specification here: https://geti2p.net/spec/ssu +**\ [anonimal]** Overview here: https://geti2p.net/en/docs/transport/ssu +**\ [EinMByte]** In case anyone is really listening: we are rewriting the SSU implementation because +**\ [EinMByte]** 1) It doesn't allow for unit tests +**\<__uguu__>** i2p needs a better udp transport +**\ [EinMByte]** 2) The design is bad, because separate concepts are not separated in code (packet parsing was done in the same functions as dealing with networking etc) +**\ [anonimal]** X) it was an unmaintainable nightmare, like much of the codebase that we have yet to refactor. +**\ [EinMByte]** __uguu__: It probably does, so let's hope SSU2 will be better +**\ [EinMByte]** (I'm not sure what the satus on SSU2 is, AFAIK there's not even a spec yet) +**\ [anonimal]** I had some ideas/problems/solutions when working on everything this week, +**\ [anonimal]** but I need more time to flesh out tangible thought. +**\ [anonimal]** I think we're on the right track, as we discussed earlier. +**\ [EinMByte]** Ok, no problem. Maybe write everything down on github? +**\ [anonimal]** Sure, I'll comment more in #140 or open an issue in your repo. +**\ [anonimal]** Essentially, I want to take a closer look at design this week as I said I would stay away when we last spoke. +**\ [anonimal]** e.g., what we discussed earlier about MAC buffer, etc. +**\ [EinMByte]** Yes, in terms of design many things are currently undecided +**\ [EinMByte]** I've mentioned before that this is more of a refactoring than a rewrite +**\ [anonimal]** Hmm... maybe I have a different vision of end-result then. +**\ [EinMByte]** At least for now, I do want design changes in the end +**\ [EinMByte]** But I wanted to make it less crappy first, and then make it good +**\ [anonimal]** I think I need to get my hands dirty and get more intimate with your new changes. +**\ [anonimal]** I understand, as I said in #1 I completely understand and agree. +**\ * anonimal** no complaints here +**\ [anonimal]** So, long story short, I'd like to get more involved. Any objections EinMByte? +**\ [EinMByte]** Of course not, I can use all help +**\ * anonimal** could work in another branch, but I think our conflicts result in better code +**\ [anonimal]** Ok, I'll comment more in #140, etc. as things progress. +**\ [anonimal]** Anything else on 3.? +**\ [EinMByte]** Not from me +**\ * anonimal** prepares for more pasting +**\ [anonimal]** Anyone here have more SSU questions? +**\ * anonimal** will work on refining better responses to such questions +**\ [fluffypony]** no that's perfect, thanks +**\ [anonimal]** Ok, moving on +**\ [anonimal]** 4. Discuss commit message labeling, e.g., how to organize first line of commits. Touch-up on C4. +**\ [anonimal]** To preface, before discussing commit titles, none of this can really be enforced at the moment because there is no payout hanging over anyone's head. +**\ [anonimal]** But our guide does ask to reference applicable ticket numbers in commit bodies - and its incredibly helpful. +**\ [anonimal]** I'm trying to be better about doing this and I hope EinMByte would also consider doing this too. +**\ [anonimal]** It should be noted that there is no mention in the guide or C4 about commit title. +**\ [anonimal]** I've been using a rough system of prepending titles with class or aspect of project worked on. +**\ [anonimal]** It does help for quick git-log searches. Again, not enforceable, but it does help IMHO. +**\ [anonimal]** Thoughts? Objections to adding to guide? +**\ [fluffypony]** can you give me an example of the prepending? +**\ [anonimal]** Yes, one moment. +**\ [EinMByte]** anonimal: I've noticed that you tend to include a longer summary +**\ [anonimal]** fluffypony: Basically what's before the colon https://github.com/EinMByte/kovri/pull/1 +**\ [EinMByte]** I currently don't do that, but if you think it's worth it, I can start doing that +**\ [EinMByte]** Other than that, the main thing should be that it should be reasonably clear what the commit is about +**\ [fluffypony]** oh yeah that's cool +**\ [EinMByte]** But we all do that already +**\ [EinMByte]** I'm fine with stricter rules, just don't shout at me too much when I forget about them :p +**\ [fluffypony]** I tend to do short summaries too, but I like the prepending thing +**\ [anonimal]** EinMByte: I agree. If I were to ask of anything, it would be to references issues that commit addresses. +**\ [anonimal]** Other than that, I personally couldn't ask you to write longer summaries. Honestly, most of what you commit I understand anyway because its well-written IMHO - but that's just me. +**\ [anonimal]** So, as usual, I think about everyone else who isn't knee-deep in our mess. +**\ [anonimal]** And maybe longer summaries would help? +**\ [anonimal]** But 4. for me was more about commit title. +**\ [EinMByte]** Ok, I'll try to reference issues more often +**\ [fluffypony]** I don't think longer summaries are massively necessary as long as the commits show the route taken to get there, referencing issues is definitely helpful +**\ [EinMByte]** (not in the title, though) +**\ [anonimal]** Ok. So shall we take a vote on adding 'prepend class or project aspect into title of commit' into contributing guide? +**\ [anonimal]** (again, at this time not enforceable - just helpful) +**\ [fluffypony]** I'm fine with it +**\ [anonimal]** + me = 2 yes. Anyone else? +**\ [anonimal]** As fluffypony pointed out long ago, its not like anyone reads contributing guides anyway ;) +**\ [fluffypony]** hah hah yeah +**\ [EinMByte]** Sure +**\ [fluffypony]** but at least it's there and we can encourage it +**\ [EinMByte]** ^ +**\ [anonimal]** Ok, good point on the encouragement. +**\ [fluffypony]** hey - we managed to get most Monero contributors to GPG sign commits, so it is doable :) +**\ [anonimal]** Great, done. +**\ [anonimal]** While we're on 4., this is off-the-cuff, +**\ [anonimal]** but bitmonero is working with only 1 branch now. +**\ [anonimal]** And, C4 kind of dictates that (IIRC). +**\ [anonimal]** So, do we scrap branch development and work solely in master? +**\ [fluffypony]** note that we have a use-case for moving back to the dev branch setup, because people just pull and compile +**\ [anonimal]** I've also used arguments for two branches. I'm curious to hear EinMByte's opinion. +**\ * anonimal** sigh, I2P lag +**\ * anonimal** doesn't want to move on yet, running out of time though +**\ [EinMByte]** anonimal: Not sure, I think it's good to have a stable branch +**\ [EinMByte]** also, it doesn't hurt anyone? (I think) +**\ [anonimal]** The argument is to instead warn users that anything that is built outside of a tagged version is... well, unpredictable. +**\ [anonimal]** But, since we don't have any releases yet... +**\ [EinMByte]** There's "unpredictable" and there's "possibly broken" +**\ [EinMByte]** In my opinion those are not really the same +**\ [anonimal]** Good point. I imagine though that broken branches would stay in forks and then, when fleshed out, could be sent to 1 branch master. +**\ [anonimal]** But then that would require more work maintainer-side. +**\ [anonimal]** Ay, too many options. +**\ [anonimal]** I vote to keep two branches for now. +**\ [anonimal]** Yea or Nay? +**\ [EinMByte]** ok, let's keep the branches and move on :) +**\ [anonimal]** Ok, moving on. +**\ [anonimal]** 5. Review open tickets (assigned and/or unassigned): status, code ideas (if applicable), etc. +**\ [anonimal]** My hands have been tied to SSU as we've discussed. I did hack a fix for the massive leak in #191. +**\ [anonimal]** It appears to be related to LogPrint and possibly GetFormattedSessionInfo(). I need more time with it and to produce a smoother fix. +**\ [anonimal]** But it doesn't address a few smaller leaks related to #191. +**\ [anonimal]** So, between now and next meeting, I'm somewhat sure I'll focus on SSU, #191, and getting a windows build in working order. +**\ [anonimal]** And in that order. +**\ [EinMByte]** Ok +**\ [anonimal]** *but* I also may start drafting a FFS proposal for a chunk of that time (I said I would last meeting). We'll see. +**\ [fluffypony]** +1, FFS proposals are welcome +**\ [anonimal]** EinMByte: do you think you'll be around sometime this coming week or the following week? Or are weekends better? +**\ [anonimal]** fluffypony: would you please refresh my memory on the zoho/fastmail decision (my brain is scattered at the moment)? +**\ [EinMByte]** I'll be around a few hours a day, but more actively in weekends +**\ [fluffypony]** started the process a few days ago, we're doing Zoho +**\ [anonimal]** EinMByte: sounds great. +**\ [anonimal]** fluffypony: sounds great. +**\ [anonimal]** Many great sounds! +**\ [fluffypony]** everyone can independently forward their mails to tutanota or i2pmail, or just use the Zoho mailbox +**\ [anonimal]** I'm looking forward to zoho's /projects, especially time-management. +**\ [anonimal]** Kimai is a horrid *#()*@#)$@#$#@ +**\ [anonimal]** If anyone has experience using it... +**\ [fluffypony]** never heard of it, will take a look +**\ [fluffypony]** or not if it's horrible +**\ * anonimal** surprised at the lack of free, personal, opensource, time-management/billable hours solutions out there +**\ [fluffypony]** MS Project +**\ [anonimal]** IMHO you should, it may be humorous. +**\ [fluffypony]** :-P +**\ [anonimal]** I can't knock their work though, I applaud what they're doing, I just wish I had more time to contribute to their project. +**\ [fluffypony]** is it meeting.end time? +**\ [anonimal]** Eek, one more thing. +**\ * anonimal** one more paste coming +**\ [anonimal]** 6. Discuss any pertinent TODO's +**\ [anonimal]** In SSU: we're closer to resolving #119 with our new design. I've noted a few spots of missing implementation that I think will be resolved during the refactor. +**\ [anonimal]** I had mentioned in the most recent PR my interest in more sanity tests, and EinMByte did note a few overflow checks. +**\ [anonimal]** I think we're still discussing design though, so that would come a little later. +**\ [anonimal]** Thoughts? +**\ [EinMByte]** Yes, we have many places where we need more checks +**\ [EinMByte]** at least we won't leak if we throw errors etc due smart pointer usage +**\ [EinMByte]** Eventually I want to rely on exception for error handling, and I want to use the error information for peer profiling +**\ [anonimal]** Ooooooooooooooo, I like that...... +**\ [anonimal]** I like that ALOT. +**\ [anonimal]** Yes, smart pointers: something the previous project had very little interest in; +**\ [anonimal]** despite the standard having been out for years. +**\ [anonimal]** Anyway, I won't start bashing as we're out of time (I love a good bashing). +**\ [anonimal]** Anything else on 6.? +**\ [anonimal]** If not, then 7.? +**\ [fluffypony]** nothing else from my side +**\ [fluffypony]** next meeting same time, same place, two weeks? +**\ [anonimal]** Works for me. +**\ [EinMByte]** Should be fine +**\ [fluffypony]** sehr gut +**\ [zzz]** will we see any kovri ppl at HOPE in 3 weeks? +**\ [fluffypony]** zzz: unfortunately not me, need to do no travelling for a little bit +**\ [fluffypony]** got too much work to do, lol +**\ [EinMByte]** not me either +**\ [anonimal]** I had planned late last year but things took a completely different turn so, nope, not this time around. +**\ [zzz]** ok, I believe echelon still has a ticket to sell, if anybody needs it +**\ [anonimal]** Thanks zzz. That echelon, quite the organizer :) +**\ [anonimal]** Anything else? Meeting? +**\ [anonimal]** I want to also thank fluffypony and dEBRUYNE and anyone else for their work on getting these logs up on the site. +**\ [fluffypony]** it's mostly dEBRUYNE, I just add spaces in at the end +**\ [anonimal]** lol, nice. +**\ [anonimal]** Ok, thanks everyone for the great meeting. +**\ [fluffypony]** thanks everyone +**\ [fluffypony]** meeting-bot going offline \ No newline at end of file diff --git a/_posts/2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md b/_posts/2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md new file mode 100644 index 00000000..3c02967a --- /dev/null +++ b/_posts/2016-07-03-overview-and-logs-for-the-dev-meeting-held-on-2016-07-03.md @@ -0,0 +1,132 @@ +--- +layout: post +title: Overview and Logs for the Dev Meeting Held on 2016-07-03 +summary: OTF, open PRs and issues, and brief update on Ring CT +tags: [dev diaries, core, crypto, 0mq] +author: dEBRUYNE / fluffypony +--- + +*July 3th, 2016* + +# Overview (by Aerbax) + +An overview [can be found on Hello Monero](https://hellomonero.com/article/monero-bi-weekly-dev-meeting-note-highlights-2016-07-03) + +# Logs + +**\** time for meeting to start +**\** ok +**\** Ok +**\** ArticMine / othe / smooth / NoodleDoodle / moneromooo / tewinget / dEBRUYNE / gingeropolous / etc. +**\** somewhat here +**\** ok +**\** welcome to the 75th annual hunger games +**\** ok so +**\** first things first, small administrative update +**\** we've re-applied for funding from the OTF, but for Kovri (given their previous response) +**\** it's the start of the process, but who knows, maybe we have a bit of funding to work on both +**\** as Monero represents an example integration +**\** then the open issues are creeping up, there are a bunch I'm going to be closing as solved +**\** #754 is an interesting onw +**\** *one +**\** https://github.com/monero-project/bitmonero/issues/754 +**\** We don't care now, since rct. +**\** good point +**\** ok so then it can be closed as wontfix +**\** Well, it's fixed, by transfer_new. +**\** yes +**\** so +**\** I'd like to reopen the discussion of deprecating transfer and replacing it with transfer_new +**\** or is that pointless because rct +**\** I've done that in the rct branch. +**\** ok great +**\** perfect +**\** then binary renames are on hold until the rct PR +**\** because I don't want to make that implode +**\** what renames? +**\** I don't think this would conflict much, if at all. +**\** bitmonerod --> monero and stuff like that prolly +**\** hyc: https://github.com/monero-project/bitmonero/issues/80 +**\** this in particular: https://github.com/monero-project/bitmonero/issues/80#issuecomment-223596750 +**\** ah +**\** moneromooo: do you want me to PR changes to your branch then? will save you a rebase? +**\** Sure. +**\** ok great +**\** Would rct be merged before the wallet2_api stuff then ? +**\** so that's the next thing for discussion +**\** the massive wallet2 PR +**\** it's rebased against master now +**\** moneromooo: what are your thoughts on merging before or after ? +**\** I don't really have one. +**\** Maybe merge Ilya's first, since there's not going to be much review/fixes anyway. +**\** ok +**\** so wallet2 a buncha stuff specifically designed for GUI? +**\** wallet2_api is. +**\** there's also been a fair amount of review on that PR because it's so hefty - is everyone comfortable that major issues (especially in git history) have been resolved and it can be merged? +**\** Depends on how high you put the bar. +**\** moneromooo: it's low - we can open issues to fix stuff after the merge +**\** But assuming the GPL code is gone, I think it's ok. It can be changed later. +**\** oh the GPL cmake stuff, I'll check on that +**\** looks like there's a BSD licensed replacement now +**\** I saw the comment, I did not look at the new code. +**\** hokay +**\** then there are a bunch of new PRs if anyone wants to take a glance at them +**\** #878, #879, #882, #883, #884, #885 +**\** they're mostly small +**\** I need someone to check mine (885, just a readme change) before merging plx +**\** huh i only see up to 881 +**\** oh PRs not issues +**\** I seem to have reviewed all these, except the windows packages one which I have no clue about. +**\** it compiled successfully +**\** couple of weird complaints about deprecations at the end +**\** C:/msys64/mingw64/include/boost/type_traits/detail/template_arity_spec.hpp:13:84: note: #pragma message: NOTE: Use of this header (template_arity_spec.hpp) is deprecated +**\** # pragma message("NOTE: Use of this header (template_arity_spec.hpp) is deprecated") +**\** +**\** I've been getting that on most builds now +**\** boost 1.60 +**\** ah +**\** boost, sigh. +**\** not sure what there is to do about that since it's an internal header file, not one thata we explicitly include +**\** http://permalink.gmane.org/gmane.comp.lib.boost.devel/264164 +**\** fixed in 1.61 +**\** ok +**\** ok so +**\** general update-y time +**\** tewinget doesn't seem to be around, he can update us on 0MQ when he is +**\** moneromooo: how goes ringct? +**\** I'm kinda blocked today, so I didn't do much. +**\** I mean in the last two weeks since the last meeting, lol +**\** Both that watch only thing that nobody wants to talk about, and waiting for shen's sybil resistant upgrade. +**\** kk +**\** Well, last two weeks, more tests, fixes, sweep_all now uses rct, and better output selection (for the general case). +**\** does rct let us do watch only with both deposits and withdrawals? +**\** No. +**\** this sorta bounces back to the MRL, so we wait for feedback +**\** hyc: are you doing anything interesting at the moment? +**\** not really. I still need to come up with a fix for txn_full on 32bit +**\** I'm traveling most of the the rest of this month +**\** so not much hacking time +**\** cool beans +**\** ok - anything else from anyone else? +**\** Hi +**\** :-) +**\** If anyone wants to start reviewing the rct-rptest branch, I don't think it's going to change again (save new commits). +**\** Like, find how to pwn it. +**\** oh luigi1112 I forgot to tag you at the beginning, apologies +**\** Would be a good job for Heuristic, except there's no picture of hte code... +**\** Oh, some other dev related thing: luigi1112, any news on the change to signing something from a standard address ? :) +**\** Nah I've been reading but don't have any time to participate atm +**\** Oops :-) +**\** Still soon +**\** you forgot the tm +**\** it's not soon if it's not tm +**\** Well it should be this week or next :-) +**\** ok I think that brings the meeting to a close - Kovri meeting is only in 23 minutes, so feel free to add / discuss new things and it'll be in the log +**\** i got nothing, catch y'all next time +**\** any new thoughts on the auto fee thing? +**\** id like to bring up the most imporant issue, fluffypony -- free XMR for me +**\** gingah: auto fee? +**\** The thing ArticMine was looking at - scaling fees based on... stuff. +**\** Setting fees based on the blocksize +**\** and the reward penalty +**\** One also has to look at optimizing what transactions miners will accept vs block penalty and fees paid diff --git a/_posts/2016-07-31-logs-for-the-Kovri-dev-meeting-held-on-2016-07-31.md b/_posts/2016-07-31-logs-for-the-Kovri-dev-meeting-held-on-2016-07-31.md new file mode 100644 index 00000000..d01436a3 --- /dev/null +++ b/_posts/2016-07-31-logs-for-the-Kovri-dev-meeting-held-on-2016-07-31.md @@ -0,0 +1,127 @@ +--- +layout: post +title: Logs for the Kovri Dev Meeting Held on 2016-07-31 +summary: Brief review of what has been completed since last meeting, and Kovri Logo +tags: [dev diaries, i2p, crypto]** +author: dEBRUYNE / fluffypony +--- + +*July 31th, 2016* + +# Logs + +**\** ping fluffypony we missed you in #monero-dev +**\** I'll proceed with the meeting as planned but the bulk of the agenda is picking on your assigned issues. +**\** https://github.com/monero-project/kovri/issues/216 +**\** Meeting Agenda: Sunday, July 31st, 17:00 UTC +**\** 1. Greetings +**\** 2. Brief review of what's been completed since the previous meeting +**\** 3. Discuss Kovri logo +**\** 4. Closing #271 +**\** 5. Closing #226 +**\** 6. Closing #105 +**\** 7. Closing #46 +**\** 8. Closing #27 +**\** 9. Any additional meeting items +**\** 10. Confirm next meeting date/time +**\** Hi. +**\ {-needmoney90}** * walks into the room and sits in the nearest available seat +**\ {-needmoney90}** Just watching for today +**\** Is anyone freenode side? This meeting is not being relayed to #monero-dev. I'll hop onto slack to see if the relay is working. +**\ {-_Slack} ** It appears so +**\ {-_Slack} ** I2P, Slack, and IRC are all relaying +**\** K, thanks. +**\** Onto point 2. +**\** $ git log --no-merges --pretty=oneline --since=1.month | wc -l +**\** 72 +**\** Code highlights include: +**\** - Mem leak fixes +**\** - New constant-time comparison for ed25519 +**\** - Two new contributors: moneromooo and rakhimov +**\** (hopefully will see more from both devs) +**\** - regex fix, clang fixes +**\** - A whole lot of build/repo work +**\** - We officially build with clang +**\** - We officially build on OSX again +**\** - Two new submodules: cpp-netlib, cryptopp +**\** - New URI parsing implementation courtesy of cpp-netlib +**\** - New clang-format config (still in development) +**\** - Updated style guide + building instructions + docs +**\** - Upstream bug hunting/fixing (huge time-suck) +**\** - Coverity's website finally works (for me) +**\** - Misc fixes, enhancements +**\** Project highlights include: +**\** - Kovri End-User Documentation Proposal - #256 +**\** - 9 new opened issues, 7 new closed issues +**\** - Creation of @kovri@quitter.se +**\** - I've also spent some time with bitmonero/monero-project +**\** That's all from me for 2. Anyone else? +**\** Ok, guess not. +**\** fluffypony fluffypony fluffypony fluffypony +**\ {-needmoney90}** * summons fluffypony from the depths +**\** 2nd meeting in a row he's missed. I hope he's alive. +**\ {-needmoney90}** D: +**\** I know this is opensource and volunteer but I'm getting a bit irritated. +**\** Being stood up is not very respectful. +**\ {-needmoney90}** oh he isnt in this room +**\ {-needmoney90}** summoning wont work from here +**\** lol needmoney90 +**\ {-needmoney90}** He isn’t even on IRC it seems +**\ {-needmoney90}** hm +**\ {-needmoney90}** thats strange, Im used to him being always on/ide +**\ {-needmoney90}** idle +**\** He's on irc2p side. +**\** Is dEBRUYNE on freenode side? Is this meeting even being logged? +**\ {-needmoney90}** Well, Slack is certainly logging it +**\ {-needmoney90}** and my client possibly is +**\ {-needmoney90}** havent checked logging settings +**\** so is my client +**\** Ok. +**\** Moving on to 3. +**\** "Discuss Kovri logo" +**\** Who did Monero's logo? +**\• anonimal:** asked in #monero-dev, no response +**\** Any thoughts on a logo for Kovri? +**\** How about a nude porn star holding a letter 'K'? +**\ {-needmoney90}** I've been thinking about it +**\ {-needmoney90}** and….I don’t think that will get us corporate/mainstream usage +**\ {-needmoney90}** then again, maybe it will +**\ {-needmoney90}** keep it on the backburner +**\** lol +**\• anonimal:** was joking +**\ {-needmoney90}** I’ve been thinking some kind of K made of nodes (like the Ethereum Classic logo), but fading out on half +**\ {-needmoney90}** though its probably too complex +**\ {-needmoney90}** https://camo.githubusercontent.com/eec95efca3ae789116e4557656898ab52ca74cba/687474703a2f2f63646e2d696d616765732d312e6d656469756d2e636f6d2f6d61782f3830302f312a6e4955617a775f75334b436843583839664c674c44672e706e67 +**\** Sounds cool. +**\** DaveyJones pointed this out https://99designs.de/logo-design/contests/monero-mro-cryptocurrency-logo-design-contest-382486 +**\** needmoney90: could that url get any longer?... +**\** Ah, I see. Interesting idea needmoney90 +**\** Maybe we should hold a contest and reward the winner with XMR? +**\ {-needmoney90}** Sorry about the URL length, I copypasta’d without minifying +**\** Np. +**\** Where would be a good place to host a Kovri logo contest? +**\** (XMR friendly place) +**\** I'll open a ticket and we can deal with it later +**\** Points 4-8 are all fluffypony +**\** 9. Any addition meeting items +**\ {-needmoney90}** None here +**\** EinMByte is MIA. SSU still not finished. From what I've worked on, debugging the rest to get it merged will require motivation on my part. +**\ {-needmoney90}** SSU? +**\** No shows at meetings + no pay != motivation for me to do lifting beyond what I'm doing. +**\• anonimal:** grabs link for needmoney90 +**\** needmoney90: #140 +**\ {-needmoney90}** tanks +**\** I'll make myself available for the next 30 minutes and then paste a link to the meeting log in #216 +**\ {-needmoney90}** I’m really curious where fluffy got off to.. +**\** We were chatting about an hour before monero's meeting was supposed to start +**\** Maybe he simply forget. This has happened several times in the past. +**\ {-needmoney90}** :( +**\ {-_Slack} ** needmoney90: is there a way to easily export channel logs here? +**\ {-_Slack} ** hrmmm +**\ {-_Slack} ** I just exported +**\ {-_Slack} ** should have the logs (from all channels) in my email soon +**\ {-_Slack} ** barring that, someone's IRC client logs will work +**\ {-_Slack} ** Nice. Would it be easy to fpaste a private paste of just our meeting? e.g., do they do any formatting or just lump everything into an email? +**\ {-_Slack} ** no idea +**\ {-_Slack} ** ill let you know +**\ {-_Slack} ** Thanks. For the time being I'll just do a quick format of my logs to takeout timestamps and paste the meeting. \ No newline at end of file diff --git a/_posts/2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md b/_posts/2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md new file mode 100644 index 00000000..e254c50f --- /dev/null +++ b/_posts/2016-07-31-overview-and-logs-for-the-dev-meeting-held-on-2016-07-31.md @@ -0,0 +1,79 @@ +--- +layout: post +title: Overview and Logs for the Dev Meeting Held on 2016-07-31 +summary: Monero Project repository, and brief update on Ring CT +tags: [dev diaries, core, crypto, 0mq] +author: dEBRUYNE / fluffypony +--- + +*July 31th, 2016* + +# Overview + +- + +# Logs + +**\** time for meeting to start +**\ {-anonimal}** Are we not having a meeting? +**\** I was wondering the same thing +**\ {-anonimal}** Kovri meeting at 17:00. I thought we were meeting at 16:00. +**\ {-anonimal}** fluffypony: ^ +**\** For Monero +**\ {-anonimal}** Yes +**\ {-anonimal}** * disappointed +**\** Maybe he died +**\** We could meet without him if people have stuff to say :-) +**\** Well, I have one thing to say: who wants to join the testnet and try random stuff to see if they can get it to break ? +**\** Preferably corner cases. +**\** How many testnet nodes are there? +**\** I think three. +**\ {-anonimal}** I would but I don't have a reliable VPS at the moment. +**\** I can set at testnet node. What are the stiings +**\** settings +**\** bitmonerod --add-exclusive-node 176.9.17.19:28080 --testnet +**\** And you need to have built with my rct-private-fork branch. +**\** And make sure you backup your db and wallet first, as they won't be compatible with "normal" version once you run rct code. +**\** https://github.com/moneromooo-monero/bitmonero/tree/rct-private-fork is the branch to use. +**\** Actually, use https://github.com/moneromooo-monero/bitmonero/commit/58ea23fa144b9eaec506461f96649d0c7b4b3914 +**\** Latest has an incompatible comms change. +**\** Great I will give this a try. Is there a test net db or sync from scratch +**\** If you don't have a testnet db already, you will have to sync. +**\ {-anonimal}** #903 has gotten some momentum. Is it too soon to come to an agreement? +**\** Can't hurt I think. +**\ {-anonimal}** So we need a name. moneromooo any thoughts? +**\<_Slack> ** Bond. James Bond. +**\** I've seen two names proposed already. I don't have a better idea. +**\<_Slack> ** (What are we naming again?) +**\** A repo, AFAICT. +**\ {-anonimal}** neemoney90: #903 +**\<_Slack> ** Repo-y McRepoface +**\ {-anonimal}** luigi1112 any thoughts? +**\ {-anonimal}** ArcticMine ^ +**\<_Slack> ** My thoughts submitted +**\** monero-organization for #903 +**\** That sounds good. +**\ {-anonimal}** Ooo, I like that best. +**\ {-anonimal}** ArcticMine will you comment in issue or I can copy/paste? +**\** You can copy past, I may comment. +**\** copy/paste +**\ {-anonimal}** K, done. I also like monero-project/organization. +**\** That is also good +**\ {-anonimal}** Kovri end-user documentation proposal is in open tasks +**\** Actually better than my original idea +**\ {-anonimal}** https://forum.getmonero.org/7/open-tasks/2592/create-end-user-kovri-documentation +**\ {-anonimal}** The problem with the forum is that its somewhat obscure and I don't get emailed notifications. +**\ {-anonimal}** So obscurity = less funding. No notifications = more babysitting. +**\ {-anonimal}** An org repo can help with things like this, imho. +**\** maybe monero-project/org +**\** org can be confused with .org Just a thought +**\ {-anonimal}** Agreed. How about https://github.com/monero-project/community +**\ {-anonimal}** Or is that too vague? +**\** I thing community is too broad. +**\ {-anonimal}** Kovri meeting in 3 minutes. +**\ {-anonimal}** I'm hopping over to #kovri-dev +**\ {-anonimal}** I wish the relay bot was online. +**\** One could say organizational +**\ {-anonimal}** I would say have it here but I don't know who is freenode side. +**\ {-anonimal}** If anyone is interested in talking about a logo for Kovri, could you please hop over to #kovri-dev? +**\ {-anonimal}** I don't know if dEBRUYNE is logging our meeting so I or slack will be taking care of it.