-
What work did the SIG do this year that should be highlighted?
- Continuing to provide critical services to enable the work of over 75,000+ contributors
- Migrating K-Dev to a managed kubernetes.io account
- We encountered a problem with the k-dev mailing list where we couldn't send out community-wide meeting invites, due to restrictions on public google groups.
- In order to overcome this issue, we migrated to Google Workspace.
- It took over 80+ hours across the Contribex team to complete this migration.
- Steering Election with Elekto
- Elekto was created by Manish Sahani as part of an LFX internship. It allows us to run Elections on our own infrastructure.
- Voters can login using their github credentials and vote from the election site.
- The previous method of holding elections was prone to issues when it came to the following:
- Obtaining the list of elegible voters from 75,000+ contributors
- Sending ballots out via email
- Elekto automated the process of obtaining the list of elegible voters
- Ballots are no longer sent out via email, and instead contributors log in to the elections site to submit their ballots.
- More information can be found in community issue #5096
- Community meeting overhaul and reboot
- EasyCLA migration
- The CLA service provided to us by the Linux Foundation was being deprecated.
- We needed to migrate to EasyCLA2 to ensure continuity of service for our 75,000+ active committers.
- Contributor Summit North America
- Contributor Celebration
- Restaffed teams
- Moderation
- Youtube Admin
- Ran three group mentoring cohorts to grow contributors in named roles (50% graduation rate) for contribex, docs, and a 'chair' cohort for multiple SIGs
- Grew @k8scontributors twitter account to 5,700 followers
- Created documentation geared towards Chairs and Tech Leads to help grow and support their roles and groups operations
- Curated and ran 8 months of Leads meetings (16 meetings total)
-
What initiatives are you working on that aren't being tracked in KEPs?
Contribex is a service and program orientated SIG. Most of our initiatives cover long term services for the Kubernetes project.
We put the following initiatives on hold, and will be revisiting these at a later date.
Subproject | Initiative / Program |
---|---|
Mentoring | Meet our Contributors |
Mentoring | Outreachy |
Mentoring | New Contributor Workshop |
Mentoring | Google Summer of Code |
-
What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details)
- GitHub Admin Subproject
- We need to bring on more new membership coordinators.
- New Membership Coordinators are current contributors to the Kubernetes project that help serve as a friendly face to newer, prospective community members, guiding them through the process to request membership to a Kubernetes GitHub organization.
- We need to bring on more new membership coordinators.
- Community Management Automation
- Zoom to Youtube
- Workspace Automation
- Mailing list management
- Calendar management
- Shared drives
- Mentoring Program Management and new Roles
- We need a Group Mentoring Coordinator
- We need a 3rd Party Mentoring Coordinator
- GitHub Admin Subproject
-
What metrics/community health stats does your group care about and/or measure?
-
Does your CONTRIBUTING.md help new contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation?
- We don't have a CONTRIBUTING.md as our SIG's contributing process does not differ from the process in the Contributor Guide.
-
If your group has special training, requirements for reviewers/approvers, or processes beyond the general contributor guide, does your CONTRIBUTING.md document those to help existing contributors grow throughout the contributor ladder?
- N/A
-
Does the group have contributors from multiple companies/affiliations?
- Yes. 25+ Different groups
-
Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why?
- A full time community manager who can maintain several subprojects and help with the overall direction of the group
- More full time support for the items under bullet point 1.
- This work will reduce toil for contributor experience and all groups in the project.
Statistics were retrieved on 2022-01-30
- Primary slack channel member count: 1895
- Primary mailing list member count: 366
- Primary meeting attendee count (estimated, if needed): 10-15
- Primary meeting participant count (estimated, if needed): 5
- Unique reviewers for SIG-owned packages: 20
- Unique approvers for SIG-owned packages: 28
Include any other ways you measure group membership
New in 2021: N/A Retired in 2021: N/A
Continuing:
- community Owns and manages overall community repo, including community group documentation and operations.
- community-management Manages operations and policy for upstream community group communication platforms.
- contributor-comms Contributor Communications focuses on amplifying the success of Kubernetes contributors through marketing.
- contributors-documentation writes and maintains documentation around contributing to Kubernetes, including the Contributor's Guide, Developer's Guide, and contributor website.
- devstats Maintains and updates https://k8s.devstats.cncf.io, including taking requests for new charts.
- events Creates and runs contributor-focused events, such as the Contributor Summit. Event Teams are part of this subproject.
- github-management Manages and controls Github permissions, repos, and groups, including Org Membership.
- mentoring Oversees and develops programs for helping contributors ascend the contributor ladder, including the New Contributor Workshops, Meet Our Contributors, and other programs.
- slack-infra Creates and maintains tools and automation for Kubernetes Slack.
New in 2021: N/A
Retired in 2021:
Continuing: N/A
Operational tasks in sig-governance.md:
- README.md reviewed for accuracy and updated if needed
- TODO : Update the README to account for slack meetings
- Subprojects list and linked OWNERS files in sigs.yaml reviewed for accuracy and updated if needed
- SIG leaders (chairs, tech leads, and subproject owners) in sigs.yaml are accurate and active, and updated if needed
- Meeting notes and recordings for 2021 are linked from README.md and updated/uploaded if needed
- Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: