PEP-62: Msa Reimbursement Request

[zaatar]

1. Where’s the value-add?
2. R&D work should be pre-approved
3. Extraneous considerations
4. Proposal premature

Where’s the value-add?

@b3n

let’s keep the focus here on a question of was there impact and what is the right reward for effort expended

@RawthiL

compensation should be to the perceived value of the contribution

In response to MSA’s request for help from GRIP with this proposal, he was advised that “your request for reimbursement will have more legs if in addition to identifying what you deem to be your contribution, you provide evidence to back up the usefulness/value of that contribution. Depending on the contribution in question this could include data following implementation of your feedback that can only be due to your feedback, or, you can quote people in the know.”

Unfortunately, however, this proposal provides little if any evidence of value-add or benefit (as distinct from the author’s subjective view). No hard data appears to be provided. (Nor is anyone with recognized expertise cited in support.) Such information is an absolute necessity.

@b3n

Let’s be pragmatic and just summarize the current state of this debate: Mostly agreed on some impact from MSA work.

Any such impact needs to be articulated and assessed with rigor. The DAO should not pay after-the-fact for R&D work unless its positive impact is proven, clearly set out, and comprehensible (for those without economic expertise).

@msa6867

If one uses the idea that only contributions that lead directly to DAO/PNF action should be compensated…

No. What counts is value-add.

R&D work should be pre-approved

@shane

I feel that moving forward all community and R&D work should go through PNF with established guidelines and accountability. Some work could be pre-approved by the DAO with established guidelines (like GRIP), but it would take a pre-approval vote.

@msa6867

I plan to request a POP from the PNF under the new GROW initiative once that gets rolled out in a few weeks

In addition to leveraging GROW, MSA is welcome to join GRIP where he can be compensated for his economic analysis on the same footing as other qualified DAO members. This will standardize the process for compensating expert feedback. If MSA joins GRIP, people who want his feedback can request it in advance, rather than get it unsolicited and see him ask the DAO to pay for it after-the-fact.

Extraneous considerations

@msa6867

That’s all I’m asking for in this proposal. $100/hr, or even slightly less, for the work shown in Table 1 only that led to direct DAO action. Nothing in addition to that for anything in Table 2 and Table 3, which are shown for supplemental purposes and only factor into the fourth evaluation methodology labeled " Using an hourly contract model"

If MSA is seeking reimbursement only for work reflected in Table 1, Tables 2 and 3 are irrelevant. They should be removed from the PEP along with “Contribution Details for Table 2” and “Research Thread Details for Table 3."

Proposal Premature

@msa6867

The pre-proposal category [is]… a place to gauge the larger community sentiment on … size of reimbursement being requested (e.g., PEPs). … In addition, community sentiment can be gauged for a…proposed reimbursement by presenting a case for the topic with less formality and rigor…24hr or 48hr straw polls could be useful in this context.

The pre-proposal category is meant as a starting point for proposals in order to facilitate review and input from the entire community. Posting to the pre-proposal category usually leads to changes that make proposals better and more coherent. It’s a win-win for the author and the DAO. (While authors can ask GRIP to give feedback in the pre-proposal category, this is optional.)

With a straw poll now seemingly in the works, the compensation being sought by MSA’s proposal is up in the air. This proposal should have been submitted in the Forum as a pre-proposal first. The messy, contentious debate, the imminent straw poll, and the inevitable amendments could all have taken place prior to floating this PEP.