blob: 04c3adf6f2d2a9b88568e15bf327ad9fb82acd9b (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
|
# Contributor Communications
The Contributor Communications team (Contributor Comms for short) is part of the `community-management` subproject in [Contributor Experience]. View our [charter] to learn more about us.
## Purpose
To better inform the Kubernetes contributor community and highlight their work to the broader ecosystem.
| Area & Handbook Link | Team | Notes |
| --- | --- | --- |
| Subproject Lead | @kaslin, @chris-short | Shadow role is available. |
| [Social Media Coordinator](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Social-Media.md) |@kaslin | Shadow role is available. |
| [Comms Tech Lead](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/Comms-Tech-Lead.md) | @Atharva-Shinde, @imnmo | @markarranz (shadow) |
| [Comms Event Lead] | @AvineshTripathi | Shadow role is available. |
| [Comms Blog Coordinator](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/role-handbooks/blog-coordinator.md) | @fsmunoz | Shadow role is available. |
| [Storytellers] & other members | @hpopal11, @Atharva-Shinde | New to Contributor Comms? Add your name here! |
| Emeritus | @parispittman, @mbbroberg |
## Contact Us!
- Reach out to an individual above via Slack
- Ping the whole team: @contributor-comms in #sig-contribex on slack
- Tag us in an issue in [kubernetes/community] with the label [area/contributor-comms]
- Set a marketing issue template in [kubernetes/community]
- Follow us on @K8sContributors on [Twitter]
## Join us!
We are always open to being a home for contributors to Kubernetes whether you code or not.
* Come to one of our [meetings] (Every Friday at 8am PT). See the [calendar] to add it to your own calendar.
* Join our [mailing-list], and/or reach out to us on the #sig-contribex channel on the Kubernetes slack ([slack.k8s.io](http://slack.k8s.io)).
Let us know you are interested and if you have any questions.
[meetings]: /sig-contributor-experience#contributor-comms
[calendar]: https://calendar.google.com/calendar/u/0/r/customday?eid=NmU5MjFnYWwwMzIwNjVwamFvNmszZHBuYzhfMjAyMDEyMDRUMTYwMDAwWiBjYWxlbmRhckBrdWJlcm5ldGVzLmlv&ctz=America/Los_Angeles&sf=true
[mailing-list]: https://groups.google.com/g/kubernetes-sig-contribex
[charter]: ./CHARTER.md
[Could be you!]: #could-be-you
[Contributor Experience]: /sig-contributor-experience
[Internal Communications]: ./role-handbooks/internal-marketing.md
[Social Media]: ./role-handbooks/social-media.md
[Comms Tech Lead]: ./role-handbooks/Comms-Tech-Lead.md
[Comms Event Lead]: ./role-handbooks/Comms-Event-Lead.md
[Comms Blog Coordinator]: ./role-handbooks/blog-coordinator.md
[Storytellers]: ./role-handbooks/storytellers.md
[Designer]: ./role-handbooks/wip-roles.md
[kubernetes/community]: https://github.com/kubernetes/community/issues
[area/contributor-comms]: https://github.com/kubernetes/community/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fcontributor-comms
[Twitter]: https://twitter.com/K8sContributors/
|
