Member request

[aurexav]

Hi, I'm Xavier Lau.
I am a core developer from Darwinia Network, having worked on Substrate and Polkadot ecosystem for the last three years.

I think I should be in the rank range of 2~3.

---

I'm:

• top 0.82% this quarter on the substrate.stackexchange.
• the author of array-bytes, and it's so proud to be a dependency of Substrate. PR
• the author of subalfred. Its goal is to be an all-in-one Substrate development toolbox. And it gets some stars from the parity core developers. (thanks, guys)

I/my team found:

• a non-deterministic behavior on Substrate. Due to security issues, @gavofyork suggests I delete the detail. So the issue is empty.
• some weird code during the Polkadot code review and reported to @kianenigma. PR
• the MMR leaves can be overwritten by the forks and reported to @tomusdrw. Issue

My PR(s) related to the protocol:

• Support MMR Pruning paritytech/substrate#9700

Most of the time, I'm doing the code review.
A little bit of shame, I don't have a lot of PRs contributions.

---

BTW, I format the markdown and sort the members by their names.

[rphmeier]

Xavier,

Thanks for the request. You're a longstanding member of the community who I recognize as a major contributor to stackexchange and in developer chats. Still, the Fellowship at the moment is constrained to core protocol contributions, and in that respect I do not see enough of a record of contribution to merit III or IV Dan. I would suggest applying for I or II Dan and to re-evaluate after some deeper protocol contributions.

Quoting from III Dan requirements:

As a foundational grade, a Fellow represents both a ceiling and a floor: becoming
a Fellow indicates the individual has enough knowledge and skill to build
substantial protocol components (i.e. all but the major protocol components,
e.g. a pallet or 2-10,000 line crate) alone and with high expectations that they
will be completed correctly and to a high standard

[aurexav]

Xavier,

Thanks for the request. You're a longstanding member of the community who I recognize as a major contributor to stackexchange and in developer chats. Still, the Fellowship at the moment is constrained to core protocol contributions, and in that respect I do not see enough of a record of contribution to merit III or IV Dan. I would suggest applying for I or II Dan and to re-evaluate after some deeper protocol contributions.

Quoting from III Dan requirements:

As a foundational grade, a Fellow represents both a ceiling and a floor: becoming
a Fellow indicates the individual has enough knowledge and skill to build
substantial protocol components (i.e. all but the major protocol components,
e.g. a pallet or 2-10,000 line crate) alone and with high expectations that they
will be completed correctly and to a high standard

Updated.

Thank you, re-formatting addressed.

[gavofyork]

Mis-read and thought this was an application for I Dan - that I would back happily.

[jacogr]

I'm a huge fan of the work I have been seeing, especially around the (mostly) thankless efforts on SE.

Having said that, I'm also on agreement on a I Dan request.

Based on the II Dan requirements, I do feel we are missing the "assisted in implementing a major component" part of the requirement.

[kianenigma]

Late to the decision, but indeed wanted to appreciate numerous valuable and insightful bug reports that I have received from @AurevoirXavier over the years 👍