Update Comms-Tech-Lead.md

Author: SD-13

communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md

@@ -4,19 +4,20 @@
 
 This handbook outlines expectations and responsibilities for Tech Leads as well as Contributor Comms team members who wish to contribute to technical efforts.
 
-Tech leads' contributions further the Contributor Comms team's efforts to communicate  contributors' stories by resolving technical issues and decisions around [contributor-site](https://www.kubernetes.dev/), social media automation tools [kubernetes-sigs/contributor-tweets](https://github.com/kubernetes-sigs/contributor-tweets), and [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message). 
+Tech leads' contributions further the Contributor Comms team's efforts to communicate  contributors' stories by resolving technical issues and decisions around [contributor-site](https://www.kubernetes.dev/), social media automation tools [buffer](https://buffer.com/) and [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message). 
 
-[contributor-site](https://www.kubernetes.dev/) is a one-stop for Kubernetes contributor content and news. It brings important documentation scattered throughout the project into one central location. 
+[Contributor-site](https://www.kubernetes.dev/) is a one-stop for Kubernetes contributor content and news. It brings important documentation scattered throughout the project into one central location.
 
-Along with contributor-site there exist two automation tools that help:
-1. To create tweets (k8scontributors) via GitHub actions (see: [workflow](https://github.com/kubernetes-sigs/contributor-tweets/blob/main/.github/workflows/main.yml)) 
-2. To broadcasts messages across multiple slack channels (see: [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message))
+A shadow for the tech lead role is someone who is expected, and in training, to take over the lead role.
 
-The [contributor-tweets repo](https://github.com/kubernetes-sigs/contributor-tweets) utilizes open source Github action [twitter-together](https://github.com/gr2m/twitter-together) project to automate tweet approval from an issue.
+Along with contributor-site these automation tools are being used:
+1. Slack-bot to broadcast messages across multiple slack channels (see: [slack-bot](https://github.com/kubernetes-sigs/slack-infra/tree/main/slack-post-message))
+2. [buffer](https://buffer.com/) to create posts in social media platforms (X and mastodon)
+3. [Zapier](https://zapier.com/) to create and maintain automations (e.g posting zoom meeting to youtube)
 
 ## Minimum Skills and Requirements
 
-- Are a member of the [Kubernetes GitHub Org]
+- Are a member of the Kubernetes GitHub Org
 - Good knowledge of Node.js, Hugo(docsy theme and frontmatter)
 - Have a basic experience in Go (for Slack bot)
 - Have a good understanding of Github actions
@@ -30,18 +31,25 @@ Team members: 2-3 hours per week.
 ## General Expectations
 
 - Be welcoming, be yourself
-- Take ownership of an issue and submit a PR for repositories like (especially if it's quick or relates to work you're already doing) Contributor-site, tweets, and, slack bot
+- Take ownership of an issue and submit a PR for repositories like (especially if it's quick or relates to work you're already doing) Contributor-site and, slack bot
 - Have an understanding of what an issue is about and able to triage them, or know who to contact to determine the required information
 - Coordinate work to fix any issues in automation tools to ensure valid tweet requests are fulfilled
 - Train new leads
 
-Team members will be expected to keep an eye out for news or issues related to slack bot or Github automation. Common sources of such announcements are the k-dev mailing list and the #contributor-comms channel on Slack.
+Team members will be expected to keep an eye out for news or issues related to slack bot. Common sources of such announcements are the k-dev mailing list and the #contributor-comms channel on Slack.
 
-## Associates Overview (Shadow)
+## Tech Lead Shadow Overview
 
-Team members who wish to become technical leads shadow should express this desire to the current lead.
+Team members who wish to become tech leads should express this desire to the current lead(s). Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including:
 
-Leads should work with shadows to understand their capacity to take on the needs of the lead role and work with the shadow on a plan for them to take on responsibility including:
+* Being an active member of the Comms team, by following the activities and the regular meetings.
+* Demonstrated knowledge of the team's [README](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/README.md) and [Charter](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/CHARTER.md).
+* Becoming a reviewer for relevant PRs.
+* Leading initiatives in the Contributor Comms subproject
+* Address and work with the team to fix techinical issues.
+* Familiar with tools like Buffer, zapier.
+
+### Tech Lead Shadow Eligibility
 
 * General familiarity with our repositories and automation tools
 * Willingness and ability to follow up with contributors about issues, on Github, Slack, and email, as appropriate