Threshold
Prices of developers in the fellowship for a comparison. Bare in mind they are in USD while in this proposal they are in EUR. It seems like a grift, these results can be achieved for way less funds and it is sad to see long time members trying to maximize their profits on the account of the treasury.
Hello and thank you for the referendum. Currently we are facing a situation where we have low funds in the treasury so cutting non essential projects seems necessary. However, we consider PAPI a very necessary project due to the obsolescence of our current developer console polkadot.js and for that reason we have voted AYE already.
However, the high salaries is not only a concern of ours but of many others so we would like to respectfully request a longer and more reasonable period to support than to January 2025. This will not only help the treasury directly but also to set an example to keep a slightly tighter belt for other teams during these important times. NAYing this proposal and delaying the funds is the least desirable option for all parties so for that reason we would like to know if it's possible to review the salaries through a longer development financing duration while the referendum is live.
I believe this is a promising project, and I appreciate the work that has gone into it. However, I have a few concerns that align with SAXEMBERG's perspective:
Funding Duration and Evaluation: How long do you anticipate the treasury should fund the development and maintenance of PAPI? Could you provide a tentative evaluation of the total funding required (e.g., $2M, $3M)? A clearer understanding of the long-term financial commitment would help the treasury make a more informed decision.
Contingency Plan: In the event that the community does not approve this proposal, what are your plans for moving forward? Having a contingency plan might demonstrate preparedness and adaptability.
Clarity on Deliverables: A significant portion of the funding is allocated to PAPI SDKs and PAPI Actions, yet the descriptions of these deliverables seem brief or unclear. Do you believe providing a more detailed technical description or even a proof of concept could help the community better assess the potential impact and value of these components?
I've been using papi for the past couple weeks, and after using polkadot.js/api for the past 5 years, it's eye opening.
This team is talented, motivated, very reactive on Github, and helpful.
The Developer experience is stellar. Strongly typed api is working very well. I'm certain that this is the future of Polkadot Dapp development, and it will enable much better applications and products. I'm porting my products to it as we speak, and I'm not looking back.
The tool is truly mindblowing and the team the best for developing it. The ecosystem dapps landscape was already revolutionized with their automatic type generation based on the metadata. They didn't stop there though, they kept on adding amazing features we didn't know were possible, like checking whether or not your dapp is compatible with the on-chain runtime and adapt automatically to runtime upgrades. Can't wait to see what they achieve next.
PAPI is the tool the ecosystem needs. Keep up the good work.