I really like this proposal… it identifies a need, proposes a good solution, has assembled a great team, and can benefit all participants in the network - proposers, voters, debaters and lurkers.
My feedback relates to implementation:
-
I agree with @JackALaing that we should be inclusive to anyone who can complement this team with additional talent and insight. I support a lite permission mechanism where anyone can opt-in to participate
-
I strongly believe experimentation and “intelligent failure” are key to success in web3 and support a 3 month trial. But learning is maximised by having some pre-defined ideas/hypothesis about success, along with rigorous measurement and regular feedback. I think a clearer definition of success is needed including how this would be measured (imo qualitative measures are completely fine but the mechanism should be expressed in advance). I also hope the team can report monthly on outcomes, learning and rewards which would increase feedback, transparency and iteration cycle velocity
-
Backchannels: Further to the points above re backchannels, as much work as possible should be in the open and through the forum or some open space (we can help create an open Notion workspace for this team to collaborate in). I think fees paid for any type of “private consulting” is not a good precedent as the work is not really verifiable.
-
Fees per hour, after the fact, up to a cap: I think this is also a bad precedent. While I think these contributors have unimpeachable integrity it would be better to set parameters for the experiment that are not based on hours, even if this requires us to be more generous or expect a lower ROI in the first month/s. This is another element to the trial/experiment. One mechanism could be to fund $X,000 of USD or POKT into a Coordinape circle which the team can allocate bottom up as they see appropriate. Against this, the community can review each month if the output matches the total fund and the team can request more funds if needed. I am more than happy to establish and help operate this mechanism if desired
Thanks for this proposal - I really hope it gets passed (with these small adjustments to implementation)