Member Request

[tifecool]

Hi!

I'm Boluwatife Bakre, a contributor to both the Substrate and Polkadot codebases. I began contributing in March 2022 and plan to continue contributing for the foreseeable future.

My first contribution

• Extract MAX_FINALITY_LAG constant from relay_chain_selection paritytech/polkadot#5159

My first non-trivial contribution

• Remove multiply_by_rational  paritytech/substrate#11598

Notable Contributions on Substrate

• Use parameter_types instead of thread_local for test-setup paritytech/substrate#12036
• nomination-pools: clear pool metadata after a pool is deleted. paritytech/substrate#12128

Notable Contributions on Polkadot

• Use a more typesafe approach for managing indexed data paritytech/polkadot#6150

Applying to rank I DAN.

[rrtti]

Hi @tifecool, thank you for your application!

The Manifesto 2.4 Audience and Non-Goals states:

It focusses on the sustenance and enrichment of technical expertise relevant to the Polkadot network primarily concerning the core protocol and its implementation. While members may engage in a number of activities beyond immediate technical work (designing, programming, debugging), the goal of the organisation is nonetheless that of building technical knowledge for the protocol.

Pure research, general education, public outreach, developer recruitment, management and mentorship may be incidental activities of some members but it must be understood that these should not constitute the primary contributions for a member to receive recognition.

For now, we explicitly include expertise surrounding parachain consensus, cross-chain message passing (xcmp, hrmp, dmp & ump), consensus algorithms concerning the Relay-chain (babe & grandpa) and any cryptographic data-structures, languages and apis specific to Polkadot.

Secondly, we include the Polkadot node implementation including peer networking protocols, topology strategies, synchronisation strategies and the internals of complete node implementations.

Thirdly, we include the Polkadot business-logic (aka the “runtime”), including frame internals, runtime and host apis, pallets utilised by Polkadot and its system chains. Finally, we also cover expertise concerning xcm, grandpa-based bridges and standard RPCs.

If you believe you are a protocol expert and long-term active core developer, please provide details of your three earliest substantial PRs to a Polkadot core repository (Substrate, Polkadot, Cumulus) as well as a list of any significant design and development contributions to core code. Other instances of the Fellowship are expected for ecosystem participants who are not protocol experts or long-term active core developers.

[tifecool]

I'd say:

• Remove multiply_by_rational  paritytech/substrate#11598
• Use parameter_types instead of thread_local for test-setup paritytech/substrate#12036
• nomination-pools: clear pool metadata after a pool is deleted. paritytech/substrate#12128
• Use a more typesafe approach for managing indexed data paritytech/polkadot#6150

Are my most substantial PRs

[bkchr]

@tifecool hey, I think you are on a good way, but you still need some more substinational prs.