Merge branch 'master' into mkt-update

3 files changed, 58 insertions, 5 deletions

diff --git a/communication/marketing-team/role-handbooks/storytellers.md b/communication/marketing-team/role-handbooks/storytellers.md
index 1d0c330f..49433f60 100644
--- a/communication/marketing-team/role-handbooks/storytellers.md
+++ b/communication/marketing-team/role-handbooks/storytellers.md
@@ -14,6 +14,51 @@ Storytelling is welcome in any medium that can be supported by the Upstream Mark
 
 Storytellers are constantly building new ways to share, and these resources are gathered in the [storytelling resources folder]. 
 
+### Upstream Marketing 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 [Upstream Marketing team](https://github.com/kubernetes/community/tree/master/communication/marketing-team) 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 Upstream Marketing, 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 Upstream Marketing 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/blob/master/communication/marketing-team/blog-guidelines.md#how-to-write-an-effective-blog)
+  * 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, Upstream Marketing 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
diff --git a/sig-contributor-experience/charter.md b/sig-contributor-experience/charter.md
index ed98ad62..8e0f1bcf 100644
--- a/sig-contributor-experience/charter.md
+++ b/sig-contributor-experience/charter.md
@@ -112,11 +112,11 @@ Chairs and Technical Leads
 [kubernetes-dev@]: https://groups.google.com/forum/#!forum/kubernetes-dev
 [@kubernetesio]: https://www.twitter.com/kubernetesio
 [r/kubernetes]: https://kubernetes.reddit.com
-[Google Summer of Code]: https://git.k8s.io/community/mentoring/google-summer-of-code.md
-[Outreachy]: https://git.k8s.io/community/mentoring/outreachy.md
-[Meet Our Contributors]:  https://git.k8s.io/community/mentoring/meet-our-contributors.md
-[Group Mentoring - WIP]:  https://git.k8s.io/community/mentoring/group-mentoring.md
-[The 1:1 Hour - WIP]: https://git.k8s.io/community/mentoring/the1-on-1hour.md
+[Google Summer of Code]: https://git.k8s.io/community/mentoring/programs/google-summer-of-code.md
+[Outreachy]: https://git.k8s.io/community/mentoring/programs/outreachy.md
+[Meet Our Contributors]:  https://git.k8s.io/community/mentoring/programs/meet-our-contributors.md
+[Group Mentoring - WIP]:  https://git.k8s.io/community/mentoring/programs/group-mentoring.md
+[The 1:1 Hour - WIP]: https://git.k8s.io/community/mentoring/programs/the1-on-1hour.md
 [kubernetes/community]: https://git.k8s.io/community/
 [Contributor Summit(s)]: https://git.k8s.io/community/events/2018/12-contributor-summit
 [contributor summits]: https://git.k8s.io/community/events/2018/12-contributor-summit
diff --git a/wg-data-protection/OWNERS b/wg-data-protection/OWNERS
new file mode 100644
index 00000000..34ec1e64
--- /dev/null
+++ b/wg-data-protection/OWNERS
@@ -0,0 +1,8 @@
+# See the OWNERS docs at https://go.k8s.io/owners
+
+reviewers:
+  - wg-data-protection-leads 
+approvers:
+  - wg-data-protection-leads 
+labels:
+  - wg/data-protection