I have followed up directly with Fluffypony on my thoughts in a personal message.
The community can decide how to proceed.
Proposal for Kovri Dev
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 # Proposal for Kovri Dev 120 hours. (should protect against increases and decreases in value) ~ 12 weeks @ 10 hrs per week. #Why * Over the last year Kovri/Monero has become my passion. I spend about 10 - 15 hours a week improving code and reading up on Kovri as well as Monero. * Any bitcoin wallet worth a grain of salt already implements Tor. I2p being more decentralized should provide the needed protection for viable remote node usage. #What Assist Kovri/anonimal on a consistent basis. * Provide support for Kovri bugs and coding needs. * Currently I am working on the proxy server fixes in Kovri. Most of this work is already complete, testing is needed. * Acquire new skills: learn lmbd to apply lmdb into kovri for address book initially. #Who Guzzi ##PRs submitted * Monero: completed a change request to force the simple wallet password to be entered 2 times. * Kovri: implemented a temporary fix to return the correct error codes throughout the proxy server. * Kovri: Coverity fixes. #How ##Time I will be able to spend 10-15 hours per week working on kovri. The work will be divided out by anonimal. Current Schedule: EASTERN times. * Tuesday 7-9 * Thursday 7-9 * Friday 7-9 * Saturday 1-4 * Sunday 1-? ##Reports Weekly reports will be submitted under this discussion on getmonero.org. This will allow me some flexibility to take a week off when needed and work extra during one week. I will supply dates and duration of the work every Sunday for the prior week. ##Offer Expiration Expires Feb 28th, 2017. ##Pay Rate Paid @ 1 xmr / hour ~ 13 USD. * To be paid in XMR delivered at the end of each 40 hour period as per weekly reports. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJYh+qDAAoJEFzcPjpYoxWy2pkH/A0+b490LO+dEhZSM0S9LIer eI45FuzeBHDD9boFH/JRMavoeoPXjc2RuY5UFv7NNVaS/TT4oFeJmnh+0B4jD0ah GhGeu/fAx3DL0CORR0w0QG8mHKxJ3NxANmYSKQk8L6ab4swquwVN3zMUoOcZ9CwC pwTDs4S8f0sBRo7hisVyHFb+zvb+9r3FvKHWAkuKQ8TLkh4qGK6EaO/cquIB2QYK JfEUOcIBBIlUp1/UdXS2kT4F20IAXIoL+cgE5bLJMfABfuT/eWN45PrfyO0DWrAC 76DCd8xs32tIMER8/gAx8jnneJ52/yJ7RCmOZUpadzW7eiqaR4390U/L0R37j9E= =Brz1 -----END PGP SIGNATURE-----
MEMO: No payout needed at this time. Initial posting of work done to inspire feedback on format.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 # 2017-02-05 thru 2017-02-11 * 2017-02-07 : CHARGEABLE : 2 hrs; proxy, boost asio * 2017-02-09 : CHARGEABLE : 2 hrs; proxy, boost asio * 2017-02-11 : CHARGEABLE : 2 hrs; proxy, boost asio # 2017-02-12 thru 2017-02-18 * 2017-02-12 : NO CHARGE : 2 hrs; boost asio rtfm * 2017-02-14 : NO CHARGE : 2 hrs; boost asio rtfm * 2017-02-17 : NO CHARGE : 2 hrs; boost asio rtfm ; google style docs rtfm * 2017-02-18 : NO CHARGE : 2 hrs; boost asio rtfm ; google style docs rtfm # 2017-02-19 thru 2017-02-25 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJYqujYAAoJEFzcPjpYoxWymxsH/1i2IwP37twx/3QciWh1R6Pk xCRk63JeQryY39bAQZ2Lz8BidY6EaKOT8yfIPcxa4BcVZW/IkD9dSWDP9ZVEIlq7 4LkWrvO0q+9g/KDImOPmM5ZlCuzpGH9FFc5LlJxf96Dm+Ko+JOOC/UNEScde/t88 QOFWcD+v3qZYi5McN8I7IoqkUi2m/h8Wutl7kPAg2QyMvUrJSoUjnHbMvY+rZsLk MK7bwULYAJjgWpWG+HH7ZebYk+o9OJXzm1yW3+h770R1/v9CxDU4vYyUlgrtL2Qh GNMnXTZzOpiYxrJiaQARM9/I7RkU73Wm0Y9ntC9cBilENt2wRAP33KWmgf5mX+4= =o0sd -----END PGP SIGNATURE-----
I must point out several issues:
A) Billable hours
2017-02-21 12:53:41 guzzi fyi, i am noting my time but not using billable hours for the boost learning.
but here you are billing those hours.
B) Following through
- On 2017-02-10: I asked you to become more familiar with clang-format, a "guru" if possible, so I wouldn't have to - but you never followed through with this
- On 2017-02-11: this was two days after the proxy work was merged and I formally asked you to start learning the Google style guide (though I had stressed this repeatedly for months now) in particular, the non-formatting style, but you continued reading boost docs instead
- On 2017-02-15: I asked you to move benchmarks code into the new utility, you said you'd start on it but then you kept reading boost docs instead - and benchmarks code still hasn't been moved
Most importantly, even before you were funded, I've repeated said that you shouldn't be spending this much time on boost documentation because it's not doing you, or the project, much good at this point. After the proxy was merged 2+ weeks ago, I insisted that you stop reading boost documentation for the proxy and work on other things (as I had assigned) - but most of this never happened.
I'm only bringing this up because your proposal specifically said:
The work will be divided out by anonimal
Assist Kovri/anonimal on a consistent basis
I'm dividing out the work but if you don't do it, it's not assisting!
Please, guzzi, let's work together to make this process go smoothly.
Anonimal, thank you for the feedback. I agree we need to be on the same page thus the post to ensure quick resolution early in the process. Current priorities are:
- On 2017-02-10: clang-format, a "guru" if possible.
- On 2017-02-15: benchmarks code into the new utility.
These lines included boost asio only because the proxy uses boost asio not because i was learning additional boost asio functionality. I will amend my internal doc so that it is clear. :
* 2017-02-07 : CHARGEABLE : 2 hrs; proxy, boost asio * 2017-02-09 : CHARGEABLE : 2 hrs; proxy, boost asio * 2017-02-11 : CHARGEABLE : 2 hrs; proxy, boost asio
Also it is probably best to just leave out the non chargeable b/c really who cares. :)