For Cycle 11

[ripcurlx]

Summary

• BSQ requested:5795 (3825 USD @ 0.66 USD/BSQ)

This is a compensation request for contributions delivered from last cycle until now (Mar 16). I calculated the amount based on the new three months average of 0.66 USD for 1 BSQ mentioned in #501.

Proposal transaction ID: dcc894597fb9fdb589c1ba78a3f7b413084795e216540024a51aed3e3c78b054

Contributions delivered

Reviews

Reviewed PRs:

View all reviewed PRs (27)

My PR reviews this month were created by reviewing the results of this GitHub Issues search query:
is:pr reviewed-by:ripcurlx updated:2020-02-14..2020-03-16 sort:updated-desc

• Add local Bitcoin node configuration detection 240 USD
• Vote Reveal - Silent Fail 70 USD
• Speed up BSQ supply view load 46 USD
• Dump failed delayedtx 34 USD
• Allow 4 refreshes per trade 28 USD
• Remove unused i18n strings 24 USD
• Speed up DAO state monitor view load 24 USD
• Update offer address to new hidden service files 22 USD
• Added graceful shutdown hook

Following PRs Review efforts are so small to track them separately:

• Change video link in greeting to blog link bisq#3968
• Set syslog identifier as "bisq" in systemd service config bisq#3950
• Use mkdir -p in seednode installer when creating bitcoin/bisq homedirs bisq#3951
• Revert setting of null to deposit tx id bisq#3958
• Allow unrecognized options in config file bisq#3967
• Remove unused uid in pricefeed service bisq#3937
• Avoid startup failure when appDataDir is a symbolic link bisq#4002
• Monitoring install scripts bisq#3985
• Display 2 decimal places for fiat trading fees bisq#3973
• Tableview multiple rows checkbox column issue bisq#4008
• Add pricenode one-command installer script, systemd service, README bisq#3997
• Add and rename Portfolio History columns meaningfully. bisq#3785
• Moved one btc node to new host bisq#4010
• Log delayed payout tx bytes as soon as it's signed during trade init bisq#4040
• Allow refresh at least every 4 hours bisq#4044
• Limit system ram to 4GB bisq#4048
• Mute unnecessary logging and minor improvements bisq#4062
• Dump delayed txs of closed trades bisq#4066

Total USD amount for this remaining PRs: 400

USD amount requested: 888

Development

I was working mainly on the v1.2.8 release and following PRs were merged to master.

View all merged PRs

My merged PRs this month were created by reviewing the results of this GitHub Issues search query:
is:pr author:ripcurlx is:merged merged:2020-02-14..2020-03-16 sort:updated-desc

• Remove redundant closing of connection 180 USD
• Introduce CoinMarketCap stub to prevent error in existing clients 60 USD
• Add an empty dummy exchange rate to prevent warning logs 50 USD
• Accept empty config values 50 USD

Following PRs are minor or not within our priorities:

USD amount requested: 340

Following PRs are covered by other role efforts already, are minor or not a prioritiy:

• Add ARS as supported currency for MoneyGram 0 USD
• Handle SNAPSHOT versioning differently for rpm packages 0 USD
• Revert "Vote Reveal - Silent Fail" 0 USD

Testing

Test reporting for v1.2.8 release testing can be found here: https://bisq.ontestpad.com/project/1/folder/f56/report/?auth=28145f4fcbb5bc8d90372112bb3f00a9

Besides that I did additional smoke testing on Mainnet.

USD amount requested: 300 USD

Release

To improve transparency I'll add the release efforts now separately and not combined with the Bisq Desktop Maintainer role anymore. Documentation of the release process can be found here.

As the last three releases always required a hotfix shortly after based on specific OS setups we'll need to change release testing to include as many contributors as possible to at least start and smoke test a release candidate. I'll announce more details shortly after our next v1.2.9 hotfix release.

USD amount requested: 720 USD

Support

Monitoring the support channel during my L2 times and am investigation atm one issue where funds are still locked up although trades were completed successfully.
Helping out L1 support whenever needed.

Support cases:

• Funds are still locked after trade has been completed
• App not launching on Windows
• Locked funds after a successful trade

USD amount requested: 422 USD

Contributions in progress

I'm focusing right now on v1.2.9 and continue to get the PR workflow more streamlined.
Besides that I'm working on account signing improvements.

All efforts for my role as dev team lead (roughly occupied ~60% of my time) won't be put up for compensation until it is proven to have the success we are looking for.

Roles performed

• Bisq Desktop Maintainer: Bisq Maintainer roles#63 (comment) 1000 USD
• Analytics Maintainer: Analytics Maintainer roles#40 (comment) 80 USD
• Bitcoin Fullnode Operator: Bitcoin Node Operator roles#67 (comment) 50 USD
• GitHub Admin: GitHub Admin roles#16 (comment) 25 USD

USD amount requested for all these roles (see detailed amount for each role): 1155 USD

The following are roles where I play a secondary role, and do not (necessarily) do monthly reports:

• YouTube Admin: YouTube Admin roles#56
• Bisq Events Maintainer: Events Maintainer roles#65
• Growth Maintainer: Growth Maintainer roles#42
• Transifex Admin (secondary): Transifex Admin roles#20
• Bisq Design Maintainer: Bisq Design Maintainer roles#75 (primary, but on-hold because of no active work)

[cbeams]

Monitoring the support channel during my L2 times

The nature of L2 work should be push, not pull, as in L1 agents should ping you when help is needed; it shouldn't be required for you to monitor the support channel. Of course it's fine if you wish to do this, but I just want to check: how much of the 422 USD being requested for L2 work is because of active monitoring vs actually addressing L2 issues? I assume it's mostly the latter, but I was a bit surprised by the number being that high. Were these just difficult / time-consuming issues?

Other than this question, the request looks good to me.

[cbeams]

Since we're getting close to the deadline, I'd say submit your DAO proposal in any case, with my approval on this. Would be good to have the answer to the above, but we don't need to hold this up on it.

[sqrrm]

I can't speak for @ripcurlx's workload from L2 support issues but for me it's been very time consuming. It's hard to differentiate though since they're genuine bugs so some of that time will be documented as dev effort and some in the support section. I have found that L1 support handles most cases that can be handled without a dev rather well. The problem is that we still have too many bugs.

[ripcurlx]

I just want to check: how much of the 422 USD being requested for L2 work is because of active monitoring vs actually addressing L2 issues? I assume it's mostly the latter, but I was a bit surprised by the number being that high. Were these just difficult / time-consuming issues?

This was mainly caused by the locked up funds issue, which made lots of code reading and back and forth communication between the affected user necessary.

[ripcurlx]

Proposal transaction ID: dcc894597fb9fdb589c1ba78a3f7b413084795e216540024a51aed3e3c78b054

[MwithM]

closing as accepted