Commit 9fd363d8 authored by D Sal's avatar D Sal Committed by GitHub
Browse files

Merge pull request #3 from monero-project/master

Merge recent changes
parents 265307a4 9f3547b0
......@@ -105,7 +105,7 @@ server {
rewrite ^ /gui/monero-linux-x64-v0.10.3.1.tar.bz2 redirect;
location /gui/inux32 {
location /gui/linux32 {
rewrite ^ /gui/monero-linux-x86-v0.10.3.1.tar.bz2 redirect;
......@@ -240,4 +240,4 @@ server {
fastcgi_pass phpfpm;
\ No newline at end of file
......@@ -119,9 +119,13 @@
- name: algoStrategic - Internet Marketing and Web Development
- name: Emmanuel Galang, Canada Immigration and Refugee Lawyer
- name: Web Developer - Python with Django web framework
- name: FlokiNET
- name: Nerdzy Lawn Care
url: http://
- category: Goods
- name: CryptoMercado - coffee and snacks
......@@ -137,7 +141,11 @@
- name: Handcrafted goods
- name: Cellphone and laptop repair online store in Sweden
- name: InvestmentArt
- name: Directvoltage
- category: Entertainment
- name: Crypto Kingdom
......@@ -29,6 +29,7 @@
<li><a href="/getting-started/donate">{% t menu.donations %}</a></li>
<li class="divider"></li>
<li><a href="/downloads">{% t menu.downloads %}</a></li>
<li><a href="">{% t menu.github %}</a></li>
<li class="divider"></li>
<li><a href="/getting-started/accepting">{% t menu.accepting %}</a></li>
<li><a href="/getting-started/merchants">{% t menu.merchants %}</a></li>
......@@ -59,7 +60,6 @@
<li><a href="">{% t menu.bitcointalk %}</a></li>
<li class="divider"></li>
<li><a href="">{% t menu.slack %}</a></li>
<li><a href="">{% t menu.rocketchat %}</a></li>
<li><a href="">{% t menu.telegram %}</a></li>
<li class="divider"></li>
<li class="dropdown-header">{% t menu.irc %}</li>
layout: post
title: Overview and Logs for the Dev Meeting Held on 2017-05-21
summary: Sub / disposable addresses, new website, CLI/GUI lightwallet integration
tags: [dev diaries, core, crypto]
author: dEBRUYNE / fluffypony
*May 21th, 2017*
# Overview
An overview [can be found on MoneroBase](
# Logs
**\<endogenic>** we have to do the dev meeting really quietly so the pony can get some sleep
**\<moneromooo>** 1. Greetings
**\<moneromooo>** 2. Brief review of what's been completed since the previous meeting
**\<moneromooo>** 3. Code + ticket discussion / Q & A
**\<moneromooo>** 4. Any additional meeting items
**\<moneromooo>** 5. Confirm next meeting date/time
**\<moneromooo>** (no relay bot btw)
**\<moneromooo>** So, since last time, I'm not sure what's been merged. Not much I think ? There was the key image flaw made public too.
**\<moneromooo>** I'm working on abstracting network addresses. Mostly works, but serialization is being a massive pain.
**\<moneromooo>** Anyone else want to say anything about what they're working on ?
**\<vtnerd>** eventually I hope to have the amd64-51-30k speedups in wallet2.cpp (assuming fluffy approves)
**\<vtnerd>** and improve the hex -> bin performance would be nice too (not nearly ready for a merge though)
**\<moneromooo>** What is that short for ?
**\<vtnerd>** oh sorry, the ASM for wallet scanning
**\<moneromooo>** What are the 51 and 30k short for ?
**\<vtnerd>** its already written so that it can be removed by cmake, and does not touch the consensus code _at all_
**\<vtnerd>** 51-bit limbs and 30k tables
**\<vtnerd>** 30k table singular, sorry
**\<moneromooo>** Anyone else doing something nice ? hyc, LMDB wallet code maybe ? :)
**\<moneromooo>** Nobody else ? tewinget ?
**\<vtnerd>** everyone is out spending bytecoins
**\<moneromooo>** Alright. Ticket discussion. The only thing I know is people reporting sync stopping. Some of them are user error, some are corrupt db, but I think there may be something else. I'd need to see good logs for both sides though.
**\<moneromooo>** Anyone wants to say anything about pending bugs ?
**\<iDunk>** Testing related... your 1982 works nicely, with no apparent issues after several days. That on a daemon with none to very light load, fwiw.
**\<moneromooo>** Cool, thanks.
**\<moneromooo>** About pending bugs: we're still waiting for finalization of the disposable address theory, IIRC RandomRun and knacc were discussing a change recently.
**\<moneromooo>** knaccc: any comment about this ?
**\<iDunk>** I'm syncing on Windows right now, albeit with non-default settings. Will report if it gets wedged.
**\<vtnerd>** change to which portion, disposable addresses or sub-addresses?
**\<vtnerd>** or I guess you specifically said disposable address
**\<moneromooo>** I don't remember. It's 1753.
**\<moneromooo>** I did, but not on purpose :)
**\<moneromooo>** I have a feeling it'll be a fast meeting.
**\<moneromooo>** luigi1112: anything new about smaller range proofs ?
**\<endogenic>** he's out spending bytecoin too
**\<jollymort>** happened to me today (sync); it just hanged; killed the process and restarted monerod; continued seamlessly
**\<jollymort>** can re-sync with different loglvl to see if it happens again
**\<moneromooo>** Next time, don't kill it before you've looked at the thread stack traces.
**\<moneromooo>** Anything else someone wants to say in the meeting ?
**\<rehrar>** Kovri test site? :D Not super dev-y, but nobody else says anything.
**\<moneromooo>** Kovri meeting is in 48 minutes.
**\<rehrar>** there is no kovri meeting today
**\<moneromooo>** aw... then feel free.
**\<moneromooo>** anonimal: around ?
**\<luigi1112>** moneromooo sorry no. will update soooooon
**\<moneromooo>** ty
**\<moneromooo>** Hmm.
**\<luigi1112>** next meeting will be exciting :-)
**\<moneromooo>** Well, no test site either then.
**\<unknownids>** oh baby i know what that means
**\<unknownids>** i think
**\<moneromooo>** Next meeting: in two weeks, same time.
**\<moneromooo>** Done. The only good meetings are short meetings.
**\<luigi1112>** am I doing this right
**\<luigi1112>** ann of ann
**\<jollymort>** mooo, how to use stacktrace?
**\<moneromooo>** Oh he's back now :)
**\<moneromooo>** jollymort: gdb /path/to/monerod `pidof monerod`
**\<moneromooo>** thread apply all bt
**\<jollymort>** so i can do it while it's running
**\<moneromooo>** Yes.
**\<jollymort>** no need to start it in some special way?
**\<jollymort>** ok
**\<jollymort>** i'll set loglvl to max also
**\<jollymort>** and start sync from 0
**\<moneromooo>** I wouldn't.
**\<jollymort>** ok, so just restart and wait for it to hang?
**\<moneromooo>** 3 and 4 are toop spammy for being much use in general usage.
**\<moneromooo>** Yes.
**\<moneromooo>** rehrar: free free if you have something to say/show.
**\<rehrar>** Anyways, Monero test site here: mobile responsive now and a brand new mobile navigation.
**\<rehrar>** Kovri test site: completely integrated into the Jekyll. The custom CSS framework was ported without issue. This bodes well for my further work on
**\<moneromooo>** Looks clean.
**\<Jaquee>** hi. a bit late to meeting. i'm working on lightwallet integration in cli and gui
**\<Jaquee>** or wallet2 mostly
**\<moneromooo>** You mean mymonero ?
**\<rehrar>** We scrubbed it down.
**\<Jaquee>** yeah. and openmonero
**\<Jaquee>** should work with both backends
**\<Jaquee>** and should be switchable from full wallet to light wallet. vtnerd. would you consider implementing input/output import in mymonero api?
**\<Jaquee>** would make it possible to switch from full wallet to light wallet without a rescan
**\<endogenic>** not clear how the mobile experience would go
**\<endogenic>** just an initial impression
**\<Jaquee>** ?
**\<Jaquee>** experience of what?
**\<endogenic>** as in how user gets wallet file on their mobile and how they pick it
**\<vtnerd>** I don't know what you mean Jacquee
**\<vtnerd>** you want to import an existing wallet quickly from a local DB to a mymonero backend ?
**\<vtnerd>** and also the other direction ?
**\<luigi1112>** that would be cool. maybe :-)
**\<Jaquee>** yeah. if i have a full wallet on my desktop and want to use the same wallet on my mobile. I could convert my full wallet to lightwallet by sending my inputs/outputs to mymonero/openmonero backend. And then login as usual on my phone
**\<Jaquee>** with seed
**\<Jaquee>** without paying the 1 xmr rescan fee
**\<Jaquee>** that was my idea
**\<Jaquee>** so the magic happens in desktop wallet.
**\<Jaquee>** on mobile you only login as usual
**\<vtnerd>** yeah, but its doable but I would have to think about it a bit
**\<vtnerd>** the backend would still want to verify correctness, so its not stomping on someone elses coins, etc
**\<vtnerd>** but it would be doing much less work
**\<Jaquee>** ok. yeah backend could verify with view key
**\<Jaquee>** that's probably best
**\<vtnerd>** yes. but it would only be looking at the set of outputs specified in the RPC call which will be much faster
**\<Jaquee>** exactly
**\<endogenic>** Jaquee: ic
**\<vtnerd>** yeah so the import out will be much easier, and you can almost do it with unspent_outs call
**\<vtnerd>** *export I think is what normal people say
**\<Jaquee>** yeah. i'm almost done with that
**\<Jaquee>** i'm trying to make wallet2 fully compatible so i can switch between light wallet and using a normal node
**\<vtnerd>** well I meant but the export from the backend side, but ok interesting that you've already started the wallet side
**\<vtnerd>** yup, understood
**\<zueore>** how monero is configured to only cpu/gpu mining?
**\<Jaquee>** so, to summarize. if i create the mymonero wallet first i can already switch between full and light wallet mode. This import call i'm suggesting also makes it possible to switch from an old full wallet never initialized on mymonero.
**\<vtnerd>** ok
\ No newline at end of file
layout: post
title: Logs for the Kovri Dev Meeting Held on 2017-06-04
summary: Brief review of what has been completed since last meeting, 96boards OpenHours showcase, website discussion, and code & open tickets discussion
tags: [dev diaries, i2p, crypto]
author: dEBRUYNE / fluffypony
*June 4th, 2017*
# Logs
**\<anonimal>** 1. Greetings
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
**\<anonimal>** 3. Status of [ OpenHours showcase for Kovri / Monero](
**\<anonimal>** 4. Code + ticket discussion / Q & A
**\<anonimal>** 5. Any additional meeting items
**\<anonimal>** 6. Confirm next meeting date/time
**\<anonimal>** Hi
**\<moroccanmalinois>** Hi
**\<anonimal>** Many crickets today, fluffypony moved monero meeting to next week. Maybe everyone thought kovri meeting was moved too.
**\<anonimal>** Hi moroccanmalinois
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
**\<anonimal>** RouterInfo, NetDb, I2NP (WIP in fork), cryptopp, HTTP, Reseed and docs work.
**\<anonimal>** This month had kept me AFK more than I'd like because of various life issues. This month *should* be better.
**\<anonimal>** Adding to 2.: rehrar website work, pigeons build work too
**\<moroccanmalinois>** I started a private testnet but it didn't work and then i was busy. i will get back to it this week
**\<rehrar>** Hi
**\<anonimal>** moroccanmalinois: cool, ok :)
**\<anonimal>** Anything else on point 2.?
**\<rehrar>** Besides the added stuff?
**\<anonimal>** I didn't get any more hackerone or VRP work done as I chose to focus on code instead. I think h1 stuff will be done soon though.
**\<anonimal>** rehrar: anything, just a general re-cap.
**\<anonimal>** Ok, moving on
**\<anonimal>** 3. Status of [ OpenHours showcase for Kovri / Monero](
**\<rehrar>** Typing
**\<rehrar>** Redesigned the custom framework, have semi-started a translation campaign, made a document on how to add and edit pages and translate them, and have done intermittent testing since then, and added a few more languages upon request.
**\<anonimal>** Cool cool. How's the monero site coming along so we know when you can do a kovri FFS?
**\<rehrar>** Leaving Russia tomorrow. Will be a 40 hour process getting home and the past week was spending time with wife's family since don't know when I'll be back. But pages are being made, and I hope to have it done in less than three weeks.
**\<anonimal>** Ok, sounds great. Safe travels.
**\<rehrar>** For the Kovri FFS I would like a full list of things desired from me so I can put it in all at once. It'd be best so as not to have "oh wait this too" after funded and started.
**\<rehrar>** Although being flexible is important obviously. :) But minimizing that is nice.
**\<anonimal>** Indeed. I'll be happy to work with you on getting that part done.
**\* anonimal** will be around when you're ready
**\<rehrar>** Aight. Thanks.
**\<anonimal>** No problem. Anything else on point 2.?
**\<rehrar>** Nah
**\<anonimal>** Oh, typo to what I said earlier this meeting. I meant "Last month had kept me AFK more than I'd like...", not "this" month. Oops X)
**\<anonimal>** Will dEBRUYNE do editing for things like this or is that still bad IRC etiquette?
**\* anonimal** fine either way
**\<anonimal>** So point 3.,
**\<anonimal>** fluffypony would need to be around. I think hyc too (if he's still onboard).
**\<anonimal>** The podcast is June 8th, 6pm-7pm SAST
**\<anonimal>** So... 4 days
**\<anonimal>** I'll try to touch base with everyone tomorrow. Would like to be as prepared as possible.
**\<moroccanmalinois>** live streamed ?
**\<anonimal>** Ah, good question. I don't think so.
**\* anonimal** wouldn't quote me on that though
**\<moroccanmalinois>** lol k
**\<anonimal>** I've only seen the podcasts on youtube and they weren't live.
**\<anonimal>** Maybe #OpenHours can answer that
**\* anonimal** checks site
**\* anonimal** asked in #OpenHours
**\<moroccanmalinois>** thanks
**\<anonimal>** Any questions/comments on point 3.? We kind of need fluffypony around since he's the official interviewee
**\<anonimal>** Alright, moving on,
**\<rehrar>** Next. :P
**\<anonimal>** 4. Code + ticket discussion / Q & A
**\<anonimal>** I don't have any questions really. Doing some much-needed I2NP refactor work and flushing out some ideas for the messaging system (or lack thereof). WIP in my fork, stash not committed yet.
**\<anonimal>** Anyone else?
**\<anonimal>** (btw, open issue re: I2NP)
**\<anonimal>** Mind you, it's all connected: RouterInfo, NetDb, I2NP -> NTCP transport layer. So this is all toward the alpha release.
**\<anonimal>** If I can skip work that doesn't lead to a release, I will do it.
**\<anonimal>** Until then, the rabbit hole needs fixing.
**\<moroccanmalinois>** Just one question : i know there are known issues with NTCP, but i didn't see any major issue with SSU. A network with only kovri nodes enabling SSU but disabling NTCP should theroetically works ?
**\<anonimal>** moroccanmalinois: yes, and we could technically release now. I thought it would be wise to remove as many of the log error messages (some of which really aren't errors per-se) so we don't get an influx of reports for known issues.
**\<anonimal>** What do you think?
**\<anonimal>** FYI the NTCP review lead to the RouterInfo rewrite -> NetDb work -> now I2NP work (because I'm here and it was driving me crazy).
**\<moroccanmalinois>** I agree.
**\<anonimal>** And there are/were lots of things to fix along the way anyway.
**\<anonimal>** Ok. I'm very open to suggestions as we proceed.
**\<anonimal>** moroccanmalinois: did you have any particular stumbling blocks when doing your testnet work?
**\<moroccanmalinois>** i need a little more time to answer this. It was easy to see that it didn't work with NTCP since 15 min after the start, routers don't have anything in their netdb
**\<anonimal>** Ah ok
**\<moroccanmalinois>** with ssu, everything looks good but the tunnel didn't work
**\<anonimal>** I can hop on slack more often and send a PM if you want to work out any details (if I can help in any way).
**\<moroccanmalinois>** Thanks but i am jumping to irc, and i won't hesitate to contact you :)
**\<anonimal>** Anything else on point 4.?
**\<anonimal>** rehrar did you say you like doing backend webdev too?
**\<anonimal>** moroccanmalinois: awesome, ok
**\<rehrar>** Not my strongest point, but I am able, yes. And all of my speaking around the Reddit and other places is getting me in touch with a large number of devs, web included.
**\<rehrar>** So what I can't do, I am positive I can get someone on.
**\<anonimal>** Cooool. I like the sound of that.
**\<anonimal>** I'm curious to know how far we could go with check.kovri.i2p
**\<anonimal>** could/should
**\<anonimal>** Anyway, that's distant stuff that we can talk more about later. I can't imagine a lot of code involved either.
**\<rehrar>** Sure thing. We'll talk bout it soon.
**\<danielesesta>** Good Evening
**\<anonimal>** Once anonimal/kovri-site is moved to monero-project/kovri-site, I think I'll move the meta issue there.
**\<anonimal>** Hello danielesesta.
**\<rehrar>** Great to have you join @danielesesta read the backlog. :)
**\<anonimal>** Ok so moving onto 5. Any additional meeting items
**\<rehrar>** Ye I got one.
**\<rehrar>** I have been thinking of starting a Kovri campaign of sorts. Marketing for devs. Just letting other open source devs know what's out there and let them know we exist and would welcome any help for improving privacy.
**\<rehrar>** There's a number of different Reddits and websites for talking about your FOSS project.
**\<rehrar>** I'd love to put a few things together (including that over-text interview with you we had discussed)
**\<anonimal>** Alright, great idea.
**\<anonimal>** When do you want to do this? I can schedule myself accordingly.
**\<danielesesta>** we @ daashaus we are launching now some products but i believe in mid-august - september we can start on working on a proof of concept web based product on the kovri i2p
**\<rehrar>** Im thinking next week. Need some time to resettle at home upon returning.
**\<danielesesta>** with @rehrar we talked about making a medium of some sort for anonimous blogging
**\<anonimal>** rehrar: ok, whenever you're ready, I'll be around.
**\<anonimal>** Interesting. danielesesta is there a chat log or overview so I can catch up?
**\<danielesesta>** we were talking privatly
**\<anonimal>** rehrar: FYI there is a meta issue about this (developer search). Could we also coordinate there too?
**\<rehrar>** Yes we can.
**\<danielesesta>** we can launch something on beta pretty quickly if i add at least 3 devs for a month
**\<danielesesta>** would be good maybe to run a design sprint of the product and get some ideas going with the team so we can put the project in the pipeline
**\<danielesesta>** idk if you rehar and anonimal would like to join it maybe the first week of august?
**\<anonimal>** danielesesta ok, so what exactly did you have in mind for the product?
**\<rehrar>** I'd love to sure.
**\<danielesesta>** i believe that at the moment being aninimous in the web is for an elite only, but there is a lot of people that has a very little know-how but still has a lot to contribute
**\<danielesesta>** about telling stories and spread their words
**\<anonimal>** So the product would be unknown at this point? Thus the meeting in August to generate ideas?
**\<danielesesta>** our idea was to create a medium with a simple user-friendly UI/UX blogging platform for anyone to use without a big knowledge on how to be aninimous in the web
**\<danielesesta>** that can protect them but still deliver
**\<anonimal>** Ah, ok, great idea. Sorry, you did say that earlier but now I see what you mean.
**\<serhack>** if you wanna help, please contact me, I am a web dev.. I'm building integrations for monero
**\<rehrar>** Serhack, I was going to out you in touch with Daniel.
**\<rehrar>** I will be making a slack channel soon for web devs.
**\<rehrar>** So we can discuss Monero/Kovri needs.
**\<danielesesta>** i think that could be a great use of a i2p browser
**\<anonimal>** Nice, I like that idea.
**\<danielesesta>** also a great proof of concept
**\<serhack>** okay thanks rehrar
**\<danielesesta>** and maybe for the first time we might apply some good design and cool features in the world of the blockchain
**\<serhack>** :)
**\<rehrar>** Ok. Anonimal I've got one thing to ask you.
**\<danielesesta>** @serhack sure PM me so we keep in touch here
**\<rehrar>** Oh, thank you you two for your contributions, Danielesesta and serhack
**\<anonimal>** Ok, so in terms of housekeeping: danielesesta or anyone, would you be willing to open a new issue at explaining your idea/proposal so we can all have a point of contact and collaboration? Or is there a better alternative?
**\* anonimal** would usually refer to the kovri repo but that's better for code issues
**\<serhack>** forum :)
**\<anonimal>** Hmm, well, the forum doesn't email me notifications (I've tried everything)
**\<danielesesta>** i believe we can move on our own without bothering anyone we are all people that can manage ourself efficiently i believe
**\<danielesesta>** if we encounter any issue we can email each other directly
**\<anonimal>** It's more of a friendly reminder, not necessarily "let's all talk here and do all our work in the meta issue"
**\<rehrar>** Given that the tasks for Kovri are more varied than just web work, as discussed above, what do you think of me opening a FFS of not necessarily web work and have it be objective based, but an hourly based sort of FFS that I can do a bunch of various tasks (Reddit, Web, Outreach campaign, etc). Whatever Kovri needs basically.
**\<anonimal>** danielesesta: otherwise, if someone wants my input, they'll have to keep me apprised because I'm pretty busy. Just an FYI.
**\<anonimal>** rehrar: I would advise two separate FFS' then: one for strictly website and one for the other.
**\<anonimal>** But then again I'd also ask for fluffy's or luigi's or any monero-dev's input too.
**\<anonimal>** A general staffer sounds good but I have no idea what everyone else thinks.
**\<anonimal>** Ok, we're out of meeting time. Any last thoughts on additional meeting items?
**\<rehrar>** Ok. If they're on board with the "general staffer" as you put it, then I'd love to give it a go. There's lots of house keeping to do. :)
**\<rehrar>** Nope
**\<anonimal>** Ok. 6. Confirm next meeting date/time
**\<anonimal>** So, monero's is next week.
**\<anonimal>** But we usually two ours every two weeks.
**\<anonimal>** Maybe we'll have a mini-meeting next week after monero's?
**\<anonimal>** \*do ours
**\<anonimal>** Any objections to a meeting next week?
**\<moroccanmalinois>** no objection
**\<anonimal>** Ok, I'll set one for next week.
**\<rehrar>** Ye. Let's do it.
**\<anonimal>** One last thing for additional meeting items: I wanted to say hi, recognize, and thank all kovri contributors for their contributions and camaraderie.
**\* anonimal** typing
**\<anonimal>** A former contributor made a erroneous comment implying there were no contributors to the project. A blatant lie that I felt was disrespectful to everyone involved.
**\<anonimal>** Anyway, so thanks everyone.
**\<anonimal>** End of meeting!
\ No newline at end of file
layout: post
title: Logs for the Kovri Dev Meeting Held on 2017-06-11
summary: Brief review of what has been completed since last meeting, FFS for MoroccanMalinois, FFS for Rehrar , 96boards OpenHours showcase, website discussion, and code & open tickets discussion
tags: [dev diaries, i2p, crypto]
author: dEBRUYNE / fluffypony
*June 11th, 2017*
# Logs
**\<anonimal>** 1. Greetings
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
**\<anonimal>** 3. Status of [ OpenHours showcase for Kovri / Monero](
**\<anonimal>** 4. Moving `anonimal/kovri-site` and `anonimal/kovri-docs` to `monero-project` #74
**\<anonimal>** 5. Resolve FFS RFC for @moroccanmalinois
**\<anonimal>** 6. Code + ticket discussion / Q & A
**\<anonimal>** 7. Any additional meeting items
**\<anonimal>** 8. Confirm next meeting date/time
**\<anonimal>** Hi
**\<ArticMine>** hi
**\<rehrar>** Hi!!
**\<johnalan>** hi
**\<anonimal>** 2. Brief review of what's been completed since the previous meeting
**\<rehrar>** Sorry. Slack being stupid.
**\<MoroccanMalinois>** Hi
**\<rehrar>** The one last week? Is this a mini-meeting?
**\<anonimal>** Yes, but it should go as long as it needs
**\<anonimal>** I was busy dealing with more guzzi drama and dis-information, so I haven't been able to prepare for 2
**\<anonimal>** This week was very busy though:
**\<i2p-relay> {-fluffypony}** sorry I missed 1. - I'm in and out, getting changed and need to get food desperately
**\<anonimal>** much preparing for 96boards (which ended up being canceled), kovri-site dev / collaboration, kovri-docs created, PR review/merges
**\<anonimal>** rehrar doing great work, MoroccanMalinois doing great work
**\<i2p-relay> {-fluffypony}** anonimal doing great work
**\<anonimal>** Everyone around doing great work. elopio pigeons and every other contributor this past week.
**\* anonimal** blushes, thank you
**\<anonimal>** #653 was interesting, still not sure what his issue was before he closed it.
**\<anonimal>** In all a very collaborative and active IRC week. Did I miss anything?
**\<anonimal>** Oh, yes, guzzi quit and left his FFS unfinished. MoroccanMalinois is stepping up to finish his FFS work (we'll talk more in point 5).
**\<anonimal>** Moving on to 3.?
**\<anonimal>** 3. Status of [ OpenHours showcase for Kovri / Monero](
**\<anonimal>** I think we're rescheduled (or will be) for July 20th or 27th
**\<anonimal>** I'll keep everyone apprised.
**\<anonimal>** Details are in the meta issue.
**\<anonimal>** I think everyone was informed about fluff's flight delay. Did anyone not get that info / reschedule notice?
**\* anonimal** posted in the reddit thread too
**\<i2p-relay> {-fluffypony}** yeah stupid fire
**\<i2p-relay> {-fluffypony}** Robert indicated that next month would suit
**\<anonimal>** Ok
**\<anonimal>** Anything else on 3.?
**\<anonimal>** 4. Moving `anonimal/kovri-site` and `anonimal/kovri-docs` to `monero-project` #74
**\<i2p-relay> {-fluffypony}** I can create empty repos for that now before I leave
**\<anonimal>** fluffypony: what do you think about this? ^
**\<i2p-relay> {-fluffypony}** I think that's good
**\<rehrar>** Sorry. Here. Checking backlog. I'm out and a guy I know decided to give me a 15 minute talk on WW2
**\<anonimal>** fluffypony: alright, cool
**\<anonimal>** Anything else on 4.?
**\<johnalan>** um
**\<johnalan>** at the risk of asking a stupid q
**\<johnalan>** is there anything that needs to be done on making Kovri Ipv6 ready
**\<johnalan>** one example is port fowarding
**\<johnalan>** on ipv6 consumer routers you can’t do that
**\<johnalan>** as all devices have public IP
**\<anonimal>** johnalan: ipv6 is supported, let's talk more at point 7.
**\<johnalan>** ok
**\<johnalan>** no probs
**\<johnalan>** sorry
**\<anonimal>** 5. Resolve FFS RFC for @moroccanmalinois
**\<MoroccanMalinois>** Just a few words before this point: I am bad at social things. I don't do politics/drama. Not a funny guy, don't feels comfortable with english, but i am happy to answer technical questions when i can. I already feel honored by the support i have received so far and whatever happens with the FFS, i am OK with it and it won't change anything to the work i am going to do or not do in the next months.So just wanted to say a big
**\<MoroccanMalinois>** THANKS !
**\<anonimal>** Woo!
**\<anonimal>** I've seen no negative responses to the RFC. Did anyone say anything in the reddit thread?
**\* anonimal** checks
**\<i2p-relay> {-fluffypony}** MoroccanMalinois: your English has been excellent, you mustn't worry about that :)
**\<MoroccanMalinois>** :)
**\<moneromooo>** MoroccanMalinois == good guy to have
**\<moneromooo>** (or gal)
**\<anonimal>** Nothing but positive reviews it seems.
**\<MoroccanMalinois>** Thank u very much mooo
**\<anonimal>** So, everyone is in agreement?
**\* anonimal** yes
**\<johnalan>** yes
**\<moneromooo>** yes
**\<johnalan>** delighted to have him
**\<johnalan>** her
**\<johnalan>** whatev
**\* MoroccanMalinois** blushing
**\<serhack>** yes
**\<anonimal>** Sold! Congrats to MoroccanMalinois. You've always been aboard so saying "welcome aboard" is redundant.
**\<anonimal>** Welcome aboard
**\<anonimal>** lol
**\<anonimal>** On this note, I'd like to point out one thing:
**\<anonimal>** We spent more time vetting MoroccanMalinois as a replacement for guzzi then we did vetting guzzi to receive an FFS in the first place.
**\<anonimal>** palexander had some great questions. In general, how can we better vet FFS proposals?
**\<anonimal>** Is this possible? If so, how?
**\<moneromooo>** I think the key is to have people contribute enough to get a feel of how it works. I don't know how much guzzi contributed at start though.
**\<endogenic>** one thing i'd like to mention is that if someone is getting paid, they should know something, and be able to ship at least what they say they know w/o reliance on others
**\<endogenic>** if that's not able to be kept then i'd say that's grounds for renegotiation or something
**\<endogenic>** aside from that, i think it's important to be careful with whether teaching someone becomes a codependency sort of situation
**\<endogenic>** not that i'm saying you wanted that at all anonimal, obviously
**\<anonimal>** I think moneromooo and endogenic hit that nail on the head HARD!
**\<anonimal>** moneromooo: to be brutally honest, guzzi contributed very little; even less AFTER he started his FFS.
**\<anonimal>** The value of the work was on par to the amount.
**\<anonimal>** He should've spent his time taking an online course or going to a community college instead of, endogenic so elegantly put it, used me as a co-dependent.
**\<anonimal>** Though the dependency was not mutual.
**\* anonimal** typing
**\<MoroccanMalinois>** :) Dear community, Thanks very much
**\<anonimal>** For guzzi to take 4 months to complete 40 hours of work, get many free hours of tutelage from me, complain about not understanding how to program c++, attack me and discredit other contributors, quit, then continue to attack the project: I don't think anyone could've predicted this would happen.
**\* anonimal** grabs meta link for FFS sticky
**\<endogenic>** lol anonimal as to the last sentence you may find it can be noticed much earlier
**\<i2p-relay> {-fluffypony}** anonimal: I've created the repos and given you access
**\<i2p-relay> {-fluffypony}** or invited you anyway
**\<i2p-relay> {-fluffypony}** on that note I have to take my leave, chat later
**\<anonimal>** Thanks fluffypony. Godspeed.
**\<anonimal>** endogenic: lol alright, you have a point ;)
**\<anonimal>** So, ^ create formalized FFS process
**\<i2p-relay> {-fluffypony}** o/
**\<endogenic>** \o fp!
**\<anonimal>** It's already in meta. endogenic moneromooo not to prod your brain too much, but does a sentence or two come to mind that could be added/revised?
**\<anonimal>** gingeropolous: ^ thanks
**\<endogenic>** may be good to put rigorous criteria to "disappears"
**\<endogenic>** taking vacation at improper times, etc, imo, is akin to abandonment
**\<rehrar>** Ok. I'm sorry for the second disappearance. O vote aye for @moroccanmalinois
**\<endogenic>** obviously that's super strict and not applicable directly to a FOSS context
**\<moneromooo>** "improper" ?
**\<endogenic>** but my point is that if someone just pops in every now and then to say "hey i'm still alive" but is dragging their heels then that may be a sticking point where you would have wanted to define what disappears means
**\<endogenic>** moneromooo: "improper" as in let's say they committed to doing something but then decided to put a vacation there
**\<moneromooo>** Maybe there could be a rough show of hands as to whether something needs fixing, then.
**\<anonimal>** Good point I think.
**\<anonimal>** fp and I had repeatedly - repeatedly - over the course of months had asked him to show up to meetings; yet he still wouldn't do it reliably. MoroccanMalinois was better at attending meetings and no one asked him to!
**\<endogenic>** moneromooo: yeah i believe it has to be judged case-by-case, anyway
**\<endogenic>** anonimal: yep
**\<anonimal>** So, maybe we should add something to the regular meeting agenda? "X. contributor / FFS check-in, status"?
**\<endogenic>** anonimal: there are so many good people who would want to work on kovri
**\<johnalan>** anonimal: good idea
**\<endogenic>** that actually sounds like a great idea
**\<moneromooo>** Yep
**\<anonimal>** And then add something to the FFS document which *enforces* something
**\<anonimal>** That's the tricky part I think.
**\<endogenic>** the contract can't enforce things per se imo
**\<endogenic>** but can give paper trail to agreement
**\<endogenic>** so imo the question is what matter needs addressing
**\<anonimal>** Ok, so make this more of a per-issue/per-person/per-meeting check-in resolution?
**\<johnalan>** its not to make it difficult or hard on the FFS contributor, just a status update. If that’s not much in a given week or two no problem
**\<anonimal>** Instead of a global catch-all?
**\<endogenic>** well it could probably be couched in general terms
**\<rehrar>** I think status updates are healthy accountability. They are hired by the community after all.
**\<johnalan>** ^^^
**\<rehrar>** As long as they are done unilaterally without preference (so anonimal too and other higher ups) then it's a good thing.
**\<endogenic>** but it's basically to have them indicate they understand that they are working for the community, not the other way around
**\<anonimal>** johnalan rehrar: I believe I've been doing that for every meeting since 2015. In the eyes of a problem contributor, any response is a good response because "it's a response and that's all I need to give"
**\<johnalan>** ok
**\<rehrar>** I'm not pointing fingers at you, bud. Just saying as long as everyone is held to a similar standard, I think it's healthy and ensures something like this doesn't happen again.
**\<johnalan>** good point
**\* anonimal** is questioning the validity / quality of the response as it pertains to the FFS
**\<johnalan>** fair
**\<anonimal>** rehrar: I didn't think that nor am I implying that. I'm not attacking you or johnalan. This is purely information relay.
**\<rehrar>** Part of a formalized FFS should include updates on a regular basis, and if this minimum thing isn't kept up, it's fair to question whether or not the person has the committment to fulfill the project
**\<rehrar>** if they can't even be bothered to give updates, how can they be bothered to complete the assigned tasks?
**\<anonimal>** Indeed
**\<rehrar>** Even if they can't make it to a meeting, they can write something up before hand and have a proxy give it on their behalf.
**\<rehrar>** It's honestly a bare minimum as far as standards go, and I'm all for it. :)
**\<anonimal>** So how can we write this into an FFS standard?
**\<johnalan>** measurable goals
**\<rehrar>** I think that's a big of a longer conversation that should involve more people if we're talking about the FFS at large, and is outside the scope of this meeting.
**\<rehrar>** \*bit of a longer
**\<moneromooo>** tbh, I'd keep it fairly generic, and keep in mind some FFSes aren't coding.
**\<rehrar>** if we're just talking about FFS's for Kovri, then sure, let's talk
**\<rehrar>** I wouldn't mind writing up a draft and presenting it to everyone. :)
**\<anonimal>** rehrar:
**\<johnalan>** sorry gents gotta dash (no pun intended)
**\<rehrar>** I'll fork and do some amends for review.
**\<ArticMine>** I would prefer this to be applied to FFS across the Monero project, not just Kovri
**\<anonimal>** ^
**\* anonimal** was just typing that
**\<rehrar>** This is actually pretty important for me, as I'm designing the new FFS interface for the new website. Have a meeting with Fluffy on Monday about some technical aspects, but getting this hammered down too would be very helpful.
**\<anonimal>** I've been hoping for this discussion for a long time now; before I even opened up my first FFS. I'm glad to see we finally have the time/space to get to this.
**\<rehrar>** It's possible to launch the new website without the redesigned FFS for the short term, and roll out the new one once this discussion has been hammered out.
**\<rehrar>** I used hammered something twice. Slap me.
**\<anonimal>** Lots of good input. I'll need to give this more thought too.
**\<anonimal>** Anything else on this point?
**\* anonimal** will add to the next meeting agenda
**\<rehrar>** Nah, but it may be a good thing to add the the next #monero-dev agenda also
**\<anonimal>** ^ fluffypony
**\<anonimal>** 6. Code + ticket discussion / Q & A
**\<anonimal>** 6 minutes left. Any questions/comments?
**\<anonimal>** MoroccanMalinois: I'd like to add your testnet bash script to /contrib. What do you think?
**\<MoroccanMalinois>** I'll wait for it to work :)
**\<anonimal>** lol, ok
**\<MoroccanMalinois>** Pretty sure it doesn't work related to the config
**\<MoroccanMalinois>** External IP Detection seems completely broken
**\<anonimal>** Which config?
**\<MoroccanMalinois>** But it works perfectly on mainnet
**\<anonimal>** I'll talk more with you about that after the meeting.
**\<MoroccanMalinois>** Sure
**\<anonimal>** Anything else on 6.?
**\<anonimal>** 7. Any additional meeting items
**\<rehrar>** I have something. So I've discussed with anonimal what it would be like for me to put in a FFS as a 'general staffer' of Kovri. There's a lot of work that needs to be done that isn't coding related. Website maintenance, reddit moderation and theme design, trying to get other developers interested, etc. I'd like some feedback from others on what the thoughts of something like this are instead of FFS for each project. Basically, bei
**\<rehrar>** from moneromooo and others as well since there's a possibility of me doing something like this for Monero as well (I had a discussion with dEBRUYNE who supported the idea)
**\<moneromooo>** This got cut: "Basically, bei [...] from moneromooo".
**\<rehrar>** sec
**\<rehrar>** Basically, being paid on a per hour basis 10ish/wk
**\<rehrar>** 10ish hours I mean
**\<ArticMine>** Maybe doing the FFS for Monero as a whole including Kovri
**\<rehrar>** that's what I was thinking yes. 10 hours/wk for Monero and 10 for Kovri or something like that in one FFS
**\<rehrar>** I would outline the goals for each project
**\<rehrar>** Would this be something that would be useful? Creating content for Monero (like the reddit posts and helping people get plugged in) is something that's super fun for me and I love to do
**\<rehrar>** and I would love to be able to devote dedicated time for it
**\<endogenic>** the reddit posts could be something of a black hole
**\<rehrar>** and Kovri, well, it's my favorite and the reason I'm here
**\<endogenic>** if it were to be funded, it might be good to formalize the plan for making posts
**\<moneromooo>** Reddit, I dunno, but website content curating would be useful, for example.
**\<endogenic>** rather than it being, purely for example, contacting specific people who might not know about kovri
**\<rehrar>** understood, content can be different
**\<rehrar>** and yeah, web maintenance for both projects is definitely one thing I had in mind
**\* anonimal** notes we don't have a formalized way of reporting completed work. Even I'm ad-hoc'ing it. Sidenote: I think we should give this more thought with FFS re-write work
**\<ArticMine>** I looked at you work for it is rock solid
**\<anonimal>** rehrar knows I'm on-board with the idea.
**\<rehrar>** thanks so much ArticMine :)
**\<ArticMine>** This kind of material is needed across the whole project
**\<anonimal>** General question: would having a single person in charge of this much be questionable in terms of de-centralization?
**\<ArticMine>** Posting in my opinion is secondary
**\<endogenic>** well they could fall into the same accountability/status update stuff
**\<endogenic>** anonimal:
**\<rehrar>** ArticMine: on slow weeks with not many updates to be made, the time can be filled with more user guides and stuff, which are desperately needed. :)