summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2020-01-31 09:28:23 -0800
committerGitHub <noreply@github.com>2020-01-31 09:28:23 -0800
commitf4c07ee36ce404979b535b6d87ac5c77e1ed3256 (patch)
treee181791282ffd13ca5ba20d7048e3f391c5117de
parenta7332305f654d2334dcffab3fdaf4bd385a3c81e (diff)
parent8ad20c7a664d72596e0b254253079c4378c86709 (diff)
Merge pull request #4459 from boluisa/blogguide
add marketing blog guidelines
-rw-r--r--communication/marketing-team/contributor-blogging.md36
1 files changed, 36 insertions, 0 deletions
diff --git a/communication/marketing-team/contributor-blogging.md b/communication/marketing-team/contributor-blogging.md
new file mode 100644
index 00000000..4f5a6006
--- /dev/null
+++ b/communication/marketing-team/contributor-blogging.md
@@ -0,0 +1,36 @@
+# Upstream Marketing Blog Guidelines
+
+Blogging serves as a way to highlight and give exposure to the work that is being done by the kubernetes [community](https://github.com/kubernetes/community).
+
+## Guidelines for contributor blogs:
+
+* Use inclusive language understandable by everyone
+* Ensure that the blog post is reviewed by the anyone being mentioned in the piece
+* Stay on topic and stick to the facts
+* Avoid interjecting personal reactions
+* Shy away from jargon and colloquial expressions
+* Revise your post before submission to make sure it’s unambiguous and accurate
+* Emphasize the things you want readers to remember; tell a story
+* Provide evidence and data where applicable, to back up your message
+* As the author, never talk about your employer, sell, promote, or pitch; this is about upstream community endeavours and the individuals+groups that create it.
+* Avoid ambiguity
+* Avoid including anything that lacks adequate evidence
+* Make sure to have at least one original quote and one picture
+* Much of what’s outlined already in the [website blog guidelines](https://github.com/kubernetes/community/blob/77aa44ba8a506b2d8a7110ff96f545c36db906f3/sig-docs/blog-subproject/README.md
+) owned by sig-docs
+
+## Blogger Expectations, Responsibilities, and Info
+
+1. Active bloggers should write one blog a quarter. The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue.
+2. Adhere to the code of conduct, values, and principles of the project.
+3. Bloggers are expected to attend at least one upstream marketing team meeting a month or check-in to remain active.
+4. If you receive a request to write about a project, an individual, or a group of people from your employer, you should ask a non-partisan blogger to write it.
+
+## Submit a Post
+
+This process is bootstrapped from the sig-docs blog [subproject](https://github.com/kubernetes/community/blob/77aa44ba8a506b2d8a7110ff96f545c36db906f3/sig-docs/blog-subproject/README.md)
+
+## Review Process
+
+This process is bootstrapped from the sig-docs blog [subproject](https://github.com/kubernetes/community/blob/77aa44ba8a506b2d8a7110ff96f545c36db906f3/sig-docs/blog-subproject/README.md). Please ask for review from community liaisons on the sig-docs-blog team.
+