Currently as we have discussed changes in terms of how we pay contributors, based off of their focuses, this proposal is for E to continue with his research alongside feedback collection from the community, to form a well suitable yam core development plan and move forward with it, scoped with updated docs that were started on, this proposal also includes other recurring focuses that E normally handles.
Background: Contributions E has made to Yam are numerous from the very beginning of the launch to date, focusing mostly on its core development, stability and security with facilitating and assisting every contributor we ever had on Yam. E believes for yam to gain further values, on a protocol level it must accomplish several milestones and be up to the level and base standards to lead by example (as uniswap aave compound optimism uma chainlink and others …), which from comes the main purpose of the yam dev documents that E has been working on and recently posted for further feedback collection. E believe going through this path will give yam a solid core yet a scalable and attractive model with value add long term.
For June and July, as i have already begun will continue progressing on figuring out the long term core vision of the yam protocol development plan as outlined on the Yam Core Development, Yam Protocol Multichain and the linked docs. My main objective prior getting into any dev work is to complete forming the mentioned with further planning, specifications and timeline updates. Which from and once fully scoped, i am going to propose and proceed with to entirely start focusing on.
For the next 3 quarters (Q3, Q4 2022, Q1 2023), i will continue maintaining infrastructure, services upkeep and the onchain activity in terms of proposal contracts development, testing, deployments, proposing, execution and following up through, as well for basic assistance, data collection from snapshots and individuals to progress forward. This however does not include things that consists of feature implementation, for example the creation of another contract or a focus that it can relate to, although i will give a feedback to whichever extent of my ability in terms of ideating around a feature request. This includes the usual of being there and help facilitate things.
For June and July:
Recurring, after finishing with (A.):
@e: Note i am pushing to finalize the plan as mentioned in A. and sooner, to then start with it around July, taking into account any changes needed which for i would revisit this section with an update accordingly. Now focusing on both Yam Core Development (Planning) and Yam Infrastructure, then once finished with A. around July i will proceed with the upcoming development while i keep maintaining the Yam Infrastructure.
Proceeding with an onchain proposal to send E the related comps as specified above.