Skip to content
This repository has been archived by the owner on Jul 14, 2023. It is now read-only.

Member Request #9

Merged
merged 5 commits into from
Sep 29, 2022
Merged

Member Request #9

merged 5 commits into from
Sep 29, 2022

Conversation

shaunxw
Copy link
Contributor

@shaunxw shaunxw commented Sep 27, 2022

My earliest non-trivial PR:

Some notable PRs:

In addition to Polkadot/Substrate/Cumulus code contribution, I also

I would like to apply for Rank 2.

@rphmeier
Copy link
Collaborator

I believe I or II Dan is more appropriate,

A member at this rank should be a core part of the team. Clear demonstration
of knowledge of the protocol is crucial, but since the individual knowledge of the
protocol is unlikely to be complete then general knowledge acquisition and communication/
sharing is also very important. The individual should be becoming
deeply familiar with at least one major area of the protocol in their role as a builder and should be becoming increasingly
familiar with design considerations typical in protocol development

Whereas the requirement of III Dan that

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. They should be able and willing to support that which they built
given that it is running 24/7 on a public network.

has not been demonstrated sufficiently by the links above

@gavofyork
Copy link
Contributor

Indeed. I think the contributions back up a solid II Dan though, especially with the XCM simulator.

@shaunxw
Copy link
Contributor Author

shaunxw commented Sep 27, 2022

Thanks for the feedback. Updated my PR to apply for II Dan.

README.md Outdated Show resolved Hide resolved
@gavofyork gavofyork enabled auto-merge (squash) September 28, 2022 15:29
@gavofyork gavofyork merged commit 4b7b004 into polkadot-fellows:main Sep 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants