Website: SIG Docs co-chair transition: Bradamant3 and kbarnard10

[zacharysarah]

SIG Docs co-chair transition

In the 10 December 2019 SIG Docs weekly meeting, @Bradamant3 announced that she is stepping down as SIG Docs co-chair and will become a chair emeritus.

@Bradamant3 nominated @kbarnard10 to replace her; @kbarnard10 accepted during the same meeting.

Transition date

Without further input, lazy consensus is to transition on January 15, 2020.

Procedures for changing co-chairs

SIG Docs follows the procedure for transitions in our community charter:

This charter adheres to the conventions described in the Kubernetes Charter README and adheres to the Roles and Organization Management specified in sig-governance.

From sig-governance:

Within this section "member" refers to a member of a Chair, Tech Lead or Subproject Owner Role. (this different from a SIG or Organization Member).
Members MAY decide to step down at anytime and propose a replacement. Use lazy consensus amongst other members with fallback on majority vote to accept proposal. The candidate SHOULD be supported by a majority of SIG Members or Subproject Contributors (as applicable).

Lazy consensus

This issue proposes lazy consensus for @kbarnard10 to replace @Bradamant3 on 15 January 2020 as SIG Docs co-chair, giving time for feedback from SIG members.

For lazy consensus, this issue needs:

• [x] A statement from @Bradamant3 that she intends to step down as SIG Docs co-chair: by comment on this issue, in a weekly meeting, or in an email to [email protected]
• [x] A statement from @kbarnard10 accepting the nomination as SIG Docs co-chair: by comment on this issue, in a weekly meeting, or in an email to [email protected]
• [x] A vote from the current co-chairs (@Bradamant3, @jimangel, @zacharysarah) to confirm the nomination of @kbarnard10.

When these two conditions are met, and without clear consensus on a different path, on 15 January 2020:

• [x] @Bradamant3 becomes a chair emeritus of SIG Docs
• [x] @kbarnard10 becomes a co-chair of SIG Docs

Required changes

Co-chair transitions require some updates.

Repo | file | Complete?
---|---|---
k/community | OWNERS_ALIASES | ✔️
k/community | sig-docs/README.md | ✔️
k/community | sig-list.md | ✔️
k/community | sigs.yaml | ✔️
k/enhancements | OWNERS_ALIASES | ✔️
k/org | OWNERS_ALIASES | ✔️
k/website | OWNERS_ALIASES | ✔️
k/website | SECURITY_CONTACTS | ✔️

Thank you

From @zacharysarah:

@Bradamant3 joined Kubernetes SIG docs in June 2017. She understood the whole of SIG Docs almost immediately, and saw better how SIG Docs interrelated with everything else in the Kubernetes project. She translated her own personal understanding into deep technical knowledge and community understanding, built relationships, improved feature docs, and changed the world. She improved everything her leadership touched--notably kubeadm docs, the release notes, and every feature she worked on. SIG Docs benefited mightily from her keen insight and gregarious humor.

Jennifer, thank you for two and a half years (and counting!) of excellence in SIG Docs. I'm so glad you said yes when I asked. You connected SIG Docs with the rest of the Kubernetes project and kept us aware of things we would otherwise have missed.

@kbarnard10, I'm excited for you to evolve your role. You've shown effective leadership in launching and managing the Kubernetes blog, and your Hugo knowledge makes you a valuable addition to the technical team. Thanks for stepping up!

/sig docs

[sftim]

A thank you from me as well, to both!

[kbhawkey]

Thanks, @Bradamant3 for your leadership!
Congrats, @kbarnard10!

[zacharysarah]

@Bradamant3 @kbarnard10 👋 In order for this PR to move forward, please comment with your assent.

[kbarnard10]

I accept the nomination for co-chair 🎉

A huge thank you to @Bradamant3 for all the leadership and, especially, mentorship that she's provided throughout my journey with SIG-Docs ❤️

[jrondeau-stripe]

And with regret because I'll miss you all, but knowing that @kbarnard10 is the right person now, when I am no longer in a position to help this amazing community, I'm commenting to say yes, let's move forward with the transition as I formally step down. Thanks to all of you for all you've taught me and shared with me ❤️

[sftim]

:wave:

[zacharysarah]

The vote to promote @Bradamant3 to chair emeritus and promote @kbarnard10 to co-chair passed in today's SIG Docs weekly meeting.

Thanks, @Bradamant3! Welcome, @kbarnard10! 🎉

[justaugustus]

Just dropping by to say this is a really beautifully written issue that we should probably formalize for Chair/TL transitions. :)
cc: @parispittman

Thanks for your work, @Bradamant3!
And congrats, @kbarnard10!

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[sftim]

Let's not autoclose this.
/remove-lifecycle stale

[zacharysarah]

@sftim Fair, and with no remaining tasks, it's time to close.

/close

[k8s-ci-robot]

@zacharysarah: Closing this issue.

In response to this:

@sftim Fair, and with no remaining tasks, it's time to close.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.