---
# System prepended metadata

title: 1.26 SIG Lead Outreach Instructions

---

# 1.26 SIG Lead Outreach Instructions

The enhancements team will be performaning an additional round of outreach this cycle to remind SIG leads that the enhancement opt-in process is changing. You should plan to reach out **during the week of September 18th.**

### Steps to follow:

**Step 1:** Take a look at the below SIG assignment to see which SIG leads you will be responsible for reaching out to on Slack.

**Ryler:**
sig-api-machinery
sig-apps
sig-architecture
sig-auth
sig-autoscaling

**Atharva:**
sig-cli
sig-cloud-provider
sig-cluster-lifecycle
sig-contributor-experience

**Mark:**
sig-docs
sig-instrumentation
sig-k8s-infra
sig-multicluster
sig-network

**Parul:**
sig-node
sig-release
sig-scalability
sig-scheduling
sig-security

**Ruheena:**
sig-storage
sig-testing
sig-ui
sig-usability
sig-windows

**Step 2:** Find the SIG leads [from the "Chairs" column on this list](https://github.com/kubernetes/community/blob/master/sig-list.md) for each SIG assigned to you.  Then you'll need to search for them on Slack to find their Slack handle.

**Step 3:** Create a new DM to the leads of each SIG and send the following message:

```
Hello <sig lead name>,

I’m part of the 1.26 release team reaching out to make sure that you are informed on the changes to our release opt-in process. Starting this release, we will replace the enhancements Google sheet with an automated Github board.

How to opt-in for SIG lead:
- On your respective KEP, ensure that the existing labels (especially stage, SIG) are correct since this will be used to populate data.
- Apply the label `lead-opted-in` on the KEP issue to opt-in. (Let me know ASAP if you don’t see this).
- That’s it! We run the script periodically so be sure to check in a few days that your KEPs are there.

Please reply here to acknowledge that you are informed about the process. Happy to answer any questions/feedback you have as well.
```