1 of 16

SIG Contributor Experience Community Meeting Update

​

2 of 16

What we did last cycle

  • New chairs, @mrbobbytables and @castrojo
    • Thanks to @phillels and @parispittman for their years of service to the SIG
  • Major themes:
    • Sustainability
    • Automation
    • Working on our tech debt
      1. AKA triaged all the bugs in k/community

​

​

3 of 16

Plans for upcoming cycles

  • Sustainability efforts
    • Consistently fixing SIG mailing lists permissions, calendars, and other manual processes across the project
    • OWNERs files
  • Automation
    • Remove workloads from SIGs, (example: automating your YouTube uploads)

​

4 of 16

Subproject: Community Management Status

  • Mailing Lists and Calendars
    • Audited and in progress to move to one consistent workflow for the entire project
      • No more manually adding the calendar to meeting invites
      • Group membership will be managed through updates�to k8s.io repo
  • YouTube
    • Zoom -> YouTube automation (splain) has not been working reliably :(
      • Investigating other options (please reach out if you have suggestions)
    • Stream team is looking for more members, specifically on the West Coast US

“The last remnants of the old republic are being swept away ...eventually”

5 of 16

Subproject Community Management Status II

  • Slack
    • 100,000+ users now, whoa!
  • Zoom
    • TLDR: Keep your clients up to date
  • discuss.k8s.io
    • CKA/CKAD cheaters, we can see you. :D
  • Moderators
    • Always looking, especially APAC.

6 of 16

Chair and Technical Lead Meeting

  • Monthly meeting for covering project-wide topics for leads
  • Augments the regular “need to know” newsletter with tips/tasks
  • Information swap between chairs/TLs too unsilo community group best practices

​

7 of 16

Subproject: Upstream Marketing

Big wins

  • We exist! See our charter and team here.
  • Launched a communication framework to provide clear and regular updates.
  • Wrote multiple blog posts on SIGs that resulted in new contributors! (Editorial board)

Up next

​

* Please follow and RT us!!!

Channels

Needs

Feedback Appreciated

ICYMI

Priority

Action Required

8 of 16

Subproject: Contributors Documentation

  • Contributor Site
    • Publish contributor guide, community �calendar, release information and more.
  • Developer Guide status
  • Erik Arneson (@pymander) and Joel Barker (@joelbyronbarker) are working on updating the developer documentation
  • They are in process of doing a comprehensive look at the end-to-end setup and testing documentation. They have audited the contents and are making changes based on a functional walk-through on multiple platforms. Completion September 1.

9 of 16

Subproject: Devstats

10 of 16

Subproject: Events

  • Potential Virtual Contributor Summit in later half of the year?
    • Looking to put together useful presentations and content for current contributors
    • Poll to be sent to k-dev to discuss options
  • New Contributor Workshop moved under mentoring subproject
    • Being reworked to be piecemeal and targeted towards online only
    • Looking for volunteers to help present and record sections
      • ping @alisondy for details

​

11 of 16

Subproject: GitHub Management

12 of 16

Subproject: Mentoring

  • Looking to work with more SIGs to build program targeting active contributors - more reviewers and approvers.
    • Ping Paris Pittman (@parispittman) or ask in #sig-contribex
  • Meet Our Contributors: audience is split 50/50 between aspiring and CURRENT contributors.
    • Not just for new contributors.
    • Second session to be added opposite of the current 730am PT slot to help with other timezones.
  • New Contributor Workshop (NCW)
    • Recently moved from events to mentoring

13 of 16

Subproject: Slack infra

  • Slack tooling is working out well (thanks Katharine~)
  • Upcoming:
    • Connecting github to #announcements so people can PR/approve �announcements
    • Channel-level moderation

14 of 16

Related KEPs

  • KEP-1553: Issue Triage Workflow and Automation
    • Removes:
      • triage/duplicate
      • triage/not-reproducible
      • triage/unresolved
    • Renames:
      • triage/support -> kind/support
      • triage/needs-information -> lifecycle/needs-information
    • Adds:
      • needs-triage
        • Default label applied to all incoming issues
      • triage/accepted
        • Issue has been triaged by a SIG representative and is ready to be worked

​

15 of 16

Related Working Groups

  • WG Naming
    • We have a new WG working with SIG Contribex!
    • We are working with GitHub for their roadmap on renaming the default branch on repos to “main”.

16 of 16

Where to find us