Fellowship Retention H1 2024

I split my work into inititives that are driven by my role in Parity, and the Community. They mostly align, but it is useful to separate them.

This is my main reasoning for not claiming my fellowship salary so far. As the proportion of my work directly for the community increase, I might consider starting to claim my salary in an on-demand basis to reflect my work for the community. I will keep this updated in my membership manifesto in PA.

Community

• RFC89 Flexible Inflation
• Instructor in PBA5 Singapore
• Ample participation in day to day governance activities of Fellowship
  • Proudly inducted many new members to the fellowship.
• Publicity
  • Polkadot Build Horizon
    • https://blog.kianenigma.nl/posts/tech/polkadot-s-build-horizon/
    • https://x.com/kianenigma/status/1761736097128677585
  • TEACHMEDEFI Podcast on JAM
  • JAM watch-group and analysis with PolytopeLabs
  • JAM AMA In OpenGuild

Parity

• Wishlist Issues to gather user feedback
  • https://github.com/paritytech/polkadot-sdk/issues/3901
  • https://github.com/paritytech/polkadot-sdk/issues/3900
  • Thanks to Joshua: https://github.com/joshuacheong/wishlist-tracker
• Steps toward (re)documenting core components of FRAME/Substrate in polakdot-sdk-docs
  • OCW
  • Pallet Coupling
  • FRAME Origin
  • FRAME Logging
  • Custom RPC and Host Function
• omni-node
  • I have prototyped the implementation to resolve possible blockers and am atm supervising further implementation and integration
  • https://forum.polkadot.network/t/polkadot-parachain-omni-node-gathering-ideas-and-feedback/7823
• Cleaning up polkadot-sdk Templates
  • https://github.com/paritytech/polkadot-sdk/issues/3155
  • https://github.com/paritytech/polkadot-sdk/pull/3460
• Other than the above, I am leading the efforts around FRAME and Staking team within Parity. The output of this can be seen in the work done by other great developers: Oliver, Liam, Nikhil, Ankan and Goncalo, all of whom are part of the fellowship now.