Bounty Progress Report: Quarter 2

[TrenchFloat]

Benefit to RChain

Quarterly reports foster the bounty system's accountability to the goals of the coop and explicitly compare its expenses to its accomplishments.

Objective

• Q2 Bounty Report

• For reference: Retrospective Report

Create a report covering May, June, and anything in April that was missing from the last report including the following details of each issue label:

1. Financial data detailing the label's expenses
2. Accomplishments outside the bounty system: where the money went
3. Problems encountered
4. Actions being taken to fix problems

In the retrospective report's issue HJ wrote "Greg @leithaus will formulate the objectives and evaluation criteria of the bounty program..." Greg is still working on these, so for this report let's continue with the objectives and evaluation criteria we have: Precedence for budgeting similar issues, value of work as opposed to time spent, direct relation to goals of the coop, and fair rewards for individuals.

HJ also wrote "This is the first management report, the next one will be better."

Let's make this one better.

Budget

Estimated Budget of Task: $950
Development, Governance, Marketing, Translation, Operations: $100 each
Branding, Events, Education, Community Building: $60 each
Financial Data: $50 @dckc and @TrenchFloat worked together
Coordination, Overview, and Conclusion: $160 to @TrenchFloat

Estimated Timeline Required to Complete the Task: EDIT: August 6th

Measure of Completion: Report includes all categories mentioned in budget proposal, accounting data, and a conclusion, and is submitted to the board.

[TrenchFloat]

@jimscarver @rayzor @makys @barneycinnamon GitHub only lets me have 10 assignees - please help us out with your respective sections!

[jimscarver]

I already added a governance section. Perhaps we need to talk about what more is needed.

[dckc]

@TrenchFloat , @jimscarver filled out a governance section in the report Alan started a while ago.

I suggest that the report you just started is superfluous. Please mark it obsolete with a link to the existing one.

[TrenchFloat]

Oops. Thanks for the pointer. Changing the link now.

[dckc]

@TrenchFloat asked me to build a table of the expenses by label like last time.

I started to do it only to realize that I didn't save the code I cobbled together to do it last time.

Before I get into that, I remembered the feature we need that gets me out of the critical path of these things: the ability for anybody to get a dump of the database at any time. So that's on the sync page now. Example result:

db dump result: 2018-07-26 20:36:58.sql.gz 0.21 Mb

Note that db dumps aren't guaranteed to stay around more than 15 minutes.

[dckc]

@TrenchFloat due to VotingTrouble and the like, I'm struggling to find time and no longer confident I can do my part by Aug 4. Here's hoping, though.

[TrenchFloat]

I took the Greeter section off the report (only issues since March has no budget), slightly expanded the budget to account for the overview and conclusion sections, and postponed 2 days to Tuesday, August 6th.

Still waiting to hear back from @kennyrowe if he'll present to the board.

[dckc]

@TrenchFloat thanks for getting started on this; finishing it up was pretty straightfoward:

• Q2 Financial Data

[Ojimadu]

I think there is a mix up in the numbers on the sheet. Some budgets were not fully claimed or voted for and this affects the actual amount paid out. Like issue #724 the 4k budget that was voted was not fully claimed hence another vote was effected the following month to those that could not claim their rewards but these reflected on the sheet.
Is there a way we can sum the budget based on the amount claimed i.e rewards with 3 or more votes?

[dckc]

The sheet is all based on actual rewards, not budgets. What do you see that suggests otherwise?

[Ojimadu]

In issue #724 for May, only 38% of the rewards was claimed while the remainder of the rewards was claimed in May. But the sheet recorded 4k and 2480 vote for May and June respectively.

[dckc]

Unfortunately, "sheet" is used both for entire google sheets as well as named tabs within those sheets, so "the sheet" may refer to any number of things. Where exactly do you see any rewards for #724 in April?

There were $4,000.00 in May:

worker	reward
cmrc2018	$1,000.00
cmycaro	$480.00
taobixin	$1,000.00
TiffWang	$520.00
wangjia184	$1,000.00

and $2,480.00 in June:

worker	reward
cmrc2018	$1,000.00
cmycaro	$480.00
taobixin	$1,000.00

I checked rewards.rchain.coop for 724 as well as the Rewards Detail tab in the Q2 google sheet ( which just imports from rewards.rchain.coop; it would be a bug in Google's IMPORTDATA function if there were any differences there).

In the Label Summary tab, we see the same results (reported under each of the issue's labels):

Label	Issue	Pay Period	Reward	Title
China	724	2018-05	$4,000.00	RChain Chinese Community First Meetup
China	724	2018-06	$2,480.00	RChain Chinese Community First Meetup
Events	724	2018-05	$4,000.00	RChain Chinese Community First Meetup
Events	724	2018-06	$2,480.00	RChain Chinese Community First Meetup

[Ojimadu]

My bad. The reward I was referring to was for May and June rather than April.

Only two people received a reward for the issue in May because the votes for other participants were not complete hence another vote was done in June for the remaining collaborators to claim their reward. The actual reward that went out in May was $1520 and June $2480 summing to $4000 total.

I suppose this error is coming from the Web app as it counts the voter quantity to include everyone that voted on the issue irrespective of whether the vote counts or not.

[dckc]

Where are you getting your information, exactly? What are you looking at? Share a screenshot or something?

What suggests that "Only two people received a reward for the issue in May"? Where did you get the number $1520? I see no error. "the Web app ... counts the voter quantity to include everyone that voted on the issue irrespective of whether the vote counts or not" makes no sense; the Web voter quantity is defined as those votes that count.

[Ojimadu]

This comment. Also looking at the rewards app for this issue notice that for the pay period 201805 only the weighted votes appear in the "voter" column but the voter quantity is higher indicating that non weighted votes were counted in the "voter quantity" column.

[dckc]

OK... that's definitely a bug. I'm limiting access to the Q2 spreadsheet until I get it figured out.

voter_qty	voters
3	Ojimadu1, sportshark1
3	sportshark*1
4	sportshark1, zsluedem3
4	Ojimadu1, sportshark1, zsluedem*3
4	Ojimadu1, sportshark1, zsluedem*3

[TrenchFloat]

Anyone know how to get in touch with Kenny (discord isn't working) or another board member to have this passed along to the board?

[dckc]

I hope you can hold off until I can fix the accounting for May (#799).

[allancto]

@TrenchFloat I think it should be fine to wait, there are so many critical events going on right now that it's not likely to be read right immediately anyway. Another approach is to share the document as a "link only" with notes as to what remains to be edited. As far as providing it to Kenny and our board, you may want to simply paste the link in #board2coop, Kenny monitors that pretty closely.

[TrenchFloat]

Good points, Allan. We'll take a breather until we have financial data, then provide a completed report.

[dckc]

OK, I'm reasonably confident about the Q2 numbers now. I restored the sharing settings so everybody can see.

pay_period	sum reward_usd	Members
2018-04	$91,796.00	64
2018-05	$60,677.00	56
2018-06	$85,790.00	62
Q2	$238,263.00	82

p.s. Darn it; I found 17 conflicts between the June frozen rewards and a July 22 snapshot from #799.