TL;DR: SIG Docs is proposing the creation of new roles and moving folks around to support the docs k8s community. Your +1 or objection is appreciated!
Hey y’all, I sent an email in August saying that SIG Docs was in need of help.
After that email, Paris Pittman and I hosted a 12 week mentoring program to help introduce folks to open source leadership roles & responsibilities. We had amazing participation and discussions around the future of SIG Docs alongside our existing SIG Docs tech leads and co-chairs.
The group identified areas, such as localization, that could use more support. We also thought there could be a better way to onboard new contributors and encourage a healthier, thriving, docs community.
Natali Vlatko led efforts to formalize the localization team into a subproject and proposed a new role: Localization Leads. Localization Leads would be similar to co-chairs with a focus on localization. Arsh Sharma proposed a New Contributor Ambassador role that would help onboard and assimilate newcomers to SIG Docs. Arsh also volunteered to pilot this new role. By adding new roles and team members, SIG Docs can evolve into a sustainable community that allows members to lean into their strengths and support each other.
I’m proposing the following changes to SIG Docs:
Finally, I’ll step down as co-chair at the end of Q1 after assisting with the transitions. It has been a true honor and pleasure to serve as a co-chair to this community over the past 2+ years. I’m going to keep it real: I’m burnt out. I’m burnt out and not giving the documentation community the time, or leadership, needed to thrive. I encourage everyone involved in Kubernetes to evaluate their own mental health and capacity to make similar choices. The multi-year pandemic has impacted us all and it can be challenging at times. I plan on continuing to remain active as an individual contributor and would love to take on other leadership roles after I spend some time recharging.
As a result, the "full" SIG Docs leadership team would look like:
I believe this new team structure, with additional roles, allows for SIG Docs to rotate more people in and out of leadership roles as needed. In addition, I encouraged the people listed above to think about their replacements and succession plan. The co-chair position remains the primary leadership role for SIG Docs and overall SIG direction.
So what are the next steps? This email is seeking lazy consensus to confirm / reject the proposed changes and role updates. After one week of review (1/17/22), PRs reflecting the above changes can be merged.
Thank you all for keeping kubernetes.io the best documentation site in all of open source! Cheers!
Jim Angel
SIG Docs Co-Chair
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-docs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-docs/8fa9a377-7ecd-40cf-94d9-5321ff7e2d78n%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-docs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-docs/9ffa1420-5039-459a-b3dd-6395e31bf6c5n%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-docs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-docs/CAMcKex2g_sdxaepC7vZqCZF%2BTBPNzSty5OfrbOsr0G1CU6VA%3DQ%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-docs/5BDE89D2-6E01-40D6-BF51-6047E8759E38%40gmail.com.