summaryrefslogtreecommitdiff
path: root/elections
diff options
context:
space:
mode:
authorNoah Kantrowitz <noah@coderanger.net>2022-09-05 23:42:43 -0700
committerNoah Kantrowitz <noah@coderanger.net>2022-09-05 23:42:43 -0700
commit83dc74e1c78ec48da4ea0010e985d0a9c5529533 (patch)
tree1be8037bde410b21d26fdbe8da3605bd17813820 /elections
parent2a5567e4509aaa2e990f944f88dff211876ce985 (diff)
🎨 Fix detached link syntax.
Diffstat (limited to 'elections')
-rw-r--r--elections/steering/2022/candidate-bentheelder.md30
-rw-r--r--elections/steering/2022/candidate-mrbobbytables.md22
2 files changed, 26 insertions, 26 deletions
diff --git a/elections/steering/2022/candidate-bentheelder.md b/elections/steering/2022/candidate-bentheelder.md
index 14c3ed66..d598267f 100644
--- a/elections/steering/2022/candidate-bentheelder.md
+++ b/elections/steering/2022/candidate-bentheelder.md
@@ -20,26 +20,26 @@ But you'll also find me contributing across the project.
## What I have done
-I first got involved in Kubernetes in the 2015, just before 1.0, as a
-[Google Summer of Code] student. during which time I developed the initial
-`iptables` kube-proxy backend, which replaced the inefficient userspace backend
+I first got involved in Kubernetes in the 2015, just before 1.0, as a
+[Google Summer of Code][Google Summer of Code] student. during which time I developed the initial
+`iptables` kube-proxy backend, which replaced the inefficient userspace backend
by default in v1.2.
-In 2017 I graduated and took up full time Kubernetes development at Google as a
-junior engineer working primarily on SIG Testing, where I've worked to improve
+In 2017 I graduated and took up full time Kubernetes development at Google as a
+junior engineer working primarily on SIG Testing, where I've worked to improve
the contributor experience.
-I developed [KIND] to make e2e testing Kubernetes faster and
+I developed [KIND][KIND] to make e2e testing Kubernetes faster and
locally reproducible without cloud access.
-I led the effort to consolidate on a single build system and eliminate bazel to
+I led the effort to consolidate on a single build system and eliminate bazel to
reduce contributor friction.
I worked with SIG docs to create and pilot a pattern for subprojects to
officially host their own docs within the project for docs that do not belong
-on the main kubernetes.io site, like [kind.sigs.k8s.io].
+on the main kubernetes.io site, like [kind.sigs.k8s.io][kind.sigs.k8s.io].
I was also release lead shadow on the 1.14 release.
-I've been one of the [most active contributors] to the project over the years and
-I've since won the 2020 CNCF [Top Committer Award] for my extensive contributions.
+I've been one of the [most active contributors][most active contributors] to the project over the years and
+I've since won the 2020 CNCF [Top Committer Award][Top Committer Award] for my extensive contributions.
You will find me active all across the project contributing where I can. I've
spent a lot of time maintaining the project's infra and helping transition older
@@ -51,8 +51,8 @@ like the project's CI, DNS, etc.
## What I'll do
-I am passionate about the Kubernetes community and I will do everything in my
-power to uphold and strengthen it's health, [values], and inclusivity.
+I am passionate about the Kubernetes community and I will do everything in my
+power to uphold and strengthen it's health, [values][values], and inclusivity.
Steering represents:
- An important interface between the project and the CNCF
@@ -62,11 +62,11 @@ Steering represents:
Steering is about people, governance, and long term project health.
Steering is *not* about arbitrating technical decisions, which are left to the SIGs.
-Within that scope, I will bring my perspective as someone who has risen from an
+Within that scope, I will bring my perspective as someone who has risen from an
inexperienced student contributor to a leader to help guide and enact processes
and policies that prioritize community health.
-In particular: I believe we need to do better enabling
+In particular: I believe we need to do better enabling
future leaders / contributor growth, and being inclusive of our existing global,
diverse contributor base. We need to put more emphasis on sustainability, and
I believe steering is well positioned to do so.
@@ -74,7 +74,7 @@ I believe steering is well positioned to do so.
## Resources About Me
- [elder.dev/about](https://elder.dev/aboput)
- - You can find a more personal bio, my [speaking] and more here
+ - You can find a more personal bio, my [speaking][speaking] and more here
- [twitter.com/BenTheElder](https://twitter.com/BenTheElder)
[most active contributors]: https://k8s.devstats.cncf.io/d/13/developer-activity-counts-by-repository-group?orgId=1
diff --git a/elections/steering/2022/candidate-mrbobbytables.md b/elections/steering/2022/candidate-mrbobbytables.md
index 14cedfd4..1a1e2268 100644
--- a/elections/steering/2022/candidate-mrbobbytables.md
+++ b/elections/steering/2022/candidate-mrbobbytables.md
@@ -19,31 +19,31 @@ Most of my tenure as a contributor in the project has been focused on growing
and sustaining a safe & healthy contributor community within the project.
A few notable things include:
-- [Defined policy around inactive members], and routinely pruned OWNERS to
+- [Defined policy around inactive members][Defined policy around inactive members], and routinely pruned OWNERS to
ensure an active reviewer/approver pool.
-- Rolled out [improved triage automation & workflow] practices across the org.
+- Rolled out [improved triage automation & workflow][improved triage automation & workflow] practices across the org.
- I have helped run every Contributor Summit since 2018, and have served as lead
- for [NA 2021], [NA 2022] along with leading both virtual Celebrations
+ for [NA 2021][NA 2021], [NA 2022][NA 2022] along with leading both virtual Celebrations
([1][c1], [2][c2]) during the Pandemic.
-- Trusted member of the [GitHub Admin Team], including acting as representative
+- Trusted member of the [GitHub Admin Team][GitHub Admin Team], including acting as representative
to GitHub for the project.
-- [Moderator of all our communications platforms]
+- [Moderator of all our communications platforms][Moderator of all our communications platforms]
- Leading the development of an online "New Contributor Course" to serve as
a replacement for the New Contributor Workshop (Slated to launch before
KubeCon)
-- As a represenative of the Steering Committee, presented a [Keynote talk] with
+- As a represenative of the Steering Committee, presented a [Keynote talk][Keynote talk] with
Aeva Black (@AevaOnline) from the Code of Conduct Committee @ KubeCon 2019 on
shaping the Kubernetes Community Culture.
-- Dogfooding leadership succession mentoring by co-leading in the
- [SIG ContribEx lead shadow program], bringing on 6 potential future chairs
+- Dogfooding leadership succession mentoring by co-leading in the
+ [SIG ContribEx lead shadow program][SIG ContribEx lead shadow program], bringing on 6 potential future chairs
and TLs.
Outside of Kubernetes, I have also been involved heavily with the CNCF as an
-[Ambassador], co-chair of the [Research User Group], and a Program Committee
+[Ambassador][Ambassador], co-chair of the [Research User Group], and a Program Committee
Member of KubeCon and various other colo events since 2018.
My efforts both for Kubernetes and the broader community were recognized in
-2019 when I received the [CNCF Chop Wood Carry Water Award].
+2019 when I received the [CNCF Chop Wood Carry Water Award][CNCF Chop Wood Carry Water Award].
[NA 2021]: https://www.kubernetes.dev/events/2021/kcsna/
[NA 2022]: https://www.kubernetes.dev/events/2022/kcsna/
@@ -71,7 +71,7 @@ understand the frustrations and boons that have come with each role.
These experiences come heavily into play as we look toward developing
strategies for the project's long-term success. Steering has recognized that the
-time of the [9 to 5 contributor] has past, and we need to develop policies and
+time of the [9 to 5 contributor][9 to 5 contributor] has past, and we need to develop policies and
processes to ensure we can continue to grow new contributors, reviewers,
approvers, and our future SIG/WG/Committee leaders.