[Retain at I Dan] Retain clangenb at rank 1

No context provided.
Reply
Up
Share

Evidence for Retention

Evidence-0002: Retention at Rank 1

Report Date Date of submission (2024/10/15)
Submitted by Christian Langenbacher

Member details

  • Matrix username: @clang:matrix.org
  • Polkadot address: 16YCL3UVpVWQLGW3p3Zx4k5WAEp9W1DwdDnxAbyAaPxVxnp3
  • Current rank: 1
  • Date of initial induction: 2024/03/27
  • Date of last report: 2024/07/02
  • Area(s) of Expertise/Interest: Parachain Builder, Runtime, Clients

Reporting period

  • Start date: 2024/07/02
  • End date: 2024/10/15

Evidence

My sole code contribution this time, was identifying, reproducing, and fixing a bug in the polkadot-sdk, which resulted in a build error under some circumstances due to an unhygenic widely-used macro, namely the format_runtime_string! macro, see the fix in PR #5632. This bug has indeed affected some parachain teams, and was backported into both stable2407 and stable2409.

I don't have any other hard evidence, but naturally, I have continued staying active in the ecosystem mostly as parachain a builder in Encointer, Integritee and Ajuna.

Voting record

Provide your voting record in relation to required thresholds for your rank.

Ranks Activity thresholds Agreement thresholds Member's voting activities Comments
I 90% N/A 2 eligible referenda: #117 #150 which missed my attention
II 80% N/A
III 70% 100%
IV 60% 90%
V 50% 80%
VI 40% 70%

Misc

  • Question(s):

  • Concern(s):

  • Comment(s):

    • As mentioned above, I was unaware that I can vote on referenda with rank I. I am now monitoring the referenda to prevent this from happening again.
    • Even though I am only rank I and I consider the bugfix above quite valuable, I think I should have more evidences (although my total salary claimed is still low with 3.33K USDT). I have periodically been checking for other small issues in the relevant repositories, but couldn't find suitable ones. I will become more proactive in the community to identify my proper role in the fellowship.
Status
Decision14d
Confirmation
1hr
Attempts
1
Tally
100%Aye
62.0%Threshold
0%Nay
Aye10
Nay0
  • 0.0%
  • 0.0%

    Threshold

  • 0.0%
Bare Aye3
Max Voters20
All votes
Check how referenda works here.
Call
Metadata
Timeline6
Comments

I am not sure if the magnitude here is sufficient as rank defence - going to let higher ranks vote first.

Reply
Up

Thank you for your proactive statement, which I completely understand. To be honest, I agree that improvements are necessary, and I am committed to making those changes. Unfortunately, due to being fully employed elsewhere (in the ecosystem), I neglected my fellowship duties more than I should have, not realizing how quickly time passed.

Moreover, it was only recently established that non-Encointer work does not qualify as valid fellowship evidence. Because of this, I hadn't mentioned it before, but I did contribute by upgrading Encointer's runtime Polkadot dependencies, whenever it was necessary.

I’m not trying to influence your deferred vote but rather providing additional context in case someone else is reading. I fully support waiting for others to vote.

Reply
Up

Hey there, I would like to note that I am indeed living up to my promised commitment. I have picked up some work in the polkadot-sdk repository, see #6302, #6301, #6300, #6299, #6294, #6291.

These are all maintenance PRs. They migrate the respective pallet's benchmarks to the Benchmark V2 syntax. I hope I can sway some minds with this comment to vote aye, as there hasn't been any resonance so far.

Naturally, I will not include those PRs in my next evaluation as evidence. I consider this overdue homework. :)

Reply
Up