-
Notifications
You must be signed in to change notification settings - Fork 59
20180704 RChain Active Member Meeting #823
Comments
How is this $800 worth/1 week of effort? Generally, I haven't seen an agenda before these meetings, and the work announcing in chat and taking minutes is maybe an hour and a half of write-up and review? Am I missing something on this? |
I'm inclined to reward @David405 for some agenda preparation and note-taking. Perhaps the update from @kitblake on bounty / marketing connections was valuable. But I just reviewed the action items and aside from my follow-up on the slashing bug in #261, I see no progress on any of them. So the rest of the meeting was just sound and fury. (I'm updating the measure of completion.) All told, maybe worth $100 or $150. |
@deannald the budget used to be $2000 but was reduced by the community to $800. The reward is distributed according to the participation and the efforts made by collaborator to make the meeting a success. What is your opinion? |
@Tonyprisca13 - Depends really on what was produced for that week. Generally, if no agenda is set up ahead of time and there is some note taking and a few announcements, dckc's quote of $100 - $150 seems like reasonable compensation. If there is additional work done that's being done and can be identified, then that number would potentially change. |
I would prefer it has a fixed limit on the budget so if there's an additional work, it can be made to reflect on the budget. Am not the sole opinion on this, I would be adding this discussion to the agenda of the meeting this week. |
No. I'm traveling to a funeral. |
Ok. Sorry for your lost please accept my condolence. |
ZOOM LINK FOR RAM MEETING
https://zoom.us/j/197490909
17:00 UTC (one hour BEFORE Greg's Debrief)
Sydney +11, Beijing +8, Greece +3, Amsterdam +2, Lagos +1,
New York -4, Seattle -7
Estimated Budget of Task: $150
Estimated Timeline Required to Complete the Task: 1week
Measure of Completion:
Legal
Task Submitter shall not submit Tasks that will involve RHOC being transacted in any manner that (i) jeopardizes RHOC’s status as a software access token or other relevant and applicable description of the RHOC as an “asset”—not a security— or (2) violates, in any manner, applicable U.S. Securities laws.
The text was updated successfully, but these errors were encountered: