Adding proposed files for Kubernetes blog subproject

Author: Kaitlyn Barnard

sig-docs/blog-subproject/README.md

@@ -0,0 +1,95 @@
+The Kubernetes Blog Subproject is owned by SIG-Docs and run by the Editorial Team.
+
+This section covers documentation, processes, and roles for the Kubernetes blog.
+
+## Meetings
+
+Regular Blog Meeting: TBD (biweekly).
+
+* Meeting notes and Agenda
+* Meeting recording
+
+## Leadership
+
+**Editorial Leads:** [Kaitlyn Barnard](https://github.com/kbarnard10), [Zach Corleissen](https://github.com/zacharysarah) (shadow)
+**Technical Editors:** [Bob Killen](https://github.com/mrbobbytables)
+**Copy Editors:** [Alex Handy](https://github.com/vonguard), [Cody Clark](https://github.com/cody-clark)
+**Blog Community Managers:** [Jorge Castro](https://github.com/castrojo), [Paris Pittman](https://github.com/parispittman) (shadow)
+
+## Contact
+
+Slack: #kubernetes-docs-blog
+Mailing List: [[email protected]](mailto:[email protected])
+Open Community Issues/PRs: area/blog label
+GitHub Team: @kubernetes/sig-docs-blog-reviews
+
+## Submit a Post
+
+Anyone can write a blog post and submit it for review. Blog posts should not be commercial in nature and should consist of content that will apply broadly to the Kubernetes community.
+
+To submit a blog post, you can either submit it using the [Kubernetes blog submission form](https://docs.google.com/forms/d/e/1FAIpQLSch_phFYMTYlrTDuYziURP6nLMijoXx_f7sLABEU5gWBtxJHQ/viewform), or follow the steps below.
+
+1. [Sign the CLA](https://kubernetes.io/docs/contribute/start/#sign-the-cla) if you have not yet done so.
+1. Have a look at the Markdown format for existing blog posts in the [website repository](https://github.com/kubernetes/website/tree/master/content/en/blog/_posts).
+1. Write out your blog post in a text editor of your choice.
+1. On the same link from step 2, click the Create new file button. Paste your content into the editor. Name the file to match the proposed title of the blog post, but don’t put the date in the file name. The blog reviewers will work with you on the final file name and the date the blog will be published.
+1. When you save the file, GitHub will walk you through the pull request process.
+1. A blog post reviewer will review your submission and work with you on feedback and final details. When the blog post is approved, the blog will be scheduled for publication.
+
+### Blog Guidelines
+
+Requested Content (with examples):
+
+* New Kubernetes capabilities
+* Kubernetes projects updates
+* Updates from Special Interest Groups
+* Tutorials and walkthroughs
+* Thought leadership around Kubernetes
+* Kubernetes Partner OSS integration
+* **Original content only**
+
+Unsuitable Content:
+
+* Vendor product pitches
+* Partner updates without an integration and customer story
+* Syndicated posts (language translations ok)
+
+## Review Process
+
+Once a blog post is submitted either via the form or a PR, it will be routed to the editorial team for review either via email for Google Docs or auto-assigning for a PR.  
+
+Each blog post requires a LGTM from one copy editor, technical editor*, and blog community manager. Once the necessary LGTMs are in place, an Editorial Lead will schedule and approve the blog post.
+
+_If a blog post does not contain any technical content (for example, [How You Can Help Localize Kubernetes Docs](https://kubernetes.io/blog/2019/04/26/how-you-can-help-localize-kubernetes-docs/)), the technical review can be omitted._
+
+### Embargoed Content
+
+The blog repository on GitHub is public, therefore any content that needs to remain confidential until a certain time (for example: release posts, security vulnerabilities) should be submitted via the form directly. On [the form](https://docs.google.com/forms/d/e/1FAIpQLSch_phFYMTYlrTDuYziURP6nLMijoXx_f7sLABEU5gWBtxJHQ/viewform), please note the time that the embargo will be lifted. In this case, the editorial team will do all reviews in Google Docs. If this is time sensitive, please email [[email protected]](mailto:[email protected]).
+
+### SLA
+
+Blog posts can take up to **2 weeks** to review. If you’d like to request an expedited review, please email [[email protected]](mailto:[email protected]).
+
+## Ongoing Blog Maintenance
+
+SIG-Docs approvers for English content can approve edits after the fact such as: broken links, copy edits, etc. However, approval and editorial review for new blog posts is limited to the Blog Team.
+
+We typically do not make edits to blog posts more than 1 years old.
+
+## Editorial Team Selection
+
+Each Editorial Team role is responsible for staffing their respective role, with this order of fall-through in mind:
+
+* training and selecting a successor from the current pool of role shadows
+* training and selecting a successor from non-Editorial Team members
+* staffing the role themselves
+
+Ultimately, if none of these can be satisfied, responsibility falls to the Editorial Team Lead and SIG-Docs to staff the roles.
+
+### Shadows
+
+We are always open to adding new shadows to the editorial team roles. If you are interested in shadowing one of the roles on the team, please fill out [this application](TBD). We review applications on a rolling basis.
+
+### Removing a Team Member
+
+If a team member can no longer fulfill their duties, the role defaults to the shadow.

sig-docs/blog-subproject/role-handbooks/blog-community-manager.md

@@ -0,0 +1,29 @@
+# Blog Community Manager
+
+## Overview
+
+The Blog Community Manager ensures that the editorial process is transparent, content serves the best interests of the community, and advocates for blog awareness and participation.
+
+## Authority and Responsibility
+
+* Ensure that content best represents the best interests of the community and is not driven by commercial interests.
+* LGTM blog posts once it is approved from a community perspective.
+
+## Skills and Experience Required
+
+* Strong written and verbal communication skills are required.
+* A working knowledge of Kubernetes concepts.
+* A working knowledge of GitHub.
+* Strong knowledge of the Kubernetes community and overall cloud native ecosystem.
+* This role should be filled by someone outside of CNCF when the editorial lead is a CNCF employee.
+
+## Activities
+
+* Attending and participating in biweekly editorial meetings.
+* Providing a review of all blog posts to ensure they meet the content guidelines and best interests of the community.
+* Work with the editorial leads to maintain transparency in the review process and proposing any necessary updates to the blog guidelines.
+* Advocating for the blog as a place for contributors to get involved and share educational content with the community. 
+
+## Time Commitments
+
+The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue.

sig-docs/blog-subproject/role-handbooks/copy-editor.md

@@ -0,0 +1,27 @@
+# Copy Editor
+
+## Overview
+
+The copy editor is the expert in spelling, grammar, and flow to ensure that all blog posts meet a high standard of quality and maintain a consistent tone of voice across the blog.
+
+## Authority and Responsibility
+
+* Ensure that content adheres to a high-level of quality with proper spelling, grammar, and logical flow of content. 
+* Own the “tone of voice” of the blog, ensuring all content has a consistent feel while maintaining the unique voice of each contributor.  
+* LGTM blog posts once it is approved from a grammar and spelling perspective.
+
+## Skills and Experience Required
+
+* Strong written and verbal communication skills are required.
+* Proficiency in English spelling and grammar.
+* A working knowledge of Kubernetes concepts.
+* A working knowledge of GitHub.
+
+## Activities
+
+* Attending and participating in biweekly editorial meetings
+* Providing a copy review on all blog posts.
+
+## Time Commitments
+
+The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue.

sig-docs/blog-subproject/role-handbooks/editorial-lead.md

@@ -0,0 +1,34 @@
+# Editorial Lead
+
+## Overview
+
+The Editorial Lead is responsible for the day-to-day management of the Kubernetes blog. This includes managing the editorial process and assembling the editorial team.
+
+## Authority and Responsibility
+
+* Ensure the editorial process runs smoothly and blogs are reviewed in a timely manner in accordance with the SLA.
+* Approve and schedule blog posts based on the editorial calendar.
+
+## Skills and Experience Required
+
+* Strong written and verbal communication skills are required.
+* Strong knowledge of the Kubernetes community and overall cloud native ecosystem.
+* Prior experience in blog management, such as PR or Marketing is extremely helpful.
+* Proficiency in GitHub and Git.
+* To properly serve as an Editorial Lead, you must have the following Kubernetes-specific qualifications:
+  * If you haven’t held an editorial team role, you must shadow the release lead for two full quarters.
+  * If you have held an editorial team role, you must shadow the release lead for one full quarter.
+  * You must be a member in good standing, and part of the Kubernetes org.
+  * You must be a member of the kubernetes-dev mailing list.
+
+## Activities
+
+* Scheduling and running biweekly editorial meetings.
+* Reviewing, assigning, and scheduling blog posts.
+* Final approval on blog posts.
+* Maintain blog documentation and process guidelines.
+* Advocating for the blog as a place for contributors to get involved and share educational content with the community.
+
+## Time Commitments
+
+The time commitment is typically 10-15 hours per quarter depending on the number of blog posts in the review queue. 

sig-docs/blog-subproject/role-handbooks/technical-editor.md

@@ -0,0 +1,26 @@
+# Technical Editor
+
+## Overview
+
+The technical editor is the subject matter expert to ensure the technical accuracy of content.
+
+## Authority and Responsibility
+
+* Ensure that content adheres to a high-level of technical accuracy and technical terminology is used consistently across the blog.
+* Assign out to the proper SIG for review if it is beyond the technical reviewers scope.
+* LGTM blog posts once it is approved from a technical perspective.
+
+## Skills and Experience Required
+
+* Proficiency in technical terminology used within the Kubernetes project.
+* Strong written and verbal communication skills are required.
+* A working knowledge of GitHub.
+
+## Activities
+
+* Attending and participating in biweekly editorial meetings.
+* Providing a technical review on all blog posts.
+
+## Time Commitments
+
+The time commitment is typically 5-10 hours per quarter depending on the number of blog posts in the review queue.