--- layout: post title: Overview and Logs for the Dev Meeting Held on 2016-05-22 summary: Clarification regarding documentation (i.e. Github wiki, consolidating information), bit on Ring CT, discussion of open PRs tags: [dev diaries, core, crypto] author: dEBRUYNE / fluffypony --- *May 22nd, 2016* # Logs **\** ok **\** das meeting **\** has started **\** heh heh **\** let the fun begin **\** hyc, smooth, moneromooo, dEBRUYNE, gingeropolous, luigi1112, luigi1114, anyone I've missed **\** hokay so **\** first up: for those that haven't done so, please commit to the StackExchange proposal: http://area51.stackexchange.com/proposals/98617/monero **\** oooh i get pinged for dev meetings? :) **\** and earn rep: https://forum.getmonero.org/20/general-discussion/2542/stack-exchange-commitment-requirements **\** you're basically just committing to asking / answering a total of 10 questions over 3 months **\** also it would be advantageous if you have over 200 rep on another StackExchange site, as xmrpromotions said **\** I earned over 200 rep on bitcoin.stackexchange by answering like 4 questions, so it's not hard **\** ok maybe like 6 questions, but still, not hard **\** I think getting 200 committers in total will be easy, but having 100 committers with sufficient rep might be a little harder **\** ok so **\** PRs **\** over the last couple of weeks we've merged a few PRs **\** obviously **\** the biggest one being the performance branch **\** which was what warptangent was working on before he passed away **\** and which was completed by hyc and everyone else **\* dEBRUYNE** pages tewinget, NoodleDoodle, ArticMine, othe **\** probably missed someone **\** we are seeing some latent issues with auto-conversions, or that appear to be coming from the auto-conversion **\** if users hit issues with that the fastest route is for them to sync from scratch **\** iirc smooth has a broken conversion that we can use to analyse the issue **\** 810 and 775 are dangling **\** moneromooo: do you want those to stay open at present ? **\** 810 might be cancelled, not sure. **\** ok **\** 775 is ready AFAIK., **\** ok will test it **\** 818 is in a holding pattern pending some discussion; based on what shen has been doing lately my feeling is that we leave that till after RingCT is done **\** on that note, RingCT seems to be pushing ahead quite nicely **\** moneromooo: how's it looking from your side ? **\** I'm not a cryptographer, so I got no clue really :P **\** hah hah **\** Once I figure out what goes where, it's just code after that. **\** I know you're waiting for input from shen, but is it starting to make a bit of sense ? **\** Though a lot of it I think **\** kk **\** Mot yet, but I've not spent a lot of time on it today (and yesterday I was out). **\** alright **\** moneromooo: I want to decrypt it manually so I can detect transactions sent to an integrated address of mine in the tx pool. Is there another way to do it? **\** then next weekend I'll be at Bitcoin in Use in Arnhem, Netherlands **\** How will you know it's an integrated address of yours in the first place ? **\** and there will be several other Monero-er-ains there as well **\** including some devs, most notably hyc **\** a few ppl told me they want to meet you there:) **\** oh it's the meeting, sorry. I'll wait to discuss that later moneromooo **\** if anyone else is going to be there please let me know, we can do a Monero supper on the Saturday or something **\** next up is a chat about documentation **\** wallet42 has raised the idea of opening up the wiki on Github **\** https://twitter.com/Falkvinge/status/731833882102910977 wants to meet you too **\** the advantages of this is that it keeps the documentation close to the code **\** and you can PR to the wiki or (I think) edit it inline **\** xmrpromotions: oh neat **\** in fact, the wiki creates a .wiki.git project that's invisible-ish **\** so it makes syncing to GitLab easy (setting up a GitLab mirror is on the list of things to do) **\** downside is that you can't edit it anonymously, although creating a GH account is trivial **\** and the other downside is that we have tons of scattered documentation right now **\** so my thinking is that the wiki is a good idea for documentation, BUT then we need to kill off all these other sources of info **\** ^ I don't mind putting part of it together **\** so the Monero wikia has to be shuttered and that info moved over **\** There is information all over BCT **\** we could put the guides from Moneroexamples over there too, but he doesn't necessarily have to shutdown his "source" imo **\** same goes for dev guides etc. on the website - we should instead spend the effort writing a small Ruby plugin for the site that pulls in info from the wiki and formats it appropriately **\** then the wiki becomes a primary source of info **\** dEBRUYNE: yeah we could do the same thing with MoneroExamples **\** just have a plugin that grabs it from his repos and formats it **\** if anyone has an issue with this speak now or forever hold your peace **\** {-anonimal} Such consolidation sounds like a good idea. **\** fluffypony: Yeah that'd be fine too **\** as long as it consolidates the information to a central place it's fine **\** I'll leave the question open till the start of the Kovri meeting, if nobody has major objections raised by then I'll consider the decision in favour of the GitHub wiki **\** It is actually really needed We have info all over the place **\** (we discussed this here a few days ago as well, and everyone generally seemed in favour of it) **\** ArticMine: agreed **\** I like the idea. Consolidation and simplification should hopefully encourage more people to contribute to it **\** that's it from my side - next meeting will be on the 5th of May, same time **\** if anyone has anything they want to discuss, or any other points they want to bring up, now's the time **\** we have 20-ish minutes till the Kovri meeting **\** I am looking at the fee structure **\** Does anyone fancy hacking the pool code to check top hash ? **\** It shold be fairly easy. **\** {-anonimal} fluffypony: s/May/June/ **\** ArticMine: Is your research going to be put in a somewhat formal paper? **\** er, s/hacking/amending/ for the peanut gallery. **\** I'll start with a post on getmonero forum to get feedback ideas **\** then one can develop a paper **\** all right **\** Along the lined of my prior post on BCT regarding the adaptive block limit and penalty function. There are issues with respect to to many options in fees with RingCT **\** Is anyone willing to work on adding Monero to Bitsquare? Afaik it's only a few minor tweaks in the UI code, see issue here -> https://github.com/bitsquare/bitsquare/issues/392 | I might be able to try if I got some more time, emphasis on try though **\** anonimal: thanks, lol **\** To th UI of... ? **\** Bitsquare itself **\** It needs an additional field for the tx key **\** Ah, I just saw the screenshot. **\** It's mainly to resolve disputes, if any occur **\** Btw fluffypony, any ETA on a new point release that includes the performance branch? Or are we awaiting any more PRs? **\** ArticMine, i look forward to the adaptive fee structure thread **\** Oh high team **\** Hi team too **\** hi luigi1112 **\** dEBRUYNE: more PRs, also gives us time to see if there are issues with auto-convert **\** *more issues **\** hi luigi1112 **\** What would I do if I wanted to try and repro that problem ? just pull, build, run ? **\** fluffypony: all right **\** im just curious... is 0mq gonna happen before ringCT? or ... or all at once? **\** moneromooo: yeah **\** gingeropolous: no clue **\** I'm certainly doing nothing about it. **\** well there's months until the next hardfork... though i guess 0mq doesn't affect consensus protocols? **\** well it was either Ring CT or 0MQ for you afaik moneromooo and I think we decided last time that Ring CT was the priority (this is just to clarify to anyone reading) **\** ok starting the meeting relay for the Kovri meeting