PEP-45: Get a GRIP: Group to Review and Improve Proposals

Thank you Jack, Ben, and Dermot for your comments. Based on your feedback, and input from the GRIP team, two aspects of PEP-45 have been revised as follows:
• a monthly budget of $5,000 will be sought from the DAO, and
• anyone deemed qualified will be able to join GRIP

I discuss these revisions in detail below. Following that I respond to your comments on back channels and pre-proposal feedback from non-GRIP members.

Please keep in mind that PEP-45 is for a three-month trial period. If we don’t get it absolutely right out of the gate, we can make changes in the follow-up proposal for renewal of GRIP.

Payment

As we chart new territory, finding the best funding mechanism is a challenge. I accept the above suggestion that a fixed amount be granted monthly to GRIP. A $5,000 cap, as Dermot proposes, is reasonable.

At the end of each month, GRIP will disburse the budget as it deems appropriate. It will report on the amount paid to each member with details on the work performed. This will enable the community to assess whether it got its money’s worth. If over the three-month life of this project, appropriate compensation for GRIP contributions is over $15,000, a request for further funding can be submitted to the DAO, which accords with Ben’s suggestion that “the team can request more funds if needed.”

Conversely, if the contributions come under $15,000, the surplus will be returned to the DAO or, if GRIP renews, roll over to the next funding period, reducing the subsequent DAO grant(s) accordingly.

As noted, GRIP will determine how it distributes payment. I prefer paying people for their time and at the same rate. Most work will be in the open, so folks can see the GRIP members’ individual contributions and what they’re getting paid for. While there’s a trust component as regards behind-the-scenes work and in respect to how much time goes into work that’s visible, paying people for their time is fairest. Allocating payment based on “how we view each other’s input and value” is too subjective. If you’re on GRIP, your contribution is treated as equal.

Coordinape is not needed; it adds unnecessary complication.

How to Join GRIP

I agree with Dermot that new members should be eligible to join once they demonstrate they have sufficient skill/knowledge/expertise and existing members of the group vouch for them. (Again, however, Coordinape is unnecessary.) A pool or roster of folks available to serve on GRIP could thus be created.

To avoid GRIP-team bloat, the number of acting team members could be limited to, or near, its current size. To ensure that it’s not a “privileged” group, active membership/participation could be rotated every three months among all interested members on the roster.

This also would make paid contribution opportunities at the pre-proposal stage available to everyone who’s qualified - albeit on a rotating basis, thereby addressing one of Jack’s concerns.

Feedback on Pre-proposals From Outside GRIP Team

Jack notes that not paying everyone for their pre-proposal contributions “would be a disservice to ourselves because we would be losing out on valuable contributions and insights.” He echoes concerns raised by Dermot:

In the main, the channel for feedback on pre-proposals will be the Pre-Proposal category in the Forum. Anyone can participate and add their input. Some community members might do so to build a reputation and establish their credentials, perhaps in order to join GRIP. If a GRIP roster is created with active paid roles rotated quarterly, the community will know that the pool of “relevant people to seek counsel from” includes inactive roster members – not just the acting GRIP team. Finally, as I note in this proposal: “If people care about Pocket Network and have a stake in its future, they will continue to weigh in on how best to grow the project and spend the treasury’s funds.”

Back Channels

Jinx has addressed this concern at length. I will add but a few comments.

Back Door to PNI

I agree. However, in the event that GRIP needs to consult the PNI Protocol and Engineering teams, it will try and do so openly in the Pre-Proposal category.

Culture of Constructive Feedback

While PEP-45 does allow for private contact between GRIP and would-be contributors – it does not encourage it. Justifications for a private-contact option are that it will hearten those who might need a nudge and those who might otherwise refrain from contributing. GRIP will encourage contributors who seek private advice to transition as soon as possible to open dialogue in the Pre-Proposal category.

Setting an Example

It’s anticipated that most or nearly all of GRIP’s work will be visible in the Forum Pre-Proposal and proposal categories where the community will be able to witness how the team “works together.”

2 Likes