kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7437 from AvineshTripathi/deprecating-storyteller-role 

Removed storyteller role
This commit is contained in:
Kubernetes Prow Robot 2023-08-25 08:24:54 -07:00 committed by GitHub
parent 6fe635851e 22cbb74f7e
commit 44e079e881
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 7 additions and 128 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
communication/contributor-comms/README.md
View File

@ -34,6 +34,10 @@ To find out what projects we're currently working on and explore what you could
* Reach out to us on the #sig-contribex-comms channel on the Kubernetes slack ([slack.k8s.io](http://slack.k8s.io)).
* Join our [mailing-list]
As with all contribution to Kubernetes, adhere to the [code of conduct], values, and principles of the project.
**NOTE**
[meetings]: /sig-contributor-experience#contributor-comms
[calendar]: https://www.kubernetes.dev/resources/calendar/
[mailing-list]: https://groups.google.com/g/kubernetes-sig-contribex
@ -50,3 +54,4 @@ To find out what projects we're currently working on and explore what you could
[area/contributor-comms]: https://github.com/kubernetes/community/issues?q=is%3Aopen+is%3Aissue+label%3Aarea%2Fcontributor-comms
[Twitter]: https://twitter.com/K8sContributors/
[Mastodon]: https://hachyderm.io/@K8sContributors
[code of conduct]: https://github.com/kubernetes/community/blob/master/code-of-conduct.md

2
communication/contributor-comms/blogging-resources/README.md
View File

@ -1,5 +1,7 @@
# Blogging resources
Contributor Comms depends on great storytelling to get the message out about our amazing community. We help Kubernetes contributors hear the latest news in the most entertaining ways. This can be done through words and visuals.
We have collected some information to get anyone started. If you're looking to get started blogging on the kubernetes.dev blog, this page contains a list of resources available to help you be successful.
## [Blog guidelines](./blog-guidelines.md)

44
communication/contributor-comms/role-handbooks/[Deprecated]Comms-Events.md
View File

