Periodic tweets and emails about SIGs

[sureshpalemoni]

What do you want send out? Twitter handle should tweet or periodical email to distribution list about the existing SIG one at a time.

What’s the intended outcome? For example we tweet/email periodically about /sig-apps/CONTRIBUTING.md

• If email - short one line what this sig about(tweet we can have this if we post some template image)
• References to active repo of this SIG
• contacts of active sig leads who can mentor new contibutors
• Next upcoming meeting. (Contributors gets lost in either emails or tweets). So we remind/inform them using these channels.

What is the sponsoring SIG or community group?

sig-contribex

Is this time-sensitive?

• On a periodic basis

Where do you want it to be visible?

• [ ] Everywhere 🌍
• [x] Email (kubernetes-dev@googlegroups.com)
• [ ] Blog post (with help from a Storyteller)
• [x] Twitter (via @k8scontributors)
• [ ] YouTube (Kubernetes)
• [x] Slack (assumes #kubernetes-dev unless otherwise mentioned)
• [ ] Contributor Calendar event entry (available here)
• [ ] Other (fill this out)

Where is your first draft available? This is basic idea:

Are you interested in contributing to Kuberenetes Networking?

• SIG: #sig-network
• Next Contrinutor meeting on SIG-Network
  • Aug 25th (Example) - Link to zoom meeting
• Mentor contacts(who can be contacted via twitter,slack or email)

  ---

  Or, SIG of the week or SIG of the day also works.

Lastly, who's the best point of contact? Myself or @mbbroberg

[sureshpalemoni]

@mbbroberg and @rajula96reddy

[sureshpalemoni]

https://guides.github.com/features/mastering-markdown/

@mbbroberg - Example Format

[mbbroberg]

LOVE this! The one thought that comes to mind is that we could talk to reader a little more.

Meet our SIG of the week: SIG-DOCS! 

You can start contributing by joining: 
- Slack link
- Group link
- The next meeting on X 

On-going agenda: 
- A
- B

#sigoftheweek

[mbbroberg]

This is coming along! Notes from working with the team:

• Do NOT link to Zoom
• Do link to the k8s.dev/calendar


[mrbobbytables]

/assign @mbbroberg

[fejta-bot]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-contributor-experience at kubernetes/community. /close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to [this](https://github.com/kubernetes/community/issues/5061#issuecomment-866173580): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >Send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.