@ -1,44 +0,0 @@
# Comms Events Lead Role Handbook
**NOTE**: This role is deprecated as of mid 2023
## Overview
As Event Co-ordinator Lead, you are responsible for
- connecting with organizers of contributor events such as the monthly community meeting or contributor summits
- working with the Contributor Comms team to ensure communications about events are being created and promoted through various means including email (k-dev), slack (slack bot, etc), twitter (K8sContributors), etc.
Time Commitment:
1-3 hours a week from 0-1.5 months in
2-5 hours a week from 1.5 months-to event
## Minimum skills and Requirements
- Kubernetes github org [membership](https://github.com/kubernetes/community/blob/master/community-membership.md)
- familiarity with the workflow of [#sig-contributor-comms](https://github.com/kubernetes/community/tree/master/communication/contributor-comms)
- has understanding of the [social guidelines](https://github.com/kubernetes/community/blob/master/communication/contributor-comms/storytelling-resources/social-guidelines.md)
- Good grasp on general marketing activities surrounding events
- Understanding of common forms of marketing communications
- Event planning experience is a plus
- Willing and able to directly coordinate across timezones and contributor groups
- commitement for the role is relative and would vary depending upon events
## Expectations and tasjs
The core task for the role would be to stay current on [upcoming](https://www.kubernetes.dev/events/) events. Planning should be done with the team about the event, target audience, mode of communication, timeline, etc. This could be coordinated via a call or async conversatios. Sometimes, some big events might require you to join a weekly or bi-weekly call. The following are the possible tasks to perform (may vary depending upon the event).
- Creating a communication schedule - what, when, how, who
- Promoting on different platforms like
- emailing on [kdev](https://github.com/kubernetes/community/blob/master/communication/mailing-list-guidelines.md)
- twitting from main or k8scontributor accounts
- coordinating with CNCF(if required)
- sending slack notification to various channels(depending on the target audience)
- Assisting in the entire blog process
- Coordinating with Contributor Comms team members to ensure above tasks are completed
Timeline for the communication can be crucial parameters so ideally timelines should at least begin to be decided weeks before the event.
## Shadowing the Event Coordinator Role
This role can include one or more shadows. The Event Coordinator Lead can delegate/assign tasks to the shadows. The expectation from a shadow is to work with the lead to develop a plan to adopt ownership of the role over time, including all tasks listed in the "Expectations and Tasks" section. The shadows to the Event Coordinator Lead are responsible for handling all Event Coordinator lead related activities in the absence of the Lead.

84
communication/contributor-comms/role-handbooks/storytellers.md
View File

@ -1,84 +0,0 @@
# Storytellers 📖 Handbook
## Overview
Contributor Comms depends on great storytelling to get the message out about our amazing community.
It's no secret that governance and technical documentation can be kind of on the boring side. And that's ok–it's not always there for entertainment purposes. It is about providing valuable information and getting you where you need to go. But that said, an important message can be lost without an entertaining messenger.
In this role, Storytellers are here to help Kubernetes contributors hear the latest news in the most entertianing ways. Storytellers will take us on journeys through words and visuals to help us craft.
## Workflow ⚡️
Storytelling is welcome in any medium that can be supported by the Contributor Comms team. This includes but is not limited to written word–as outlined in [blogging guidelines]–or through video following our [YouTube guidelines].
Storytellers are constantly building new ways to share, and these resources are gathered in the [storytelling resources folder].
### Contributor Comms Process
#### Idea Paths
There are multiple ways to successfully contribute a Kubernetes blog post. Here are some of the common paths to help you do so:
**To start:**
* Open a [Contributor Comms Requests issue](https://github.com/kubernetes/community/issues) to share your blog idea, or attend an [Contributor Comms team](https://github.com/kubernetes/community/tree/master/communication/contributor-comms) meeting to discuss it ahead of time
**To write:**
* Create an initial draft -- it is always easier to work from some written down ideas than to do so from scratch
* A draft can be written in:
* Google Docs or
* Markdown (and shared via [Gist](https://gist.github.com/) or [HackMD](https://hackmd.io/))
* Connect with a storyteller -- if you reach out to Contributor Comms, you will be paired with someone to help you through writing, editing, and getting your article published
* Discussion happens via GitHub issue or through working group meetings
* This includes working with Contributor Comms team to polish, and format your blog post
* There is not a single canonical format for documents, but we do have [guidelines for effective articles](https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject#blog-guidelines)
* There are further technical considerations by the [Blog team](https://github.com/kubernetes/community/blob/4026287dc3a2d16762353b62ca2fe4b80682960a/sig-docs/blog-subproject/README.md#submit-a-post)
When it's ready, submit the blog post:
* Go to the `kubernetes/website` repository
* Open a PR with your added blog post
* If you need help with this process, Contributor Comms will look to pair you with someone for PR and shepherd it through the review cycle
Or if you already have everything you think you need you can:
* Go to the `kubernetes/website` repo and send a PR
* There's a Kubernetes blog team that will walk you through [the process](https://kubernetes.io/docs/contribute/new-content/blogs-case-studies/)
### Tips
Converting a Google Doc to markdown? Here is a helpful way to do so:
* go to: https://discuss.kubernetes.io/
* Open a new topic
* Paste the Google Doc into new topic window
* Discourse will automatically convert it to markdown 🎉
* Now you can copy the markdown text, with all its original formatting, and paste it into your blog post file (this will often be a text file you are editing on your computer from a text editor like VS Code)
* Be sure to add the syntax required at the top of the blog post (see links above)
* Now you are ready to submit it as a PR
## Minimum Skills and Requirements
- Have a passion for telling stories, technical writing, journalism, and painting pictures with words
- Desire to be a Kubernetes Org Member and if not already, work your way towards membership
- Helpful but not required: Comfortable with working with GitHub workflows or working in a collaborative document like Hackmd.io
## Expectations
Anyone is welcome to contribute when they have time. The core expectation of storytelling is taking responsibility for getting the story from inception to published.
If you would like to be listed as a member of the team, here are the expectations:
1. Be prepared to write one blog a quarter and participate in edits to other articles. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue.
2. Storytellers are expected to attend at least one Contributor Comms meeting a month or check-in to remain active.
3. Remain non-partial: if you receive a request to write about a project, an individual, or a group of people from your employer, you should ask an impartial blogger to write it.
4. As with all contribution to Kubernetes, adhere to the [code of conduct](/code-of-conduct.md), values, and principles of the project.
There are no shadow roles for Storytellers. If Storytellers are interested in becoming a shadow they can read more about the available leadership roles in the Contributor Comms [Role handbooks](https://github.com/kubernetes/community/tree/master/communication/contributor-comms/role-handbooks).
[blogging guidelines]: ../storytelling-resources/blog-guidelines.md
[YouTube guidelines]: /communication/youtube/youtube-guidelines.md
[storytelling resources folder]: ../storytelling-resources/
[Marketing Council Handbook]: ../role-handbooks/council.md