Merge pull request #4424 from jimangel/meeting-mins-archive

adding readme and past minutes

5 files changed, 6350 insertions, 0 deletions

diff --git a/sig-docs/meeting-notes-archive/2016_Weekly_Meeting_Minutes.md b/sig-docs/meeting-notes-archive/2016_Weekly_Meeting_Minutes.md
new file mode 100644
index 00000000..450765a3
--- /dev/null
+++ b/sig-docs/meeting-notes-archive/2016_Weekly_Meeting_Minutes.md
@@ -0,0 +1,314 @@
+**12/13/2016**
+
+*   1.5 is out the door.  Wooo.
+    *   New site org in 1.5
+    *   Added to tasks, tutorials, and concepts
+    *   Statefulset docs fell under concepts, tutorials, and tasks.
+    *   We want to do this the same way going forward.
+*   Template issues :(
+    *   Github issues with templates :(
+    *   They update, we break.  Markdown processor breaks the site.
+        *   First update broke the site chrome.
+        *   Current change breaks how we automate page titling.
+    *   AI: 
+        *   Explore Moving to using netlify to stage the site? (Jessfraz, Ddonnelly) 
+        *   Fix Page title needs to be fixed. 
+        *   Explore fixing templating in github pages.
+        *   Propose hiring a web-dev for the team. 
+*   TOCs
+    *   Some pages that have TOCs in flux (tools page, for example)
+    *   Should figure out a standard for organizing these pages. 
+        *   Concepts (Ddonnelly)
+        *   Tasks, Tutorials (Stevepe)
+*   Issues Triaging, Templates, Standards
+    *   [https://github.com/kubernetes/kubernetes.github.io/pull/1860](https://github.com/kubernetes/kubernetes.github.io/pull/1860) (AI: jaredb, review) 
+    *   Jan 10th is issue triage day :)
+*   1.5 RefDocs Update
+    *   [https://github.com/kubernetes/kubernetes.github.io/pull/1818](https://github.com/kubernetes/kubernetes.github.io/pull/1818)
+    *   Manually reviewing some content, verifying HTML content.
+    *   Using Deploy preview to review. 
+    *   Mehdy wants to release a blog post around the work that he’s done.
+*   Versioning
+    *   Some thoughts:
+        *   Maintain a release branch for each release
+        *   Stage using netlify
+        *   Clarify the level of support for release branches
+        *   Only 1.5 going forward
+*   Deprecation notices
+    *   Going to land on the site.  Devin will decide. 
+
+**11/28/2016**
+
+
+
+*   Meeting using Zoom
+*   1.5 Launches (Ihor, Jared)
+    *   Launch Process Updates
+    *   Link to spreadsheet https://docs.google.com/spreadsheets/d/1g9JU-67ncE4MHMeKnmslm-JO_aKeltv2kg_Dd6VFmKs/edit#gid=0
+*   License Updates (Jared) 
+    *   cla/linuxfoundation is required, google license is not.
+    *   Associated PRs:
+        *   [update LICENSE](https://github.com/kubernetes/kubernetes.github.io/pull/1763)
+        *   [update footer](https://github.com/kubernetes/kubernetes.github.io/pull/1764)
+        *   [update "how to contribute"](https://github.com/kubernetes/kubernetes.github.io/pull/1765)
+*   Style Guides (Steve) 
+    *   PRs checked in
+    *   Old Templates deleted.  Long live the new templates.
+    *   In progress: Remove some content from README and editdocs, and blend it into the new contribution pages.
+*   Issues Triaging (Abby)
+    *   PR coming soon
+    *   1/10 triage day!
+    *   Kubernetes swag will be given
+*   Quickstart Discussion: Bill Prin
+    *   Move getting started and creating a cluster content to “tasks”
+    *   Revamp content, remove GKE “Hello Node”
+    *   Jeff and Bill will come up with a more in depth proposal for next week. 
+*   API Reference docs (Phillip)
+    *   [docs.k8s.replicatingperfection.net](http://docs.k8s.replicatingperfection.net)
+    *   Questions?
+        *   Need folks to review API Docs
+        *   Sync with Devin on bandwidth
+        *   Soft launch for 1.5? 
+
+**11/15/2016**
+
+Agenda:
+
+
+
+*   Site Updates
+    *   Issue Triaging (Abby)
+        *   [http://kubernetes.io/docs/contribute/](http://kubernetes.io/docs/contribute/)
+        *   Should schedule issue-triaging day
+        *   Steve suggests review-issue.md
+    *   Reference Docs Update? (Phillip)
+        *   Should have something in two weeks
+        *   Will use the updated refdocs for 1.5
+    *   Style and Contributor Guides
+        *   PRs ready
+    *   Preparing for K8s 1.5 Release: [https://docs.google.com/spreadsheets/d/1PcAW-ZQnzlwEs59ygHdFA-72n6FUcGIc2lx4IeoXvco/edit?ts=57ced759#gid=110968752&vpid=A1](https://docs.google.com/spreadsheets/d/1PcAW-ZQnzlwEs59ygHdFA-72n6FUcGIc2lx4IeoXvco/edit?ts=57ced759#gid=110968752&vpid=A1)
+*   Dev Summit Feedback
+    *   [Brainstormed Issues with Site](https://github.com/kubernetes/kubernetes.github.io/issues/1686)
+    *   [UX issues ](https://docs.google.com/document/d/1BoF_wA7J6N-zuCUgwMMj27ngaj3e4T0YJhvTNwWiWj8/edit#heading=h.y2ttshn5nulr)
+    *   [Brainstorm on Developer Onboarding](https://docs.google.com/document/d/19B2vcK6Y3xE3JO7sd4n6lPF0m9bBVZpNucvcR3MwEXA/edit)
+*   PR backlog
+
+**10/25/2016**
+
+Agenda
+
+
+
+*   Site Updates
+*   Issue Backlog
+    *   Doc shared with the SIG docs group
+    *   [https://docs.google.com/document/d/1j1A6sVW_t5RF_dlxIxpWVbAQeLUlzR1Z26zENBltRms/edit](https://docs.google.com/document/d/1j1A6sVW_t5RF_dlxIxpWVbAQeLUlzR1Z26zENBltRms/edit) 
+*   Reference Docs Update
+*   Redirects on Github?
+*   API and CLI Docs updates
+    *   [http://docs.k8s.replicatingperfection.net/](http://docs.k8s.replicatingperfection.net/)
+    *   [http://kubectl.k8s.replicatingperfection.net/](http://kubectl.k8s.replicatingperfection.net/)
+*   Suggested task docs
+    *   
+
+**10/11/2016**
+
+No meeting due to technical issues. 
+
+**9/27/2016**
+
+Announcements
+
+
+
+*   1.4 went live!  Hoorays!
+*   Templates and new site layout went live! ([http://kubernetes.io/docs/](http://kubernetes.io/docs/))
+    *   Tons of work to do here. 
+*   Bootcamp pages integrated into site:
+    *   http://kubernetes.io/docs/tutorials/getting-started/create-cluster/
+
+Agenda
+
+
+
+*   Launch process for upcoming releases
+    *   [Keep the spreadsheet](https://docs.google.com/spreadsheets/d/1PcAW-ZQnzlwEs59ygHdFA-72n6FUcGIc2lx4IeoXvco/edit?ts=57ced759#gid=0)
+        *   Sync with [Community Spreadsheet](https://docs.google.com/spreadsheets/d/1MeTQbtSiTCoQ74zjEGRI1rXRSP0Tzmo9-kMJSK_HGoA/)
+    *   Communicate out which branch to use
+        *   Delete the version branch immediately after launch? (most people say yes)
+        *   Number each branch
+*   Pointing to the “right” version of kubernetes:
+    *   [https://groups.google.com/forum/#!topic/kubernetes-sig-docs/d5vB92b4HaI](https://groups.google.com/forum/#!topic/kubernetes-sig-docs/d5vB92b4HaI)
+    *   Toolset with the documentation deploys 1.3
+    *   Please push to master :)
+*   Issues:
+    *   PR template is in!
+    *   Jeff Menoza needs to merge template with “create issue” button
+    *   Proposal for issues will be out for review. 
+
+Kudos
+
+
+
+*   Phillip Wittrock
+*   Devin Donnelly
+
+**9/20/2016**
+
+Agenda
+
+
+
+*   1.4 Delayed until next week ([1.4 Spreadsheet)](https://docs.google.com/spreadsheets/d/1PcAW-ZQnzlwEs59ygHdFA-72n6FUcGIc2lx4IeoXvco/edit?ts=57ced759#gid=0)
+*   [Doc Templates ](https://github.com/kubernetes/kubernetes.github.io/pull/1205)
+    *   Any more feedback?
+    *   Still adding canonical examples
+    *   Outstanding questions for those TBD by jeffmendoza
+*   Bootcamp integrated into master ([pending PR](https://github.com/kubernetes/kubernetes.github.io/pull/1203))
+    *   Not using the templates
+    *   Keeping the existing CSS
+*   Issue Template update?
+    *   PR filed
+        *   CLA isn’t approved. Weird.
+        *   Is your github account under your company’s email?
+    *   Next Steps:
+        *   Submit PR
+        *   AI: Develop proposal for handling backlog of issues (Abby)
+        *   Run it by Frank for review
+*   Dead link report:
+    *   AI: Regenerate the report, mark what will fixed in the upcoming release (1.4), focus on fixing manually generated content
+
+Updates:
+
+
+
+*   New “edit docs” button at the bottom of the page
+*   Fix in for generating API and Kubectl docs (no more broken links! Won’t get in until 1.4).
+*   Kudos to Abby for creating the PR for issue templates
+
+**9/13/2016**
+
+Agenda
+
+
+
+*   Update on Netlify! (Devin)
+*   Dan Paik - new PM on Gcloud/K8s - will be working on cluster deployments, GKE UI, and PetSet deployments
+
+Updates:
+
+
+
+*   “I wish” is gone.  “File an issue” instead. (thanks Jeff!)
+    *   Still need guidelines to close issues :)
+*   Status of issue templates and guidelines? (Abby?)
+    *   Took a stab at [making an issue template](https://docs.google.com/document/d/1aZ6vlxOhNtKNhNOUx_KTUw1bXCPPRH2_TJsNRz7CA58/edit?ts=57d83501) (in Google Doc)
+    *   Feedback:
+        *   Keep existing title with URL
+        *   Specify feature vs. bug (new doc vs. doc update)
+    *   File a PR :)
+*   [1.4 Process](https://docs.google.com/spreadsheets/d/1PcAW-ZQnzlwEs59ygHdFA-72n6FUcGIc2lx4IeoXvco/edit?ts=57ced759#gid=0)
+*   [Templates ](https://github.com/kubernetes/kubernetes.github.io/pull/1205)(Steve)
+    *   - Netlify
+*   [SEO Issues with K8s](https://docs.google.com/document/d/19A8GL7lNpvrVZJyPLHYgM7axcw6PWxT1yjQydno58L0/edit#heading=h.ucf6rfasc6ai)
+
+**August 30, 2016**
+
+Agenda:
+
+
+
+*   Customer Feedback:
+    *   “I wish”
+        *   Make an issue / Make an edit
+        *   Remove the functionality, replace with make an issue/made edits
+        *   AI: Jeff Mendoza
+    *   Star ratings vs. Thumbs Up
+*   Issues :(
+    *   300 issues
+    *   Write up a md file for issue guidelines?
+    *   Issue templates?
+        *   AI: Abby: 
+            *   Issue guidelines
+            *   Issue template
+    *   Close issues that don’t conform
+*   Steve chat [through new templates](https://github.com/kubernetes/kubernetes.github.io/tree/docsv2/_includes/templates). 
+*   1.4 Features and Publishing
+    *   Alpha: [14 Open Issues](https://github.com/kubernetes/features/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Aalpha-in-1.4%20)
+    *   Beta: [8 Open Issues](https://github.com/kubernetes/features/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Abeta-in-1.4%20)
+    *   Stable: [5 Open Issues](https://github.com/kubernetes/features/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3Astable-in-1.4%20)
+    *   Publishing process?
+        *   Current release branch 
+        *   Under development release
+        *   Make a rule that any change in the current version has to be made in the “under development” version.
+
+**August 23, 2016**
+
+Agenda
+
+
+
+*   Introductions - New Members
+    *   Jared, Abby (Apprenda), Frank Solomon (Blogger, SWE)
+*   Items from the past meeting: 
+    *   Third party docs?  Process for moving them?  Plan?  
+        *   [Issue in current UX Backlog](https://github.com/kubernetes/kubernetes/milestone/24)
+*   [Dead Link Report](https://docs.google.com/spreadsheets/d/1vLmdCSZngIRUtBcG04QGWSQ42Pr3198n-RMctq8Kv7I/edit#gid=969833937) 
+    *   If you have time please fix!
+    *   Please keep the status up to date
+*   Kubernetes Bootcamp (Beta)
+    *   [https://kubernetesbootcamp.github.io/kubernetes-bootcamp/](https://kubernetesbootcamp.github.io/kubernetes-bootcamp/)
+    *   Please review if you have a chance
+
+**August 16, 2016**
+
+Kickoff Meeting!
+
+Agenda
+
+
+
+*   Introductions - New Members
+    *   Jared (TW, Manager), Phillip (SWE, UX), Devin (TW), Steve (TW), Josh (SWE), Dan Romlein (UX, Apprenda), Abby (TW, Apprenda), Sarah Novotny (Community), Janet (SWE, UX), Frank, Morgan (TW, IBM)
+*   Current state of the docs (Jared)
+    *   John Mulhausen has left the group
+    *   Devin and Steve are joining full time from Google
+    *   We want to make things easier for users navigating the site, and contributors contributing to the site. 
+*   Doc goals and doc plans (Devin)
+    *   Building on John’s work, building new processes. 
+    *   Some findability and readability improvements in the short term. 
+    *   Significant problems with findability.
+        *   Title != URL != Place in table of contents.  
+    *   Good content with some better organization
+        *   For example:
+            *   Glossary is a collection of “conceptual articles”.  Should better explain the “kubernetes model”
+            *   Also, a good place for new diagrams.
+    *   Better guidance on audience.  Explicitly state who our audience is:
+        *   App Builders - Just running an application on top of K8s. Probably don’t want/need to know too much about what’s “under the hood”
+        *   Container Maintainers/Builders - Want to know the deeper aspects of K8s. 
+    *   Build out the contributor 
+        *   Style Guide (titling docs, content fit into categories, tone and term usage to unify content and fix SEO) 
+        *   Templates - Build out 
+        *   Contribution process
+    *   Questions:
+        *   Third party docs?  How do we build and maintain them?
+            *   Proposal - that content should not live inside the core repo, since we can’t maintain it well. 
+            *   No objections to this proposal so far....  Need to have a way to separate this process out and find new homes for it. 
+            *   Need an owner for this process. 
+
+Additional Agenda Items?
+
+*   New contributor onboarding process (Phillip)
+    *   **_Style guide (Josh)_**
+    *   Initial tasks for new contributors
+    *   Repo Issues list
+        *   Github Issues that writers take on?
+    *   Getting help
+        *   Slack Channel (#sig-docs) for folks who need help or guidance. 
+        *   Feel free to ping 
+        *   To login to Zoom: Phillip directly. 
+*   Diagrams - How should we create these? (Phillip)
+
+Issues, suggestions, concerns, kudos?
+
+*   Kudos:  Thanks to Phillip Wittrock and Kelsey Hightower for closing out our list of outstanding docs PRs
\ No newline at end of file
diff --git a/sig-docs/meeting-notes-archive/2017_Weekly_Meeting_Minutes.md b/sig-docs/meeting-notes-archive/2017_Weekly_Meeting_Minutes.md
new file mode 100644
index 00000000..da372618
--- /dev/null
+++ b/sig-docs/meeting-notes-archive/2017_Weekly_Meeting_Minutes.md
@@ -0,0 +1,1373 @@
+**12/19/2017**
+
+**NOTE: No meeting 12/26, Happy Holidays!**
+
+**NOTE: Jared B. will run first meeting of 2018 (Zach on vacation)**
+
+New attendees?
+
+*   
+
+Version 1.9 retrospective
+
+
+
+*   Docs are live! Thanks to: 
+*   Topics for retrospective?
+    *   Feature docs:
+        *   Last-minute mess from an unclear PR
+        *   In the future, clean PRs only (no reverts/rebases)
+    *   Release notes:
+        *   Script adjustments, pull in descriptions from PRs
+*   Future docs release meisters
+*   1.10: Jennifer Rondeau
+*   1.11: Nick Chase
+*   Chris Short (@chris-short) wants to shadow a release
+
+Docs summit 2018
+
+
+
+*   Polling for interest in a SIG-Docs summit
+*   Early 2018? May/June?
+
+Supported documentation versions
+
+
+
+*   Need to follow up on https://github.com/kubernetes/website/pull/6442 re:current+4 
+
+Reviewer conventions in docs files (Steve & Andrew)
+
+
+
+*   Follow-up: automation and names in front matter of file?
+*   Andrew will follow up with tooling people to modify bots to specify category
+
+Automation meeting
+
+
+
+*   Do we still want to have an automation summit? I.e., a meeting dedicated solely/heavily to autogenerated docs
+*   Set a date for early February
+
+Building a community site (community.k8s.io) for developer contributions:
+
+From Joe Beda: 
+
+https://github.com/kubernetes/community/pull/1401/files
+
+
+    As we start thinking about KEPs and community guides I think it makes sense to consider a new site that is community facing (vs. user facing).  This is something that came up in the last SIG-architecture meeting.
+
+
+    Concretely, I'd like to find a way to have a good cross-indexed and nicely looking site to expose the KEPs.  But there is a need to make our community facing documentation much more approachable also. The pile of markdown files in github isn't working well IMO.
+
+
+
+*   Follow up on streamlining the contributor process
+*   Contributor user journey (Andrew/Paris)
+*   Action item: Steve will take on for study and report back in Q1
+
+What to do with Kops docs?
+
+
+
+*   Talk about provider-specific docs in January (date TBD, Chris Love invited to join)
+
+**12/12/2017**
+
+**NOTE: No meeting 12/5, KubeCon or bust!**
+
+New attendees?
+
+
+
+*   Chris Short (Michigan)
+
+Doc sprints at Kubecon (Zach)
+
+
+
+*   How’d they go?
+*   Steve: one improvement: different way to claim an issue (hard to track in Slack, doing it in issue create overlapping edits)
+*   Jennifer: confusing to have first-time contributor review sprint PRs, created need for multiple review rounds: shepherd first-time contributors into creator roles, not reviewer roles
+*   Registration: remove cap? Expose cap? 
+
+Version 1.9 status
+
+
+
+*   Steve: Here are the [four PRs](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Aopen+is%3Apr+author%3Asteveperry-53+base%3Arelease-1.9) for the auto-generated ref docs.
+*   Steve: What's the plan for the remaining [PRs for release-1.9](https://github.com/kubernetes/website/pulls?utf8=%E2%9C%93&q=is%3Apr+is%3Aopen+base%3Arelease-1.9)?
+    *   Thaw, merge, re-freeze on Thursday 12pm PST
+*   Zach: Release cut delayed until Friday
+    *   Send email to sig-docs-maintainers about freeze
+*   Jennifer: A heads up or two for retrospective/lessons learned/proposals for 1.10 release notes
+    *   For release notes: embed docs contributors in other SIGs early in the release process?
+    *   Talk with Sig-PMs/release meister EARLY in the release process
+
+Future docs release meisters
+
+
+
+*   1.10: Jennifer Rondeau
+*   1.11: Nick Chase
+
+Supported documentation versions
+
+
+
+*   Current+4 (as of 1.9, that means 1.9-1.5 docs are published)
+*   Add release playbook to repo (including release notes)
+*   Specify in style guide that supported versions = current+4
+*   Specify that we do not accept PRs against older versions
+
+Reviewer conventions in docs files:
+
+
+
+*   Follow-up from 11/28
+*   Tech reviewers: set up a discussion about conventions (reviewers in front matter? OWNERS file?) and automation
+    *   Set up OWNERS file for automation (categories for tech review by SIG)
+    *   Add SIG names to individual file front matter (Andrew & Steve will research)
+
+Note for 2018: Revisit automation after 1/1, aka “automation summit”
+
+**11/28/2017**
+
+New attendees?
+
+
+
+*   
+
+Doc sprints at Kubecon (Zach)
+
+
+
+*   Where are we at?
+*   Send questionnaire to participants: poll for experience level/pre-load participant distribution [zach]
+*   Jason K is local to Austin and can help ferry donuts
+
+Proposal: issue bankruptcy (Zach)
+
+
+
+*   Managing backlog of issues we can’t or won’t touch
+*   Monthly triage to close issues that haven’t been updated in past 6 months
+*   Provide specificity in closing comments
+*   Provide notice initially
+*   Ongoing monthly maintenance
+*   Triage issues in kubernetes/kubernetes
+
+Mentoring program (Paris)
+
+
+
+*   How to build in tech reviewers for docs
+*   Slide deck: [https://docs.google.com/presentation/d/1bRjDEPEn3autWzaEFirbLfHagbZV04Q9kTCalYmnnXw/edit](https://docs.google.com/presentation/d/1bRjDEPEn3autWzaEFirbLfHagbZV04Q9kTCalYmnnXw/edit)
+*   Test cohort expertise: kubeadm, helm, charts
+*   Tech reviewers: set up a discussion about conventions (reviewers in front matter? OWNERS file?) and automation: next SIG meeting
+
+Note for 2018: Revisit automation after 1/1, aka “automation summit”
+
+Auto generation of ref pages (Steve)
+
+
+
+*   The scripts for generating the federation docs were broken, but have been repaired. Thanks to Maru Newby. [PR 158](https://github.com/kubernetes/federation/pull/158), [PR 157](https://github.com/kubernetes/federation/pull/157). These scripts generate the docs that we publish [here](https://kubernetes.io/docs/reference/federation/v1/operations/) and [here](https://kubernetes.io/docs/reference/generated/kubefed/).
+*   I'm still working on [PR 6366](https://github.com/kubernetes/website/pull/6366).
+
+**11/21/2017**
+
+New attendees?
+
+Versioning follow-up (Zach, Steve)
+
+
+
+*   Follow up on conversation from 10/31 weekly meeting
+*   [Example of versioned doc set](https://v1-7.docs.kubernetes.io/docs/home/)
+*   Problem: Site search doesn't stay in the versioned set ([https://github.com/kubernetes/website/issues/5930](https://github.com/kubernetes/website/issues/5930))
+*   Open issues against search functionality vs. versioning
+*   Related issues:
+    *   [https://github.com/kubernetes/website/issues/322](https://github.com/kubernetes/website/issues/322)
+    *   [https://github.com/kubernetes/website/issues/3992](https://github.com/kubernetes/website/issues/3992)
+    *   [https://github.com/kubernetes/website/pull/4386](https://github.com/kubernetes/website/pull/4386) (PR for previous issues)
+
+Doc sprints at Kubecon (Zach, Jennifer)
+
+
+
+*   Where are we at?
+*   Steve Perry will be a facilitator!
+*   Create a project dedicated to the doc sprint, more chunkable/understandable in context of a single sprint
+*   Schedule a short meeting with Andrew, Jennifer, Steve
+
+Auto generated reference docs (Steve)
+
+
+
+*   [Main discussion and long-term plan](https://docs.google.com/document/d/1z358PD4qyD5fawwmqPuE1YPulAmzn7rx4JazaWQzc70/edit?ts=59dd113d#heading=h.yj4trut19r8z)
+    *   This is Joe's document. This is where I think we should have the discussion about the overall vision and long-term plan for generated reference docs.
+*   [Proposal for Q4 and Q1](https://docs.google.com/a/google.com/document/d/1P4h-IES6zDV4P3tBagNLbLfh6QtfnNd__jHewqwAbxY/edit?usp=sharing)
+    *   This is Steve's proposal. This is what Steve thinks is reasonable to get done during 2017 Q4 and 2018 Q1.
+*   [Issue for tracking work on ref docs](https://github.com/kubernetes/website/issues/6037)
+    *   This issue is for keeping track of getting the various Kubernetes reference docs all organized under /docs/reference.
+*   [WIP: PR for documenting the generation process](https://github.com/kubernetes/website/pull/6366)
+    *   [Preview topic](https://deploy-preview-6366--kubernetes-io-master-staging.netlify.com/docs/home/contribute/generated-reference/kubernetes-components/)
+*   Surprises
+    *   We generate [man pages](https://github.com/kubernetes/kubernetes/tree/master/docs/man/man1). And they get published [here](http://manpages.org/kube-controller-manager) and [here](http://rpm.pbone.net/index.php3/stat/45/idpl/30415699/numer/1/nazwa/kubectl-create).
+    *   We generate the kubectl docs in [YAML](https://github.com/kubernetes/kubernetes/tree/master/docs/yaml/kubectl) format. I don't know whether these get used.
+*   Three separate areas of concentration: \
+
+    *    **API ref docs and kubectl command ref docs**: We generate these using Phil Wittrock's code at [github.com/kubernetes-incubator/reference-docs](https://github.com/kubernetes-incubator/reference-docs). Steve Perry is now the owner of this code. This code requires a lot of human attention at each Kubernetes release. Steve is working on reducing the amount of human attention required, but doesn't expect to have the updated code in place until 2018 Q1. \
+**Note**: In the past, the kubectl command docs were generated by [gen_kubectl_docs.go](https://github.com/kubernetes/kubernetes/blob/master/cmd/gendocs/gen_kubectl_docs.go). This is no longer the case. Now they are generated by [kubernetes-incubator/reference-docs/gen-kubectldocs](https://github.com/kubernetes-incubator/reference-docs/tree/master/gen-kubectldocs).
+    *   **kubeadm ref docs**: Fabrizio is working on improving the kubeadm ref docs. The kubeadm ref docs will be a blend of generated content and human-authored content. Steve will take a close look at this effort today. [https://github.com/kubernetes/website/pull/6103](https://github.com/kubernetes/website/pull/6103) \
+
+    *   **All other ref docs**: kube-apiserver, kube-scheduler, kubectl-proxy, etc. We generate most of these using [https://github.com/kubernetes/kubernetes/blob/master/cmd/genkubedocs/gen_kube_docs.go](https://github.com/kubernetes/kubernetes/blob/master/cmd/genkubedocs/gen_kube_docs.go).
+*   Revisit automation after the first of 2018 for an “automation summit”
+
+**11/14/2017**
+
+New attendees?
+
+
+
+*   
+
+Auto generated reference docs (Steve Perry)
+
+
+
+*   Delayed one week: 11/21
+
+Improving Kubeadm reference (Fabrizio)
+
+
+
+*   [https://github.com/kubernetes/website/pull/6103](https://github.com/kubernetes/website/pull/6103)
+*   -If no blockers, will remove [WIP] and start merging for 1.9
+*   SIG docs will review and comment on the PR by 11/14
+
+Google Container Engine name change
+
+
+
+*   From [https://github.com/kubernetes/website/pull/6300#issuecomment-344069008](https://github.com/kubernetes/website/pull/6300#issuecomment-344069008):
+    *   Google Container Engine is now Kubernetes Engine
+    *   Use “Google Kubernetes Engine” instead of GKE acronym
+*   Open issue for find/replace: [https://github.com/kubernetes/website/issues/6302](https://github.com/kubernetes/website/issues/6302)
+*   Should be covered by [PR #6300](https://github.com/kubernetes/website/pull/6300), but please double check.
+
+Kubecon doc sprints (Zach)
+
+
+
+*   Reaching out to registered participants this week (by Friday 11/17)
+
+**11/7/2017**
+
+
+
+*   New attendees?
+    *   
+*   Steve (via Ahmet): Search for "kubernetes deployment". The top result is a paid advertisement that goes to the [Platform 9](https://get.platform9.com/glp-kubernetes-deployment-models-the-ultimate-guide/?_bk=%2Bkubernetes%20%2Bdeployment&_bt=196922830976&_bm=b&_bn=g) site. In general, is this type of thing something we should be concerned about?
+    *   (Zach) From Dan Kohn: \
+1. It’s not that problematic. \
+2. There’s nothing we can do about it.
+*   Improving Kubeadm reference (Fabrizio)
+    *   [https://github.com/kubernetes/website/pull/6103](https://github.com/kubernetes/website/pull/6103)
+    *   -If no blockers, will remove [WIP] and start merging for 1.9
+    *   SIG docs will review and comment on the PR by 11/14
+*   Doc sprints at KubeCon
+    *   Update on user journeys for doc sprints: Jennifer Rondeau
+        *   There’s suitable work to support discrete aspects of user journeys
+        *   Repo labels: help wanted
+    *   Consider options for two rooms: one SIG structured (user journeys), one participant structured (individual/small team goals)
+        *   Encourage K8s experts to choose user journeys
+        *   User journeys: help wanted label
+        *   Glossary: [[Issue #5993](https://github.com/kubernetes/website/issues/5993)]
+    *   Reviewers needed: if you’re not attending, you can still participate!
+        *   Tuesday 1-5pm December 5th
+    *   Custom t-shirts for SIG-doc attendees ;-) (Radhika)
+        *   Use CNCF’s existing flow ([the Kubernetes store](https://store.cncf.io/collections/kubernetes))
+    *   Social media outreach to spread the news about K8s Doc sprint (Radhika)
+        *   Boost visibility for SIG
+    *   Usability study (questionnaire to distribute among randomly selected K8s users)? (Radhika)
+        *   Meet UX people at Kubecon
+        *   Poll after user journeys are released
+*   Tech reviews (Zach)
+    *   We need a fresher [list of tech reviewers](https://github.com/kubernetes/website/wiki/Tech-reviewers) with a wider base of issue coverage
+    *   Work with Paris Pittman to get a list of reviewers per SIG
+    *   Use @mentions to ask for a reviewer from that SIG
+    *   SIG-contribex is working on mentorship process
+    *   Check kubernetes/kubernetes for OWNERS file
+        *   Talk with people who work on Kubernetes robots to find reviewers
+        *   @cjwagner
+
+**10/31/2017**
+
+
+
+*   New attendees?
+    *   
+*   Agenda items
+    *   Doc sprints KubeCon (Jared)
+        *   Is there a pre-reg list? (Ask Jared) Yes!
+        *   Is there a way to contact sprint registrants? (Jared/Sarah Novotny)
+            *   Send notification for license agreement
+    *   i18n update (Zach)
+        *   Fixing original docs is a non-goal for translation
+        *   Mature style guide: explicit standards for internationalization (action item for Zach)
+            *   Include explanations for why guidelines are in place: readability for English speakers of all levels
+            *   Standards to mention: present tense; aim for reusability long-term; minimize text in diagrams
+            *   Expectations for L10n workflow: what do we set, what do they set?
+            *   Specify separation of labor
+            *   Provide a method for upstream contribution
+            *   Set expectations for how commits are made/bundled (commits need to not be made through website)
+    *   Kubernetes version requirements for tasks and tutorials in 1.8 docs (Steve)
+        *   [Example](https://kubernetes.io/docs/tasks/run-application/run-stateless-application-deployment/)
+        *   Versioning content: we need to figure it out!
+        *   Revisit on 10/31 for deeper discussion
+        *   Pertinent to GKE as well: when is it appropriate to update documentation? How to position new API/K8S versions to users on older versions? (Ryan)
+        *   Specify required Kubernetes version in "Before you begin" for tasks needing a higher version due to an `apiVersion` change.
+        *   Steve to provide example solution at next meeting.
+
+**10/24/2017**
+
+
+
+*   New attendees?
+    *   Peter Zhao
+*   Agenda items
+    *   Doc sprints KubeCon (Jared)
+        *   Tuesday, December 5, 1:00pm - 5:00pm
+        *   Setup is two rooms, so it makes sense to do two projects? 
+        *   [https://github.com/kubernetes/website/projects/3](https://github.com/kubernetes/website/projects/3)
+        *   [https://github.com/kubernetes/website/issues/5741](https://github.com/kubernetes/website/issues/5741)
+        *   Suggested projects:
+            *   Glossary [[Issue](https://github.com/kubernetes/website/issues/5993) to add more terms]
+            *   User Journeys
+                *   Jennifer Rondeau will scope out some foundational work to support user journeys, will give up or down by 11/3
+        *   Sprint ideas: “Is there something you’ve always wanted to work on?”
+    *   Docs development branch (Jordan Liggitt)
+    *   Monthly 404 update (Zach)
+    *   Translation efforts: changing scope (Zach)
+        *   Fixing original docs is a non-goal for translation
+    *   Kubernetes version requirements for tasks and tutorials in 1.8 docs
+        *   [Example](https://kubernetes.io/docs/tasks/run-application/run-stateless-application-deployment/)
+        *   Versioning content: we need to figure it out!
+        *   Revisit on 10/31 for deeper discussion
+*   Code sample styling prototype, Part 2 (Jessica Yao)
+
+**10/17/2017**
+
+
+
+*   New attendees?
+    *   
+*   Agenda items
+    *   1.9 release shadow
+        *   Need a shadow for the 1.10 release (must be a sig-docs maintainer)
+            *   Brad Topol, Abigail McCarthy, Jessica Yao (will follow up)
+    *   Recent updates:
+        *   Glossary
+        *   Chinese translation process
+    *   Doc sprints KubeCon 
+    *   How to improve kubeadm reference doc (Fabrizio)
+        *   Goal to improve docs for 1.9 release
+        *   Currently maintaining pages manually
+            *   Want to improve reference docs like kubectl or kubefed through automation
+        *   Want to add docs for advanced topics
+        *   Fabrizio and Joe Heck will talk more about automation
+    *   Code sample styling prototype (Jessica Yao)
+        *   It looks awesome :-)
+
+
+#### 10/10/2017
+
+
+
+*   New attendees?
+    *   Anthony Bushong at Google (welcome!)
+*   Agenda items
+    *   Doc sprints (Jared)
+        *   Write the Docs Melbourne (Issue, TBD): Friday, November 24, 9am-12pm
+        *   Kubecon ([Issue](https://github.com/kubernetes/kubernetes.github.io/issues/5741)): Tuesday, December 5, Time: 1pm - 5pm
+    *   Onboarding for new contributors (Zach)
+    *   Migrate K8s blog from Blogger to GitHub ([#5823](https://github.com/kubernetes/kubernetes.github.io/issues/5823)) (Zach)
+    *   Renaming kubernetes/kubernetes.github.io to kubernetes/website (Andrew)
+        *   Yes: Andrew will work to perform cutover
+    *   How To - Generated Docs (/docs/admin/…) and managing those (Joe Heck)
+        *   Document how to update docs; *not* with manual updates to generated output in docs repo.
+        *   Steve Perry has taken on automation process in general
+        *   Heckj will create a [Google doc](https://docs.google.com/document/d/1z358PD4qyD5fawwmqPuE1YPulAmzn7rx4JazaWQzc70/edit#), coordinate with other collaborators; where to store it in GitHub is an open question (GitHub wiki?)
+    *   Glossary [demo](https://deploy-preview-5657--kubernetes-io-master-staging.netlify.com/docs/reference/glossary/?fundamental=true)? (Jessica, Andrew)
+        *   PR: [#5657](https://github.com/kubernetes/kubernetes.github.io/pull/5657)
+*   Bump to next week
+    *   Code sample prototype (Jessica Yao)
+
+
+#### 10/3/2017
+
+
+
+*   New attendees?
+    *   Brad Topol, IBM
+    *   Ryan Jarvinen (ryanj), Red Hat
+*   Agenda Items
+    *   1.8 release went out the door last week!
+        *   Thanks, Steve Perry and Jaice Singer Dumars!
+        *   Retrospective is scheduled for this Friday, October 6
+    *   [1.8 Release note writeup](https://docs.google.com/document/d/17af5ZkRX83ISvizml9FKPc9TCtCIp9PecXpNGh324M8/edit?usp=sharing) (Jennifer)
+        *   Seeking feedback in the doc
+        *   Jennifer/Radhika: improving visibility for release notes?
+            *   Where are release notes published? 
+                *   Dual-sourcing content?
+                *   Build/site automation pulling build from another source?
+            *   How can we maximize quality?
+            *   Poll Jaice Singer Dumars (and Brian Grant) for vision on what users actually want from release notes
+            *   Two different challenges:
+                *   How to create content
+                    *   1.8 processes seemed to work really well; this seems solved
+                *   How to serve it/what do users need
+    *   Code sample formatting
+        *   Why is it the way it is?
+        *   Are we willing to consider adding prompts?
+            *   CSS and formatting for “best of both worlds”
+        *   Please keep bikeshedding to a minimum :-)
+        *   Jessica Yao will build a prototype for 10/10
+            *   Steve Perry requests: command format, output format, and how command/output will be explained
+        *   Continue this discussion at 10/10 meeting
+*   Docs Sprint @ Kubecon
+    *   Date: Tuesday, December 5
+    *   Time: 1:00pm - 5:00pm
+    *   30 boardroom seating, split across two non-conjoining rooms (this does account for AV)
+    *   There is a cost for renting the room during the conference, which I’m trying to figure out with CNCF/Community folks.
+    *   Any ideas for themes? 
+        *   Glossary
+        *   User Journeys
+    *   Assistants: 4 (2 for each room)
+    *   Tracking issue: [https://github.com/kubernetes/kubernetes.github.io/issues/5741](https://github.com/kubernetes/kubernetes.github.io/issues/5741)
+    *   Jared is running a half-day sprint in Melbourne on Nov 27, guinea pigs abound! :-)
+
+
+#### 9/26/2017
+
+
+
+*   New Attendees?
+    *   Chris Negus (Red Hat)
+    *   Andrew Burden (Red Hat)
+*   Agenda Items
+    *   [Updates](https://groups.google.com/d/msg/kubernetes-dev/IC-A0opoeno/Bmi4mOIGAwAJ) on 1.8
+        *   Release notes (Jennifer)
+            *   Radhika and I are working through new edits.
+            *   Focus is on content
+            *   Lot to say in the retrospective today
+            *   Getting the information from SIGs, chasing folks down. Started with SIGs now going after individuals. 
+            *   Features vs. Issues vs. PRs.  What should release notes refer to? 
+            *   Is there a space between automating everything, and a human chasing every release note down? 
+            *   Process and/or tools needed.  Jennifer will write up a plan. 
+        *   Feature docs (Steve)
+            *   Official blog post is not quite done
+            *   All PRs are merged except for reference docs.
+            *   [Reference docs](https://github.com/kubernetes/kubernetes.github.io/pull/5632) for API and kubectl need tech review. Plan to merge today.  On track. 
+            *   Still need to auto generate the [reference docs for cloud controller manager](https://github.com/kubernetes/kubernetes/pull/47934). @mengqiy is working on this.
+    *   New maintainers
+        *   Tim Zhang ([https://github.com/zhangxiaoyu-zidif](https://github.com/zhangxiaoyu-zidif))
+        *   Peter Zhao ([https://github.com/xiangpengzhao](https://github.com/xiangpengzhao)) 
+        *   Tim and Peter will working mostly on Chinese language PRs
+    *   Documentation of cloud providers config (Luke).
+        *   OpenStack: 
+        *   Current docs: [https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/)
+        *   Create a PR and work from there. 
+*   No presentation today from Radhika; will reschedule for the future.
+
+
+#### 9/19/2017
+
+
+
+*   New Attendees?
+    *   heckj - Joe Heck
+*   Agenda Items?
+    *   [Updates](https://groups.google.com/d/msg/kubernetes-dev/IC-A0opoeno/Bmi4mOIGAwAJ) on 1.8
+        *   Release notes (Radhika)
+            *   Cutoff date was September 9, but deadline extended until testing is more stable
+            *   More PRs coming in, working with Jaice DuMars
+        *   Feature docs (Steve)
+            *   Large influx submitted within past day
+            *   Reviewers welcome! 1.8 release branch/1.8 milestone to find PRs for review
+        *   [1.8 tracking board](https://docs.google.com/spreadsheets/d/1AFksRDgAt6BGA3OjRNIiO3IyKmA-GU7CXaxbihy48ns/edit#gid=0)
+    *   Community & Repo Maintenance
+        *   126 open PRs in [queue](https://github.com/kubernetes/kubernetes.github.io/pulls)
+            *   21 in 1.8 milestone
+            *   18 in Chinese translation milestone
+            *   Only 13 need tech review
+            *   Review help is welcome! (Stick to [1.8 branch](https://github.com/kubernetes/kubernetes.github.io/pulls?utf8=%E2%9C%93&q=is%3Aopen%20is%3Apr%20milestone%3A1.8%20) for now: [needs tech review](https://github.com/kubernetes/kubernetes.github.io/pulls?q=is%3Aopen+is%3Apr+milestone%3A1.8+label%3A%22Needs+Tech+Review%22))
+            *   Lots of tiny PRs; in the past, release time = more PRs
+            *   Difficult to parse relevant PR's due to low signal:noise ratio.
+            *   Come up with a scalability plan for PRs two weeks after release
+        *   Monthly 404 maintenance
+            *   404s are leveling off post-netlify deploy
+            *   Props to Andrew Chen for clearing the log!
+        *   GitHub UI bug (Zach)
+            *   Contacted support about UI behavior for “allow edits from maintainers”, waiting for a response 
+            *   In the meantime, how do we want to alert contributors to the workaround?
+*   Presentation: open source projects (Radhika)
+    *   Rescheduled for 9/26
+
+
+#### 9/12/2017
+
+
+
+*   New Attendees?
+    *   
+*   Agenda Items?
+    *   Repo labels (Zach)
+        *   Down from 154 to 30 [#5339](https://github.com/kubernetes/kubernetes.github.io/issues/5339)
+        *   By request, new label for tutorial-related content: team/katacoda
+        *   If we need a label and there isn’t one, open an issue
+    *   [Updates](https://groups.google.com/d/msg/kubernetes-dev/IC-A0opoeno/Bmi4mOIGAwAJ) on 1.8
+        *   (from Jennifer) Where are we at with release notes?
+            *   Short with information: many changes remain undocumented
+            *   Jennifer will approach contributors from feature development; may ask for help from other docs contributors
+            *   Need affirmative information from feature developers, even if there’s no release notes needed
+        *   Herding cats: still in progress :-) 
+        *   [1.8 tracking board](https://docs.google.com/spreadsheets/d/1AFksRDgAt6BGA3OjRNIiO3IyKmA-GU7CXaxbihy48ns/edit#gid=0)
+    *   Kubernetes code contributor guide [#892](https://github.com/kubernetes/community/issues/892) (Andrew)
+        *   Update: Andrew’s working with Paris
+            *   Need two key people: Michael Hausenblas & Jorge
+            *   High level framework first
+            *   Initial MVP shouldn’t be too difficult; initial materials already exist, have been assembled by Michael
+    *   Chinese Translation Project (Andrew)
+        *   Request from translation team for a special monthly sync meeting:
+            *   Schedule a first meeting: 8am PDT / 11pm Beijing
+        *   How many times does it need to repeat?
+            *   Unknown; do one first, then figure it out.
+    *   Handling PRs with the “Needs Tech Review” label (Zach)
+        *   There’s a [list of tech reviewers](https://github.com/kubernetes/kubernetes.github.io/wiki/Tech-reviewers)
+            *   @mention reviewers as needed
+            *   Help keep the list fresh!
+            *   Zach will open an issue describing updates to contributor docs: if someone wants to submit a PR, that would be awesome.
+            *   Let’s single source this info!
+    *   From Jennifer: How much latitude do we have to say yes/no to PRs based on language quality?
+        *   We have a lot of latitude when it comes to quality of information
+        *   TLDR: use your best judgment
+        *   It’s OK to work on language in the PR
+        *   We can ask contributors to allow edits from maintainers and make language changes for them
+
+POSTPONED - Presentation: open source projects (Radhika)
+
+
+#### 9/5/2017
+
+
+
+*   New Attendees?
+    *   Jason Kennedy - Cloudy-things for IBM :)
+*   Agenda Items?
+    *   Kubernetes code contributor guide [#892](https://github.com/kubernetes/community/issues/892) (Andrew)
+        *   Suddenly got a lot of attention
+        *   Lots of folks want to help 
+        *   Paris - new community manager - helping lead this effort
+        *   Helping: Zach, Jennifer
+    *   [Updates](https://groups.google.com/d/msg/kubernetes-dev/IC-A0opoeno/Bmi4mOIGAwAJ) on 1.8
+        *   (from Zach) Write access to kubernetes/features--necessary to what degree?
+        *   [1.8 tracking board](https://docs.google.com/spreadsheets/d/1AFksRDgAt6BGA3OjRNIiO3IyKmA-GU7CXaxbihy48ns/edit#gid=0)
+    *   Zach’s back
+        *   Thanks, Radhika, for doing issue triage!- Woohoo!
+        *   Zach will resume running SIG-Docs meetings next week
+        *   Catching up: message Zach on Slack with things that need attention
+        *   Added back to OWNERS to be assigned PRs :)
+    *   Feature repo access
+        *   Is that what we want? Do we need it? 
+        *   We should have something like what we have for the docs repo.
+    *   Kubecon Docs Sprint (Jared)
+        *   Thanks Radhika for advice on running a sprint
+        *   Still waiting to hear back from event coordinators at Kubecon
+*   Talk about experience about open source projects (Radhika)
+    *   15-20 minutes. 
+*   Chinese Translation:
+    *   Organizing to bundle PRs into many PRs.  Trying to reduce the barrage of PRs.  Whoohoo :)
+    *   Any plans to do this for other languages?  Not at the moment, since other language efforts would have to bootstrap themselves.
+    *   We should consider putting together a landing page in the docs to discuss localization. Gauging interest in other languages. 
+*   Docs analytics:
+    *   Tracking updated date to content? Is it easy? 
+    *   “what are quality docs” — there’s a great blog post series here (starting with most recent): [http://docsbydesign.com/](http://docsbydesign.com/)
+    *   Google Analytics: 
+        *   Standard site analytics
+        *   Customer SAT surveys
+    *   Github Analytics:
+        *   # of issues against docs
+        *   Outstanding PRs to review
+    *   What metrics do we care about?
+        *   User satisfaction and happiness?
+    *   Timeline:
+        *   Q3: Strategize and research
+        *   Q4: Plan and implement
+
+
+#### 8/29/2017
+
+
+
+*   New Attendees
+    *   James Turnbull - Engineer for 25 years, docs for docker and puppet
+    *   Michael Hausenblas - Red Hat, OpenShift
+    *   Damian Igbe - Cloud Technology Experts (CTE)
+    *   Tim Pepper - Open Source Technology Center - VMware
+*   New SIG-Docs Maintainers
+    *   Vacation - please let Chenopis@ know 
+*   Agenda items
+    *   There should be a kubernetes contributor guide [#892](https://github.com/kubernetes/community/issues/892)
+        *   General framework for user journeys created by Chenopis and others.
+        *   Good material in the issue
+        *   Who owns “contributor materials”?  Unknown :)
+        *   Cuts across the following SIGs:
+            *   API machinery
+            *   Architecture
+            *   Contributor experience
+        *   Michael Hausenblas (compiling list of material), Andrew Chen (liaison with SIGs, scoping)
+*   Additional Agenda Items?
+    *   Style guidelines for release notes (issue [#5234](https://github.com/kubernetes/kubernetes.github.io/issues/5234), Radhika)
+        *   Radhika - you’re the first TW working on release notes.
+        *   We should tie release notes into the feature release process.
+        *   Create a suggested process for the 1.8 process.
+    *   Coordinating docs and release notes (Jennifer and Radhika)
+        *   Right now, no process :(
+        *   Meeting with Stevepe@google.com next week to discuss and create a process
+        *   Chat with [dawnchen@google.com](mailto:dawnchen@google.com) who ran release notes for 1.7
+        *   [Tracking board for 1.8](https://docs.google.com/spreadsheets/d/1AFksRDgAt6BGA3OjRNIiO3IyKmA-GU7CXaxbihy48ns/edit#gid=0) 
+    *   Docs Home vs. Setup? (Jared)
+        *   Will be replaced by user journey portals.
+    *   Kubecon docs sprint (Jared)
+        *   Radhika, Chenopis, Jennifer Rondeau, James Turnbull, Damian Igbe
+
+
+#### 8/22/2017
+
+
+
+*   New Attendees
+*   New SIG-Docs Maintainers
+    *   Cody Clark (Yay!!!)
+*   Agenda items
+    *   Luke: working on User Journey user/personas -- would like input in [doc](https://docs.google.com/document/d/1dYvSUeeThZIG4Nyf7M9PFuI2vsUnwANM0w5-CZD4CbE/edit?usp=sharing)
+    *   Luke: Kubernetes Iconography Standards [proposal](https://docs.google.com/document/d/1lmIYjRIJhIRBRdFqZ8WCf3j79Lr_kFhZ_CFjMRjEQro/edit#heading=h.b3nffphwka8z)
+    *   Jessica: Inconsistency between permissions of _sig-docs-maintainers_ and _kubernetes.github.io-maintainers_ on Github for force-merging PRs that are not up-to-date but don’t have merge conflicts (see [Slack](https://kubernetes.slack.com/archives/C1J0BPD2M/p1502995558000653)). [Note from Steve] [This page](https://help.github.com/articles/repository-permission-levels-for-an-organization/) shows the difference between Write permissions and Admin permissions.
+    *   Jennifer: quality of PRs
+        *   Andrew to reach out to CN translation group to see what's up
+        *   We should decide some guidelines for worthwhile PRs
+        *   From Jessica: “require branches to be up-to-date” (see [https://help.github.com/articles/types-of-required-status-checks/](https://help.github.com/articles/types-of-required-status-checks/))
+    *   Radhika: Release Notes - collaborator w/ write access -  you can merge :)
+    *   Steve: People who have been added to sig-docs-maintainers no longer need to be listed as outside collaborators. Is everybody OK with removing these people from the outside collaborators list?
+    *   Steve: Is it OK to add Zach to sig-docs-maintainers now. Currently his name isn't in the list.
+    *   Kubecon in December 7-8 - in Austin
+        *   Doc hack-a-thon?
+        *   Doc talk?  Site talk? 
+    *   Write the Docs - Melbourne Nov 24th
+
+
+#### 8/15/2017
+
+
+
+*   New Attendees
+    *   Stephen Augustus - Field Eng @ CoreOS
+*   New SIG-Docs Maintainers
+    *   Zach Corleissen
+    *   Jennifer Rondeau
+*   Agenda items
+    *   Steve: Giving people analytics access
+    *   Luke: Doc to review for common diagram assets? 
+        *   (<-- just reported that he’s at the doctor’s office, we should bump this to next time)
+    *   Zach: There are 144 labels (too many), but removals are permanent.  He will get consensus & identify contingencies before deleting unused labels. 
+    *   Zach: Will be on vacation from Friday of next week through Tuesday Sept 5.  
+        *   Radhika will be doing issue triage!  Hoorays!
+        *   Jennifer and Abigail are willing to do PR triage and merging.  Hoorays!
+        *   Andrew will hand off incoming issues to Jennifer & Abigail.
+*   Additional Agenda Items
+    *   Steve: Process for taking an issue. In the issue, create a comment that says, "@steveperry-53, @chenopis, I will work on this issue." Steve or Andrew will make you an outside collaborator with Read permissions. Steve or Andrew will assign the issue to you. In [Kubernetes Doc Projects](https://github.com/kubernetes/kubernetes.github.io/projects/3), Steve or Andrew will move the issue to the **In Progress** column.
+    *   We're considering adding additional reviewers to the OWNERs file to split the incoming pull requests among more than two reviewers.
+
+
+#### 8/8/2017
+
+
+
+*   New Attendees?
+    *   Radhika - Core OS - 4th OS project - Rel-notes coordinate for the 1.8 release
+*   Agenda Items to add?
+*   Luke: On-Premises! Whoo.  Andrew worked with Luke. Doc to review for common diagram assets.
+*   Steve: If you would like to be a user of the Kubernetes Google Analytics account, either let me know on the [sig-docs slack channel](https://kubernetes.slack.com/messages/C1J0BPD2M/team/), or send me an email ([stevepe@google.com](mailto:stevepe@google.com)). I need to know the username of the account you will use to sign in to a browser. I will submit a batch of names to Nate Kartchner later today. Going forward, people who would like to become users of the Kubernetes Google Analytics account can contact Nate Kartchner directly ([nkartchner@linuxfoundation.org](mailto:nkartchner@linuxfoundation.org))
+*   Steve: The GA account does not show search queries. But the [Google Search Console](https://www.google.com/webmasters/verification/verification?hl=en&authuser=0&theme=wmt&siteUrl=https://kubernetes.io/&continue=https://www.google.com/webmasters/tools/dashboard?hl%3Den%26authuser%3D0%26siteUrl%3Dhttps://kubernetes.io/%26sig%3DALjLGbOQbaiUBJVBO0pfU0sDlGqWTa_hSQ) does. This requires that you go through a short verification process.
+*   Andrew: User Journeys [[rough mock](https://deploy-preview-4630--kubernetes-io-master-staging.netlify.com/docs/home/)] [WIP [project plan](https://docs.google.com/a/google.com/document/d/1EdQ8acmuKGlzZy1agejLqmB7cLpTRBJKC0JYptJ-ylg/edit?usp=sharing)]
+    *   Looks good - let’s test this with a few users after we flesh it out further
+*   Andrew: Version drop down UI [[preview](https://deploy-preview-4386--kubernetes-io-master-staging.netlify.com/docs/home/)] [[Versioned Docs Issue](https://github.com/kubernetes/kubernetes.github.io/issues/3992)]
+    *   Make a larger announcement to the community about versioning
+    *   SEO - already de-listed - but does it work for site-search? 
+    *   Good time to do another SEO audit. 
+*   Zach: Labels
+    *   [https://github.com/kubernetes/kubernetes.github.io/labels](https://github.com/kubernetes/kubernetes.github.io/labels)
+        *   Fewer labels! 
+        *   Safe to delete!
+    *   [https://docs.google.com/document/d/1BiJ-r64RqaiEVh17o5MjzRiCURqPeIcPM0q9QFRvkKQ/edit#heading=h.li68i6k30j4b](https://docs.google.com/document/d/1BiJ-r64RqaiEVh17o5MjzRiCURqPeIcPM0q9QFRvkKQ/edit#heading=h.li68i6k30j4b)
+        *   Adding links to slack channel for kubernetes in the footer.
+*   Zack: Vacation 
+    *   Triage needed for 8/21-9/5.  Any volunteers?
+    *   Radhika will give it a try!  Whooo. 
+
+
+#### 8/1/2017
+
+New Attendees?
+
+
+
+*   Luke Heidecke - WELCOME
+
+Additional Agenda items?
+
+
+
+*   Formatting Callouts in our Docs - Cody
+*   Steve: Playground links in prerequisites, [PR 4550](https://github.com/kubernetes/kubernetes.github.io/pull/4550)
+*   Steve: [Kubernetes Doc Projects](https://github.com/kubernetes/kubernetes.github.io/projects/3)
+    *   References issues in the repo
+    *   One of the docs maintainers would have to do it
+    *   Currently a feasibility study - how useful are “Projects” for tracking our issues?
+    *   AI: Steve will report back next week on the usefulness of Projects. 
+*   Luke: On-premise, On-premises or on-prem? Dictionary? Common diagram resource library?
+*   Ahmet: About importing tutorials from kubernetes/examples repository.
+*   Zach: Automation in the repo? What’s happening? Webhooks for labels?
+    *   AI: Jared will take offline with Zach
+*   Andrew: Moving the Heptio folks along in the maintainers onboarding process 
+*   Diagrams: 
+
+Agenda:  
+
+
+
+*   Google Analytics for docs site -- export reports? What do we want to see?
+    *   Most visited pages | time on page ?
+    *   What else?
+
+
+#### 7/25/2017
+
+Additional Agenda items?
+
+
+
+*   Zach: issue triage
+*   Jaice: 1.8 release
+    *   need release notes coordinator (different from docs lead)
+        *   Jennifer (jrondeau) interested
+        *   [proposal](https://docs.google.com/presentation/d/1f-Td0Fs1kR3rSWlYzR0EJ2PFgd8_R2srlE_O_vxwdlk/edit#slide=id.p) (Dawn Chen) re: changing release notes process
+        *   SIG Docs should set standard for engineers to write to
+            *   what is going to look different in your cluster?
+    *   Steve will be Docs Lead
+        *   Link to playbook: [https://docs.google.com/a/google.com/document/d/1PCkAwPWadlu7beprhtQLtZzgsbO8CD7SvMVzta3fhcw/edit?usp=sharing](https://docs.google.com/a/google.com/document/d/1PCkAwPWadlu7beprhtQLtZzgsbO8CD7SvMVzta3fhcw/edit?usp=sharing)
+
+New Attendees?
+
+
+
+*   Jaice Singer DuMars (Microsoft, 1.8 Release Lead)
+*   
+
+Agenda:
+
+
+
+*   Steve: Added work items to [kubernetes-documentation-projects](https://docs.google.com/a/google.com/document/d/1IuzRGsznx9RcLWsvLjXmTHrGGDYxKqbMgfkYmJzYg3w/edit?usp=sharing). I propose we delete this doc, and instead track these work items in GitHub issues. The editing work items could all go in one umbrella issue. Each of the larger projects and smaller projects could have its own issue. And we could create a GitHub project for this effort.
+    *   will combine w/ GitHub Projects
+    *   example GH Project board for sig-release: [https://github.com/kubernetes/sig-release/projects/2](https://github.com/kubernetes/sig-release/projects/2)
+*   Steve: What do people think of this idea? In the Tasks TOC, have two big buckets:
+    *   Tasks for Application Developers
+    *   Tasks for Cluster Administrators
+    *   Have further discussions -- revisit at subsequent sig docs meetings
+    *   Andrew: how about refactoring the /docs/home landing page into user journey portal? -- i.e. thread users through docs
+
+Project Updates:
+
+
+
+*   Andrew: move to Netlify update
+    *   moving to production today or tomorrow
+    *   v1-6.docs.kubernetes.io (example of versioned docs subdomains)
+        *   nav dropdown for version will be added after everything is live
+
+
+#### 7/18/2017
+
+Welcome to the first weekly meeting.  Wooo
+
+Additional Agenda items? 
+
+Project Updates: 
+
+
+
+*   Steve is working on a document that describes writing projects: [kubernetes-documentation-projects](https://docs.google.com/a/google.com/document/d/1IuzRGsznx9RcLWsvLjXmTHrGGDYxKqbMgfkYmJzYg3w/edit?usp=sharing). This is where contributors can go to pick and choose a project. This document is a work in progress, and is currently in rough format. Steve will add detail this week.
+    *   Great work.  How do we include this in the existing issue list?  What’s the difference between a “Project” and an “issue”?
+    *   Github projects?
+*   Zach is triaging all issues that are outstanding in our issues queue and reviewing outstanding PRs
+    *   Some statistics (so far) about open issues
+    *   Interactive tutorial is consistently biggest issue-opener
+*   Andrew
+    *   v1.7
+    *   Moving to Netlify
+
+
+#### 7/11/2017
+
+
+
+*   Agenda items to add?
+    *   What is the process to add jrondeau and jessicayao from Heptio as sig-docs-maintainers?
+        *   Attend SIG docs
+        *   Submit PRs
+        *   Add you to the group!
+    *   Working on updating community contribution guidelines, will give more information at next week’s meeting.  PR in progress: [https://github.com/kubernetes/kubernetes.github.io/pull/4324](https://github.com/kubernetes/kubernetes.github.io/pull/4324)
+*   New Attendees? (no)
+*   K8s 1.7 Release Update and Post-mortem
+    *   The Kubernetes v1.7 release went out EOD 6/29. The corresponding docs were deployed to [kubernetes.io](http://kubernetes.io/) shortly afterwards. There were no significant docs issues during the release cycle. Hooray!
+    *   Special shout out to Jessica Yao from Heptio and Cody Clark for helping w/ doc reviews. Thank you!!!
+    *   Andrew Chen ([@chenopis](https://github.com/chenopis)) created a [playbook](https://docs.google.com/a/google.com/document/d/1PCkAwPWadlu7beprhtQLtZzgsbO8CD7SvMVzta3fhcw/edit?usp=sharing) for whoever wants to be the next docs release meister (aka Docs Lead for the Kubernetes release).
+*   Netlify
+    *   Planning has begun for the move of the [kubernetes.io](http://kubernetes.io/) production site to Netlify. Changes will be made in the netlify-move branch and staged and tested here at: [https://netlify-move.kubernetes.io/](https://netlify-move.kubernetes.io/). 
+    *   In parallel, we are testing having different versions of the docs on separate subdomains. The first one can be found at: [https://v1-6.docs.kubernetes.io/](https://v1-6.docs.kubernetes.io/).
+    *   Previous versions are snapshots. 
+*   K8s has a new SIG.  SIG-Architecture
+    *   Break us out of having sig-silos.  Get a big-picture view. 
+    *   Big ideas
+    *   Bi-weekly, monday @ 10am, jrondeau, zach, jaredb, jyao will attend
+*   Meeting update:
+    *   Moving to weekly meetings @ 10:30
+    *   AI: Add SIG-Docs to the community calendar. 
+*   Site revamp: 
+    *   Working through content, some of them are going to be done by 8/15
+    *   Taking a family of topics and editing them.
+    *   Zombie project :)  Just won’t die.
+    *   jrondeau and jessicayao 
+
+Followups:
+
+
+
+*   Versioning discussion - should set up a separate discussion to discuss how we handle release branches. Refdocs issues should be considered.
+*   SEO - Should present on this in the future.
+*   Site revamp: [Stevepe@google.com](mailto:Steveperry@google.com), jrondeau@heptio.com and [jessica@heptio.com](mailto:jessica@heptio.com), [zoidbergwill@gmail.com](mailto:zoidbergwill@gmail.com) - Steve will set up a meeting with folks. 
+
+
+#### 6/27/2017
+
+
+
+*   Agenda items to add?
+    *   Ahmet – tutorials moved from kubernetes/examples, where the content should live, where the manifests should live.
+        *   [k8s.io/docs/samples](http://k8s.io/docs/samples) is now removed and merged into /tutorials
+        *   I moved tutorials [[1](https://kubernetes.io/docs/tutorials/stateless-application/guestbook/)][[2](https://kubernetes.io/docs/tutorials/stateful-application/mysql-wordpress-persistent-volume/)][[3](https://kubernetes.io/docs/tutorials/stateful-application/cassandra/)] to the docs site. But the manifests, source code for apps and Dockerfiles remain at kubernetes/examples repo. Should it stay that way? Discussion: [kubernetes/examples/pull/16](https://github.com/kubernetes/examples/pull/16#issuecomment-311349828)
+            *   Check with Jeff Mendoza about dockerfile. 
+            *   Local yaml files
+        *   Setting up redirects from old tutorials at kubernetes/examples repo.
+*   New attendees?
+    *   Zach Corleissen - CNCF editor.  Hoorays!
+    *   Bob Reselman - Developer, journalist, researching OS, devops.com :)
+    *   Cody Clark - Google 
+    *   Dan Kohn - CNCF
+*   1.7 Update
+    *   Original release date, 6/28
+    *   Release delayed to possibly Fri 6/30
+    *   Waiting on tech approvals ([tracking spreadsheet](https://docs.google.com/spreadsheets/d/1IJSTd3MHorwUt8i492GQaKKuAFsZppauT4v1LJ91WHY/edit#gid=0))
+    *   Big launches / important items:
+        *   Security for multi-tenant clusters
+        *   Stateful set support
+        *   Api aggregation
+        *   Network policy
+        *   Encrypted secrets (Alpha)
+*   SIG-Docs Strategy Shift Proposal (Devin) 
+    *   Sarah Novotny requested a presentation at the k8s community meeting
+    *   Proposal for working with docs, out of the k8s leadership summit
+    *   Other SIGs are dependent on us.
+    *   In the past:  worked on meta documentation tasks:  Templates, launch processes, SEO improvements, information architecture
+    *   Moving forward:  How do we increase our contributions? 
+        *   Current interface: PRs which we respond to.  
+        *   Get in front of the PRs, either thought having liaisons to other SIG meetings, or by inviting SIG-Leads to the meeting.
+    *   Dan:
+        *   CNCF governing board, aware that docs are under-resourced
+        *   Can we reach consensus on a request for headcount in the next month?
+    *   SIG-docs maintainers have to have some level of expertise in what the other SIGs are doing.
+    *   Goal: Get better communication between other SIGs and us. Move it up a level from PRs. 
+    *   Next Steps:
+        *   Write up the needs and goals for improving sig-docs communication
+        *   Present at the upcoming k8s community meeting
+    *   Feedback:
+        *   Embedding folks in SIG groups is a large burden.  Perhaps pick a few large, important groups to integrate with.  Smaller groups will need to bring their story/documentation request to us. 
+        *   Provide use-case personas
+*   Moving to a once a week meeting
+    *   Next week, no meeting.  Week after, moving to weekly meetings
+*   Moving k8s.io prod to Netlify in Q3
+    *   Real server-side redirects
+    *   Potential to do versioned docs (which we’ll have to figure out how to do/support)
+    *   
+
+
+#### 6/13/2017
+
+
+
+*   Agenda items to add?
+    *   Sahdev - “told to be here to chat about docs” - moving docs generation [https://github.com/kubernetes/kubernetes/issues/47361#issuecomment-307923794](https://github.com/kubernetes/kubernetes/issues/47361#issuecomment-307923794)
+*   New attendees?
+    *   Sahdev @ IBM
+    *   Jessica @ Heptio
+*   New starts:
+    *   Zack Corleissen - Editor CNCF
+    *   Cody Clark
+*   Netlify
+    *   Evaluating when to roll this out, looking at ~2 weeks after 1.7 launch
+*   Generating docs: 
+    *   [https://github.com/kubernetes/kubernetes/issues/47361#issuecomment-307923794](https://github.com/kubernetes/kubernetes/issues/47361#issuecomment-307923794)
+    *   Provided that Phillip and Andrew are ok with it, then that sounds good to me. 
+*   How do we share work that needs to be done better with the community, and get feedback from the community
+    *   Solicit help and content from Write the Docs
+    *   Help identify work items from people in the community
+    *   Share a doc of work-items for Heptio 
+    *   Q: How are developers working with the docs? 
+        *   Friction logs from new developers
+        *   Jorge has some info to share with the group
+    *   Q: Maintenance - Sig-docs-maintainers - How do you join the group?
+        *    
+
+
+#### 5/30/2017
+
+
+
+*   Agenda Items to add?
+*   New attendees? 
+    *   New Starts:
+        *   Cody Clark - Google Intern on K8s 
+        *   Charles Butler - Canonical (lead on canonical distro of kubernetes)
+    *   Potential Hires
+        *   [Zack Corleissen](https://github.com/zacharysarah) - CNCF Editor
+*   Write the Docs - [Kubernetes Docs Sprint Writeup](https://docs.google.com/document/d/13jBBINd0XaSXrt3ihJdYdXLMb1hmzmEI0VztVm0XJGw/edit#) (Jared / Andrew) 
+*   API Server Tasks and Tutorials?
+    *   Got a request for documentation on how to use watch on the api server from Joe Beda.  I noticed that there isn’t must documentation on the API server in general. 
+*   Netlify Approved! (Andrew) [[proposal](https://goto.google.com/k8sio-netlify-move-proposal)]
+    *   Reasons we’re using:
+        *   Addressing upstream breakages - github updates won’t break us.
+        *   Uptime SLA provided.  SIG-Docs is for content, not front end development :)
+        *   Host multiple branches - useful for versioning and testing UX
+        *   HTTPS support natively
+        *   Server-Side redirects for moar better SEO
+        *   400/month - enterprise tier - figuring out the contract now. 
+    *   Any questions?
+        *   Does Netlify support i18n standards? 
+            *   Don’t know, but would be useful to merge in the chinese language docs. 
+        *   When are we going to migrate? 
+            *   Post 1.7, beginning Q3.  
+    *   Does this/how does this change the contribution workflow for contributors?
+        *   No, it shouldn’t affect the contributor workflow.
+        *   PR > Site gets rebuilt > Goes live
+*   Is there a local developer experience where they can view the content using the same stylesheets/etc? 
+    *   We actually want to give alternatives to the local workflow.
+    *   There’s a difference between staging locally vs. staging using your own fork.  Staging your own fork leads your topic to be indexed :(  
+*   Don’t know about local staging with Netlify, we’ll ask.
+*   SEO (Steve) 
+    *   [SEO for K8s Docs](https://docs.google.com/document/d/1VG5JMpA_uyLn-zrBi32z4OYKzuEyLAxD4e5yA0jNRCc/edit#heading=h.w9xlvj486o54)
+        *   We got internal site search turned on for the kubernetes.io Google Analytics account.
+
+            [http://k8sdocs.github.io/docs/tasks/run-application/run-java-app/](http://k8sdocs.github.io/docs/tasks/run-application/run-java-app/)
+
+        *   [http://kubernetes-io-vnext-staging.netlify.com/docs/admin/master-node-communication/](http://kubernetes-io-vnext-staging.netlify.com/docs/admin/master-node-communication/)
+        *   [https://steveperry-53.github.io/docs/home/](https://steveperry-53.github.io/docs/home/)
+    *   Fixed netlify staging, removed instructions for local staging on github.io forks. 
+    *   Follow up with Charles on redirects and META descriptions using Jekyll templates
+        *   jekyll front matter for meta tags: http://vrepin.org/vr/JekyllMeta/
+    *   Webmaster URL removal: [https://support.google.com/webmasters/answer/1663419?hl=en](https://support.google.com/webmasters/answer/1663419?hl=en)
+*   Upcoming dates for 1.7 
+    *   PRs - please open PRs by June 14th
+    *   Release slated for th 28th
+    *   Engineering feature repo - code freeze is this week, reviewing at end of this week
+*   Sig-on-prem:
+    *   Needs some guidance on documentation
+    *   Looking to add examples for on-prem implementations
+    *   This should be done in combination with the docs effort on revamping Setup Guides
+
+
+#### 5/16/2017
+
+
+
+*   Agenda items to add
+*   New Attendees?
+*   Write the Docs - Kubernetes Docs Sprint
+    *   Doc sprint process: [www.tinyurl.com/k8s-doc-sprint](http://www.tinyurl.com/k8s-doc-sprint)
+    *   ~22 docs [PRs filed](https://docs.google.com/spreadsheets/d/1L6f8sU6SM6rdwbzvL8oc8FGWgHIqHZykcbxWhuVbNh0/edit#gid=0) (more PRs listed) 
+    *   Lesson’s learned? 
+        *   CLA process is terrible :(
+        *   Use the github login on the CLA page. 
+        *   People were confused by how to use the template tags. Improve the process for using templates. {% include templates/concept.md %} should be called out. 
+        *   Call out how to view the netlify preview. Perhaps break this out into a sep
+    *   AI: jrondeau will tweet about our awesomeness. 
+
+
+
+<p id="gdcalert1" ><span style="color: red; font-weight: bold">>>>>>  gd2md-html alert: inline image link here (to images/Copy-of0.jpg). Store image on your image server and adjust path/filename if necessary. </span><br>(<a href="#">Back to top</a>)(<a href="#gdcalert2">Next alert</a>)<br><span style="color: red; font-weight: bold">>>>>> </span></p>
+
+
+![alt_text](images/Copy-of0.jpg "image_tooltip")
+
+
+
+
+*   Site migration:
+    *   Still “shuffling” table of contents
+    *   Still thinking about pages that need to be split / combined. 
+    *   Shuffling should stop by end of may. 
+    *   June will be focused on editing and getting content into templates. 
+    *   Sitemap.xml - still listing all of our old files :(  Trying to fix. 
+*   New Starts / Positions: 
+    *   Cody Clark - Intern - Starts May 30th
+    *   Editor - Part time - Vetting candidates and helping CNCF to come up with the process. [Position Posting](https://docs.google.com/document/d/1LFTOMV9R4KnGWQk4vhsVZl9k8mSbj9mr3KqOYz9X74g/edit)
+*   1.7 tracking sheet: [https://docs.google.com/spreadsheets/d/1IJSTd3MHorwUt8i492GQaKKuAFsZppauT4v1LJ91WHY/edit?usp=sharing](https://docs.google.com/spreadsheets/d/1IJSTd3MHorwUt8i492GQaKKuAFsZppauT4v1LJ91WHY/edit?usp=sharing)
+
+**Tools I’d like to explore:**
+
+
+
+*   Write Good: [https://github.com/btford/write-good](https://github.com/btford/write-good)
+    *   Doc linter
+*   Netlify: [https://www.netlify.com/](https://www.netlify.com/)
+    *   Site versioning, redirects
+
+
+#### 5/2/2017
+
+
+
+*   Agenda items to add
+    *   New Attendees? 
+        *   Vanessa Wilburn - IBM
+    *   Content migration done. Hoorays!
+        *   User guides removed from top level nav
+        *   Migration is not complete in that topics are not edited, and not in the new templates, and some of them might need to be moved from where they landed.  Shuffling will continue.
+*   Issue triaging (ahmetb) need to create a gh team, work with wg-contribex to enable this
+    *   [Current issues - 347](https://github.com/kubernetes/kubernetes.github.io/issues)
+    *   Bankruptcy for some issues
+    *   Don’t really have enough people :(
+    *   Upsides:
+        *   Improves responsiveness to users
+        *   Prevents buildup of issues. 
+    *   Downsides:
+        *   Major refactors will accumulate open issues 
+        *   Random assignments make it difficult to track duplicates
+*   Discuss proposal: [Moving examples/ out of main kubernetes repo](http://drive.google.com/a/google.com/open?id=15eRNrOtofhl1tFyXgZYw3pV4Z9S4PF1TU1iejGnv1f4) (ahmetb) These are listed on [k8s.io/docs/samples](https://kubernetes.io/docs/samples). Currently there are divided opinions. My proposal is that maintain only the maintained 4 samples to the [new repo](http://github.com/kubernetes/examples). Please weigh in with your opinions. There’ll be a followup meeting in SIG-Apps.
+    *   The samples directory as it exists was a bit of a “stop-gap”.  In practice, it’s a crap shoot. 
+    *   Duplicate use case to tutorials?  
+    *   Remove samples from top-nav?
+*   Process for adding suggestions for Tasks, Tutorials, and volunteers to write them? (chenopis)
+    *   Some of it is handled by the issue queue, but it gets lost.
+    *   Make a comment in the table of contents planning doc?
+    *   Spreadsheet for new content? 
+    *   Issue queue - improve tagging (Andrew Chen)
+    *   [https://github.com/jasonbellamy/git-label](https://github.com/jasonbellamy/git-label)
+*   UX Updates to the site? 
+    *   If you see issues, please tag them. 
+*   Job Opening: [Seeking a part-time editor for the site. ](https://docs.google.com/document/d/1LFTOMV9R4KnGWQk4vhsVZl9k8mSbj9mr3KqOYz9X74g/edit)
+*   Netlify migration? 
+    *   An informal “one major project per quarter” 
+    *   Need to understand potential issues.
+    *   Why we want this:  
+        *   Have to serve out to two named branches
+        *   Makes it easier to do versioned branches
+        *   Https support
+        *   Easier redirects (with support for 301 redirects)
+        *   Possibly has less outages than github pages.  Better visibility into builds and logs :)
+*   Locking down contributions
+*   Write the docs:
+    *   Setting aside a set of content on the site that can be edited. 
+    *   AI: Jaredb - Send a blurb with the content [jrondeau@heptio.com](mailto:jrondeau@heptio.com)
+
+
+#### 4/18/2017
+
+
+
+*   New attendees
+    *   Jennifer Rondeau - from Heptio
+    *   Marco Ceppi - from Canonical
+    *   Joe Beda (late) - Heptio 
+*   Items to add
+    *   Maybe for next meeting: Netlify migration plan?
+    *   Knowing more about netlify would be useful :)
+    *   How much retooling (redirects, https forwarding) would need to be rebuilt? 
+    *   Other sites on CNCF want to use netlify for staging. 
+*   Status of current projects
+    *   Docs migration (stevepe)
+        *   Finished in one sense.  Everything is moved to its new home. 
+        *   Not finished, in that content needs to be edited and refactored.
+        *   Some of the topics still show up in the old TOC
+        *   Next Steps:
+            *   Use the tracking sheet to continue to track the editing. 
+            *   Provide a link to the style guides and make a group-editing effort
+            *   Docs fixit-week?
+                *   Potentially work on this during the “docs hack day” at Write the Docs?
+            *   Integrate engineering feedback on docs structure
+    *   Reference refactor ([go/k8sio-ref-refactor](https://docs.google.com/document/d/1sVkp1OplIPANoAqC_LHbw76DnwVUcqdT5vvCXCr0C4k/edit))
+        *   Solid restructuring!
+        *   “API Overview’ under “using the API” needs a rewrite. 
+        *   Jennifer is willing to help out. 
+    *   1.7 (ddonnelly)
+        *   Release Tzars: Dawn, Maru
+        *   Docs: Andrew
+        *   1.7 branch is open
+
+
+#### 4/4/2017
+
+
+
+*   New Attendees?
+    *   Luke from Weaveworks
+    *   Antonio Rosales from Canonical
+    *   Ilya from Weaveworks
+*   Agenda items to add
+    *   Discuss adding dropdown menu in k8s.io (re: [PR #2389](https://github.com/kubernetes/kubernetes.github.io/pull/2389)) w/ Luke and Ilya
+        *   Context: KubeAdm Installation Guide
+        *   One of the choices that users make -> Which Network they’re going to use (Weave, Calico, etc)
+        *   Getting sent off to another page is a bad user experience.
+        *   No default is selected
+        *   Discussion:
+            *   Structure the documentation to improve the workflow? 
+            *   Worries about maintenance burden
+            *   List the options?  Can we do this by rewriting content? 
+            *   Ilya described the issues that made tabs not appropriate as they’re currently implemented :(
+            *   Luke is willing to work with a writer on SIG-Docs for a rewrite, and look into a way to do toggled content via tabs or drop-downs on the site that is reusable. 
+            *   Can we use Jekyll plug-ins? No, we can’t without moving off github pages :(
+            *   Andrew, Ilya, and Luke will work together and try to come up with something. 
+    *   URL Structure of the site - post-Migration
+        *   Migration Status
+        *   Rearranging site structure significantly. 
+        *   Migrating content from “guides” to “setup” “tasks” “concepts” and “tutorials”
+        *   We also want to change the URL structure of the site. 
+            *   /tasks
+            *   /concepts
+            *   /tutorials
+        *   “Getting-started-guides” gets thorny :(
+            *   Current plan is to leave /getting-started-guides where it’s at.
+            *   Will be called “setup” guides on the page. 
+            *   Kubeadm falls under this section. 
+        *   Suggestion: Create a README with where pages moved to.   
+        *   Andrew will own the redirects
+    *   Kubernetes Reference docs refactoring plan w/ Ahmet and Andrew
+        *   Plan of action: https://docs.google.com/document/d/1sVkp1OplIPANoAqC_LHbw76DnwVUcqdT5vvCXCr0C4k/edit#
+*   1.6 Launch Review, 1.7 Prep
+    *   We will likely get a lot of questions about the new directory structure.  
+    *   “Interesting release” process.  Highest percentage of untracked pull requests. 
+    *   Supposed to be a stabilization release. 
+    *   Lessons learned:
+        *   We need to get involved earlier. 
+        *   Andrew Chen will be taking the duty for the 1.7 release. 
+        *   Release Czar should be determined tomorrow. 
+        *   We could keep the deprecation notices around?  Stevepe: No, we should remove those sooner rather than later. 
+*   Setup/Onprem Document Fixup (Jorge Castro)
+    *   At Kubecon we discussed with some of the people who care about onprem documentation if they would be interested in helping flesh out the “Setup” section of the proposed doc to match the depth and quality of the rest of the proposed doc structures.
+    *   We figure this would be a great place for sig-onprem to contribute to the docs. ([Proposal](https://groups.google.com/forum/#!topic/kubernetes-sig-on-prem/yfimLUpdIw8))
+    *   We got some verbal nodding from those in attendance and would like to help out with this. 
+    *   Discussion:
+        *   Once we break out “Setup” guides, create subsections with cloud and on-prem - use this proposal for on-prem
+        *   One concern: “I feel like I can be busting out a whole bunch of things to make this page better, but I don’t want to get in the way of the migration” 
+        *   Stevepe:  I can make a directory where the on-prem content can land.  
+
+
+#### 3/21/2017
+
+
+
+*   Agenda items to add
+    *   New folks - Ryan McGinnis,ryanmcginnis - GH 
+*   1.6 Launch
+    *   All launches are posted on the tracking board
+    *   Launches should be based against the launch branch (in this case 1.6)
+    *   Reviewed by someone on Sig-Docs before accepting
+    *   Launch happens tomorrow.  Hoorays!
+    *   Some issues:
+        *   Launch is managed by a new person every time :(
+        *   Lots of new people that need to be trained
+        *   Will need to train a new person every time
+    *   1.7:  Andrew Chen volunteers as tribute!  Docs launchmeister for 1.7. 
+*   Share TOC plan with SIG-docs
+    *   https://docs.google.com/document/d/18hRCIorVarExB2eBVHTUR6eEJ2VVk5xq1iBmkQv8O6I/edit#
+*   Migration Status 	
+    *   https://docs.google.com/spreadsheets/d/1DGnDEUo2Y9lxJkKmQmGfno-4qpTE8WIDgOi3QDI-MJM/edit#gid=0
+*   Reducing access to who can publish
+    *   Protected branches
+
+
+#### 3/7/2017
+
+
+
+1. Any agenda items to add?
+    1. Migration Status (Steve)
+        1. Migrating Guides to Tasks - Tutorials - Concepts
+        2. Reviewing new TOC today.  
+        3. AI:  Will present at next meeting.
+        4. Should be able to move quickly - Once we get the TOC, we’ll move first and edit later.
+        5. Rough Timeline:
+            1. EOM: Have TOC migrated.
+            2. EO June: Clean up Content
+    2. Questions:
+        6. What will the new migration look like?  Is there a demo? 
+2. New People
+    3. Shar: Works at Heptio (https://www.heptio.com/)
+3. 1.6 Update/Launch (Devin)
+    4. Following the release tracking board for 1.6: [https://docs.google.com/spreadsheets/d/1nspIeRVNjAQHRslHQD1-6gPv99OcYZLMezrBe3Pfhhg/edit#gid=0](https://docs.google.com/spreadsheets/d/1nspIeRVNjAQHRslHQD1-6gPv99OcYZLMezrBe3Pfhhg/edit#gid=0)
+    5. 1.6 docs PR should be targeted at the 1.6 release branch (not master)
+4. Giving members of the community access to the docs:
+    6. **Step 1: Become a member of the Kubernetes organization. From the [draft governance documentation](https://github.com/kubernetes/community/blob/master/governance.md), a kubernetes organization member should be:**
+        7. An active contributor for at least 3 months; 
+        8. A member of the relevant SIG-groups (Sig-Docs in this case) 
+        9. Trusted enough to run tests on their own PRs automatically (or for docs purposes, understand our templates, style guides, and processes)
+        10. Follow the code of conduct
+        11. Have two-factor authentication enabled
+
+        Once you have accomplished these tasks, ask the Sig-Docs leads (Jared, Devin, or Steve) and cc Sarah Novotny to add you to the kubernetes organization.
+
+    7. **Step 2: Apply to become a SIG-Docs maintainer**
+        12. Ask the maintainersSig-Docs leads to add you to the newly-minted "[sig-docs-maintainers](https://github.com/orgs/kubernetes/teams/sig-docs-maintainers)" group. 
+        13. The Sig-Docs leads will review previous PRs of yours and verify you as a member of the group.
+        14. Your name will be announced at the following SIG-Docs group as a group maintainer.  Hoorays!
+    8. Abigail McCarthy is our first new SIG-Docs Maintainer.  Hoorays!
+5. Good info for Kubernetes:
+    9. Youtube Channel: https://www.youtube.com/c/KubernetesCommunity 
+    10. Livestreams for GCP NEXT: https://cloudnext.withgoogle.com/schedule
+
+
+#### 2/21/2017
+
+
+
+1. Any agenda items to add?
+2. New People!
+    1. Ianeta: works at Intel - Welcome!
+    2. Abraham - Welcome!
+3. 1.6 is coming up quick - Release Branch Created (Devin Donnelly) 
+    3. Devin Donnelly is managing 1.6 release.
+    4. Master branch is always live.
+    5. Devin will keep master in sync with the 1.6 branch.
+    6. Issues fixes should be pushed to master, 1.6 release feature docs should be pushed to 1.6 branch.
+    7. Netlify staging works for master.  Devin will be set up for 1.6 after this meeting :)
+4. Have some notes on the getting started guides (Chris Hoge)
+    8. Just looking for a place to start filing issues and sending patches.
+    9. [https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md](https://github.com/kubernetes/kubernetes/blob/master/CONTRIBUTING.md)
+    10. [https://github.com/kubernetes/community/blob/master/contributors/devel/README.md](https://github.com/kubernetes/community/blob/master/contributors/devel/README.md)
+    11. [https://groups.google.com/forum/#!topic/kubernetes-dev/XcYA6gLXYYE](https://groups.google.com/forum/#!topic/kubernetes-dev/XcYA6gLXYYE)
+5. Update on content migration from guides
+    12. Pods -> Moving to tasks, tutorials, and concepts
+    13. Tracking spreadsheet: [https://docs.google.com/spreadsheets/d/1DGnDEUo2Y9lxJkKmQmGfno-4qpTE8WIDgOi3QDI-MJM/edit#gid=0](https://docs.google.com/spreadsheets/d/1DGnDEUo2Y9lxJkKmQmGfno-4qpTE8WIDgOi3QDI-MJM/edit#gid=0)
+    14. If it says “Need owner” feel free to claim it.  If it’s blank, ask first :)
+6. Issues are stacking up:
+    15. [https://github.com/kubernetes/kubernetes.github.io/issues](https://github.com/kubernetes/kubernetes.github.io/issues)
+    16. Getting tech review
+        1. Code Sample Review
+        2. Engineering Review
+7. Audiences for our content?
+    17. Audience assessment? 
+    18. People who are going to build a Kubernetes Cluster (Cluster Setup and Admin)
+    19. People who already have a kubernetes cluster setup and want to do something with it 
+    20. AI: Share audience assessment with Sig-Docs
+8. Onboarding new contributors:
+    21. Slack Channel
+    22. Editing docs: https://kubernetes.io/editdocs/
+
+ 
+
+
+#### 2/7/2017
+
+
+
+9. Sparse meeting today.  Summit happening.
+10. Any agenda items to add?
+    23. New folks at the meeting:
+        3. Ahmet Balkan: Googler working on k8s
+        4. Richard Edwards: Samsung CNCT in Seattle
+        5. Chris Hoge: OpenStack Foundation
+11. 1.6 is coming up quick 
+    24. We’ll be creating a release branch
+12. Site migration update - building out concepts and tasks. 
+    25. Some history:
+        6. Original site was organized around a large series of guides
+        7. Migrating the existing long-form guides into “tasks” “tutorials” and “concepts”
+        8. Created a tracking spreadsheet for content under guides, and migrating over to guides.  Steve Perry is migrating tasks and tutorials, Andrew Chen is working on concepts. 
+        9. Spreadsheet tracking effort: [https://docs.google.com/spreadsheets/d/1DGnDEUo2Y9lxJkKmQmGfno-4qpTE8WIDgOi3QDI-MJM/edit#gid=0](https://docs.google.com/spreadsheets/d/1DGnDEUo2Y9lxJkKmQmGfno-4qpTE8WIDgOi3QDI-MJM/edit#gid=0)
+        10. If you’d like to contribute to the effort:
+            1. AI: Steve will take on labeling “needs owner” in spreadsheet for ones that are up for grabs.
+            2. Folks on SIG-Docs can grab them and start working. Ping Sig-docs if you have questions. We’ll be around to help. 
+            3. We’ll check in at the next meeting. 
+    26. [Proposal for dealing with setup guides](https://docs.google.com/document/d/1iBUaDIP3eHvEc0A_Bm1Rn_zbKJdlzwEWrt53WQbc6Ns/edit#)
+        11. Everything under “[Creating a Cluster](https://kubernetes.io/docs/getting-started-guides/)” should be in its own section.: Partner docs, using turnkey solutions, setup guides for folks not contributing to core k8s code. 
+13. Helping us close issues
+
+
+#### 1/24/2017
+
+
+
+1. Any agenda items to add?
+    1. AI: Update topic in Slack Channel - Done.
+2. Fixit congrats! (Jared)
+    2. From our original 530 issues, [we're down to 202 open issues](https://github.com/kubernetes/kubernetes.github.io/issues). All remaining issues have been prioritized and tagged.
+    3. Special thanks to Abigail McCarthy for coming up with our [documentation prioritization process](https://kubernetes.io/docs/contribute/review-issues/).  
+    4. Thanks also to Andrew Chen, Devin Donnelly, Steve Perry, and Jeff Mendoza.
+3. Adrienne Schroeder - Docs Editor (Jared)
+4. Migration for guides to concepts, tasks, and tutorials. (Devin)
+    5. Guides is an all-inclusive TOC (junk drawer) of content 
+    6. Ground rules for migrating content:
+        1. “Guides” will eventually be deprecated. Content in guides will be moved to tasks, tutorials, and concepts
+        2. Deprecated pages will be taken out of TOC
+        3. Have a notice at the top with links to new content. 
+        4. Eventually, deprecate old content. 
+    7. Present at the next meeting.
+    8. Open questions:
+        5. “Setup Guides” location?
+        6. How do we handle redirects consistently? 
+        7. How big is this migration?  How many links are involved?
+5. Where can the community help?
+    9. Helping us sanity check the migration.
+    10. Testing our structure.
+
+
+#### 1/10/2017
+
+
+
+1. Happy New Year!
+2. Site Outages and Issues (Devin) 
+3. Jorge’s issues with netlify (Jorge)
+    1. Ubuntu Issues
+    2. PR: [https://github.com/kubernetes/kubernetes.github.io/pull/1932](https://github.com/kubernetes/kubernetes.github.io/pull/1932)
+    3. Travis: 4-5 issues identified when travis checks kicked on. 
+    4. AIs: Evangelize Docs processes and templates in other SIG meetings. 
+    5. Netlify: Jekyll issue.  Likely a template failure? 
+        1. Log access: Jessfraz, Jaredb, stevepe, ddonnelly, pwittrock
+        2. AI: Devin will take a look at the Netlify log. 
+4. Docs Issue Triaging
+    6. [New Process ](http://kubernetes.io/docs/contribute/review-issues/)
+    7. For existing issues:
+        3. [Pick an issue that hasn’t been labeled](https://github.com/kubernetes/kubernetes.github.io/issues?q=is%3Aopen+is%3Aissue+no%3Alabel).
+        4. Verify that the issue is still accurate and valid.
+        5. [Label appropriately](http://kubernetes.io/docs/contribute/review-issues/)
+        6. If it’s in the top 100 pages, look at the following spreadsheet: [https://docs.google.com/spreadsheets/d/1pXfrCs2YlYjoFK5Z0mUmgSx_stMryhI-OmtGU8GXGN4/edit#gid=2130667426&vpid=A1](https://docs.google.com/spreadsheets/d/1pXfrCs2YlYjoFK5Z0mUmgSx_stMryhI-OmtGU8GXGN4/edit#gid=2130667426&vpid=A1)	
+        7. If the issue was created before 10/1/2016, and it isn’t actionable, close it. Please be aggressive about this. 
+    8. If you’re going to be tagging issues, please let me (Jared) know so I can give you the proper level of access to do so. 
diff --git a/sig-docs/meeting-notes-archive/2018_Weekly_Meeting_Minutes.md b/sig-docs/meeting-notes-archive/2018_Weekly_Meeting_Minutes.md
new file mode 100644
index 00000000..2dc0b199
--- /dev/null
+++ b/sig-docs/meeting-notes-archive/2018_Weekly_Meeting_Minutes.md
@@ -0,0 +1,2443 @@
+**12/18/2018**
+
+**10:30am PST**
+
+New contributors
+
+*   Suresh Kumar Palemoni
+
+Updates and Reminders
+
+*   Kubecon last week!
+
+Agenda
+
+*   [Misty] PR Wrangling, Configure stale issues bot
+    *   Bot’s current configuration needs to be improved.
+    *   Why do we stale-out issues after 90 days? Organization’s defaults
+    *   In GH: A PR is a type of issue, stale-bot shouldn’t close these
+    *   AI: We should create a doc that guides issue triage, response time, priorities
+*   [Jim] 1.14 release meister / shadow
+    *   Steven Augustus sent out last call for shadows: Cody Clark, Jared Bhatti are current shadows
+    *   Shadows: Working to write up a guide for future release meisters
+*   [Jennifer] Covering for Zach during vacation
+    *   AI: Jennifer: Will cover (loosely) over vacation 
+*   [Jared] Holiday meetings?
+    *   Next two weeks meetings are cancelled. 
+    *   AI: Jared: Will announce on SIG-Docs and Slack
+*   [paris] kubernetes.io/community redesign 
+    *   [https://cjyabraham.gitlab.io/community](https://cjyabraham.gitlab.io/community)
+    *   Will circulate in the contribex meeting tomorrow, too. 
+    *   Final comments?
+        *   Goals of the site: surface our resources/communication channels and the why, modern design, mobile friendly, general community voice vs one/two personas. 
+    *   Need to clean up final copy, populate events, and we are ready to roll. Need to figure out a launch date that works. 
+*   [Andrew] Kubecon Planning and Feedback 
+    *   [Planning Document](https://docs.google.com/document/d/12lgT9usnk2vEKb9Fvnz2stXBZ35xvx8yEPTJDhwicic/edit#)
+        *   Q1 planning - let’s check in on these regularly during meetings starting next year - Steve volunteers to work on this.
+        *   AI: Jennifer will get an agenda up with the Q1 goals
+        *   Overall feedback: Felt more concrete, let’s do a short one again for Q2 and a longer one for Q3-4. 
+    *   Need to make a decision (in Jan) about pwittrock’s kubectl content. 
+        *   Make sure it aligns with our overall content strategy
+        *   It’s likely SIG-Docs will have some level of ownership in the future, let’s figure that out early. 
+    *   Paris/Misty: We welcome more help at the Diversity lunch next year
+        *   Jared: I’m interested in helping out at an upcoming conference
+*   AIs:
+    *   AI: We should create a doc that guides issue triage, response time, priorities
+    *   AI: Jared: Will announce on SIG-Docs and Slack that the next two meetings are cancelled
+    *   AI: Jennifer: Will cover PR Wrangling (loosely) over vacation 
+    *   AI: Jennifer will get an agenda up with the Q1 goals for our first meeting of the year. 
+
+**12/04/2018**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   None today
+
+Updates and Reminders
+
+
+
+*   PR wrangler this week: @bradtopol
+*   KubeCon Seattle: SIG Docs meeting is part of contributor day on Monday, 10 December.
+
+Agenda
+
+
+
+*   Congratulations to @tfogo and @jimangel on the 1.13 release! 
+    *   Big thank you to @jrondeau for helping thoroughly and often, especially during crunch time
+    *   [Zach] Need to add netlify site for 1.13, clean up old sites (1.8, 1.7)
+*   [Zach] For the good of the order
+    *   PR wranglers: 
+        *   For week of 12/10, @mistyhacks is listed. Is she still available?
+        *   Expectations for approvers to keep their status
+    *   Meeting next week/KubeCon?
+        *   NO regularly scheduled meeting
+    *   Meetings through end of the year?
+        *   @jrondeau will lead 12/18
+        *   @jaredb will take first meeting 1/8/19
+    *   Zach on vacation through mid-January: need someone to run/record
+*   [Zach] Still working on planning session agenda, will finish by 5pm on Thursday, December 6th. 
+    *   Placeholder issue: [https://github.com/kubernetes/website/issues/11331](https://github.com/kubernetes/website/issues/11331)
+        *   Zach will find out the specific locations 
+        *   We will meet from 10-2
+        *   Please add our meeting to the [community meeting calendar](http://bit.ly/kubernetes-summit)
+    *   [Jared] Can we please make this a google doc for collaborative editing and note-taking during the meeting?  
+        *   Yes! Hoorays. 
+*   [Jennifer, Jared, others?] Phil Wittrock’s [proposal for kubectl docs](https://groups.google.com/forum/#!topic/kubernetes-sig-docs/TXiYNIAB5hA) [[demo site](https://pwittrock-kubectl.firebaseapp.com/)]
+    *   Can we (iteratively) incorporate into k8s.io?
+            *   Current content: [https://kubernetes.io/docs/reference/kubectl/kubectl/](https://kubernetes.io/docs/reference/kubectl/kubectl/)
+            *   Interlinking between K8s.io and this site
+            *   Define contribution process
+    *   What’s the contribution process?
+        *   Would have to be defined. Owned by CLI group
+    *   Is this a model we’d like to develop for other areas of the docs?
+        *   [pwittrock] How do we feel about comprehensive linear “book” structure for specific topics - Tooling, Workload APIs, Cluster Management, etc?
+*   ~~[Jennifer, Cody] Need to add information about separate PRs for different language directories to docs contributor guide ~~Thanks to @zachorsarah!
+*   
+*   [Jim--DEFER until 12/18, review Jared’s additions] Continued discussion of limiting simple / typo PRs on X-old blog posts
+    *   [https://github.com/kubernetes/website/pull/11456#pullrequestreview-180862330](https://github.com/kubernetes/website/pull/11456#pullrequestreview-180862330)
+    *   [https://github.com/kubernetes/website/pull/11451#pullrequestreview-180889637](https://github.com/kubernetes/website/pull/11451#pullrequestreview-180889637)
+    *   Similar issue in k/k [https://github.com/kubernetes/community/issues/2953](https://github.com/kubernetes/community/issues/2953) focused on people “gamifying” PRs (I don’t know if that really is what we’re seeing or people just trying to submit a simple first PR).
+    *   OpenFaaS handles it by having users open issues and then later creating a bulk PR ( more ownership on us) [https://github.com/openfaas/faas/blob/master/CONTRIBUTING.md#ive-found-a-typo](https://github.com/openfaas/faas/blob/master/CONTRIBUTING.md#ive-found-a-typo)
+    *   Outcome: Do we want to define / document a policy on minor PR’s that address old or unused docs (If yes, what)?
+    *   AI: Jared, will take a look at
+    *   Tangentially relevant/helpful: [“what to leave out”](http://www.writethedocs.org/guide/contributing/#what-to-leave-out) from the WTD guide to contributing to the WTD documentation guide 
+*   [Andrew, Dominik] Kubernetes Modeling
+    *   Project update at SIG Docs planning meeting during contributor summit
+        *   What time?
+    *   Latest blog post [The Mechanics of Kubernetes](https://medium.com/@dominik.tornow/the-mechanics-of-kubernetes-ac8112eaa302)
+        *   Feedback welcome!
+    *   Upcoming: The Scheduler
+        *   blog post
+        *   will propose unconference session @ contributor summit
+
+
+## Past Meetings {#past-meetings}
+
+
+### 2018 Meetings {#2018-meetings}
+
+**11/27/2018**
+
+**7pm Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates and Reminders
+
+
+
+*   PR wrangler this week: @jrondeau (@bradamant3 on GH)
+*   1.13 updates?
+*   KubeCon Seattle is in two weeks: SIG Docs meeting is part of contributor day on Monday, 10 December. Anyone from APAC planning to attend?
+
+Agenda
+
+
+
+*   Netlify configuration for release 1.12 branch should have build-per-PR turned on
+*   Chinese contribution/membership: How is it going?
+    *   Conversion from Google Doc to GH issues is going great
+    *   Netlify builds for 1.12 PRs are working
+    *   Progress is great!
+*   Korean contribution/membership: How is it going?
+    *   Meetup last week: new members joining project
+    *   Working on dev-1.13 branch, coordinating with @tfogo for final PR on December 3
+    *   About 10 pages of updates for 1.13
+
+**11/20/2018**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Dennis Salama - Microsoft - Azure services and support team
+
+Updates and Reminders
+
+
+
+*   1.13 updates?
+    *   Update from Tim
+    *   Big crunch yesterday, down to 3 PRs that need to be reviewed
+        *   Review deadline: Nov 27
+        *   Release: Dec 3
+    *   All PRs in review except 3. Tracking [here](https://docs.google.com/spreadsheets/d/1umeZ-AHjjD6ntbFv1J2dJOjWd0Ft0WKAV2Wtd8EQ8FM/edit#gid=0).
+        *   Kubeadm
+*   PR wrangler this week is @tengqm, with thanks for swapping because of Thanksgiving in the U.S. Thank you!
+
+Agenda
+
+
+
+*   Kubectl docs generation -- inspired by [this PR](https://github.com/kubernetes/website/pull/10778). PR might could be fixed with a PR to upstream code to fix string literal. But another option is to change the generator that we use for the kubectl docs. What says the docs community?
+    *   (late addition to notes) AI: Jennifer will find right resource to get PR to upstream code merged, and submit said PR
+*   [chenopis] Simplifying the solution buckets on the [Setup landing page](https://kubernetes.io/docs/setup/).
+    *   Managed Solutions, e.g. GKE, EKS, etc. -- simpler billing, not paying for master
+    *   Hosted Solutions, e.g. K8s on GCE or EC2 -- more control of the # of machines, version of K8s, monitoring code, identity management
+    *   Custom Solutions - bare metal, on-premises
+    *   Local Machine - Minikube, etc.
+    *   Notes from meeting: 
+        *   Looks good to the SIG-Docs group
+        *   Codyclark can send an email to chenopis
+*   [jrondeau/Bradamant3] PRs against old blog posts. Inspired by [this PR](https://github.com/kubernetes/website/pull/11009), which fixes a 404 but points uselessly to an old release of a project no longer actively under development. Link checking is a good thing. How do we deal with the old blog posts part, though?
+    *   Document in contributor guide
+        *   Past one year don’t update :)
+        *   AI: Jared will submit a PR
+    *   Compassionate responses to PRs that come in from outside sig-docs
+*   [jrondeau/Bradamant3] [Redirects to current page for earlier version](https://github.com/kubernetes/website/pull/10985) -- PR raises an excellent issue, but seems non-trivial to address properly. (Will remove from agenda before meeting if assignees come up with solution.)
+*   [Jaredbhatti] Docfixit at Kubecon Seattle?
+    *   Someone leading this? Specific efforts we’d like to do?
+    *   Main Focus: Doc Summit instead of doc sprint
+    *   AI: Jared and Jennifer will discuss in Slack, consider scheduling options
+
+**11/13/2018**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Shavi Dissanayake -- new CNCF intern!
+
+Updates and Reminders
+
+
+
+*   1.13 updates? (no updates this week)
+*   PR wrangler this week is @Bradamant3 (jrondeau on Slack)
+
+Agenda
+
+
+
+*   N/A -- Jennifer, Shavi, Steve only attendees
+
+**11/6/2018**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Robin Rakowski 
+
+Updates and Reminders
+
+
+
+*   PR wrangler this week is @cody-clark
+*   Reminder: test changes locally, even for trivial PRs
+    *   Verify that Netlify builds succeed before merging
+        *   Add guidance to contributor section
+
+Agenda
+
+
+
+*   Content updates:
+    *   Fun with Modeling (@chenopis, @dtornow) ~15 min
+        *   Who is our audience exactly?
+        *   We believe these questions should be able to be answered by reading the documentation:
+            *   [https://github.com/kubernetes/kubernetes/issues/62415](https://github.com/kubernetes/kubernetes/issues/62415)
+            *   [https://www.reddit.com/r/kubernetes/comments/9u4b3a/is_there_a_way_to_specify_order_of_containers_to/](https://www.reddit.com/r/kubernetes/comments/9u4b3a/is_there_a_way_to_specify_order_of_containers_to/)
+    *   Refactoring home page: [https://github.com/kubernetes/website/pull/10795](https://github.com/kubernetes/website/pull/10795) (@chenopis) [[proposal](https://docs.google.com/document/d/1PxuMaXm7hFjO3MuzWmog-IW62ZnrTQ1S3GLcaAsOiIY/edit?usp=sharing)]
+        *   Content structure: google doc
+        *   Wait until WIP is dropped from title to add comments to PR
+    *   CNCF devoting more resources to initial onboarding
+*   Tooling updates:
+    *   Working group? (Luc)
+        *   (Zach C) https://discourse.gohugo.io/t/ignorefiles-and-i18n-expected-behavior/15097
+*   KubeCon/CloudNativeCon Seattle
+    *   Quarterly planning
+        *   Contributor day info (draft): [https://github.com/kubernetes/community/tree/master/events/2018/12-contributor-summit](https://github.com/kubernetes/community/tree/master/events/2018/12-contributor-summit)
+        *   We’re currently scheduled for 2 hours but can have more. I’ve asked that SIG Docs have 4 hours. 
+        *   It looks like we have 2 or 3 things going on in the same space. Let’s make sure we understand what we’re doing so we can explain to others what we’re doing :-) 
+*   Intro to contributing to k/website video (@Steve, @Jen)
+
+**10/30/2018**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Sam @ Heptio
+
+Updates and Reminders
+
+
+
+*   PR wrangler this week (and next!) is @cody-clark
+
+Agenda
+
+
+
+*   Content updates:
+    *   Fun with Modeling (@chenopis, @dtornow) ~15 min
+        *   Pod [[slides](https://docs.google.com/presentation/d/13vOH98rTGT4x-9cQznJLbsWtW472TIdawLxsSFI7R5s/edit?usp=sharing)]
+        *   [What the hell is a Pod anyways?](https://medium.com/@dominik.tornow/what-the-hell-is-a-pod-anyways-72e5534b892c) blog post
+    *   GH project cleanup? (Steve Perry -- update from APAC meeting last week)
+*   KubeCon/CloudNativeCon Seattle
+    *   December 10-13, who’s going?
+        *   8-9
+    *   Yearly retrospective
+        *   SIG Docs awards
+    *   Quarterly planning
+        *   Zach: get details by 11/6
+
+**10/23/2018**
+
+**Fourth Tuesday**
+
+**7pm Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates and Reminders
+
+
+
+*   
+
+Agenda
+
+
+
+*   Fun with Modeling (@chenopis, @dtornow) ~15 min
+    *   [High Availability](https://docs.google.com/presentation/d/1stVHEnEf1tr83gq4Am2MCTqhmJvF5XdXm3mJbGZzlNk/edit?usp=sharing)
+*   Content updates: GH project cleanup? (Steve Perry -- defer to next week, Jennifer can also help coordinate, brainstorm) (Zach C: Defer to 10/30)
+*   Logistics surrounding #sig-docs-tools WG (Luc)
+    *   [Slack channel](https://kubernetes.slack.com/messages/CCTBSCVB9/details/) for docs tooling proposals/questions 
+*   Internationalization workflows
+    *   Language labels
+    *   Write permissions for branches/labels: [https://github.com/kubernetes/website/issues/10682](https://github.com/kubernetes/website/issues/10682)
+
+**10/16/2018**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates and Reminders
+
+
+
+*   Congrats and thanks to new reviewers/approvers:
+*   New English reviewer: Jim Angel (GH: jimangel)
+*   New English approver: Stewart Yu (GH: stewart-yu)
+*   New Chinese reviewer: Yang Li (GH: idealhack)
+
+Agenda
+
+
+
+*   Fun with Modeling (@chenopis, @dtornow) ~15 min
+    *   [High Availability](https://docs.google.com/presentation/d/1stVHEnEf1tr83gq4Am2MCTqhmJvF5XdXm3mJbGZzlNk/edit?usp=sharing)
+*   Content updates: GH project cleanup? (Steve Perry -- defer to next week, Jennifer can also help coordinate, brainstorm)
+*   Logistics surrounding #sig-docs-tools WG (Luc)
+    *   Luc will consider labels for issues to help track
+    *   Generated docs
+    *   Need a list (everything that’s not content)
+*   NCW SIG Doc Presentation for KubeCon Shanghai (@bradtopol -- deferred, Brad unable to attend today)
+
+**10/9/2018**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates and reminders
+
+
+
+*   [Weekly PR wrangler](https://github.com/kubernetes/website/wiki/PR-Wranglers) for 10/8: Qiming Teng (@tengqm)
+*   SIG Docs Leads: Jared Bhatti stepping down, Jennifer Rondeau stepping up
+
+Agenda
+
+
+
+*   Renewed focus on content (Zach)
+    *   Let’s make sure our onboarding content rocks
+    *   Focus on content first
+    *   Defer tooling/automation to the #sig-docs-tools WG, get updates
+    *   Need to improve project tracking for content work (see next item)
+*   Longer-term project planning (paris)
+    *   Some suggestions from Paris Pittman
+    *   [Project board from Contrib-x](https://github.com/orgs/kubernetes/projects/1)
+    *   Each project has an owner, each work-item has an issue
+    *   Issues that aren’t owned are given a “help wanted” label
+    *   New contributors are directed at “help wanted” issues
+    *   Projects have standups during the meeting - makes the meeting run a bit faster.
+    *   Sub-projects, or projects that need more time can use the remaining time in the meeting. 
+    *   Zach: [Current progress in repo](https://github.com/kubernetes/website/projects)
+    *   Steve: AI: I can take on cleaning up 
+    *   Jennifer: Think about division between website projects and larger kubernetes (umbrella) projects
+        *   Paris
+            *   Those umbrella issues are key and labels for areas/foo

+            *   areas/foo being your subprojects
+*   Quarterly/yearly goals (Paris Pittman, Zach C)
+    *   Start setting goals/priorities on a quarterly basis ongoing
+        *   Paris: plan projects better using the process above, which leads to better quarterly planning. It’s not a science, so we’re not ready for OKRs
+    *   Zach and Paris will meet and discuss
+    *   Meet at KubeCon Seattle and chat further
+*   Fun with Modeling (@chenopis, @dtornow) ~15 min
+    *   [The great lie](https://docs.google.com/presentation/d/1UuinyQSyuL0bsp4lYcfl4O-4GP5bSkdEdH4GRPflnuE/edit?usp=sharing)
+*   Accessibility tools (@rajie)
+    *   NOTE: Deferred to SIG Docs tooling working group
+    *   Move to docs tools WG for consideration
+    *   http://pa11y.org
+    *   http://khan.github.io/tota11y/
+
+**10/2/2018**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Sam - TW @ Hepito
+*   Alasdair - IBM - Java Runtime
+*   YK - IBM - Java Runtime
+*   Michal - IBM - Java Runtime
+
+Updates and reminders
+
+
+
+*   [Weekly PR wrangler](https://github.com/kubernetes/website/wiki/PR-Wranglers) for 10/1: Zach Arnold (@zparnold)
+
+Agenda
+
+
+
+*   Update on 1.12 (Zach A)
+    *   DONE! 
+    *   Moar automation!
+*   Accessibility tools (@rajie)
+    *   DEFER for 1 more week and revisit 10/9
+    *   http://pa11y.org
+    *   http://khan.github.io/tota11y/
+*   I18n repo branching strategy (Zach A)
+    *   Move i18n repos back into k/website BUT need to:
+        *   add labels for languages so folks can scope PRs (Zach A. demo)
+        *   Need to add OWNERS files in various content/** folders (Zach C)
+        *   Need to update localization guidelines (Zach A)
+*   Quarterly/yearly goals (Zach C)
+    *   Meet at KubeCon Seattle
+    *   Start setting goals/priorities on a quarterly basis ongoing
+    *   Jared: Check-in on this 10/9
+*   (10/2, Ben Hall) SIG Docs and Katacoda tutorial content
+*   (10/2, Michal Broz, Brad Topol) Desire to add a new interactive tutorial for deploying Java Applications to Kubernetes 
+    *   Interactive guides are very valuable
+    *   Currently use a Node.js container
+    *   Want to add another flow with the Java runtime
+    *   Where will it sit in the overall k8s architecture?
+        *   Current flow is 6 pages telling a story
+*   Is there an ongoing Spanish effort? else I could work on/coordinate that. How about a German one?[Silvia]
+    *   There are currently no Spanish or German translations in progress, but you're welcome to start one! We're updating the localization guidelines to reflect an updated workflow--please feel free to follow along in the next two weeks!
+
+**9/25/2018**
+
+**Fourth Tuesday: 7pm Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates and reminders
+
+
+
+*   Thanks to @jrondeau for wrangling PRs this week--down a net of 23 PRs!
+*   [Weekly PR wrangler](https://github.com/kubernetes/website/wiki/PR-Wranglers) for 9/24: Zach Corleissen (@zacharysarah)
+
+Agenda
+
+
+
+*   Update on 1.12 (Zach A)
+    *   Going well (rumor has it!)
+*   Accessibility tools (@rajie)
+    *   DEFER for 1 week and revisit 10/1
+    *   http://pa11y.org
+    *   http://khan.github.io/tota11y/
+*   I18n repo branching strategy (Zach C)
+    *   After more research, subtrees look unlikely to work
+    *   WG is meeting on Thursday 9/27 to confirm and recommend an official strategy (passing commits between repos)
+    *   (June Yi) Korean docs branching strategy
+        *   Open PR to move OWNERS to content/ko/
+    *   Jim Angel, Svetlana: please message me in Slack (@zacharysarah) with your email so I can invite you to the WG meeting
+*   Quarterly/yearly goals
+    *   Meet at KubeCon Seattle
+    *   Start setting goals/priorities on a quarterly basis ongoing
+*   (10/2, Ben Hall) SIG Docs and Katacoda tutorial content
+*   (10/2, Michal Broz, Brad Topol) Desire to add a new interactive tutorial for deploying Java Applications to Kubernetes 
+
+    [Silvi]
+
+
+**9/18/2018**
+
+New contributors
+
+
+
+*   AGV - Google customer engineer
+*   Dominik returned
+
+Updates and reminders
+
+
+
+*   Thanks to @bradtopol for wrangling PRs this week (and surviving!)
+*   [Weekly PR wrangler](https://github.com/kubernetes/website/wiki/PR-Wranglers) for 9/17: Jennifer Rondeau (@jrondeau on Slack, @bradamant3 on GH)
+
+Agenda
+
+
+
+*   Update on 1.12 (Zach A)
+    *   All docs are staged, Jen Rondeau is working on kubeadm docs, and I will hopefully have final merge done this week
+    *   Had to back out CoreDNS
+    *   Hit the tripwire that restarted the branching discussion with maintainers :)
+*   Fun with Modeling (@chenopis, @dtornow) ~25 min
+    *   What is a model? [[slides](https://docs.google.com/presentation/d/1gkT67nnS0STPMZR2rdA1Jj9fHjFp291PU3M2_e9dd_c/edit?usp=sharing)]
+    *   Imperative vs Declarative [[slides](https://docs.google.com/presentation/d/1-FjTUxuJo3nvGS8jnFdsDMS9B8jniEuU5FgQ0rOFk0I/edit?usp=sharing)]
+    *   [Request for Comment (RFC)](https://docs.google.com/document/d/1eolKdH_LaT1dfMn8zry9CJ5gbs6hCm7prctkgmH3HZQ/edit?usp=sharing)
+*   Accessibility tools (@rajie)
+    *   DEFER for 1 week and revisit
+    *   http://pa11y.org
+    *   http://khan.github.io/tota11y/
+*   I18n repo branching strategy (Zach C)
+    *   After some discussion, commits back and forth could work but subtrees have the potential to be awesome and easier (after some initial setup)
+    *   Zach C is working on a prototype
+    *   Add [AGV](mailto:agv@google.com) and Brad Topol to the WG meeting
+    *   Add Jim Angel and Svetlana Karslioglu
+*   Quarterly/yearly goals
+    *   Meet at KubeCon Seattle
+    *   Start setting goals/priorities on a quarterly basis ongoing
+
+**9/11/2018**
+
+New contributors
+
+
+
+*   Welcome to Silvi TSM
+
+Updates and reminders
+
+
+
+*   Thanks @tengqm for wrangling last week
+*   [Weekly PR wrangler](https://github.com/kubernetes/website/wiki/PR-Wranglers) for 9/10: Brad Topol (@bradtopol)
+*   Thanks, Brad for stepping in so Zach A can get 1.12 docs out the door
+    *   Update: Brad is facing down Hurricane Florence
+
+Agenda
+
+
+
+*   (Zach A) 1.12 update
+    *   Ability to create 1.13 milestone? (Zach C can help create)
+    *   Teams to mention for docs: 
+        *   @kubernetes-website-admins

+        *   @sig-docs-pr-reviews

+    *   Where do SIG Docs tools live in k/website?
+*   (Vlad) K8s chatbot: gives answers to user questions based on docs, stack overflow, Slack convos
+    *   Working group: Q&A was yesterday
+    *   (Zach) Should SIG Docs implement answerbot for #sig-docs? 
+    *   (Jennifer) Talk about data from #kubernetes-novice and #kubernetes-users
+    *   Let’s take a look at the raw data from Vlad/Foqal for Foqal use in existing channels
+    *   Follow up with Jennifer in week after release for advice about how/whether to proceed (9/??)
+        *   Steve: As we examine research, can we examine that data may be mixed/in cheatsheet form? Consider that URLs may have mixed info.
+*   (Luc) Tools/infra WG update
+    *   Link to: [https://docs.google.com/presentation/d/1W_M3jAirn5tl8kN2B8pd4OEradZIJONJf988aIQiLhE/edit?ts=5b968ea9#slide=id.p](https://docs.google.com/presentation/d/1W_M3jAirn5tl8kN2B8pd4OEradZIJONJf988aIQiLhE/edit?ts=5b968ea9#slide=id.p)
+    *   Rajie: How can we improve site accessibility? Will initially present recommendations to the WG regarding tooling, i.e. how we can measure site accessibility and point out instances of non-compliance. Plan(s) of action to be discussed later as a group.
+*   (Zach A./Zach C./Zachs/Zachii?) Branching strategy WG update
+    *   We met on Monday, meeting again at 11:30am for a follow-up.
+*   (Misty/Tim F) best practices for using `for_k8s_version`?
+    *   DEFER until Misty/TFogo attend
+    *   Zach C will contact Misty in advance of next meeting: devote time for sufficient discussion, as it’s a large issue
+
+**9/4/2018**
+
+New contributors
+
+
+
+*   Vlad Shlosberg
+
+Updates and reminders
+
+
+
+*   [Weekly PR wrangler](https://github.com/kubernetes/website/wiki/PR-Wranglers) for 9/3: Qiming Teng (@tengqm) 
+
+Agenda
+
+
+
+*   (Vlad) K8s chatbot: gives answers to user questions based on docs, stack overflow, Slack convos
+    *   Working group: Zach C will set up a time for Q&A with Vlad
+*   (Zach A.) Code Freeze/Docs Deadline is today, so expect an exciting update from me. I’ve intentionally not merged any PR’s into the 1.12 branch to I could have time to ensure that everything was ship shape from a Git standpoint
+    *   43 features need docs updates
+    *   29 features have permission to pull from milestone
+    *   [Tracking spreadsheet](https://docs.google.com/spreadsheets/d/177LIKnO3yUmE0ryIg9OBek54Y-abw8OE8pq-9QgnGM4/edit)
+    *   Jennifer will help with kubeadm docs
+    *   Generated ref docs: where are those at?
+        *   Jim and/or Jim are fixing bugs in refdoc generation process
+        *   Steve: Which doc tools are being revised?
+        *   Jim: [Link to PR](https://github.com/kubernetes/website/pull/10123)
+        *   Steve: role is changing, but happy to help with refdocs in release PRs
+    *   PR reviewers:
+        *   Make sure 1.12 releases base on release-1.12, not master
+        *   Add 1.12 feature PRs to 1.12 Milestone
+*   (Luc) Update on tooling and infra working group. Proposal document: [https://docs.google.com/document/d/12RTw9s7zGncKuaY6zXiTJ4f7cWf_7iAWlaWgoJJyQ3g/edit](https://docs.google.com/document/d/12RTw9s7zGncKuaY6zXiTJ4f7cWf_7iAWlaWgoJJyQ3g/edit)
+*   (Zach A.) Proposal/Idea from the Korean Translation team on how to do some automated branch syncing for long running (i.e. release style) branches 
+    *   (Zach C.) Branching strategy for l10n repos: working group to figure out addition to l10n guide?
+    *   (Misty / Zach) Release management branching strategy [proposal](https://docs.google.com/document/d/159xLCtr_0SffB28qXPlWGVefn6ihMM3z9DAU_V-oJMQ/edit#)
+    *   Further discussion will take place in the Tooling and Infra working group
+*   Misty role change
+    *   Tech lead for Google GKE docs, focusing less on K8s docs
+
+**8/28/2018**
+
+**Fourth Tuesday (7pm Pacific)**
+
+New contributors
+
+
+
+*   None :-(
+
+Updates and reminders
+
+
+
+*   Reminder: 8/28 is a Fourth Tuesday, so this meeting happens at 7pm Pacific. Next week’s meeting resumes at 10:30am Pacific.
+
+Agenda
+
+
+
+*   Follow up from last APAC meeting (7/24):
+    *   Is the localization guideline document up to date?
+        *   Yes: [#9192](https://github.com/kubernetes/website/pull/9192)
+*   Proposal: tooling and infrastructure working group (Luc)
+    *   Dedicate a smaller group to ongoing, more immediate work
+    *   Andrew: good idea!
+    *   Luc will communicate and create a Slack channel if need be
+*   I18n repo status: OWNERS and OWNERS_ALIASES files
+    *   kubernetes-docs-ja: updated
+    *   kubernetes-docs-ko: updated
+    *   kubernetes-docs-zh: need updates
+        *   Follow prow workflow
+        *   Update their OWNERS* files
+    *   Korean team: Put June Yi in touch with Zach Arnold
+    *   Set up Netlify for i18n teams for preview builds
+*   Branching strategy for i18n repos
+    *   What do teams need?
+*   Follow up on [https://kubernetes.io/docs/setup/pick-right-solution/](https://kubernetes.io/docs/setup/pick-right-solution/) and left navi panel inconsistencies;  Are we still updating [https://kubernetes.io/docs/setup/pick-right-solution/](https://kubernetes.io/docs/setup/pick-right-solution/) to ensure it is up to date? Also see discussion in https://github.com/kubernetes/website/pull/10028
+*   KubeCon @ Shanghai
+    *   Who is planning to attend?
+    *   What do people want to do for the doc sprint?
+
+**8/21/2018**
+
+New contributors
+
+
+
+*   
+
+Updates & reminders
+
+
+
+*   Zach Arnold Joining Late
+
+Agenda
+
+
+
+*   [Andrew] WTD conversation about where we are, where to go
+    *   Treading water, not really advancing
+    *   What 1-2 things do we focus on through end of Q4?
+    *   Zach & Luc will talk with Chris A at CNCF about how to approach partners (AWS, Azure) to fulfill writer hiring commitments, especially in the context of Getting Started refactors
+
+**8/14/2018**
+
+New contributors
+
+
+
+*   
+
+Updates & reminders
+
+
+
+*   PR wrangler this week is Brad Topol
+*   Zach is still semi-unavailable due to health reasons, DM him directly on Slack for response
+
+Agenda
+
+
+
+*   HOLD [Zach Arnold] Update on 1.12
+    *   Will be joining late
+*   [Jennifer/Andrew] Kubelet generated docs [k/k PR #66034](https://github.com/kubernetes/kubernetes/pull/66034) -- we need someone or a small working group focused on generated docs
+    *   Specific to kubelet, but representative of issues specific to generated docs as a whole
+    *   Needs to be addressed by k/k and sig-docs
+    *   Andrew is tapped, Jennifer can’t work alone, need folks to step up
+    *   Another option may be to contact SPF folks to turn off third-party flags
+    *   Jim Angel is available! Yay!
+*   [Jennifer reporting only] should this sig be taking the lead on containerd docs?
+    *   Link to diagram for underlying runtime diagrams:  [https://docs.google.com/drawings/d/1vb31vSh3qwzRgjevjJayVZsnh7tRsAszx__EzXoddZA/edit](https://docs.google.com/drawings/d/1vb31vSh3qwzRgjevjJayVZsnh7tRsAszx__EzXoddZA/edit)
+*   [Jennifer] add to style guide: avoid patronizing language, specifically the major “weasel” words “just”, “only”, “simply”, “simple”, “easy”
+*   [Zach] We need someone to lead next week’s meeting (8/21), many folks will be at Write the Docs Cincinnati
+    *   Use meeting time for SIG Docs planning
+*   [Andrew] WtD @ Cincinnati -- what do people want to do there?
+    *   Mon - coordinated PR bash vs doc sprint?
+        *   Jennifer will run doc sprint, Andrew will run coordinated PR bash
+    *   Tue - SIG Docs planning
+        *   Andrew/Zach will help plan/retrospective like SIG Docs Summit
+*   [Zach] What should we do with OWNERS_ALIASES files in i18n repos?
+    *   I propose stripping them/providing empty files, but letting SIGs make subsequent additions for members with fluency
+    *   Empty files, SIGs can add to empty files as preferred/needed
+*   [Andrew] K8s.io Search Outage post-mortem
+    *   Published in public GitHub [Issue #9758](https://github.com/kubernetes/website/issues/9758#issuecomment-413698701)
+*   [Zach A.] Message Dan Kohn sent to Sig Docs
+    *   CDN speed for kubernetes.cn [https://github.com/kubernetes/website/issues/9634](https://github.com/kubernetes/website/issues/9634) 
+        *   Prefer to use a mirror in China (Alibaba) for assets that are coming from elsewhere
+    *   Search engine selection for kubernetes.cn [https://github.com/kubernetes/website/pull/9845](https://github.com/kubernetes/website/pull/9845) 
+        *   Want to adjust the PR to include a way to adjust the search engine by drop-down if possible
+        *   Additionally use Google Analytics to back up decision
+
+**8/7/2018**
+
+New contributors
+
+
+
+*   Svetlana Karslioglu (Rackspace)
+*   Pooja Gadige
+
+Updates & reminders
+
+
+
+*   Zach C is semi-unavailable due to ongoing health stuff, message him directly on Slack for attention
+
+Agenda
+
+
+
+*   1.12 Update (Zach A) [[status spreadsheet](https://airtable.com/shrqQbRD8oSDQizgY)]
+    *   Things are going well, just managing the branch.
+    *   There are 7 PR’s at present in k/k that will need docs and we’re beginning to bother them
+*   PR Wrangling update
+    *   82 open PR’s, and things seem to be operating as normal, but will reach out if conditions worsen
+    *   354 open issues, will be going through those as well
+*   [Google Search problem](https://github.com/kubernetes/website/pull/9767) discussion (Misty added on behalf of Andrew)
+*   What to do about docs that reference maintenance [releases by number that have to be bumped manually, such as 1.11.1](https://github.com/kubernetes/website/pull/9613/)? (Misty)
+    *   Follow up from 7/31
+    *   Fix with a contractor (Zach)
+    *   Release meister: update point release variables? 
+    *   Update release notes for point releases as well? (Nick Chase)
+*   Tactics for importing content from localization repos into k/website
+    *   Subtree: [https://stackoverflow.com/questions/1683531/how-to-import-existing-git-repository-into-another](https://stackoverflow.com/questions/1683531/how-to-import-existing-git-repository-into-another)
+    *   Follow up from 7/31
+    *   ...Or just open a giant PR for the first import, then set up webhooks for subsequent changes?
+    *   Zach will start a WG for automation
+*   [Fundamental Modeling Concepts (FMC) for Kubernetes](https://docs.google.com/presentation/d/1vUAkRP-MjNqusqDHBptycdSbC_HSTBKyEHAFZ5OdbQA/edit?usp=sharing) (Andrew, Dominik)
+    *   Dominik will reach out to Zach to initiate a contract
+*   DSathe: Talk about cluster operator docs next week (8/7) [[slides](https://docs.google.com/presentation/d/1ebkJBOE2r-UeEGe7Ua5TUAHadd4Xm9Wri6FacUY8G9U/edit#slide=id.g3e00e93648_0_25)]
+*   [Docs Contributor guide](https://kubernetes.io/docs/contribute/) update (MIsty)
+*   WtD @ Cincinnati -- PR bash, SIG Docs planning (Andrew)
+    *   Propose doing PR bash on Tue, SIG Docs planning on Wed
+    *   Planning would be a continuation of the discussions from the SIG Docs Summit @ last WtD Portland
+*   kubernetes.io/community redesign (paris)
+    *   Next steps: copy decisions and calendar mechanisms 
+    *   Will update this group when we have more to show
+    *   [Issue is still collecting suggestions and updates](https://github.com/kubernetes/website/issues/7795)
+*   Refactoring _[Picking the Right Solution](https://kubernetes.io/docs/setup/pick-right-solution/)_ page (Cody)
+
+**7/31/2018**
+
+New contributors
+
+
+
+*   Dhananjay Sathe - cloud robotics startup (+1)
+
+Updates & reminders
+
+
+
+*   Maintainers, check the wiki for the PR wrangler schedule through the end of the year: [https://github.com/kubernetes/website/wiki/PR-Wranglers](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+*   Maintainers, please check this list for accuracy/completeness: [https://github.com/kubernetes/website/pull/9510#issuecomment-409056524](https://github.com/kubernetes/website/pull/9510#issuecomment-409056524) 
+
+Agenda
+
+
+
+*   What to do about Black Friday (Luc)
+    *   Talked to BEP--Black Friday 2 is on the way, but developmentally costly
+    *   Porting Kramdown to Go may be more effort than it’s worth
+    *   Follow up conversation about next steps with Luc/BEP
+*   1.12 Update
+    *   Zach A. Has a meeting conflict, but all is going well so far! 
+    *   We’ve automated a chunk of our workflow: [https://airtable.com/shrqQbRD8oSDQizgY](https://airtable.com/shrqQbRD8oSDQizgY) and the release team is now going to be borrowing from our Airtable for task coordination. Go docs!
+    *   Docs PR Deadline is 3 weeks away!
+*   What to do about docs that reference maintenance [releases by number that have to be bumped manually, such as 1.11.1](https://github.com/kubernetes/website/pull/9613/)? (Misty)
+*   Tactics for importing content from localization repos into k/website
+    *   Subtree: [https://stackoverflow.com/questions/1683531/how-to-import-existing-git-repository-into-another](https://stackoverflow.com/questions/1683531/how-to-import-existing-git-repository-into-another)
+    *   Other possibilities?
+    *   Revisit this on 8/7
+*   Improvements to site UX (Neha, Andrew)
+    *   Link to presentation:
+    *   How to contact Neha with questions:
+*   [Fundamental Modeling Concepts (FMC) for Kubernetes](https://docs.google.com/presentation/d/1vUAkRP-MjNqusqDHBptycdSbC_HSTBKyEHAFZ5OdbQA/edit?usp=sharing) (Andrew, Dominik)
+    *   Deliverables: what would they be? (SVGs in docs)
+    *   Replace/augment: “What is a Pod” section in Docs
+    *   Pilot: proposed to be Pod, but could it be Kubernetes as a whole?
+        *   It could be; but
+        *   Pods are fundamental concepts to Kubernetes
+    *   Dominik will come back on 8/7 to talk more
+*   DSathe: Talk about cluster operator docs next week (8/7)
+
+**7/24/2018**
+
+REMINDER: Fourth Tuesdays are APAC meeting times (7pm Pacific)
+
+Agenda
+
+
+
+*   
+*   New localization repositories:
+    *   Korean: [https://github.com/kubernetes/kubernetes-docs-ko](https://github.com/kubernetes/kubernetes-docs-ko)
+    *   Japanese: [https://github.com/kubernetes/kubernetes-docs-ja](https://github.com/kubernetes/kubernetes-docs-ja) 
+    *   NEXT STEPS:
+        *   Get familiar with the Kubernetes bot workflow commands: [https://prow.k8s.io/command-help](https://prow.k8s.io/command-help)
+            *   Specifically: /lgtm, /approve, and /hold
+        *   Migrate the existing repositories into the Kubernetes organization
+            *   Some guidance: 
+                *   [https://stackoverflow.com/questions/1683531/how-to-import-existing-git-repository-into-another](https://stackoverflow.com/questions/1683531/how-to-import-existing-git-repository-into-another) 
+        *   Open a PR to create your own OWNERS files
+*   Kubernetes.cn is live!
+    *   Some issues: Dan will contact Kaitlyn/Zach to resolve
+*   Is the localization guideline document still up to date?
+    *   Luc Perkins is working on a PR (1 week deadline, 7/31)
+
+**7/17/2018**
+
+New contributors
+
+
+
+*   
+
+Updates & reminders
+
+
+
+*   
+
+Agenda
+
+
+
+*   Zach Corleissen is out sick :(
+*   PR Wrangler (Zach C.)
+    *   Queue is growing longer; need to manage it more intentionally
+        *   For PRs with no CLA or no response from contributors, it’s OK to close more aggressively
+            *   15 days of no response warning, 30 days to close 
+            *   Close after 15 days to close if it’s a CLA based issue
+            *   Things on hold or in a milestone should probably not be automatically closed
+            *   For typo (or simple fixes) with an unsigned CLA, recreating the commit and closing the original is usually best after a period of silence (like 2 weeks)
+        *   PR queue bash: Sprint days at WtD Cincinnati (August 20-21)
+            *   Will there be remote participation? Zoom meeting? Slack?
+            *   Tuesday August 21st is the proposed day for a bash, and whenever people can participate is great. Thanks!
+                *   Potentially check in at the sig-docs meeting that day for the status of the bash.
+    *   PR queue bash: Mid- to late October
+        *   Potentially last opportunity for big, coordinated push for PR queue bashing before the holidays and both KubeCons
+*   Docs 1.12 Release Update
+    *   Meet the team (Tim, Jim, and Sam)
+    *   Meet our strategy (do the same as always and ask lots of questions)
+    *   Meet the program pulling PR’s from the milestone for our review
+*   Ref docs format
+    *   [https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.11/)
+    *   [https://deploy-preview-9536--kubernetes-io-master-staging.netlify.com/docs/reference/generated/kubernetes-api/v1.11/](https://deploy-preview-9536--kubernetes-io-master-staging.netlify.com/docs/reference/generated/kubernetes-api/v1.11/)
+    *   Suggestions:
+        *   Docs working with engineers to add examples
+        *   Docs to add examples directly
+        *   “PEFixit day” - taking time to work with engineers to add examples with docs together
+
+**7/10/2018**
+
+New contributors
+
+
+
+*   
+
+Updates & reminders
+
+
+
+*   New SIG Docs approvers:
+    *   Kaitlyn Barnard (CNCF), @kbarnard10 on Slack/GitHub
+    *   Zach Arnold (Ygrene), @zparnold on Slack/GitHub
+*   Congratulations to Misty Linville, Zach Arnold, and Nick Chase on the 1.11 docs!
+*   PR [wranglers](https://github.com/kubernetes/website/wiki/PR-Wranglers) (Zach)
+    *   Feel free to flesh out the wrangler description
+    *   Best guess for shift assignments based on what I know of folks’ schedules through the end of 2018 (KubeCon Shanghai, KubeCon Seattle, WtD Cincinnati, OSCon)
+*   Translation repos (Zach)
+    *   On agenda for discussion with SIG Arch this week (Thursday, 12pm Pacific)
+*   Big thank you to @tengqm for moving all YAML configuration files to a common directory. This involved fifteen PRs. [Issue 9283](https://github.com/kubernetes/website/issues/9283).
+
+Agenda
+
+
+
+*   kubernetes.io/community: CNCF (Kaitlyn) will be doing a mock of a site redesign, includes more modern calendar view, other community topics, communication platforms
+    *   Future presentation of mock when it’s ready for review
+    *   Feedback will be in a related [GH issue](https://github.com/kubernetes/website/issues/7795) for a single source of truth
+*   Netlify auth tokens (Misty)
+    *   Check back on progress in 1 week 7/17
+*   Zoom maintenance (Zach C)
+    *   Paris will do an AMA for Zoom moderation
+*   REVISIT from 6/26: Docs accuracy discussion with SIG Arch
+    *   POSTPONE until Andrew can join--revisit 7/17
+*   [Issue with generated docs for kubelet](https://github.com/kubernetes/website/pull/9344) (link is to PR for temporary fix; PR links to well-documented issue) (Jennifer)
+    *   Jennifer will open an issue in k/k for the underlying issue -- [PR already exists](https://github.com/kubernetes/kubernetes/pull/66034). But see discussion there and in [this issue in the docs repo](https://github.com/kubernetes/website/issues/9413). Summary: there’s disagreement about whether the fix should be to the kubelet help code or to the gen-docs script. If the latter, we’d need a separate script and process to generate kubelet docs. Right now the script takes care of multiple tools at once.
+    *   Merge the PR to fix the immediate problem
+    *   Follow up on 7/24 for issue in k/k
+    *   It's live: [https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/](https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/)
+*   Docs contribution landing page is weird. :( (Jared)
+    *   [https://kubernetes.io/docs/home/contribute/](https://kubernetes.io/docs/home/contribute/) which is the primary docs contribution page. It’s ironic, but not useful. 
+    *   Seems like a new landing page for this content would be the best path forward. Is someone working on this? 
+    *   Communty guide: [https://kubernetes.io/docs/imported/community/guide/](https://kubernetes.io/docs/imported/community/guide/)
+    *   Misty is working on this; timeline 2 weeks (7/24)
+        *   June Harton will share her own observations/work with Misty
+
+**7/3/2018**
+
+NO MEETING--canceled due to the US holiday.
+
+**6/26/2018 (APAC)**
+
+Introductions
+
+
+
+*   Zach Corleissen, SIG Docs Lead
+
+Updates & Reminders
+
+
+
+*   This meeting follows the [CNCF code of conduct](https://github.com/cncf/foundation/blob/master/code-of-conduct.md)
+*   Please speak one at a time
+*   Please mute unless you are speaking
+
+Agenda
+
+
+
+*   First meeting!
+*   Julia: Hugo migration
+    *   Ready by June 28th
+*   Rajie: How to add new contributors to this meeting time?
+    *   Zach: Feel free to add participants directly to the meeting invitation
+*   Ian (Korean l10n):
+    *   Team meets weekly
+    *   New leader: June Yi
+    *   How to add reviewers to repository
+        *   Zach: I can help you add an OWNERS file
+    *   Zach: If June Yi sends GH ID and email, I can help set up repo permissions
+*   Zach: contact Taylor Waggoner with request to open Korean translation mailing list
+*   Beijing birthday for Kubernetes
+    *   21st and 22nd of July
+    *   Photos on Twitter! Hooray!
+*   Zach will work with Jared to manage agenda invitations
+
+**6/26/2018 (Pacific)**
+
+New contributors
+
+
+
+*   Tim, SF, EmLab
+
+Updates & Reminders
+
+
+
+*   APAC meeting time starts today at 7pm
+    *   (Zach) Proposal to have only one SIG meeting on Tuesdays going forward. For example, next fourth Tuesday (July 24) would have one meeting at 7pm PST.
+    *   Consensus: YES
+*   Next week (July 3): US holiday 
+    *   Zach and Andrew out on vacation
+    *   Who can lead? Steve Perry can.
+*   New maintainers:
+    *   Qiming Teng (@tengqm)
+    *   Misty Linville (@mistyhacks)
+
+Agenda
+
+
+
+*   (Andrew) [@timothysc](https://github.com/timothysc) brought up in a recent K8s steering committee the question about how to ensure docs are created and maintained when code changes happen. How do we enforce this? They want to empower us to take this on. Do we need a policy/process for the lifecycle of docs (e.g. when a feature is introduced and moves from Alpha to Beta to GA)?
+    *   video of discussion: [https://www.youtube.com/watch?v=UKJYy9Oiuv0&t=5m59s](https://www.youtube.com/watch?v=UKJYy9Oiuv0&t=5m59s)
+    *   Discussion:
+        *   Gate checks in feature development repos would likely require more bandwidth/headcount than we have
+        *   SIG Release also wants to track feature release status: we don’t have a formal list of feature status
+            *   What about features with multiple moving parts that advance at different stages?
+        *   SIG Release spreadsheet: late notification of features that require docs
+        *   If we have a hard line against documenting alpha features, that makes it harder to document beta features
+            *   If we do document alpha features, we need to require specific guidelines about what docs are required
+        *   How to improve feature/area ownership?
+            *   Add a SIG to front matter of each document
+            *   Work with SIGs for annual review
+            *   Surface the last-updated date on the page (Hugo feature)
+            *   Use Hugo shortcodes to indicate feature state, instead of having feature state info in prose
+            *   Steve: Include a dedicated field in front matter (“sig”)
+            *   Work with SIG release to make sure docs are identified/included at earlier phases
+        *   Carrots and sticks
+            *   Carrot: For SIGs that clean up their docs for a release, highlight them in the release notes
+            *   Sticks: If a particular doc stales out/no review within <X> time (1 year?), remove it from docs
+                *   Add a label for Technical LGTM, require it annually or doc rots
+        *   Revisit in two weeks (7/10)
+            *   Andrew will put together a doc of action items
+            *   Approach SIG Release, SIG Arch
+            *   One immediate approach: ask ourselves, “Does it make sense to assign a single SIG to a topic?”
+            *   Ask other SIGs to tag themselves in topics (provide a sample PR)
+*   (Misty) 1.11 updates
+*   BUMP to 7/10 - (Misty) Retro of branching strategy for 1.11, proposal for 1.12 based on discussions with lots of Git-experienced folks
+*   BUMP to 7/10 - (Luc) Questions “Kubernetes Day Two” documentation.
+*   (Steve) Moving YAML files to common directory. Several PRs. Example: [https://github.com/kubernetes/website/pull/9236](https://github.com/kubernetes/website/pull/9236) \
+
+
+**6/19/2018**
+
+New contributors
+
+
+
+*   Jim Angel (Austin)
+
+Updates & Reminders
+
+
+
+*   (Misty) 1.11 docs update
+    *   Things are on track
+    *   Ping Misty if you are blocked on a PR, first release candidate (RC) may be cut on Wednesday 6/20
+*   (Zach) PR wrangler update (6/19)
+    *   Partial fix: repo project to enable monitoring at a glance, make it easier to hand off week-to-week - VERDICT: Don’t do it, it’s a bad idea
+    *   Exclude release meister
+    *   Given current maintainer numbers, we’re looking at 2 wrangler shifts per maintainer per quarter. 
+
+Agenda
+
+
+
+*   Style guide: Should we capitalize Containers? ([#9040](https://github.com/kubernetes/website/pull/9040))
+    *   Jennifer’s answer: NO (and yes I have Further Thoughts About Capitalization Generally In The Docs. No surprise there ...) Wait, no, maybe … (like all things style-wise …)
+    *   Zach’s answer: I’m strongly ambivalent! It’s useful to distinguish between objects vs. instances, but we apply the distinction inconsistently at best.
+    *   Steve's answer: This needs to be part of a larger discussion about capitalizing API objects. Note that Container is an API object even though users don't create Container objects directly. [https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.10/#container-v1-core](https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.10/#container-v1-core)
+    *   Zach: Create clear style guide guidance for capitallzation
+        *   Open an issue, allow multiple PRs against it for style guide fixes
+        *   Create a checklist with some guidance for different levels of editorial difficulty/passthrough
+        *   (Steve) Prioritize markdown fixes \
+
+*   APAC Meeting time
+    *   Proposal: start with monthly meetings on Tuesdays at 7pm Pacific:
+        *   Wed 7:30am Bangalore
+        *   Wed 10am Beijing
+        *   Wed 11am Tokyo
+        *   Tuesday 10pm Eastern
+    *   Advertise to make time visible
+    *   Revisit after 3 months
+*   Internationalization
+    *   Issue open for Korean and Japanese translations: [https://github.com/kubernetes/community/issues/2221](https://github.com/kubernetes/community/issues/2221)
+    *   In conversation with Bjorn Erik Pedersen about optimizing k/website for internationalization
+*   How best to generate kubectl docs
+    *   [https://groups.google.com/forum/?pli=1#!topic/kubernetes-sig-docs/ZMVVNBu2TD8](https://groups.google.com/forum/?pli=1#!topic/kubernetes-sig-docs/ZMVVNBu2TD8)
+    *   Whatever we do must be different from what we do right now; it’s difficult, cumbersome, and always changing
+    *   Moving targets for correctly documented processes are a time sink
+    *   Not just kubectl, but all generated API/component docs
+    *   One idea may be to break up single (huge) HTML file into separate files for each command (several hundred HTML files)
+        *   Be sure before action; would be difficult to redirect in the future
+    *   (Misty) CSS for different refdocs are all slightly different; also look unlike the rest of the site
+    *   (Misty) Can we abstract the content from the presentation layer?
+        *   (Steve) k/k may have some options for format generation in the generation scripts; we’re currently using the generated Swagger spec
+            *   (Steve) Start by investigating Swagger spec
+        *   How Docker does it for Swagger API docs ([source](https://github.com/docker/docker.github.io/tree/master/engine/api/v1.37)) ([output](https://docs.docker.com/engine/api/v1.37/)) using [redoc](https://swagger.io/blog/api-development/redoc-openapi-powered-documentation/)
+        *   How Docker does it for CLI refs ([YAML](https://github.com/docker/docker.github.io/blob/master/_data/engine-cli/docker_checkpoint_create.yaml) and [stub file](https://github.com/docker/docker.github.io/blob/master/engine/reference/commandline/checkpoint_create.md)) ([output](https://docs.docker.com/engine/reference/commandline/checkpoint_create/))
+    *   Involve Qiming Teng in this discussion--Zach will create an offline meeting
+*   Anyone else notice that some choices from [https://kubernetes.io/docs/setup/turnkey/aws/](https://kubernetes.io/docs/setup/turnkey/aws/)  disappeared compared to previous  versions of the docs?** **
+    *   Short term fixes are possible (Steve will open a PR for orphaned topics)
+    *   BUT remember that larger Setup changes are in the works
+    *   New SIG Cloud Provider meeting: [https://zoom.us/my/sigcloudprovider](https://zoom.us/my/sigcloudprovider)
+        *   https://github.com/kubernetes/community/tree/master/sig-cloud-provider#meetings
+    *   Tangentially, Jennifer will be reorganizing kubeadm content post-1.11
+*   Anyone besides Brad going to KubeCon Shanghai to help run a Doc Sprint?
+    *   Andrew (chenopis) is going too. Current thinking is to craft the Doc Sprint around the Chinese translation efforts to make sure their translation workflow is solid.
+*   PRs that fix the double bullet issue via css hacks?
+
+**6/12/2018**
+
+New contributors
+
+
+
+*   Takuya Takuda (Japanese translation)
+
+Updates & Reminders
+
+
+
+*   Rotations for the PR queue?
+    *   last week
+        *   Zach/Misty
+    *   this week
+        *   Brad Topol (intermittent, starting on Friday)
+    *   next week
+        *   ?
+    *   PR assignments: ad hoc no longer working, need to come up with regular shifts
+        *   Check in with other SIGs
+        *   Report back on 6/19 (Jared will send an email)
+*   (Misty) 1.11 docs updates
+    *   Docs are going well, PRs assigned out to SIG Docs reviewers
+    *   For release-specific PRs, only release meisters should be approving/merging
+        *   Function of /lgtm is configurable
+
+Agenda
+
+
+
+*   (Andrew) Consider alternating SIG Docs weekly meeting times for APAC participation
+    *   7pm Pacific meeting once per month on Mondays
+*   (Zach) Review how the prow (k8s-ci-bot) command `/hold` works
+*   (Zach) Looking for another sponsor for K8s org membership for @cstoku: [https://github.com/kubernetes/website/pulls/cstoku](https://github.com/kubernetes/website/pulls/cstoku)
+    *   (Jennifer) I’m happy to sponsor if he still needs another sponsor.
+*   (Steve) Prototype by Qiming in [PR 8965](https://github.com/kubernetes/website/pull/8965). Move all YAML files to a dedicated directory. Our current practice is to put a YAML file in the same directory as the topic that uses it. Two problems: 1) When we move a topic, we have to move all the associated YAML files. 2) When we move a YAML file, we have to update [examples_test.go](https://github.com/kubernetes/website/blob/master/test/examples_test.go).
+*   (Andrew, Zach) Status of Hugo migration
+    *   If you see doubled bullet points in the TOC for a page, make sure to apply a template shortcode
+    *   Steve: Do we need another template type for reference material? (Concepts are fine for now)
+    *   We may need a new template for generated refdoc (Steve will follow up in 1 week, 6/19 and two weeks 6/26)
+*   (Jennifer, per discussion today in #sig-docs) Guidelines for documenting alpha features (or docs at any specific feature state)
+    *   We need guidelines for how to document feature state (Jennifer will follow up in 2-3 weeks)
+    *   Tim St. Clair: Don’t document alpha features in the wild; creates a supportability nightmare
+        *   Alpha features are disabled on purpose
+    *   Another possibility is a standard disclaimer warning
+    *   How about having a feature_state variable in the front matter that would trigger an include of a disclaimer at the top of the page for alpha features?
+*   (Zach A) Have made a prototype link checker in Go [https://github.com/zparnold/k8s-docs-link-checker](https://github.com/zparnold/k8s-docs-link-checker) what would we like to do with it? Email broken links? Have it create issues in k/website?
+    *   Sounds lovely! Limit scope to files in PR
+*   Tim St Clair wants to restructure some docs
+    *   Wants to reorganize kubeadm
+
+**6/5/2018**
+
+New contributors
+
+
+
+*   Yasmary Diaz: Alternate Software
+*   Ian Choi: Translation efforts 
+
+Updates & Reminders
+
+
+
+*   Rotations for the PR queue?
+    *   last week
+        *   Zach
+    *   this week
+        *   Misty
+        *   Zach
+    *   next week
+        *   ?
+*   (Misty) 1.11 docs updates
+
+Agenda
+
+
+
+*   (Zach) Approvers for individual files: [https://github.com/kubernetes/website/pull/8506](https://github.com/kubernetes/website/pull/8506)
+    *   Change “approvers” to “reviewers”
+    *   Misty: These should go in the contributors guide!
+    *   Steve: will take on remaining legacy approvers and change to reviewers
+*   (Misty) Related to the above PR, should we have something in the PR template and maybe in official docs about how other SIGs interact with us, that before a PR is raised which tries to change sig-docs processes, that change should be discussed and approved in a sig-docs meeting? This was also Steve’s comment in the PR.
+*   (Misty) Korean translation -- had another query on Slack from someone interested in contributing. Send them to Ian?
+    *   Direct them to Ian (#kubernetes-docs-ko)
+    *   Zach will create a K8s org repo for Korean translation
+    *   Add guidelines for repository structure
+*   (Jennifer, Steve) Update docs generation instructions
+    *   Steve will update doc generation instructions
+    *   New files to generate are now at https://github.com/kubernetes-incubator/reference-docs
+    *   Jennifer and Steve will examine and report back 6/12
+    *   Steve will generate ref docs for 1.11
+*   (Zach) Followup on fixing broken links. Originally (Steve): Would someone have the time/interest to do a big comprehensive fixing of broken links? This would save us the time it takes to handle a bunch of PRs, each of which fixes a few broken links.
+    *   Misty and Zach Arnold will take a look at automating checks and performing regular maintenance
+    *   Please include @masaya_aoyama
+    *   DEFER 6/12 - 6/19
+*   (Zach) Doc sprint at KubeCon Shanghai
+    *   Brad is going 
+        *   Brad: Please at least one other person go too. Zach?
+        *   Jared: Will try, but gotta find out from others. 
+    *   Jared/Andrew: Google still evaluating how many people it will send. Coordinating with Paris. 
+    *   Jberkus: Contributor summit organizer
+*   (Andrew) Update Zach on post-Hugo bug bash. 
+    *   Do we need another one?
+    *   We need to identify ones that Bjorn (@bep) has to address and assign them to him.
+    *   Zach C & Andrew will review how to flag issues for BEP, how others can do likewise
+    *   REPORT 6/12
+*   (Jennifer) Followup on including generated docs in release PRs
+    *   1.10: Generating docs happened at release cycle. 
+    *   1.11: New commands need to have placeholders or breakage happens 
+        *   Found this out with kubeadm
+    *   (Misty) Should we ask the testing team to develop a per-PR test that tries to detect PRs raised by those who are not sig-docs maintainers but modify generated content like reference docs? Another potential test is for a PR which attempts to modify both manual and generated files in the same PR
+    *   AI: Jennifer and Misty will discuss options going forward. 
+*   (Misty) Git class
+    *   Is this still a thing?
+    *   Git Office hours? 
+    *   Decision: Overview of git should be in contributor guide written by Misty. Refer to other resources for in depth knowledge. Misty can answer in-depth questions. 
+*   (Brad) New Hugo code base review/walk through?
+    *   Would like a walkthrough from BEP on design concerns
+    *   +1 from Misty
+    *   Office hours or presentation
+    *   Andrew: Did @bep implement no-index in netlify.toml, which used to be implemented in the Netlify build commands?
+    *   AI: Sync with Andrew offline, follow 
+*   (Brad) Best way for folks to provide feedback on blogs (PRs are of course rejected) 
+*   (Ian) Korean translation status
+    *   Initial pull request: [https://github.com/kubernetes/website/pull/8636](https://github.com/kubernetes/website/pull/8636)
+        *   Can Korean team get review from Docs SIG members?
+    *   AI: Ask Andrew to review - Jared
+*   (Josh Berkus) Looking at reviewing all PR’s since about March on k/k to see if there is a need for Docs
+*   (Zach Arnold) Potentially look at working on the weekends doing docs sprints (for those contributors who cannot do a lot during the week because of jobs.
+    *   Jared: Work-life balance warning :) - If folks from google want to work on a doc sprint outside of normal work hours, let me know and we’ll figure out time management. 
+*   HOLD for 6/19 or 6/26 (Misty) Recommendation for workflows in 1.12
+*   HOLD for 6/19 or 6/26 (Zach) Best practices for SIG Docs workflows
+
+**5/29/2018**
+
+New contributors
+
+
+
+*   Masaya Aoyama
+*   Neha
+*   June Harton
+
+Updates & Reminders
+
+
+
+*   Zach C is back
+*   Rotations for the PR queue?
+    *   this week
+        *   @zcorleissen
+    *   next week
+        *   
+*   Misty is release meister for 1.11 release
+
+Agenda
+
+
+
+*   Steve: Fixing broken links. Would someone have the time/interest to do a big comprehensive fixing of broken links? This would save us the time it takes to handle a bunch of PRs, each of which fixes a few broken links.
+    *   Misty and Zach Arnold will take a look at automating checks and performing regular maintenance
+*   Steve / Jennifer (via Misty): Generated reference docs update
+    *   Several PRs in flight about this and several issues coming in each week
+    *   There is a big PR that needs review. Jennifer / Steve to talk about it offline this week.
+    *   Kubeadm docs updates are problematic as per @jrondeau
+        *   Let’s follow up on June 5 about including generated docs in release PRs
+        *   Zach & Jennifer will chat
+    *   Big docs PRs coming from outside of sig-docs need to be discussed either in a sig-docs meeting (person can add to agenda and not be at the meeting) or in a GH issue before dropping a huge PR
+*   Misty: 1.11 docs updates
+    *   Still 7 1.11 features with unknown docs state
+    *   Deadline for placeholder PRs for features is past (5/25/2018). Pinged all feature PRs to remind.
+    *   Placeholder PRs (or already merged PRs) open for lots of other features
+    *   Rebased release-1.11 last week
+    *   Working with sig-PM to improve feature tracking spreadsheet and add some stats
+*   Misty: `kubernetes/website` security contacts ([#8724](https://github.com/kubernetes/website/issues/8724#issuecomment-392319946))
+    *   Zach C will review by June 5
+*   Misty: GCE content in open source docs
+    *   Style guide guidance for vendor-specific commands in K8s docs
+*   Andrew: update Zach on post-Hugo bug bash. 
+    *   Do we need another one?
+    *   We need to identify ones that Bjorn (@bep) has to address and assign them to him.
+    *   Zach C & Andrew will review how to flag issues for BEP, how others can do likewise
+*   Brad: New Hugo code base  review/walk through?
+    *   Would like a walkthrough from BEP on design concerns
+    *   +1 from Misty
+    *   Office hours or presentation
+    *   Andrew: Did @bep implement no-index in netlify.toml, which used to be implemented in the Netlify build commands?
+*   Brad: Best way for folks to provide feedback on blogs (PRs are of course rejected) 
+*   Andrew: Going to WtD Cincinnati (Aug 18-22, 2018)
+    *   Wants to run a doc sprint for K8s
+
+**5/22/2018**
+
+New contributors
+
+
+
+*   June
+*   Riona - Google, open source
+
+Updates & Reminders
+
+
+
+*   Rotations for the PR queue?
+    *   this week
+        *   @steveperry-53
+        *   @bradtopol
+    *   next week
+        *   Jennifer Rondeau?
+*   Misty is release meister for 1.11 release
+*   Zach C returning next week
+
+Agenda
+
+
+
+*   post-Hugo bug bash
+    *   [Spreadsheet](https://docs.google.com/spreadsheets/d/1MBwcTaDo9tNUOxfemH065v1leghO-pfYM0b2rIiHotM/edit#gid=0)
+    *   any issues that require HTML workaround or direct fix to Blackfriday should be assigned to Bjorn (@bep)
+    *   things that look like a list in a code block are not rendered correctly
+    *   use GitHub Issues, tag w/ "Needs Tech Review", assign/cc @bep
+    *   can use Hugo server for local dev and preview
+        *   need to update docs for how to run local copy of site w/ Hugo server
+*   k/website + prow
+    *   go to k8s community to get support for feature branches and rebasing workflow
+    *   AI: @chenopis to review test-infra [issue](https://github.com/kubernetes/test-infra/issues/8058) and get more sponsors
+*   [DEFERRED 5/29] Reviews on WIP pull requests [Zach]
+*   (Chris Negus) 
+    *   How to fix left nav issues? [Example PR](https://github.com/kubernetes/website/pull/8635)
+    *   Ok to add in changes re: Fedora content -- create PR against `master`
+*   (Jennifer Rondeau)
+    *   Issues discussion upstream
+    *   Generated kubeadm docs
+*   (Andrew Chen)
+    *   break out onboarding to different tiers
+        *   use existing env, like Play w/ Kubernetes
+        *   Minikube
+        *   dev/prod/hosted environment
+    *   Neha to revamp app dev foundational user journey, including Minikube docs
+        *   
+
+**5/15/2018**
+
+New contributors
+
+
+
+*   Neha Dhawan - Google intern with us through July :)
+*   Melissa Anderson - TW @ Digital Ocean
+
+Updates & Reminders
+
+
+
+*   Rotations for the PR queue (Andrew) - Update
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute.
+    *   **We need wranglers!**
+        *   Jennifer can help w/ some PR reviews
+        *   
+*   Misty is release meister for 1.11 release
+    *   [transition gist](https://gist.github.com/zacharysarah/c7dfb90fe1d48762f48d8d6cbb0040b2)
+    *   [previous playbook](https://github.com/kubernetes/sig-release/blob/master/release-process-documentation/documentation-guides/update-release-docs-new.md)
+*   Zach C is on vacation for the next two weeks, returning 5/29
+*   Steve will miss today's meeting. Has been working on Hugo migration issues. For example, moving topics to new directories so they appear in the proper place in the left nav.
+
+Agenda
+
+
+
+*   SIG Docs Summit Recap [Jared, Tom]
+*   Hugo migration bug bash
+    *   Fri - Jennifer, Andrew, Misty (needs admin priv), Brad
+*   [DEFERRED 5/29] Reviews on WIP pull requests [Zach]
+    *   
+*   PR wrangling
+    *   Large percentage of PRs on hold
+        *   We may not want to merge many of these
+        *   Need style guidance
+        *   Need a way to address them so they don't bloat the queue
+    *   Missing CLAs
+        *   Misty working on improving contributor docs, which should improve this.
+        *   Some may not be sure if they can sign on behalf of company or whether they should sign individually instead.
+        *   If they explicitly say they can't CLA then we should close the PR.
+    *   **Need a policy to close stale PRs**
+        *   Ping them, if we don't hear back within **one month**, close the PR.
+*   Kubernetes governance [Andrew]
+    *   automation overreach
+    *   how do we escalate when we run into issues?
+        *   e.g. non-SIG Docs maintainer was able to merge because of Kubernetes org admin?
+        *   prow policies applied w/o our knowledge
+    *   Andrew to:
+        *   talk to Paris
+        *   ask at Community meeting
+        *   ask Steering Committee
+*   (May 15): How did a PodSecurityPolicy change break our test build last week (Jennifer)
+    *   (THANK YOU TO QIMING for fixing it!!: [https://github.com/kubernetes/website/pull/8086](https://github.com/kubernetes/website/pull/8086))
+    *   Revisit documentation options that don't appear in generated docs. See [https://github.com/kubernetes/website/pull/7887](https://github.com/kubernetes/website/pull/7887) and [https://github.com/kubernetes/website/issues/8280](https://github.com/kubernetes/website/issues/8280)
+    *   DEFERRED to 15 May - Docs tests: no consistent ownership
+    *   Automation governance discussion
+    *   **Need to add task to release meister process: update release we are testing against to be current release not master**
+        *   File to update is [https://github.com/kubernetes/website/blob/master/test/examples_test.go](https://github.com/kubernetes/website/blob/master/test/examples_test.go)
+        *   High-level additional requirements: check release/release notes for changes to API resources that the tests call.
+
+**5/1/2018**
+
+New contributors
+
+
+
+*   nope
+
+Updates & Reminders
+
+
+
+*   **No weekly meeting next week**, 5/8 (Write the Docs)
+*   There WILL BE a Kubernetes session during the Write the Docs Writing Day (May 6, Portland). Andrew and Jennifer will run it, with Misty and Steve to provide their special expertises.
+*   Rotations for the PR queue (Andrew) - Update
+    *   Jennifer Rondeau - 4/30 - 5/6
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute.
+    *   Who’s up next? We’ll need coverage during WTD!
+*   **SIG Docs Summit: Wednesday, May 9, Portland**
+    *   [https://github.com/kubernetes/website/issues/8116](https://github.com/kubernetes/website/issues/8116) 
+
+Agenda
+
+
+
+*   5/1: Chenopis will run this meeting.
+    *   Jared and Zach will send update on Docs Sprint / Contrib Summit. 
+*   Write the Docs @ Portland
+    *   Sprint instructions: [https://bit.ly/2rcZ3YU](https://bit.ly/2rcZ3YU)
+    *   [Hugo migration issues](https://github.com/kubernetes/website/milestone/20) from KubeCon docs sprint need to be triaged.
+    *   Hugo preview: [https://hugo-migration.docs.kubernetes.io](https://hugo-migration.docs.kubernetes.io)
+    *   Migration script will be run again before final migration, so we can continue working and merging content like normal.
+    *   **Decision: avoid Hugo migration issues for doc sprint.**
+    *   **Jennifer will get the donuts!**
+    *   **Issues for doc sprint: [https://github.com/kubernetes/website/projects/8](https://github.com/kubernetes/website/projects/8)**
+    *   **Andrew will dump issues into assignment [spreadsheet](https://bit.ly/2KrwPT7).**
+*   PR wrangling
+    *   Large percentage of PRs on hold
+    *   Missing CLAs
+        *   Misty working on improving contributor docs, which should improve this.
+        *   Some may not be sure if they can sign on behalf of company or whether they should sign individually instead.
+    *   **Need a policy to close stale PRs**
+*   [Jennifer] Do we want to standardize on how to document options that don’t appear in generated docs? (Related discussion: should they do so if they’re deprecated). See [https://github.com/kubernetes/website/pull/7887](https://github.com/kubernetes/website/pull/7887) and [https://github.com/kubernetes/website/issues/8280](https://github.com/kubernetes/website/issues/8280)
+    *   Is a bug and should be fixed in 1.10. Need to verify.
+    *   Need to understand why this is happening.
+        *   Followup on 8280: see [https://github.com/kubernetes/kubernetes/blob/master/pkg/kubeapiserver/options/admission.go#L67ff](https://github.com/kubernetes/kubernetes/blob/master/pkg/kubeapiserver/options/admission.go#L67ff). New flag is not properly documented. See especially l75. (Still need to dive after where flag is defined)
+    *   Need to coordinate w/ upstream efforts to fix it.
+*   **Kubernetes version needs to be updated in the test code for each release as part of Docs Lead process.**
+*   Kubernetes governance
+    *   automation overreach
+    *   Changing automatically protecting branches: [https://github.com/kubernetes/test-infra/pull/7900](https://github.com/kubernetes/test-infra/pull/7900)
+    *   chenopis@
+        *   Figure out chain of escalation
+        *   Find champion on steering committee
+        *   Work w/ governance to establish policy
+*   Refactor Minikube docs [[issue #6339](https://github.com/kubernetes/website/issues/6339)]
+    *   Jennifer and Misty team up!
+*   DEFERRED (May 15): How did a PodSecurityPolicy change break our test build last week (Jennifer)
+    *   (THANK YOU TO QIMING for fixing it!!: [https://github.com/kubernetes/website/pull/8086](https://github.com/kubernetes/website/pull/8086))
+    *   Revisit documentation options that don't appear in generated docs. See [https://github.com/kubernetes/website/pull/7887](https://github.com/kubernetes/website/pull/7887) and [https://github.com/kubernetes/website/issues/8280](https://github.com/kubernetes/website/issues/8280)
+    *   DEFERRED to 15 May - Docs tests: no consistent ownership
+    *   Automation governance discussion
+
+**4/24/2018**
+
+New contributors
+
+
+
+*   Jason Van Brackel - Rancher - Member of Sig Windows
+*   Zach Arnold - here to help out with release for 1.11 
+
+Updates & Reminders
+
+
+
+*   Rotations for the PR queue (Andrew) - Update
+    *   Andrew’s turn this week!
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute.
+    *   Andrew Chen - 4/23 - 4/29 (Andrew taking this since Joe covered for him) 
+    *   Jennifer Rondeau - 4/30 - 5/6
+*   SIG Docs Summit: Wednesday, May 9, Portland
+    *   [https://github.com/kubernetes/website/issues/8116](https://github.com/kubernetes/website/issues/8116) 
+
+Agenda
+
+
+
+*   Jennifer and Joe both send apologies for today’s meeting
+*   Next two weekly meetings: what to do?
+    *   5/1: Jared, Brad, and Zach will both be at KubeCon
+        *   Chenopis will run this meeting.
+        *   Jared and Zach will send update on Docs Sprint / Contrib Summit. 
+    *   5/8: Many folks will be at Write the Docs
+        *   Cancel this meeting since the Docs Meetup is the same week.
+*   ANNOUNCEMENT: There WILL BE a Kubernetes session during the Write the Docs Writing Day (May 6, Portland). Andrew and Jennifer will run it, with Misty and Steve to provide their special expertises.
+*   Paris agenda slot 
+    *   Contributor Experience Deep Dive for Contrib Summit @ Kubecon
+    *   Want to add new facet to the contrib / developer guide on api conventions
+    *   Want to do a mini doc sprint 
+    *   35 minutes
+    *   Suggestions:
+        *   Do a demo
+        *   Brainstorming session?
+        *   Breakout session afterwards?
+*   Git tech talk (Misty)
+    *   Let’s do a git tech talk for best practices! (June)
+    *   Considering doing office hours.
+    *   Show people how to set up their environment (TBD)
+    *   Available for one-off Git questions in Slack as time permits
+*   Zach gives an update on Hugo?
+    *   Very close to “flipping the switch” in Hugo. 
+    *   Syncing with chinese translation team to give them the heads up.
+    *   Aiming for Thursday - 4/26
+*   DEFERRED (June 1): How did a PodSecurityPolicy change break our test build last week (Jennifer)
+    *   (THANK YOU TO QIMING for fixing it!!: [https://github.com/kubernetes/website/pull/8086](https://github.com/kubernetes/website/pull/8086))
+    *   Andrew will approach test-infra for notification about upstream changes
+    *   DEFERRED to 1 June - Docs tests: no consistent ownership
+
+**4/17/2018**
+
+New contributors
+
+
+
+*   
+
+Updates & Reminders
+
+
+
+*   Rotations for the PR queue (Andrew) - Update
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute.
+    *   Brad Topol - 4/16 - 4/22
+    *   Andrew Chen - 4/23 - 4/29 (Andrew taking this since Joe covered for him) 
+    *   Jennifer Rondeau - 4/30 - 5/6
+
+Agenda
+
+
+
+*   SIG Docs Summit: Wednesday, May 9, Portland
+    *   [https://github.com/kubernetes/website/issues/8116](https://github.com/kubernetes/website/issues/8116) 
+    *   Attendees: Brad, Zach, 
+*   A few notes from PR wrangling (heckj)
+    *   Updated the PR wrangler gist
+    *   More changes starting to appear for generated content - closing politely and trying to point people to the relevant source to update upstream
+        *   Example: [https://github.com/kubernetes/website/pull/8108](https://github.com/kubernetes/website/pull/8108)
+*   How did a PodSecurityPolicy change break our test build last week (Jennifer)
+    *   (THANK YOU TO QIMING for fixing it!!: [https://github.com/kubernetes/website/pull/8086](https://github.com/kubernetes/website/pull/8086))
+    *   Andrew will approach test-infra for notification about upstream changes
+    *   DEFERRED to 1 June - Docs tests: no consistent ownership
+*   Release-1.10 branch and merge conflicts (Zach)
+    *   Make sure you aren’t committing conflict markers
+    *   Zach will work with Misty to hard reset release-1.10 to master
+*   Git tech talk (Misty)
+    *   Let’s do a git tech talk for best practices! (June)
+*   External content (Rajie)
+    *   What should we do with useful external content?
+        *   [https://eyskens.me/building-a-kubernetes-ingress-controller/](https://eyskens.me/building-a-kubernetes-ingress-controller/)
+        *   Link to it but don’t host
+*   Summit: Define K8s content strategy very clearly
+
+Reference:
+
+
+
+*   Hugo migration meeting notes
+    *   Early discussion summary: [https://gist.github.com/heckj/2129560e68c6104690dfa6bf9099c3e9](https://gist.github.com/heckj/2129560e68c6104690dfa6bf9099c3e9)
+    *   16 apr 2018 progress/sync meeting [https://gist.github.com/heckj/ab20589283e2029f0a6d928173ce1767](https://gist.github.com/heckj/ab20589283e2029f0a6d928173ce1767)
+
+**4/10/2018**
+
+New contributors
+
+
+
+*   Everything old is new again. 
+
+Updates & Reminders
+
+
+
+*   Rotations for the PR queue (Andrew) - Update
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute.
+    *   Joe Heck - 4/10 - 4/15
+    *   Brad Topol - 4/16 - 4/22
+    *   Joe Heck - 4/23 - 4/29 (Andrew might take this one) 
+    *   Jennifer Rondeau - 4/30 - 5/6
+*   Reminder: no cookie licking!
+
+Agenda
+
+
+
+*   PR/Style Guide suggestions (rajie)
+    *   Accessibility guidelines: [https://github.com/kubernetes/website/pull/7991](https://github.com/kubernetes/website/pull/7991) Reference: [https://www.w3.org/WAI/intro/wcag](https://www.w3.org/WAI/intro/wcag)
+    *   Capitalization/usage additions: [https://github.com/kubernetes/website/pull/8017](https://github.com/kubernetes/website/pull/8017)
+    *   Chatbot?
+        *   Do some user acceptance testing for search at Write the Docs?
+*   Hugo Migration plan/update (zach)
+    *   Page weighting: how will it be done in Hugo?
+*   Need some cross-browser CSS help! (heckj)
+    *   Pull-down nav rendering issue (safari only): [https://github.com/kubernetes/website/issues/7801](https://github.com/kubernetes/website/issues/7801)
+
+**4/3/2018**
+
+New contributors
+
+
+
+*   Marcus Heese (@mheese) 
+
+Updates & Reminders
+
+
+
+*   Migrate kubernetes.io from Jekyll to Hugo ([Discussion Doc](https://docs.google.com/document/d/1XAmCSueuhU6YOvO2ensdiJX63jVapr9XijwY3HlENl4/edit#)) (Jared B, Zach)
+    *   Rescheduled for 4/4
+*   Master branch strategy (Andrew, Steve, Jennifer) [[slides](https://docs.google.com/presentation/d/1OIs-Hdq7ZaVyuwSzzCw-ww3o9rSn5EMEpy5QvpF3Oik/edit?usp=sharing)]
+    *   Today (4/3) at 1pm
+        *   Add Nick Chase, Tall Tom
+*   Rotations for the PR queue (Andrew) - Update
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute.
+    *   Steve Perry - 4/2 - 4/8
+    *   Andrew Chen - 4/9 - 4/15
+    *   Brad Topol - 4/16 - 4/22
+    *   Joe Heck - 4/23 - 4/29
+
+Agenda
+
+
+
+*   New Provider Hosting (Chris Hoge) (with impact on docs for providers)
+    *   [https://github.com/kubernetes/community/pull/1942](https://github.com/kubernetes/community/pull/1942)
+    *   Zach will set up a working meeting, invite: Joe Heck, Andrew, Steve
+*   API group naming (@mheese)
+    *   Steve will republish with long names 
+    *   Nobody present understood why there currently are short names in the reference docs
+*   Issues: No cookie licking Good First Issues! (Zach): [https://github.com/kubernetes/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22](https://github.com/kubernetes/website/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22)
+    *   If you don’t have a PR after 3 days on a Good First Issue then it is no longer yours. 
+    *   Mark work in progress PRs as “WIP” in the title of the PR. 
+*   Serving Kubernetes fonts from a server other than Google
+    *   Google font serving slows down China web load times
+    *   Need an alternative font server
+        *   For example: https://landscape.cncf.io/ has fonts served from elsewhere
+    *   Suggestion: 
+        *   Serve fonts directly from kubernetes.io
+        *   Fallback font that users have locally on their machine. 
+        *   Zach will file an issue. (Arial for ALL!) 
+*   Considering improvements to CI/CD (Zach)
+    *   Link checker
+    *   Linter
+    *   Proposal:
+        *   Check after build is done, like the netlify check or travis. 
+        *   Options: Xenu link checker, linklint, w3c checker (very slow)
+*   Proposing Korean documentation translation (@ianychoi): \
+[https://groups.google.com/forum/#!topic/kubernetes-sig-docs/akgMNB_pHXU](https://groups.google.com/forum/#!topic/kubernetes-sig-docs/akgMNB_pHXU) 
+    *   Get the Chinese translation working first before we give guidance to Korean team
+*   SIG Docs contributor process (Andrew / Jared) 
+    *   Writing out how to become a member of the SIG Docs org and a site maintainer. 
+    *   Reorging the docs contributor content / style guide / doc processes content.
+    *   This page needs love/improvements/context ([https://kubernetes.io/docs/home/contribute/participating/](https://kubernetes.io/docs/home/contribute/participating/))
+    *   Joe, Steve, Rajie, Misty, Tall Tom, Jennifer
+
+Add results as a single point of truth to community site/resources
+
+**3/27/2018**
+
+New contributors
+
+
+
+*   Rajie (hi officially!)
+*   Misty Stanley-Jones (hello!)
+
+Agenda
+
+
+
+*   1.10 update (jrondeau, nickchase)
+    *   Posted yesterday!
+    *   Standing items:
+        *   Steve is taking care of generated docs
+    *   Some maintenance still required:
+        *   1.9 deprecation banner
+    *   Documentation for release process needs more love
+    *   Release notes: Andrew will help import 
+*   Migrate kubernetes.io from Jekyll to Hugo ([Discussion Doc](https://docs.google.com/document/d/1XAmCSueuhU6YOvO2ensdiJX63jVapr9XijwY3HlENl4/edit#)) (Jared B, Zach)
+    *   Check in on initial assessment tomorrow
+    *   Zach will track overall process (in a GH issue)
+    *   Paris: community guidelines for rolling out big changes: SIG contribex charter
+*   Rotations for the PR queue (Andrew) - Update
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute.
+    *   Jennifer Rondeau - 3/26 - 4/1
+        *   PRs frozen for 1.10 release day, feel free to remove /holds
+    *   Brad Topol - 4/1
+    *   Steve Perry - 4/2 - 4/8
+    *   Andrew Chen - 4/9 - 4/15
+    *   Brad Topol - 4/16 - 4/22
+    *   Joe Heck - 4/23 - 4/29
+*   Master branch strategy (Andrew, Steve, Jennifer) [[slides](https://docs.google.com/presentation/d/1OIs-Hdq7ZaVyuwSzzCw-ww3o9rSn5EMEpy5QvpF3Oik/edit?usp=sharing)]
+    *   Changing SIG Docs branch workflow to match the rest of K8s orgs/SIG workflows
+    *   This will be a greatly complex project; deserves full, dedicated treatment in Q3
+    *   Misty: let’s consider alternate workflows to optimize how we do things
+    *   Work with Paris to present migration proposal to community (meeting)
+    *   Meeting to talk about branch strategy
+        *   Andrew, Steve, Misty, Jennifer, Zach, Jared, Joe, Brad
+*   New Provider Hosting (Chris) (with impact on docs for providers)
+    *   [https://github.com/kubernetes/community/pull/1942](https://github.com/kubernetes/community/pull/1942)
+    *   Follow up on 3/27 after reviewing PR
+    *   Migrated current cloud providers to new repositories.
+    *   Followup next week. 
+*   Linter? (Zach)
+*   Offline docs (Zach)
+
+**3/20/2018**
+
+New contributors
+
+
+
+*   Jmosco - worked on a few PRs already
+
+Agenda
+
+
+
+*   1.10 update (jrondeau)
+    *   Reverting an Alpha feature
+    *   Content looking good, go/no go signal on Thursday for Monday release
+*   Front loading docs in the release process (calebmiles/chenopis) 
+    *   KEP process: how can we use it to front load early quality drafts of release notes?
+    *   Pilot example of KEP for docs: [https://github.com/kubernetes/community/blob/master/keps/sig-cluster-lifecycle/0003-cluster-api.md](https://github.com/kubernetes/community/blob/master/keps/sig-cluster-lifecycle/0003-cluster-api.md)
+    *   Question from Zach: Does this fix early contribution in the way we hope?
+    *   Question from Steve: is this across all sig-groups for 1.11? Does this replace PRs for release notes?
+    *   Andrew/Caleb: it’s a test-drive
+*   New/ongoing project to improve release note content at the source (Jennifer). See [new issue for discussion ](https://github.com/kubernetes/website/issues/7791)
+*   Migrate kubernetes.io from Jekyll to Hugo ([Discussion Doc](https://docs.google.com/document/d/1XAmCSueuhU6YOvO2ensdiJX63jVapr9XijwY3HlENl4/edit#)) (Jared B, Zach)
+    *   Bjorn Erik Pedersen: [http://bep.is/](http://bep.is/)
+    *   PR Jubilee (what else to call it?): 
+        *   PRs still open at merge may cause merge conflicts
+        *   Need to merge/close all PRs in progress prior to merge
+    *   Initial stage: two “days” of work for initial assessment, resulting in a PR
+    *   SIG Docs maintainers: input/review needed on upcoming migration PRs.
+        *   Look for changes to site tooling
+    *   Zach will track overall process (in a GH issue)
+    *   Paris: community guidelines for rolling out big changes: SIG contribex charter
+*   Rotations for the PR queue (Andrew) - Update
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute.
+    *   Steve Perry (last week) Lots of Tech Review Needed and Docs Open Issues.
+    *   Zach Corleissen - 3/19 - 3/25 (Currently at 65 PRs, check your queues)
+    *   Jennifer Rondeau - 3/26 - 4/1
+    *   Andrew Chen - 4/2 - 4/8
+*   Next meeting 3/27: Let’s revisit the master branch strategy (Andrew, Steve, Jennifer)
+*   New Provider Hosting (Chris) (with impact on docs for providers)
+    *   [https://github.com/kubernetes/community/pull/1942](https://github.com/kubernetes/community/pull/1942)
+    *   Follow up on 3/27 after reviewing PR
+*   Steve will reopen issues related to the migration from user-guides to tasks, tutorials, and concepts.
+*   Homonym pun (Jennifer)
+
+**3/13/2018**
+
+New contributors
+
+
+
+*   Tom van Waardhuizen (Google)
+*   Rajie Kodhandapani
+
+Agenda
+
+
+
+*   1.10 update (jrondeau)
+    *   According to past docs wranglers, we’re in unusually good shape. A few stragglers, will be merged today or tomorrow
+    *   Jennifer might need help with generated docs; already alerted Steve
+*   [Spell-checking PR](https://github.com/kubernetes/website/pull/7691): take a different approach? (Steve, Jennifer)
+    *   There are already some excellent spell checkers out there. 
+    *   Long explanation and rationale for rejection in the PR comment 
+    *   Make sure note about local spellchecker gets added to contrib guidelines
+*   DEFERRED (1 week, 3/20, depends on state of release) Reviewing release note copy: possibly rotate reviewers from sig-docs throughout release cycle, the way we’ve started doing for rotating docs repo PRs? (Jennifer)
+*   Future of [https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html](https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html) (Ben Hall) - Update? 
+    *   UPDATE from Ben: “we need to do it via a HTML or JavaScript tag instead of any github based approach”, “Should have it tested and a PR ready for next week”
+    *   Related issue: [https://github.com/kubernetes/website/issues/7506](https://github.com/kubernetes/website/issues/7506)
+    *   Yes, redirect plz. 
+    *   AI: Ben will submit a PR, Steve will review. 
+*   Brad Topol for SIG Docs maintainer (Zach)
+    *   Approved! Hoorays! 
+*   New team: kubernetes-blog-maintainers (Zach)
+    *   Part of getting ready for blog migration
+    *   Sarah Conway, Bob Hrdinsky, others who had been updating the blog. 
+*   Migrate kubernetes.io from Jekyll to Hugo ([Discussion Doc](https://docs.google.com/document/d/1XAmCSueuhU6YOvO2ensdiJX63jVapr9XijwY3HlENl4/edit#)) (Jared B, Zach)
+    *   We are proceeding. Hoorays!
+    *   Working with a contractor. Bjorn Eric Pederson
+    *   Aiming to schedule start for first week of April (after 1.10 goes out the door). 
+    *   Estimated to take 3-4 weeks
+        *   Expect a doc freeze at some point in the migration process
+    *   Migration work should be invisible to contributors/users
+    *   What you have to do differently: nothing (hopefully)
+*   Rotations for the PR queue (Andrew) - Update
+    *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+    *   Every week, someone volunteers as tribute. 
+    *   Steve Perry - 3/12 - 3/18
+    *   Zach Corleissen - 3/19 - 3/25
+    *   Jennifer Rondeau - 3/26 - 4/1
+    *   Andrew Chen - 4/2 - 4/8
+*   Docs proposal: Move away from hosting Operating System/platform-specific and link to it instead [Zach]
+    *   Highly out of date: [https://kubernetes.io/docs/setup/pick-right-solution/](https://kubernetes.io/docs/setup/pick-right-solution/)
+        *   Cloud Provider working group: all in favor
+        *   Impact assessment: [https://github.com/kubernetes/website/pull/7501#issuecomment-371342046](https://github.com/kubernetes/website/pull/7501#issuecomment-371342046) (thanks Philip Mallory!)
+        *   PR in progress: [https://github.com/kubernetes/website/pull/7501](https://github.com/kubernetes/website/pull/7501)
+*   Twitter handles for Kube Doc folks [Brad]
+    *   Go for it: offline discussion about ownership and best practices
+        *   Jennifer Rondeau (@Bradamante)
+*   K8s site metrics (Andrew, Joe)
+    *   Process for determining/adding metrics is just starting
+
+**3/6/2018**
+
+New contributors
+
+
+
+*   
+
+Agenda
+
+
+
+*   1.10 update (heckj, jrondeau)
+    *   
+*   Future of [https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html](https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html) (Ben Hall) - Update? [DEFERRED 1 week]
+    *   Related issue: [https://github.com/kubernetes/website/issues/7506](https://github.com/kubernetes/website/issues/7506)
+    *   Yes, redirect plz. 
+    *   AI: Ben will submit a PR, Steve will review. 
+*   Migrate kubernetes.io from Jekyll to Hugo ([Discussion Doc](https://docs.google.com/document/d/1XAmCSueuhU6YOvO2ensdiJX63jVapr9XijwY3HlENl4/edit#)) (Jared B, Zach)
+    *   
+*   Rotations for the PR queue (Andrew) - Update
+    *   Week 1: Joe, what did you learn?
+    *   Suggested process:
+        *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+        *   Every week, someone volunteers as tribute. 
+        *   Joe Heck - This week 
+        *   Brad Topol - 3/5 - 3/11
+        *   Steve Perry - 3/12 - 3/18
+        *   Zach Corleissen - 3/19 - 3/25
+        *   Jennifer Rondeau - 3/26 - 4/1
+        *   Andrew Chen - 4/2 - 4/8
+*   Docs proposal: Move away from hosting Operating System/platform-specific and link to it instead [Zach]
+    *   Highly out of date: [https://kubernetes.io/docs/setup/pick-right-solution/](https://kubernetes.io/docs/setup/pick-right-solution/)
+        *   Indicative of larger problems with freshness/staleness and maintaining dual source
+        *   Better to link to canonical docs from an OS/platform’s own community
+        *   sig/open-stack lead agrees: externalize docs
+        *   Discuss this at the cloud provider working meeting (when is that? Zach will find out!)
+        *   ZACH: Action item to assess externalizing impact
+    *   PR in progress: [https://github.com/kubernetes/website/pull/7501](https://github.com/kubernetes/website/pull/7501)
+*   First annual SIG Docs Summit: May 9, Portland, CENTRL Office
+    *   Day after Write the Docs in Portland
+    *   Attendees?
+        *   Zach Corleissen
+        *   Jared Bhatti
+        *   Jennifer Rondeau
+        *   Chris Hoge
+        *   Andrew Chen
+        *   Steve Perry
+        *   Brad Topol
+        *   Stephen Augustus
+*   Twitter handles for Kube Doc folks [Brad]
+    *   ZACH: Find out CNCF/LF policy (if any) about Twitter accounts for individual K8s SIGs
+
+How many folks on the call have a twitter handle that they use with some frequency? When I tweet doc related information tweets I would like to include those who are active to help amplify our messages. For example, last night I tweeted out Joe Heck’s review document.  I got lots of interest. Please share your twitter handles!
+
+@bradamante
+
+@stephenaugustus
+
+@bradtopol 
+
+@zachorsarah
+
+For next meeting: 
+
+
+
+*   Update on I18n support (Chenopis) (next week, 3/13)
+
+**3/6/2018**
+
+New contributors
+
+
+
+*   None this week :-(
+
+Agenda
+
+
+
+*   1.10 update (heckj, jrondeau)
+    *   4 features without doc information; looks as though 1 may not make it into the release, and 1 possibly doesn’t need docs. Tracking 2X/day at this point
+    *   Some PRs that should have been submitted to master were submitted to 1.10 branch. This has made things a bit more challenging to track. Ideas for solutions? Add to review guidelines? Promote branch PR practices better?
+*   Future of [https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html](https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html) (Ben Hall) - Update? [DEFERRED]
+    *   Related issue: [https://github.com/kubernetes/website/issues/7506](https://github.com/kubernetes/website/issues/7506)
+    *   Yes, redirect plz. 
+    *   AI: Ben will submit a PR, Steve will review. 
+*   Migrate kubernetes.io from Jekyll to Hugo ([Discussion Doc](https://docs.google.com/document/d/1XAmCSueuhU6YOvO2ensdiJX63jVapr9XijwY3HlENl4/edit#)) (Jared B, Zach)
+    *   
+*   Rotations for the PR queue (Andrew) - Update
+    *   Week 1: Joe, what did you learn?
+    *   Suggested process:
+        *   PR Wrangler guidelines: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+        *   Every week, someone volunteers as tribute. 
+        *   Joe Heck - This week 
+        *   Brad Topol - 3/5 - 3/11
+        *   Steve Perry - 3/12 - 3/18
+        *   Zach Corleissen - 3/19 - 3/25
+        *   Jennifer Rondeau - 3/26 - 4/1
+        *   Andrew Chen - 4/2 - 4/8
+*   Docs proposal: Move away from hosting Operating System/platform-specific and link to it instead [Zach]
+    *   Highly out of date: [https://kubernetes.io/docs/setup/pick-right-solution/](https://kubernetes.io/docs/setup/pick-right-solution/)
+        *   Indicative of larger problems with freshness/staleness and maintaining dual source
+        *   Better to link to canonical docs from an OS/platform’s own community
+        *   sig/open-stack lead agrees: externalize docs
+        *   Discuss this at the cloud provider working meeting (when is that? Zach will find out!)
+        *   ZACH: Action item to assess externalizing impact
+    *   PR in progress: [https://github.com/kubernetes/website/pull/7501](https://github.com/kubernetes/website/pull/7501)
+    *   Related to Update CoreOS install docs (Stephen Augustus, following)
+*    [Tentative] Update CoreOS install docs [Stephen Augustus]
+    *   [https://github.com/kubernetes/website/issues/6859](https://github.com/kubernetes/website/issues/6859)
+*   First annual SIG Docs Summit: May 9, Portland, CENTRL Office
+    *   Day after Write the Docs in Portland
+    *   Attendees?
+        *   Zach Corleissen
+        *   Jared Bhatti
+        *   Jennifer Rondeau
+        *   Chris Hoge
+        *   Andrew Chen
+        *   Steve Perry
+        *   Brad Topol
+        *   Stephen Augustus
+*   Twitter handles for Kube Doc folks [Brad]
+    *   ZACH: Find out CNCF/LF policy (if any) about Twitter accounts for individual K8s SIGs
+
+How many folks on the call have a twitter handle that they use with some frequency? When I tweet doc related information tweets I would like to include those who are active to help amplify our messages. For example, last night I tweeted out Joe Heck’s review document.  I got lots of interest. Please share your twitter handles!
+
+@bradamante
+
+@stephenaugustus
+
+@bradtopol 
+
+@zachorsarah
+
+For next meeting: 
+
+
+
+*   Update on I18n support (Chenopis) (next week, 3/13)
+
+**2/27/2018**
+
+**Note: **Jared Bhatti leads this meeting (Zach is traveling)
+
+New contributors
+
+
+
+*   Philip Mallory - Google, Kubernetes Engine
+*   Abraham - IBM, lurking :)
+
+Agenda
+
+
+
+*   1.10 update (heckj, jrondeau)
+    *   Tagging PRs related to the upcoming release
+    *   Most have been merged into the 1.10 branch
+*   Updating interactive tutorials [Ben Hall] - Update? (heckj, stevepe)
+    *   All done. Hooray!
+    *   All using the new minikube. Much improved. Thank you!
+*   Future of [https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html](https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html) (Ben Hall)
+    *   Related issue: [https://github.com/kubernetes/website/issues/7506](https://github.com/kubernetes/website/issues/7506)
+    *   Yes, redirect plz. 
+    *   AI: Ben will submit a PR, Steve will review. 
+*   Migrate kubernetes.io from Jekyll to Hugo ([Discussion Doc](https://docs.google.com/document/d/1XAmCSueuhU6YOvO2ensdiJX63jVapr9XijwY3HlENl4/edit#))
+    *   Will have update next week. 
+*   Rotations for the PR queue (Andrew)
+    *   PR are going up. Suggest assigning a “PR Wrangler” for the week
+    *   Keeping it <50 PRs
+    *   Time to first response/closing - actually doing pretty good. 
+    *   Suggested process:
+        *   Every week, someone volunteers as tribute. 
+        *   Joe Heck - This week 
+        *   Brad Topol  - Next week
+        *   Steve Perry - Third week
+    *   Heckj wrote up a "how I do this.." for Brad: [https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17](https://gist.github.com/heckj/50df12da789ee8402a937be83a88ef17)
+*   First annual SIG Docs Summit: May 9, Portland, CENTRL Office
+    *   Day after Write the Docs in Portland
+    *   Attendees?
+        *   Zach Corleissen
+        *   Jared Bhatti
+        *   Jennifer Rondeau
+        *   Chris Hoge
+        *   Andrew Chen
+        *   Steve Perry
+        *   Brad Topol
+*   [Tentative] Update CoreOS install docs [Stephen Augustus]
+    *   [https://github.com/kubernetes/website/issues/6859](https://github.com/kubernetes/website/issues/6859)
+
+For next meeting: 
+
+
+
+*   Update on Hugo (jaredb, zach)
+*   Update on I18n support (Chenopis) (in 2 weeks)
+
+**2/20/2018**
+
+**Note: **Jared Bhatti leads this meeting (Zach is running a doc sprint at IBM Index)
+
+New contributors
+
+
+
+*   Chris Hoge - Sig Open-Stack
+
+Agenda
+
+
+
+*   Updating interactive tutorials [Ben Hall]
+    *   [https://github.com/kubernetes/website/issues/7240#issuecomment-365327820](https://github.com/kubernetes/website/issues/7240#issuecomment-365327820)
+    *   Steve: Let's talk about both locations:
+        *   [https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html](https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html)
+        *   [https://kubernetes.io/docs/tutorials/kubernetes-basics/](https://kubernetes.io/docs/tutorials/kubernetes-basics/)
+        *   (Heckj: there’s a 3rd location for the hosted content: [https://github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios](https://github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios))
+*   [Ilya] status update on getting started guides (~1min) ([kubernetes/website#7278](https://github.com/kubernetes/website/issues/7278))
+*   Migrate kubernetes.io from Jekyll to Hugo
+    *   [Discussion Doc](https://docs.google.com/document/d/1XAmCSueuhU6YOvO2ensdiJX63jVapr9XijwY3HlENl4/edit#)
+*   First annual SIG Docs Summit: May 9, Portland, CENTRL Office
+    *   Day after Write the Docs in Portland
+    *   Attendees?
+        *   Zach Corleissen
+        *   Jared Bhatti
+        *   Jennifer Rondeau
+        *   Chris Hoge
+        *   Andrew Chen
+        *   Steve Perry
+        *   
+*   [Tentative] Update CoreOS install docs [Stephen Augustus]
+    *   [https://github.com/kubernetes/website/issues/6859](https://github.com/kubernetes/website/issues/6859)
+
+For next meeting: 
+
+
+
+*   Rotations for the PR queue (Andrew)
+*   Future of [https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html](https://kubernetesbootcamp.github.io/kubernetes-bootcamp/index.html) (Ben Hall)
+
+**2/13/2018**
+
+New attendees?
+
+
+
+*   None
+
+Agenda items
+
+
+
+*   Consensus/Guidance for issue #7232([https://github.com/kubernetes/website/pull/7232](https://github.com/kubernetes/website/pull/7232)) - how to represent API changes with different versions (heckj, Qiming)
+    *   related PR: [https://github.com/kubernetes/website/pull/7385](https://github.com/kubernetes/website/pull/7385)
+    *   a) changing the front-matter of the markdown file per Steve
+    *   b) using the {% feature state%} jekyll add-in - [https://kubernetes.io/docs/home/contribute/includes/#feature-state-code](https://kubernetes.io/docs/home/contribute/includes/#feature-state-code)
+    *   c) comments in YAML about the min version required (getting common, but not consistent)
+        *   What do we do about referencing earlier versions? Do we include a comment with what k8s.io v.prior used?
+    *   Joe: Send an email to approvers: check version information, make sure that include statements are included, that samples are updated, that version comments in samples are removed
+    *   Steve: No blind updates to YAML files; carefully review for versioning
+*   Follow up on responsiveness, roles & responsibilities for reviewers and maintainers (heckj)
+    *   PR: [https://github.com/kubernetes/website/pull/7133](https://github.com/kubernetes/website/pull/7133)
+        *   Comments due by Thursday, 2/15
+    *   For example, what expectations do we have & should we have of a reviewer or approver in handling PRs, issues, etc.
+    *   Clearer reviewer guidelines
+        *   Set an SLO for when we’ll respond to PRs: 1 week
+        *   Do we need to codify standards for reviewers: for example, don’t merge a PR assigned to someone else? Is our current method sustainable?
+    *   As we're talking about SLO for getting attention on PRs, Paris shared this view of how we're doing today:
+        *   [https://k8s.devstats.cncf.io/d/000000013/first-non-author-activity?orgId=1&var-period=w&var-repogroup_name=Docs&var-repogroup=docs&from=1454786880740&to=1516735680740](https://k8s.devstats.cncf.io/d/000000013/first-non-author-activity?orgId=1&var-period=w&var-repogroup_name=Docs&var-repogroup=docs&from=1454786880740&to=1516735680740)
+    *   
+
+**2/6/2018**
+
+New attendees?
+
+
+
+*   Kris Nova
+*   PMallory
+*   Ivan Font
+*   Matt Dorn
+
+Follow-ups from last meeting (10 minutes max): 
+
+
+
+*   CNCF is hiring! (Zach)
+*   Update/revisit style guide. [Issue 7030](https://github.com/kubernetes/website/issues/7030) (Steve)
+    *   Revisit this next week (2/6) to talk about whether it would be better to adapt an existing style guide (for example, Google Cloud if they have one) or continue creating from scratch
+    *   Keep the existing style guide, reorganize its contents, promote its visibility better
+*   Repo team cleanup (Zach)
+    *   Cleanup for individual contributor permissions (Steve)
+    *   Cleanup for teams: add reviewers and approvers teams (Zach)
+        *   Nominating Brad Topol (@bradtopol) as a reviewer
+    *   When changing OWNERS file, change OWNERS_ALIASES as well and vice versa
+
+Agenda items
+
+
+
+*   Approval workflow
+    *   We may need to adjust our review commands from /lgtm to /lgtm+/hold
+    *   Issue: [https://github.com/kubernetes/test-infra/issues/6589](https://github.com/kubernetes/test-infra/issues/6589)
+    *   SIG Test update meeting at 1pm PST today
+*   User journeys update (Jennifer & Andrew)
+    *   Victory dance!
+    *   What next? 
+        *   Improve quality of linked docs
+        *   Improve navigation/UX
+        *   Test it!
+        *   Analytics and monitoring: are we seeing improvements?
+
+                Some good material on measuring: [Bob Watson’s articles](http://docsbydesign.com/2017/08/29/measuring-your-technical-content-part-3/) (and see linked items, plus more throughout his site)
+
+*   Expectations and how to volunteer for reviewing duties (heckj): DEFER for one week 2/6
+    *   PR: [https://github.com/kubernetes/website/pull/7133](https://github.com/kubernetes/website/pull/7133)
+    *   For example, what expectations do we have & should we have of a reviewer or approver in handling PRs, issues, etc.
+    *   I have been asked “how do I volunteer” informally a couple of times, with this being the topic behind the question
+    *   Clearer reviewer guidelines
+        *   Set an SLA for when we’ll respond to PRs: What’s a reasonable standard? 48 hours? 4 business days?
+        *   Do we need to codify standards for reviewers: for example, don’t merge a PR assigned to someone else? Is our current method sustainable?
+    *   As we're talking about SLO for getting attention on PRs, Paris shared this view of how we're doing today:
+        *   [https://k8s.devstats.cncf.io/d/000000013/first-non-author-activity?orgId=1&var-period=w&var-repogroup_name=Docs&var-repogroup=docs&from=1454786880740&to=1516735680740](https://k8s.devstats.cncf.io/d/000000013/first-non-author-activity?orgId=1&var-period=w&var-repogroup_name=Docs&var-repogroup=docs&from=1454786880740&to=1516735680740)
+*   Cluster-registry looking for "how/where to host" advice for their docs (heckj)
+    *   @font (Ivan Font) of sig-multi-cluster requesting...
+    *   Do we advise on best practices for projects within sigs?
+    *   Hosting binary usage (aka like kubeadm, kubectl), API reference, etc.
+    *   Current docs are markdown-in-github: [https://github.com/kubernetes/cluster-registry/blob/master/docs/development.md](https://github.com/kubernetes/cluster-registry/blob/master/docs/development.md)
+
+**1/30/2018**
+
+New attendees?
+
+
+
+*   
+
+Follow-ups from last meeting (10 minutes max): 
+
+
+
+*   Bot automation: it’s alive!
+*   Steve: Update/revisit style guide. [Issue 7030](https://github.com/kubernetes/website/issues/7030)
+    *   Revisiting to make sure we recommend what we actually enforce (including usage of “we”)
+    *   Add a style guide template to the [PR template](https://github.com/kubernetes/website/blob/master/.github/PULL_REQUEST_TEMPLATE.md) in kubernetes/website
+    *   Revisit this next week (2/6) to talk about whether it would be better to adapt an existing style guide (for example, Google Cloud if they have one) or continue creating from scratch
+
+Agenda items
+
+
+
+*   Zach will be out Weds-Sunday, returning on Monday 2/5
+*   What to do with repo teams/collaborators now that approvals are automated (Zach)
+    *   [https://github.com/kubernetes/website/settings/collaboration](https://github.com/kubernetes/website/settings/collaboration)
+    *   Zach: Add teams for reviewers/approvers (https://github.com/orgs/kubernetes/teams/sig-docs-pr-reviews/members)
+    *   Steve will take on individual contributor admin cleanup
+*   Expectations and how to volunteer for reviewing duties (heckj): DEFER for one week 2/6
+    *   For example, what expectations do we have & should we have of a reviewer or approver in handling PRs, issues, etc.
+    *   I have been asked “how do I volunteer” informally a couple of times, with this being the topic behind the question
+*   User journeys update (Jennifer & Andrew)
+    *   Prioritize content improvements to content inside user journey paths
+*   Questions about static generation of the [community repo docs](https://kubernetes.io/docs/imported/community/guide/) (Jorge)
+    *   Script is self-service: https://github.com/kubernetes/website/blob/master/update-imported-docs/community.yml
+*   CNCF is hiring! (Zach)
+
+**1/23/2018**
+
+New attendees?
+
+
+
+*   
+
+Follow-ups from last meeting (10 minutes max): 
+
+
+
+*   [https://github.com/kubernetes/website/issues/6906](https://github.com/kubernetes/website/issues/6906) [[PR 6378](https://github.com/kubernetes/test-infra/pull/6378)] (Aaron Crickenberger)
+    *   We are proceeding with this!
+    *   /lgtm: serves as Tech LGTM
+    *   /approve: serves as Docs LGTM, will flag for automatic merging
+    *   Repo maintenance teams: can we streamline?
+        *   [https://github.com/kubernetes/website/settings/collaboration](https://github.com/kubernetes/website/settings/collaboration)
+
+Agenda items
+
+
+
+*   Prioritizing 2018
+    *   In flight projects: [https://github.com/kubernetes/website/issues/6935](https://github.com/kubernetes/website/issues/6935)
+*   Expectations and how to “volunteer” for reviewing duties (heckj)
+    *   For example, what expectations do we have & should we have of a reviewer or approver in handling PRs, issues, etc.
+    *   I have been asked “how do I volunteer” informally a couple of times, with this being the topic behind the question
+*   Steve: Update/revisit style guide. [Issue 7030](https://github.com/kubernetes/website/issues/7030)
+
+Follow-ups for 1/30: 
+
+
+
+*   User journeys update (Jennifer & Andrew)
+*   Automation meeting: Need to set an hour-long meeting for early Feb to discuss doc automation needs. (Zach)  (interested folks: Andrew, Steve, Chris, Jessica, Jennifer, Zach)
+
+**1/16/2018**
+
+New attendees?
+
+
+
+*   None :-(
+
+Followups from last meeting: 
+
+
+
+*   SIG-Docs summit 2018.  (Zach)
+    *   Portland, May 9-10 (immediately following Write the Docs)
+    *   Working with LF event team to start logistics in motion
+        *   Jaredb: We can host in the Google Portland office if that helps. Or, for something more fun, I recommend picking a McMennamin’s property like Edgefield :)
+*   Community site followup (Jessica) 
+    *   Jorge is taking the lead on this ([See netlify](https://deploy-preview-6863--kubernetes-io-master-staging.netlify.com/docs/imported/community/keps/))
+    *   Import is live
+*   [https://github.com/kubernetes/website/issues/6906](https://github.com/kubernetes/website/issues/6906) (Aaron Crickenberger)
+    *   Need to up/down the proposal
+    *   Jennifer: need to have approver/reviewer roles well defined and in place
+        *   Community discussion about normalizing expectations across project
+        *   SIG Docs could benefit from rigor of roles defined in kubernetes/kubernetes
+    *   Steve: Do we copy what they do in kubernetes/kubernetes?
+        *   /lgtm & /approve
+        *   /lgtm can mean tech approval
+        *   /approve can mean doc approval
+    *   Zach: Take an action item for better PR review guidelines, specifically: clean commit history in PRs
+    *   End result: +1, yes to Aaron to implement bot proposal
+
+Agenda items?
+
+
+
+*   Steve: Removal of getting started guides that result in a non-conformant cluster.
+    *   Question from Ilya Dmitrichenko to sig-docs, sig-cluster-lifecycle: \
+ \
+Over time, a number of Getting Started Guides had been contributed to Kubernetes website. General quality and levels of maintenance of all of these guides vary. Some achieve similarly end goals with different tools. At sig-cluster-lifecycle, we believe that the best way to ensure all documentation related to cluster provisioning and bootstrap that is published on the website results in a conformant cluster configuration. \
+ \
+We would like to enforce conformance rules on getting started guides, and remove any guides that result in non-conformant cluster configuration by end of March (i.e. after 1.10 release). \
+ \
+Before we go ahead and implement this, we would like to hear from sig-docs folks and any maintainers or users of getting started guides.
+    *   SIG-Docs: All in favor
+        *   SIG Cluster Lifecycle will open a PR of GSGs to remove (Ilya)
+        *   Reach out to owners for state of guide conformance?
+        *   Add conformance/GSG removal to in-flight guide (Zach)
+*   Better review habits (Zach)
+    *   Get reviews before merging
+    *   Reject PRs for static branches (currently anything prior to 1.9)
+    *   Review for quality, not just test-passing
+    *   (Steve) Establish /lgtm as tech approval, /approve as doc approval?
+    *   Mature style guide (Zach, add to in-flight guide)
+        *   What does it mean when you /approve?
+    *   How to deal with editorial debt:
+        *   Open an issue against editorial need
+        *   Add to a dedicated project?
+*   User journeys update (Jennifer)
+    *   Deferred one week (1/23)
+*   Writing mentorship proposal (Jennifer)
+    *   Embedding writers in SIGs (Zach, add to in-flight guide)
+    *   Need a list of SIGs in need:
+        *   SIG cluster lifecycle (Jennifer)
+        *   SIG apps (writer?)
+        *   SIG community (Steve Perry)
+*   Automation meeting: Need to set an hour-long meeting for early Feb to discuss doc automation needs. (Zach)  (interested folks: Andrew, Steve, Chris, Jessica, Jennifer, Zach)
+
+**1/9/2018**
+
+**NOTE: Zach on vacation.**
+
+New attendees?
+
+
+
+*   Aaron Crickenerger
+
+Followups from last meeting: 
+
+
+
+*   Move to the release repo and link to it from the docs repo (Jennifer)
+    *   Move docs playbook for releases; content audit of current docs in release repo also needed; WIP (no PR yet, will announce to SIG when ready)
+*   SIG-Docs summit 2018.  Eyeing May/June in 2018. (Zach)
+*   Supported documentation versions: Need to follow up on https://github.com/kubernetes/website/pull/6442 (Andrew and Steve)
+    *   [https://github.com/kubernetes/website/pull/6882](https://github.com/kubernetes/website/pull/6882)
+    *   [Preview](https://deploy-preview-6882--kubernetes-io-master-staging.netlify.com/docs/home/supported-doc-versions/)
+*   Community site followup (Jessica) 
+    *   Jorge is taking the lead on this ([See netlify](https://deploy-preview-6863--kubernetes-io-master-staging.netlify.com/docs/imported/community/keps/))
+*   1.9 Retro (Zach) 
+    *   Deferred
+
+Agenda items?
+
+
+
+*   [https://github.com/kubernetes/website/issues/6906](https://github.com/kubernetes/website/issues/6906) (Aaron Crickenberger)
+    *   Thoughts on implementation?
+        *   Probably need to keep Docs LGTM/Tech LGTM separate
+        *   We can probably implement the existing system for /hold, /lgtm, /approve--just need to be clear and specific about approval chain
+        *   Discussion in issue; Aaron will not pull trigger on merge until we (SIG docs maintainers) signal that we’re ready
+*   Request to do a doc sprint at IBM Index on 2/20, SF (Zach)
+    *   Export a planning kit for doc sprints at other meetups?
+*   We should define our big site/docs goals for 2018. What’s our process? I suggest OKRs/KPIs. (Jared)
+    *   OKRs are OK!
+    *   Set them up at the Summit in May
+    *   SIG Maintainers meet separately beforehand
+        *   List projects currently in flight
+            *   Zach will set up contrib doc by 1/12
+            *   Proposed meeting on 1/23
+    *   Zach: set up some goals/OKRs
+    *   Summit: talk about how to implement
+    *   Possible top level objectives:
+        *   Improve Kubernetes onboarding
+        *   Findability
+        *   One-stop-shop for broader community docs
+        *   Improve (make more efficient) PR approval process
+        *   Improve docs release process for quarterly k8s releases (including release notes) 
+        *   Create tighter loop w/ community feedback on docs
+        *   Increase the number docs contributors 
+        *   ?
+*   Importing docs from other repos, creating guidelines [PR #6863](https://github.com/kubernetes/website/pull/6863) [Preview](https://deploy-preview-6863--kubernetes-io-master-staging.netlify.com/docs/imported/) (Andrew)
+    *   Follow up in three weeks: 1/30 (Andrew)
+
+Next week: 
+
+
+
+*   Reviewer conventions in docs file. Automation and names in front matter of file? (Steve & Andrew) 
+*   Automation meeting: Need to set an hour-long meeting for early Feb to discuss doc automation needs. (Zach)  (interested folks: Andrew, Steve, Chris, Jessica, Jennifer, Zach)
+*   We have a staleness/rot bot now (Zach) 
+
+**1/2/2018**
+
+**NOTE: Zach on vacation.**
+
+New attendees?
+
+
+
+*   Nope :(
+
+Followups from last meeting: 
+
+
+
+*   Future docs release meisters:
+    *   1.10: Jennifer Rondeau
+    *   1.11: Nick Chase
+    *   Chris Short (@chris-short) wants to shadow a release
+    *   Move to the release repo and link to from the docs repo
+        *   Jennifer is on it :)
+*   SIG-Docs summit 2018.  Eyeing May/June in 2018. Details to follow from Zach.
+*   Supported documentation versions: Need to follow up on https://github.com/kubernetes/website/pull/6442 re:current+4 
+    *   Andrew and Steve
+*   Reviewer conventions in docs files (Steve & Andrew)
+    *   Follow-up: automation and names in front matter of file?
+    *   Steve: Check in on this in 2 weeks. 
+    *   Andrew will follow up with tooling people to modify bots to specify category
+*   Automation meeting: Need to set an hour-long meeting for early Feb to discuss doc automation needs. 
+    *   Andrew, Steve, Chris, Jessica, Jennifer, Zach
+*   Community site (community.k8s.io) for developer contributions (from Joe Beda). 
+    *   Any Updates? 
+        *   Jessica will do a follow up
+    *   Any thoughts?
+        *   Start with Keps. Keps.kubernetes.io
+        *   ContribEx should own this. (via Paris)
+        *   Onboarding should fall under the contributor site
+    *   “Lightweight process”
+        *   Questions of ownership for KEPs and Community
+        *   Developer perception? If the dev perception is entirely launch based, we should emphasize the process outside of launches
+*   SIG Docs representation on other sigs?
+    *   What are the highest priority SIGs?
+        *   Reach out to previous release leads and features leads - ex. Jaice, Ihor
+        *   Reach out to SIG-Arch
+*   1.9 Retro is happening next week
+*   Chinese translation work:
+    *   Researching best practices for i18n
+    *   [Refactoring k8s.io for i18n](https://docs.google.com/document/d/10teK1YmLBcRVc6B6GjgJxRP1KcuGjL-KpHwSaANr4J4/edit?usp=sharing) doc
+*   Upcoming Kubecons for 2018:
+    *   [Europe: May 2-4, Copenhagen](https://events.linuxfoundation.org/events/kubecon-cloudnativecon-europe-2018/)
+    *   [China: June 25-27, Bejing](https://www.lfasiallc.com/linuxcon-containercon-cloudopen-china)
+    *   [North America: Dec 11-13, Seattle](https://events.linuxfoundation.org/events/kubecon-cloudnativecon-north-america-2018/)
diff --git a/sig-docs/meeting-notes-archive/2019_Weekly_Meeting_Minutes.md b/sig-docs/meeting-notes-archive/2019_Weekly_Meeting_Minutes.md
new file mode 100644
index 00000000..57cf22c3
--- /dev/null
+++ b/sig-docs/meeting-notes-archive/2019_Weekly_Meeting_Minutes.md
@@ -0,0 +1,2207 @@
+**12/17/2019**
+
+**APAC - 02:00 UTC (6 Pacific)**
+
+New contributors
+
+*   
+
+Updates/reminders
+
+
+
+*   This week's PR wrangler is @kbarnard10
+*   No PR wranglers the weeks of December 22 and 29
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   Review ZH release-branch issue / path forward
+*   Wrapping up the year
+    *   We passed the 18000 - (combined issues and PRs) mark.
+    *   Vacations?
+        *   Zach C on vacation Dec 14-Jan 6
+        *   Jared Bhatti on vacation: Jan 1 - Jan 13
+        *   Brad Topol out Dec 16-Jan 4
+*   Monthly Korean l10n update (June Yi)
+    *   Membership update: No
+    *   One team milestone branch is merged (dev-1.16-ko.6)
+    *   Current team milestone branches: dev-1.17-ko.1, dev-1.16-ko.7(bug fix only, final for 1.16)
+    *   @seokho-son and @ianychoi made a [presentation](https://youtu.be/1TLBSmeaVJc) about participating SIG Docs and Korean l10n at Kubernetes Forum Seoul 2019 (Dec 9)
+
+**12/10/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   none
+
+Updates/reminders
+
+
+
+*   This week's PR wrangler is @jaredbhatti
+*   Next week's PR wrangler is @kbarnard10
+*   No PR wranglers the weeks of December 22 and 29
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   Release 1.17 update
+    *   Last week was quite hairy, many thanks to Bob Killen, Guin Saenger, Jim Angel
+    *   Website repo is FROZEN until thaw post-release
+    *   Official release PR is now: [https://github.com/kubernetes/website/pull/18011](https://github.com/kubernetes/website/pull/18011)
+*   Chair business
+    *   Jennifer stepping down as chair, not going away
+    *   Kaitlyn stepping up as chair
+    *   Dates / Comms
+        *   Coming to a theatre near you.
+*   Better approver guidelines
+    *   [https://docs.google.com/document/d/1JCWVEn5h-Wfa-yEirvfRU0FjxHYIMT0nTvq0dBvK2gA/edit?pli=1](https://docs.google.com/document/d/1JCWVEn5h-Wfa-yEirvfRU0FjxHYIMT0nTvq0dBvK2gA/edit?pli=1)
+        *   Kaitlyn and Brad requesting feedback for v1 (and location)
+    *   David: Can we look further into the New Contributor Ambassador role
+        *   Jennifer: Maybe we need to schedule / announce regularly.
+        *   Brad to own in January.
+            *   Maintain / list / onboard / announce
+*   Docsy Status? (Zach C)
+    *   Work in progress
+    *   Jared: Contractor is lined up w/ tech writers @ Google. Snags during migration will be surfaced. Still trying to get resources / no timeline yet.
+    *   David: Is there any visual uplift / styling being considered?
+*   KEP Update (Zach C)
+*   Wrapping up the year
+    *   We passed the 18000 mark.
+    *   Vacations?
+        *   Zach C on vacation Dec 14-Jan 6
+        *   Jared Bhatti on vacation: Jan 1 - Jan 13
+        *   Jennifer Rondeau out week of Dec 9 (evidently not today)
+        *   Brad Topol out Dec 16-Jan 4
+*   PR Wrangler schedule: needs building for Q1/Q2 2020
+    *   Jennifer will create first draft, circulate for anyone who needs to amend
+    *   DONE: Zach C will freshen OWNERS_ALIASES list
+        *   [https://github.com/kubernetes/org/pull/1459/](https://github.com/kubernetes/org/pull/1459/files)
+        *   [https://github.com/kubernetes/website/pull/17929/files](https://github.com/kubernetes/website/pull/17929/files)
+*   Overlapping initiatives across sigs (docs, contribex, more): JimA suggests opening up meetings, slack conversations
+*   Blog subproject: [https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject](https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject)
+    *   Aging out docs: don’t fix older than a year, but can be lenient 
+    *   tutorials / how-tos / walkthroughs / examples
+*   No recommendation around use of sudo in doc. There should be a suggestion around this in ‘[Documentation Style Guide](https://kubernetes.io/docs/contribute/style/style-guide/)’. (Vanou Ishii)
+    *   Related Issue \
+[https://github.com/kubernetes/website/issues/17181](https://github.com/kubernetes/website/issues/17181)
+    *   Needs consistency
+    *   Style Guide update is needed - Vanou
+*   Rob: I need some Hugo / how-is-this-table-generated help ? :-D
+    *   on[ https://github.com/kubernetes/website/issues/16281](https://github.com/kubernetes/website/issues/16281)
+    *   website/content/en/docs/reference/command-line-tools-reference/feature-gates.md
+*   Next week is APAC time
+
+**12/3/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Simon Forster - joining after a long hiatus :)
+*   Jaime Duncan - @VMWare, looking to contribute to docs :)
+
+Updates/reminders
+
+
+
+*   This week's PR wrangler is @rajakavitha1
+*   Next week's PR wrangler is @jaredbhatti
+*   No PR wranglers the weeks of December 22 and 29
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   Release 1.17 update
+    *   [https://github.com/kubernetes/website/pull/17065#issuecomment-561029393](https://github.com/kubernetes/website/pull/17065#issuecomment-561029393) 
+    *   Looks like there’s a CLA problem to resolve before release on Monday, December 9 - Can’t merge otherwise. 
+    *   Tracking down how this happened
+*   KubeCon update
+    *   Thank you Jim for putting together the contributor day experience for docs
+    *   Deep dive on Hugo - it’s good to highlight the tooling we support for content. Most people don’t realize this. 
+    *   Got lucky with timing, had a lot of experienced contributors
+*   4th Tuesday meetings 
+    *   Move APAC meeting up 1 hour so we’re not interfering with lunch time with folks in Korea
+    *   One hour earlier is easier for east coast folks too.
+    *   Overall consensus - yes :)
+    *   AI: Jim to send out email comms around this conversation
+        *   Lazy consensus on hour change (update)
+        *   Move 4th tuesday -> 3rd for Dec
+        *   Cancel holiday week (last week of Dec)
+        *   Cancel New Years (first week of Jan)
+    *   AI: Zach will update the calendar invite. 
+*   Configuring a Kubernetes Microservice katacoda tutorial (Brad)
+    *   Hosting this with other tutorials? 
+    *   Under: [Kubernetes Basics](https://kubernetes.io/docs/tutorials/kubernetes-basics/create-cluster/cluster-intro/) or [Kubernetes Bootcamp](https://kubernetesbootcamp.github.io/kubernetes-bootcamp/)?
+    *   History of poor maintenance, but we can remove if issues are not addressed within ~30 days 
+    *   Decision: Place under Kubernetes Basics with agreement on maintenance.
+*   Docsy Status? 
+    *   Cat herding in progress, still possible by EOY
+*   Wrapping up the year
+    *   On track for 18,000 issues/PRs by EOY
+    *   Vacations?
+        *   Zach C on vacation Dec 14-Jan 6
+        *   Jared Bhatti on vacation: Jan 1 - Jan 13
+        *   Jennifer Rondeau out week of Dec 9 (will miss Dec 10 meeting)
+        *   Brad Topol out Dec 16-Jan 4
+*   PR Wrangler schedule: needs building for Q1/Q2 2020
+    *   Jennifer, Jim, Brad, and Kaitlyn will create
+    *   AI: Zach C will freshen OWNERS_ALIASES list
+*   Overlapping initiatives across sigs (docs, contribex, more): JimA suggests opening up meetings, slack conversations
+*   Blog subproject: [https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject](https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject)
+
+**11/26/2019**
+
+**APAC 7pm Pacific**
+
+New contributor:
+
+
+
+*   
+
+Updates/reminders:
+
+
+
+*   This week's PR wrangler is @tengqm
+*   Next week's PR wrangler is @rajakavitha1
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   AI: Change APAC meeting time, 1 hour earlier, Jim to propose in SIG-Docs and implement with lazy consensus.
+*   Post-kubecon / holidays
+*   Korean l10n team update (June Yi)
+    *   Membership Update: No
+    *   Three team milestone branches are merged onto master
+        *   dev-1.16-ko.3~5
+    *   Current team milestone
+        *   dev-1.16-ko.6 (~ Dec 5)
+    *   Next team milestone
+        *   Freeze until 1.17 release
+        *   dev-1.17-ko.1 / dev-1.16-ko.7
+    *   Preparing for Kubernetes Forum Seoul 2019 (Dec 9-10) https://sched.co/WIRH
+
+**11/19/2019**
+
+**10:30am Pacific**
+
+New contributor:
+
+
+
+*   Luis Figueroa (Red Hat)
+
+Updates/reminders:
+
+
+
+*   This week's PR wrangler is @ryanmcginnis
+*   Next week's PR wrangler is @tengqm
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+No agenda
+
+
+
+*   Minimal attendance, presumably bc KubeCon: Steve Perry, Jennifer Rondeau, Luis. Steve went over Q4 planning a bit, we discussed Luis's possible first contributions. Light discussion, no recording.
+
+**11/12/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   David K (formerly Marz)
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @tfogo
+*   Next week’s PR wrangler is @ryanmcginnis 
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   Docs: 
+    *   Number of PRs looking good: [https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+label%3Alanguage%2Fen](https://github.com/kubernetes/website/pulls?q=is%3Aopen+is%3Apr+label%3Alanguage%2Fen) 
+    *   Issue health also looks good: repo stats are healthy (yay!)
+*   Repeat visibility:
+    *   [Zach] Docsy update? 
+        *   Zach is working with contractors; hope is by EOY
+        *   Zach is less confident that we’ll have testing available by KubeCon NA, good to make a backup plan
+    *   Lists and code blocks
+        *   Black Friday may be replaced by Goldmark: [https://github.com/gohugoio/hugo/issues/5963](https://github.com/gohugoio/hugo/issues/5963) 
+*   Process:
+    *   Jim, Zach, and Cody meeting tomorrow (Wednesday) to finalize sprint topics
+    *   PR wranglers through EOY:
+        *   Brad Topol will wrangle Dec 8, Jan 5
+    *   Need to update OWNERS_ALIASES to remove approvers who are no longer current
+        *   Everyone can play along! :) 
+    *   Quarterly Meeting date: Thursday, Nov 14, 5pm-8pm Pacific
+        *   [https://zoom.us/j/191972276](https://zoom.us/j/191972276) 
+    *   What is needed to drive 3rd party content KEP forward?
+        *   Zach update: responded to initial feedback, pushing back on the idea that feature developers can handwave inclusion
+        *   Did an initial review to clarify wording/intent
+        *   BUT we need to make some specific policy recommendations to gain traction
+            *   Zach will link to specific policy introduced in content guidelines TODAY (11/12)
+            *   Brad Topol: Beware bikeshedding!
+*   KubeCon meetup:
+    *   Pacific Ballroom 23 all day
+
+**11/5/2019**
+
+**10:30am Pacific**
+
+**If you're reading this document today, please join zoom at https://zoom.us/j/299255558?pwd=VHc1S0VjQVJ4OXJJZEJKUkxRaDNoZz09**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @makoscafee
+*   Next week’s PR wrangler is @tfogo 
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   Docs: 
+    *   [Zach] Docsy update? 
+        *   Zach is working with contractors; hope is by EOY
+        *   Zach is less confident that we’ll have testing available by KubeCon NA, good to make a backup plan
+    *   Lists and code blocks
+        *   Black Friday may be replaced by Goldmark: [https://github.com/gohugoio/hugo/issues/5963](https://github.com/gohugoio/hugo/issues/5963) 
+*   Process:
+    *   PR wranglers through EOY:
+        *   Need to revise through EOY due to Google withdrawals
+        *   Need to update OWNERS_ALIASES to remove approvers who are no longer current
+    *   Finalize Quarterly Meeting date: Thursday, Nov 14, 5pm-8pm Pacific
+        *   Lazy consensus
+        *   Can we change to Wednesday Nov 13?
+    *   What is needed to drive 3rd party content KEP forward?
+        *   Zach update: responded to initial feedback, pushing back on the idea that feature developers can handwave inclusion
+        *   Did an initial review to clarify wording/intent
+        *   BUT we need to make some specific policy recommendations to gain traction
+
+**10/29/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Jamie Coleman
+*   ykchang
+*   Mbroz
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @bradtopol (replacing @chenopis)
+*   Next week’s PR wrangler is @makoscafee
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   Docs: 
+    *   [Zach] Docsy update? 
+        *   Zach is working with contractors; hope is by EOY
+        *   It may be possible to align testing with KubeCon NA
+    *   [Brad] Java microservices tutorial?
+        *   Brad introduced Michal, who’s giving a demo
+            *   Link to demo tutorial: [https://katacoda.com/jamiecoleman/scenarios/kubeconfig](https://katacoda.com/jamiecoleman/scenarios/kubeconfig)
+            *   Zach C: Looks good, but raises questions about where tutorial content lives. SIG Docs needs to discuss best practices about where tutorial content lives
+            *   Jim: Who owns tutorial content?
+    *   New localizations:
+        *   Active: Vietnamese ([https://github.com/kubernetes/website/pull/16965](https://github.com/kubernetes/website/pull/16965))
+        *   WIP: Russian ([https://github.com/kubernetes/website/pull/16404](https://github.com/kubernetes/website/pull/16404))
+        *   ?: Arabic ([https://github.com/kubernetes/community/pull/4172](https://github.com/kubernetes/community/pull/4172))
+*   Process:
+    *   Finalize Quarterly Meeting date: Thursday, Nov 14, 5pm-8pm Pacific
+        *   Lazy consensus
+    *   What is needed to drive 3rd party content KEP forward?
+        *   [https://github.com/kubernetes/enhancements/pull/1327](https://github.com/kubernetes/enhancements/pull/1327) 
+        *   [zach] Clear path for action forward (lazy consensus) and expectations.
+            *   Avoid opinions encourage actions
+            *   Clear set of deadlines for feedback
+            *   Criteria needed
+        *   [marz] Framework (decision making). How it’s approved / vetted vs. specialized process.
+        *   [brad] document certain areas that are not in scope if sensitive
+        *   AI: zach to drive kep
+
+**10/22/2019**
+
+**7pm Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @bradtopol
+*   Next week’s PR wrangler is also @bradtopol (replacing @chenopis)
+
+Agenda
+
+
+
+*   Docs
+    *   Reference doc generation: @aimeeu is working on an automation script: [https://github.com/kubernetes/website/pull/16681/](https://github.com/kubernetes/website/pull/16681/)
+    *   Better UX: Zach C is working with contractors to apply the Docsy Hugo template to the website. [https://github.com/google/docsy](https://github.com/google/docsy) 
+        *   Will probably do a section at a time, starting with docs
+        *   Hopefully on track before the end of the year
+        *   [Brad] If we can line this up for sprint testing at KubeCon NA, all the better!
+    *   [Brad] We may get a preview next week of a Java microservices tutorial put together by IBM team on Katacoda
+*   Process
+    *   Quarterly SIG meeting--we’re overdue what date shall we choose?
+        *   Prefer dates in November of December
+        *   Tentatively planning Thursday, Nov 14, 5pm-9pm Pacific
+        *   Confirm at weekly meeting on 10/29
+    *   Should we create a KEP to finalize policy regarding [dual-hosted content (issue #16091)](https://github.com/kubernetes/website/issues/16091)?
+        *   We did, courtesy of @sftim: [https://github.com/kubernetes/enhancements/pull/1327](https://github.com/kubernetes/enhancements/pull/1327) 
+        *   [Kubernetes Repository Guidelines](https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md) does not contain guidelines on content that should be in the project repo vs k8s docs
+        *   Hopeful for KEP passing by end of year
+        *   [Brad] Uncomfortable removing k8s.io/setup/ because it’s high value
+            *   [Zach C] Two different conversations: how does 3rd party content get in VS. what should be removed?
+            *   Make sure we focus on what/how 3rd party content gets in; what/how to remove will follow sequentially in follow-up action for conformity
+*   Korean l10n team update
+    *   Membership Update: None
+    *   Final team milestone branch for 1.15 is merged
+        *   Dev-1.15-ko.6
+    *   Two team milestone branches are merged onto master
+        *   dev-1.16-ko.1, dev-1.16-ko.2
+    *   Current team milestone
+        *   dev-1.16-ko.3 (~ Oct 24)
+    *   Proposal of @seokho-son and @ianychoi have accepted for Kubernetes Forum Seoul 2019 (Dec 9-10) [https://sched.co/WIRH](https://sched.co/WIRH)
+        *   request for contributor patches for the speakers
+            *   [Zach C] Contact @paris (Paris Pittman) for patches
+            *   Paris Pittman <parispittman@google.com>
+
+**10/15/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Tamao Nakahara (Weaveworks), finally introduced!
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @zparnold
+*   Next week’s PR wrangler is @bradtopol
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   Docs: 
+    *   Third party content KEP
+        *   [https://docs.google.com/document/d/1vtA6iNCCzaX-6uUvWA6WtwanBd5EDiFtz9CI0Ek1-lM/edit?usp=sharing](https://docs.google.com/document/d/1vtA6iNCCzaX-6uUvWA6WtwanBd5EDiFtz9CI0Ek1-lM/edit?usp=sharing)
+            *   @sftim: Work in progress, can become a PR - [done](https://github.com/kubernetes/enhancements/pull/1327)
+            *   Review / grooming prior to Sunday 10/20 - @sftim will open PR 
+    *   
+*   Process:
+    *   Approver responsibilities
+        *   [https://github.com/kubernetes/website/pull/16750](https://github.com/kubernetes/website/pull/16750)
+            *   AI: Zach updates PR to move to emeritus approvers and slack (jim and jenifer) with contact information.
+        *   [https://github.com/kubernetes/community/blob/master/community-membership.md#approver](https://github.com/kubernetes/community/blob/master/community-membership.md#approver)
+    *   Nagging bot: [https://github.com/kubernetes/community/issues/3999](https://github.com/kubernetes/community/issues/3999)
+
+**10/8/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Rin Oliver
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @zacharysarah
+*   Next week’s PR wrangler is @zparnold
+*   Approvers, make sure you know your scheduled [PR wrangler shifts](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+    *   Zach C will ask in Slack for a replacement for @chenopis in week of October 27
+
+Agenda
+
+
+
+*   Docs: 
+    *   Third party content KEP
+        *   [https://docs.google.com/document/d/1vtA6iNCCzaX-6uUvWA6WtwanBd5EDiFtz9CI0Ek1-lM/edit?usp=sharing](https://docs.google.com/document/d/1vtA6iNCCzaX-6uUvWA6WtwanBd5EDiFtz9CI0Ek1-lM/edit?usp=sharing)
+        *   Source issue: [https://github.com/kubernetes/website/issues/15748](https://github.com/kubernetes/website/issues/15748) 
+        *   Content guide: [https://kubernetes.io/docs/contribute/style/content-guide/](https://kubernetes.io/docs/contribute/style/content-guide/)
+        *   PR repo: [https://github.com/kubernetes/enhancements/tree/master/keps](https://github.com/kubernetes/enhancements/tree/master/keps)
+        *   @sftim and @bradtopol will port umbrella issue and content guide into the KEP template [Complete in 1 week, 10/14]
+    *   Release 1.17
+        *   Jeefy is a release shadow!
+        *   Docs freeze date: EOD Tuesday 15 October
+        *   Code freeze date: 14 November
+        *   Docs review complete: 19 November (in the middle of KubeCon)
+        *   Release date: 9 December
+        *   Ping Damini Satya for release date changes/awareness
+            *   @sftim: Let’s move up the dates for placeholder PRs to give more time for docs awareness
+*   Process:
+    *   OWNERS cleanup
+        *   Zach will send Bob’s email to SIG Docs googlegroup
+        *   Use the link in the email to check your OWNERS file membership
+*   Contributor Summit
+    *   Docs Sprint - What can we accomplish? 
+        *   Cover the basics of starting (CLA, repo)
+        *   Create **theme** / agenda prior to (what do we want to cover)
+            *   Preso overview about contrib (docs 101)
+            *   Then workshop (get in groups)
+            *   Have approvers on hand to approve PRs
+            *   Maybe split the day, new intros in beginning and more experienced later on.
+            *   Note: Themes have been “needs” driven
+            *   Advertise the date/time of the sprint
+        *   Glossary and low-hanging fruit is a good starting spot
+            *   Compared to previous KubeCons, glossary has fewer gaps in it
+        *   “good-first-issues” are good too
+            *   Maybe curate a list to label on the day of the summit (@sftim)
+        *   Target: get folks into docs, get folks into code (git)
+            *   Demo as an entry path
+        *   Start the day with docs sprint (run to lunch) and break off. Socialize afternoon (last 2 hours)
+        *   Sample sprint issue: [https://github.com/kubernetes/website/issues/7452](https://github.com/kubernetes/website/issues/7452) 
+        *   Swag?
+            *   Zach C: Please no swag, let’s focus on inclusion instead
+        *   Any opportunities to promote / reference inclusion?
+            *   Zach C: Yes, let’s do it! Open to ideas
+            *   @sftim will try to think of something
+    *   Lightning talks / subtopics?
+
+**10/1/2019**
+
+**10:30 AM Pacific**
+
+New contributors
+
+
+
+*   Matt Boersma (MS, AKS the service/open source)
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @stewart-yu
+*   Next week’s PR wrangler is @zacharysarah
+*   Welcome back from vacation Zach and Jen!
+*   The OFFICIAL official announcement that Jim Angel is a SIG Docs chair
+
+Agenda
+
+
+
+*   [aimee] For 10/1 meeting, please review for discussion:
+    *   [How should we handle pages that contain “allowed project” content that is similar but not exactly a duplicate of the project’s README, especially when the README appears to be more up-to-date](https://github.com/kubernetes/website/issues/16527)
+    *   [Content Guide: Revisit wording around adding content relating to CNCF, kubernetes, kubernetes-sigs projects with their own documentation](https://github.com/kubernetes/website/issues/16143)
+        *   Defer until KEP resolves from #15748
+*   [Zach C] Larger issue of third party content 
+    *   Feedback on [https://github.com/kubernetes/website/issues/15748](https://github.com/kubernetes/website/issues/15748)
+    *   /hold if Zach returns 
+    *   Putting together a KEP:
+        *   Draft in a google doc
+        *   Put draft in issue for review
+            *   Tim, Jay, Brad, Aimee, Zach C
+        *   [https://docs.google.com/document/d/1vtA6iNCCzaX-6uUvWA6WtwanBd5EDiFtz9CI0Ek1-lM/edit?usp=sharing](https://docs.google.com/document/d/1vtA6iNCCzaX-6uUvWA6WtwanBd5EDiFtz9CI0Ek1-lM/edit?usp=sharing)
+    *   When working with a steering committee, be patient and keep breathing :)
+    *   
+*   [Savitha R] Should production setup examples be a part of[ Docs ](https://kubernetes.io/)or[ K8s examples](https://github.com/kubernetes/examples) site? Ref: [https://github.com/kubernetes/website/issues/16635](https://github.com/kubernetes/website/issues/16635) . Can we have examples in K8s examples site and reference the link in [https://kubernetes.io/](https://kubernetes.io/) pages?
+    *   Recommend PVs to be a set of tasks - Steve
+    *   Savitha to take point on issue alongside engaging sig-storage for assistance with issue 16635
+    *   Larger question of how to deal with example content in tutorials
+        *   Revisit on 10/8 at top of agenda
+        *   Not that many tutorials: we could test them ourselves
+*   [Jim A]: Quick note: reference-docs have been “officially” relocated from [https://github.com/kubernetes-incubator/](https://github.com/kubernetes-incubator/) to [https://github.com/kubernetes-sigs](https://github.com/kubernetes-sigs). PR’s have been merged to reflect this change and links to the old repo redirect to the new one.
+    *   This is mainly for awareness / docs release team.
+*   [Zach C] Technical discussion for what happens if a chair “vanishes”
+    *   If a host drops, whoever becomes host, please resume recording
+*   Erick Carty
+    *   Can we provide specific guidance for which version where localizers start?
+
+**9/24/19**
+
+**FOURTH TUESDAY - APAC **
+
+**7 PM PACIFIC**
+
+New contributors
+
+
+
+*   n/a
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @steveperry-53
+*   Next week’s PR wrangler is @stewart-yu
+*   Zach is OOO this week; returns 9/30
+
+Agenda
+
+
+
+*   1.16 released! Thanks everyone, especially @simplytunde
+*   [aimee] Could an approver please merge these two LGTM PRs?
+    *   [Enhance Triage and categorize issues section](https://github.com/kubernetes/website/pull/16295)
+    *   [Add references to Content guide alongside Style guide](https://github.com/kubernetes/website/pull/16101)
+*   [aimee] For 10/1 meeting, please review for discussion:
+    *   [Content Guide: Revisit wording around adding content relating to CNCF, kubernetes, kubernetes-sigs projects with their own documentation](https://github.com/kubernetes/website/issues/16143)
+    *   [How should we handle pages that contain “allowed project” content that is similar but not exactly a duplicate of the project’s README, especially when the README appears to be more up-to-date](https://github.com/kubernetes/website/issues/16527)
+    *   Note: Moved to next week
+*   Korean team update
+    *   Membership Update
+        *   New K8s Members from Korean L10n: @ysyukr 
+    *   One team milestone branch is merged
+        *   dev-1.15-ko.5
+    *   Current and next team milestone
+        *   Current: 
+            *   dev-1.15-ko.6 (~ TBD)
+            *   dev-1.16-ko.1 (~ Sep 26)
+        *   Next: dev-1.16-ko.2 (Sep 27 ~ )
+    *   @seokho-son and @ianychoi have submitted a proposal for Kubernetes Forum Seoul 2019 (Dec 9-10)
+
+**9/17/2019**
+
+**10:30 AM Pacific**
+
+New contributors
+
+
+
+*   n/a
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @mistyhacks (acknowledged)
+*   Next week’s PR wrangler is @steveperry-53
+*   Zach and Jennifer both OOO this week at Write the Docs Prague
+
+Agenda
+
+
+
+*   1.16 Release update
+    *   Going through milestones / needing /lgtm and /approve
+    *   Nothing currently blocking atm
+    *   Overall good
+    *   4pm PDT (branch manager, docs going out)
+*   Jim A: Triage Issues and assign owners for beginning of sig-docs meeting?
+    *   Could also manage stale issues.
+    *   [aimee] Is there a “Triage Wrangler” role?
+    *   Idea: Looking at stale (closing / removing label).
+    *   Time box issues / bring up and look at stale issues.
+    *   Enhance Triage and Categorize Issues PR [https://github.com/kubernetes/website/pull/16295](https://github.com/kubernetes/website/pull/16295)
+*   Jim A: [https://github.com/kubernetes/website/issues/15748](https://github.com/kubernetes/website/issues/15748) - 3rd content
+    *   Google dev email thread: [https://groups.google.com/a/kubernetes.io/forum/#!msg/steering/8v8_IkHFX8M/2MXV0z6PAgAJ](https://groups.google.com/a/kubernetes.io/forum/#!msg/steering/8v8_IkHFX8M/2MXV0z6PAgAJ)
+*   Aimee: Survey Ended, 99 responses. Nothing to share at the moment. Across the board, users would like more detailed content and advanced tutorials. [https://www.surveymonkey.com/results/SM-2TLG8VVJ7/](https://www.surveymonkey.com/results/SM-2TLG8VVJ7/)
+    *   Next time, use google analytics for question origins
+
+**	**
+
+**09/10/2019**
+
+**10:30 AM Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @cody-clark
+*   Next week’s PR wrangler is @mistyhacks, Jennifer will confirm
+*   Zach and Jennifer both OOO next week at Write the Docs Prague
+
+Agenda
+
+
+
+*   Docs
+    *   [aimee] Triaging issues - sometimes hard to tell which issues have been looked at by SIG Docs team member; should we add [priority labels](https://github.com/kubernetes/website/labels?page=3&sort=name-asc) to all issues? priority/backlog to low issues, perhaps create a new label for medium priority? Thoughts?
+        *   Aimee: Suggest priority/medium
+        *   Jared: [Defined prioirties here](https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md#define-priority) - might be useful to include examples of each of these in [our triage documentation for SIG-Docs](https://kubernetes.io/docs/contribute/intermediate/#triage-and-categorize-issues). Should make tagging issues with a priority mandatory for triaging
+        *   Jay: Sorting by date/staleness ("last touched")
+            *   Diff between priority/backlog and priority/important-longterm?
+                *   backlog is stuff we accept may never be done
+                *   important-longterm is stuff we agree should be done at some point?
+        *   Zach: Don’t think we need more granularity - will we work on this now, later, or “never”? (👍 from Tim B, +1 from Jennifer)
+            *   
+        *   AI: [Aimee] - Will update contributing guide with the following: 
+        *   What labels to use
+            *   priority/backlog - could defer this forever
+            *   priority/important-longterm - within 6 months
+            *   priority/important-soon - within 3 months
+            *   priority/critical-urgent - need this yesterday
+            *   [Labels](https://github.com/kubernetes/website/labels?page=3&sort=name-asc)
+        *   AI: Zach C will remove old triage/priority labels from k/website. 
+    *   [Vineeth] Docs Release Team update.
+    *   [Zach C] Location for upstream fixes to generated reference docs? [https://github.com/kubernetes/website/pull/16263](https://github.com/kubernetes/website/pull/16263) 
+*   Layout(?)
+    *   [Rob K / Tim B] [Sortable, filterable tables](https://github.com/kubernetes/website/issues/16281)
+        *   Rob will update the issue with a summary
+        *   Zach suggested that @kbarnard10 might be able / willing to help
+*   Community
+    *    [Aimee] Survey - where to store questions and results? [https://github.com/kubernetes/community/tree/master/sig-docs](https://github.com/kubernetes/community/tree/master/sig-docs) seems like the correct repo, if we follow contrib-ex’s lead - lazy consensus is YES
+*   Tooling
+    *   [Zach C] Script for localization diffs by June Yi (@gochist): [https://github.com/kubernetes/website/pull/15789](https://github.com/kubernetes/website/pull/15789) 
+
+**9/03/2019**
+
+**10:30 AM Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @jimangel
+*   Next week’s PR wrangler is @chenopis (but will almost certainly reschedule)
+    *   @codyclark will wrangle instead
+
+Agenda
+
+
+
+*   Docs
+    *   Aimee: Consensus on how to handle PRs that add instructional content about a CNCF, kubernetes, or kubernetes-sig project that has its own docs; see [Issue 16143](https://github.com/kubernetes/website/issues/16143) 
+        *   Revisit 9/10: Take the week to review and comment on the issue
+        *   My worry is if we end up with neither of 2 projects willing to document how they work together - Tim B
+        *   (no real strong opinions BTW - Tim B)
+    *   Jim A - Deprecate kubernetes-incubator in favor of kubernetes-sigs (ref gen)
+        *   Issues:
+            *   Deprecation announce: [https://github.com/kubernetes/community/issues/1922](https://github.com/kubernetes/community/issues/1922)
+            *   Docs issue to move from release 1.14: [https://github.com/kubernetes/website/issues/13904](https://github.com/kubernetes/website/issues/13904)
+        *   I will open the issue to migrate and comment on the community issue, need alignment with sig-docs on timing.
+            *   [https://github.com/kubernetes/org/issues/new/choose](https://github.com/kubernetes/org/issues/new/choose)
+            *   pick: Repository migration
+    *   Release updates: 9/9 all docs need to be reviewed and merged.
+    *   Aimee - removing third-party content - running into an issue in which the localizations (fr, it) point to English docs that I want to remove… so just want to make everyone aware when reviewing PRs to ensure localized docs aren’t broken as a result
+        *   I’m going to push up a WIP and CC relevant localization leads
+        *   Link checker issue: [https://github.com/kubernetes/website/issues/15893](https://github.com/kubernetes/website/issues/15893)
+        *   Resolution: share when you come across this, but it’s not realistic to expect approvers to dig into localizations when approving a PR
+*   Community
+    *   Survey - the Kubernetes Documentation survey test site is live: [https://www.surveymonkey.com/r/8SWG2W3](https://www.surveymonkey.com/r/8SWG2W3)    Please take a look today and direct feedback to @aimeeu on k8s slack
+        *   Intro paragraph: The Kubernetes SIG Docs team would like Kubernetes users to evaluate the Kubernetes documentation ([https://kubernetes.io/docs/home/](https://kubernetes.io/docs/home/)). Please take a moment to provide your feedback so we can plan how to improve the Kubernetes docs.
+        *   Do we include the survey in this week’s KubeWeekly, which is published tomorrow?
+*   [Tunde] 1.16 release is going well, working with shadows to get docs PRs merged by 9/7 (deadline of 9/9)
+*   [Zach C] Meeting coverage
+    *   Jennifer: will run 9/10
+    *   Jim will run 9/17, 9/24
+
+**8/27/2019**
+
+**Fourth Tuesday**
+
+**7pm Pacific**
+
+New contributors
+
+
+
+*   Jesang
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @zparnold (thanks for stepping in!)
+*   Next week’s PR wrangler is @jimangel
+
+Agenda
+
+
+
+*   Docs
+    *   Removing duplicate content: [https://github.com/kubernetes/website/issues/16091](https://github.com/kubernetes/website/issues/16091) 
+    *   Removing third party content: [https://github.com/kubernetes/website/issues/15748](https://github.com/kubernetes/website/issues/15748) 
+        *   Definition of third party content: [https://kubernetes.io/docs/contribute/style/content-guide/](https://kubernetes.io/docs/contribute/style/content-guide/) 
+    *   Aimee is creating a site survey for pain points
+        *   Thanks to Brad Topol for his Twitter survey research!
+*   Community
+    *   Jared Bhatti is stepping down as co-chair in mid September
+    *   Chairs have nominated Jim Angel to replace Jared as co-chair
+    *   [https://github.com/kubernetes/website/issues/16106](https://github.com/kubernetes/website/issues/16106) 
+*   Site engineering
+    *   Fixing the deprecation warning: [https://github.com/kubernetes/website/issues/16066](https://github.com/kubernetes/website/issues/16066)
+        *   Resolved :-) 
+    *   Zach C is searching for a contractor to apply the Docsy template to the site
+*   Korean team update
+    *   Membership Update
+        *   New Korean content approver: @seokho-son
+        *   New K8s Members from Korean L10n: @yoonian, @lapee79
+    *   Three team milestone branches are merged
+        *   [dev-1.15-ko.2](https://github.com/kubernetes/website/pull/15533), [ko.3](https://github.com/kubernetes/website/pull/15744), [ko.4](https://github.com/kubernetes/website/pull/16063)
+    *   Current and next team milestone
+        *   Current: dev-1.15-ko.5 (~ Sep 5)
+        *   Freeze: Sep 5 ~ Sep 9 (waiting for 1.16 release)
+        *   Next: dev-1.15-ko.6, dev-1.16-ko.1 (Sep 9 ~ )
+    *   Kubernetes Forum Seoul 2019 (Dec 9-10)
+        *   @seokho-son is preparing for a proposal (~ Aug 31)
+*   Can deprecation warnings (set in config.toml) be overridden at the localization level? 
+    *   Luc Perkins has strong Hugo expertise
+    *   May not be possible to toggle deprecation per localization, but it is totally possible to localize deprecation warnings (layouts/shortcodes/deprecationwarning.html) to be accurate about maintenance per each localization
+
+**8/20/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @kbarnard (thanks for stepping in at the last minute!)
+*   Next week’s PR wrangler is @zparnold (replacing @jaredbhatti)
+
+Agenda
+
+
+
+*   Docs
+    *   JD & deprecated flag
+        *   Zach C: I realize I hand-waved you off to test-infra without much guidance on adding a new label
+        *   Check out [https://github.com/kubernetes/test-infra/pull/9835](https://github.com/kubernetes/test-infra/pull/9835) 
+*   Release notes formatting?
+    *   [Jennifer will investigate]
+*   Kubecon 2019 SIG Workshop(Barnie)
+    *   we're looking for Session and Workshop submissions for pre-programmed sessions([https://forms.gle/6tgMmJ4sYHJ4CDxy9](https://forms.gle/6tgMmJ4sYHJ4CDxy9)) - Team will not have/participate or prepare the workshop but will do Meet and Greet.
+    *   SIG Meet and greet ([https://forms.gle/hxx1qz8XtwtXEBMm8](https://forms.gle/hxx1qz8XtwtXEBMm8))
+        *    Cody will lead, Zach will attend
+*   [aimee] Pain Points Survey [https://github.com/kubernetes/website/issues/15828](https://github.com/kubernetes/website/issues/15828)
+*   Third-party content: are we truly neutral? [cody] [https://github.com/kubernetes/website/pull/15919](https://github.com/kubernetes/website/pull/15919)
+*   Style Guide PR - guidelines for removing third-party content: [https://github.com/kubernetes/website/pull/15892](https://github.com/kubernetes/website/pull/15892)
+*   Umbrella issue for removing third-party content: [https://github.com/kubernetes/website/issues/15748](https://github.com/kubernetes/website/issues/15748)
+*   1.16 release update (Vineeth): 
+    *   Aug 23 placeholder PR deadline
+        *   On track
+*   Etiquette for requesting PR reviews
+    *   Once every 7 days drop into #sig-docs
+    *   and/or once every 7 days ping existing reviewers
+    *   Would be great to add this to the style guide :-) 
+    *   Savitha will add a PR to the style guide
+
+**8/13/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Savitha Raghunathan
+
+Updates/reminders
+
+
+
+*   This week’s [PR wrangler](https://github.com/kubernetes/website/wiki/PR-Wranglers) is @xiangpengzhao (Peter)
+*   Next week’s PR wrangler is @zhangxiaoyu-zidif (Tim)
+
+Agenda
+
+
+
+*   Docs
+    *   (JD) Proposal for handling deprecated content
+        *   [https://docs.google.com/document/d/1pMkSQuiFAbxIP9FxJJRiTPwrpbOqWbOvE26YbWPiQbE/edit?usp=sharing](https://docs.google.com/document/d/1pMkSQuiFAbxIP9FxJJRiTPwrpbOqWbOvE26YbWPiQbE/edit?usp=sharing) 
+        *   Can we resolve this with a new repo label/Prow command? (/deprecated)
+        *   Flag into @mentions for SIGs and content authors
+        *   Create an issue template for deprecated content
+        *   Different kinds of obsolescence:
+            *   Completely taken down
+            *   Outdated code sample
+            *   No longer best practice
+    *   Pain point discovery
+        *   Brad: results on Twitter?
+            *   (Brad) [https://stackoverflow.com/search?tab=newest&q=kubernetes%20answers%3a3%20views%3a1000](https://stackoverflow.com/search?tab=newest&q=kubernetes%20answers%3a3%20views%3a1000)
+            *   Revisit on 8/20
+        *   Seth, Simon?
+    *   Survey (Aimee U.)
+        *   Proposal [https://github.com/kubernetes/website/issues/15828](https://github.com/kubernetes/website/issues/15828)
+        *   Revisit on 8/20
+    *   Style guide & third party content
+        *   Context: [https://github.com/kubernetes/website/issues/15576](https://github.com/kubernetes/website/issues/15576)
+        *   No dual-sourced content from anyone
+        *   No links to content outside kubernetes/kubernetes-sigs or the CNCF
+*   [PR wranglers](https://github.com/kubernetes/website/wiki/PR-Wranglers) & approvers (Zach C)
+    *   Some folks have been unresponsive for a while, and Google’s involvement has scaled back considerably
+    *   Will Google folks be filling their PR wrangler shifts?
+    *   PR wrangling is the one real responsibility we ask of approvers
+        *   Audit at end of September
+        *   Slackbot to remind folks
+*   SIG Docs Chair changes (Jared B)
+    *   Planning on stepping down as SIG-Docs Chair End of September
+*   Bad certificates
+    *   (Luc) More to say about proposal/DNS? (Revisit 8/20)
+    *   k/k8s.io
+*   Issue triage: how’s it going?
+    *   REVIEW: Cody will write issue for how to deal with dual-hosted tutorial content, Brad/Steve/Zach will review (8/20)
+*   Slow page serving from East Asia
+    *   Flagged to CNCF, waiting on internal response
+
+**8/6/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Aimee Ukasick (@aimeeu)
+*   Abhinav.Korpal
+*   Nono
+*   Savitha
+*   Welcome back, Jared!
+
+Updates/reminders
+
+
+
+*   This week’s [PR wrangler](https://github.com/kubernetes/website/wiki/PR-Wranglers) is @zacharysarah
+*   Next week’s PR wrangler is @xiangpengzhao (Peter)
+
+Agenda
+
+
+
+*   Docs
+    *   (Zach C) Pain point discovery
+        *   1. Find pain points
+        *   2. Open an issue with a link to specific pain point
+    *   1 week volunteers: Seth, Brad, Simon Forster (check in 8/13 on results)
+*   Bad certificates
+    *   (Luc) More to say about proposal/DNS? (Revisit 8/13)
+*   Issue triage: how’s it going?
+    *   (Cody C) Issues are lots of requests for support, Katacoda bugs
+    *   Zach C will provide support request boilerplate
+    *   Katacoda: Remove Katacoda text and link to it instead
+    *   Assign remaining Katacoda issues to @BenHall
+    *   Cody will write issue for how to deal with dual-hosted tutorial content, Brad/Steve/Zach will review (8/13)
+*   Slow page serving from East Asia
+*   (JD) Proposal for handling deprecated content
+    *   [https://docs.google.com/document/d/1pMkSQuiFAbxIP9FxJJRiTPwrpbOqWbOvE26YbWPiQbE/edit?usp=sharing](https://docs.google.com/document/d/1pMkSQuiFAbxIP9FxJJRiTPwrpbOqWbOvE26YbWPiQbE/edit?usp=sharing) 
+    *   Review on 8/13, place early on agenda
+
+**7/30/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @ryanmcginnis
+*   Next week’s PR wrangler is @zacharysarah
+
+Agenda
+
+
+
+*   Highlights from [Q2 review/Q3 planning](https://docs.google.com/document/d/10EFtv-DEIaMStLjWNiGgmLTJMG6UGY0iEOcPTfJLplY/edit#)
+    *   We’re focusing on documentation pain points in Q3.
+    *   Call to action:
+        *   Find pain points on Stack Overflow, Disqus, and other sources
+        *   Open issues in k/website to report them with links
+    *   Chair goals through end of year: completely document the chair role and make it possible for new folks to step into the role
+*   Site is serving bad certificates for deprecated/deleted branches: [https://github.com/kubernetes/website/issues/12303](https://github.com/kubernetes/website/issues/12303)
+    *   (Zach C) Will reach out to netlify and find what it would take to return a 410 instead of a bad certificate
+*   Issue triage leads
+    *   We need issue triage!
+    *   We decided in April to actively pursue issue triage, but life happened and all the folks who agreed to do it have stepped away.
+    *   Jdpalomino, jaypipes, codyc
+*   Slow page serves from China
+    *   Zach C will talk to CNCF about site registration with China
+    *   (Tim B) Might there be firewall issues since this was last fixed?
+*   (Ryan McG) Good open source citizenship
+    *   Thanks everyone for being conscientious <3 
+*   (Luc) Issue 14332: how to resolve legacy content for 3rd party content
+    *   How should we remove that content?
+    *   JD: Will write a design doc proposing how to flag content for deprecation, to be removed during a community day/doc sprint/someone with extra time & energy :-)
+*   (Jay Pipes) 
+
+**7/23/2019**
+
+**7pm Pacific - Fourth Tuesday**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @tengqm [Confirmed]
+*   Next week’s PR wrangler is @ryanmcginnis
+*   [Q2 quarterly review & Q3 planning meeting](https://docs.google.com/document/d/10EFtv-DEIaMStLjWNiGgmLTJMG6UGY0iEOcPTfJLplY/edit#): Thursday, 25 July at 5pm Pacific
+
+Agenda
+
+
+
+*   Docs
+    *   Controller guide update needs review! Work with @sftim: [https://github.com/kubernetes/website/pull/15373](https://github.com/kubernetes/website/pull/15373) 
+*   (Seth) Link checker updates, if any?
+*   Korean team update
+    *   No membership update but meaningful number of contributors are getting interest in docs l10n after the local event, Open Infrastructure & Cloud Native Days Korea 2019.
+    *   Two team milestone branches are merged
+        *   dev-1.15-ko.1 (merged to master, Jul 10)
+        *   dev-1.14-ko.6 (merged to release-1.14, Jul 23)
+    *   Current and next team milestones
+        *   Current: dev-1.15-ko.2 (Jul 9 ~ Jul 25 KST)
+        *   Next: dev-1.15-ko.3 (Jul 26 ~ Aug 8 KST)
+    *   Changed Ko l10n team online meeting schedule from weekly Tuesday 22:00 to biweekly Thursday 22:00 (KST)
+        *   Currently the team is posting meeting records to [personal playlist](https://www.youtube.com/playlist?list=PLAOP7m08QDCWZ7RwGca6cU4vzrOMw3ht7). Is there better place to post them?
+            *   Can you confirm that you’re using Zoom to host meetings?
+
+**7/16/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Sam Marder
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @bradamant3, who's likely to get to the queue on the late side
+*   Next week’s PR wrangler is @tengqm
+*   Q2 review/Q3 planning is on Thursday, July 25, 5-8pm Pacific
+    *   Make [agenda proposals](https://docs.google.com/document/d/10EFtv-DEIaMStLjWNiGgmLTJMG6UGY0iEOcPTfJLplY/edit#heading=h.ghlki2544yp0)
+
+Agenda
+
+
+
+*   Docs
+    *   Think about which sections to work on next for kubeadm
+        *   Look at Stack Overflow for “desire lines”, actual exhibited behavior about folks’ docs needs and pain points -- any volunteers?
+        *   Jennifer AI find other volunteers
+*   (Seth) Link checker [update](https://kubernetes.slack.com/archives/C1J0BPD2M/p1562689035218300)
+    *   Maybe add a “broken links” tag, to expedite issues/PRs with broken links
+    *   Sharing the load, @lucperkins (and anyone else) are welcome to help
+    *   Investigating -  [https://github.com/raviqqe/liche](https://github.com/raviqqe/liche) - seems to work decent, may fall over under load, still investigating
+    *   Update: “No update” :( 
+*   (Jay Pipes) LFG update?
+    *   From 7/2/2019: Jay Pipes: Looking for folks wanting to pair on PR for removing cluster directory in k/k
+    *   (jaypipes): Sorry, no update from me. Still working on this and will try to have a curated list of items for others to take on at next meeting.
+*   (Kaitlyn) [Blog process overview ](https://github.com/kubernetes/community/tree/master/sig-docs/blog-subproject)
+    *   See team list in doc for assigning blog post PRs
+    *   Greater sig-docs team can review and approve minor updates; only new content needs review by editorial team
+    *   See also dedicated Slack channel (#kubernetes-docs-blog)
+*   [PR 15373](https://github.com/kubernetes/website/pull/15373)
+    *   Comments about direction welcome
+    *   Also ideas for how to break down into manageable chunks (106 files!)
+
+**7/9/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is @zparnold
+*   Next week’s PR wrangler is @bradamant3
+*   Jennifer will run next week’s meeting
+*   Q2 review/Q3 planning is on Thursday, July 25, 5-8pm Pacific
+    *   Make [agenda proposals](https://docs.google.com/document/d/10EFtv-DEIaMStLjWNiGgmLTJMG6UGY0iEOcPTfJLplY/edit#heading=h.ghlki2544yp0)
+
+Agenda
+
+
+
+*   Docs
+    *   (Jennifer) No kubeadm update
+    *   Think about which sections to work on next
+        *   Look at Stack Overflow for “desire lines”, actual exhibited behavior about folks’ docs needs and pain points
+*   (Seth) Link checker [update](https://kubernetes.slack.com/archives/C1J0BPD2M/p1562689035218300)
+    *   Maybe add a “broken links” tag, to expedite issues/PRs with broken links
+*   PR queue is much better this week. Thanks for closing out assigned PRs!
+*   (Jay Pipes) LFG update?
+    *   From 7/2/2019: Jay Pipes: Looking for folks wanting to pair on PR for removing cluster directory in k/k
+    *   (jaypipes): Sorry, no update from me. Still working on this and will try to have a curated list of items for others to take on at next meeting.
+
+**7/2/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Jay Pipes
+*   Vinay Amaranathan
+*   Abhinav Korpal
+
+Updates/reminders
+
+
+
+*   Q3/Q4 PR wrangler schedule is up: [https://github.com/kubernetes/website/wiki/PR-Wranglers](https://github.com/kubernetes/website/wiki/PR-Wranglers) 
+*   This week’s wrangler is @cody-clark (June 30)
+*   Next week’s wrangler is @zparnold (July 7)
+*   Happy to announce that Jim Angel is a shadow for SIG Docs chair
+*   Q2 review/Q3 planning is on Thursday, July 25, 5-8pm Pacific
+
+Agenda
+
+
+
+*   Docs
+    *   Start thinking about what we want to accomplish in Q3
+    *   [https://github.com/kubernetes/website/projects/3](https://github.com/kubernetes/website/projects/3) 
+    *   (Jennifer) Any input on kubeadm setup?
+    *   [https://docs.google.com/document/d/10EFtv-DEIaMStLjWNiGgmLTJMG6UGY0iEOcPTfJLplY/edit#](https://docs.google.com/document/d/10EFtv-DEIaMStLjWNiGgmLTJMG6UGY0iEOcPTfJLplY/edit#)
+        *   Jay Pipes can reach out to SIG Cluster lifecycle about current state of cluster API vs. kubeadm setup
+        *   Jim, Brad, Jay, Jennifer: Cluster API still very alpha-state, kubeadm docs still needed
+        *   Jennifer: Will create a plan to move forward by Q3 planning
+*   Open PRs
+    *   (Zach C) A lot of fresh ones in English, but a lot of older ones too--let’s resolve what we can, close the others, and get the queue down to size.
+    *   AI: add tips on closing PRs to guide somewhere?
+        *   Zach C: We need to add better guidelines for closing to [https://kubernetes.io/docs/contribute/advanced/#be-the-pr-wrangler-for-a-week](https://kubernetes.io/docs/contribute/advanced/#be-the-pr-wrangler-for-a-week) 
+*   Brad Topol on KubeCon Shanghai:
+    *   “Death or glory”! 
+    *   Rui Chen translated slides: awesome! 
+    *   New contrib workshop content, plus more for deep dive
+    *   Indonesian l10n folks, Chinese l10n folks showed up to help
+    *   ~18-20 people
+*   (Jay Pipes): What’s the etiquette for asking for PR reviews?
+    *   @mention the team’s PR review
+    *   Ask them in Slack
+    *   Mailing lists may not get a quick response
+*   (Simon Forster) Update on English review pool for i18n questions?
+*   (Seth McCombs) Link checker update?
+    *   Found 3 different tools, running them each to see what they find
+    *   Scans take time
+    *   Poor/unstable internet while traveling is slowing efforts
+    *   Manual step to one of “Contributing to the docs” pages?
+    *   Jim: Link checkers are more for validity; need an external resource checker as well, if we care about running the site offline
+*   Running Hugo locally? 
+    *   Anyone able to run locally with success? [https://github.com/kubernetes/website/issues/15245](https://github.com/kubernetes/website/issues/15245)
+*   Jay Pipes: Looking for folks wanting to pair on PR for removing cluster directory in k/k 
+
+**6/25/2019**
+
+**7pm Pacific - Fourth Tuesday APAC meeting**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   This week’s PR wrangler is Kaitlyn Barnard (@kbarnard10)
+*   We’re still making the schedule for PR wranglers in Q3/Q4, hopefully an update by next week.
+*   Happy to announce that Jim Angel is a shadow for SIG Docs chair 
+*   Q2 review/Q3 planning meeting is July 25th, 5pm Pacific 
+
+Agenda
+
+
+
+*   (Paris) San Diego contributor summit
+    *   Defer to next week
+*   Docs updates:
+    *   [https://github.com/kubernetes/website/projects/3](https://github.com/kubernetes/website/projects/3) 
+    *   Follow up with Jennifer about kubeadm docs from project card
+        *   Review during Q2/Q3 meeting
+*   (June Yi, Claudia Kang) Korean team update?
+    *   No membership update
+    *   Running two team milestone branches temporarily 
+        *   dev-1.15-ko.1 -> master
+        *   dev-1.14-ko.6 -> release-1.14
+    *   Called for a new single point of contact: no volunteer
+        *   June Yi remains as a contact point
+    *   PTAL: [#14787](https://github.com/kubernetes/website/pull/14787)
+    *   Kaitlyn & Zach: Can we boost visibility for Korean and other localization teams?
+*   Japanese team update?
+    *   No attendees
+*   Chinese team update?
+    *   Happy KubeCon! Zach is sorry to miss you this week.
+*   (Seth McCombs) Link checker update?
+    *   No progress this week, update next week
+*   (Qiming) PR queue update--looks better now?
+    *   Seeing some old PRs for English
+*   (Simon Forster) Update on English review pool for i18n questions?
+
+    	Defer to next week
+
+
+**6/18/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Tunde Oladipupo
+*   Josiah (@josiahbjorgaard)
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: Steve Perry (@steveperry-53)
+*   PR wrangler next week: Kaitlyn Barnard (@kbarnard10)
+*   Need PR wranglers schedule for Q3/Q4
+    *   Automate? Do it by Thursday :-) 
+*   (Barnie) 1.15 updates?
+    *   We are trying figuring out how to resolve conflicts in dev1.15 [https://github.com/kubernetes/test-infra/issues/13065](https://github.com/kubernetes/test-infra/issues/13065)
+    *   I have proposed Tunde to be docs Lead for next release. He has been a docs Shadow for the past 2 releases.
+    *   Zach C: will add Barnie & Jim as ICs with write permissions so they can work directly with branches to resolve merge conflicts
+
+Agenda
+
+
+
+*   Docs progress: [https://github.com/kubernetes/website/projects/3](https://github.com/kubernetes/website/projects/3) 
+*   Q2 review, Q3 planning (Zach C)
+    *   When should we meet? Mid-July? Late July?
+        *   Meeting on Thursday, July 25th, same time slot but 1 hour earlier
+        *   [Zach C] Agenda doc for Q2/Q3 and make it available for input at least 2 weeks in advance
+*   jimangel - I can't recall, do we have anyone looking into broken links / adding in redirects? With the updated layout, some links that return from google are broken - see: https://kubernetes.slack.com/archives/C0SJ4AFB7/p1560874030038300. Does anyone know if we can re-index the site for google? 
+    *   [Seth] Looking into a link checking tool and re-indexing the site from Google
+    *   Will be ongoing effort - Jim
+    *   PR that shook a few things up: [https://github.com/kubernetes/website/pull/14826](https://github.com/kubernetes/website/pull/14826)
+
+**6/11/2019**
+
+**10:30am Pacific**
+
+New contributors 
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: Cody Clark @cody-clark
+*   PR wrangler next week: Steve Perry
+*   (Barnie) 1.15 updates?
+    *   All PR associated with enhancements for this release are merged.
+    *   
+
+Agenda
+
+
+
+*   (cody-clark) 
+    *   Analytics Reports 
+        *   Have access to K8s analytics and can create reports
+        *   Need explicit permission from CNCF to proceed
+        *   Does each localization effort already have a mailing list? 
+            *   To not spam kubernetes-sig-docs@googlegroups.com
+    *   Page Satisfaction Survey ([#11037](https://github.com/kubernetes/website/pull/11037))
+        *   Highlight: [/docs/tutorials/kubernetes-basics/](https://kubernetes.io/docs/tutorials/kubernetes-basics/) (83% found helpful)
+        *   Lowlight: [/zh/docs/home/](https://kubernetes.io/zh/docs/home/) (49% found helpful)
+    *   Cloud Provider-specific info on the [Service Concept page](https://kubernetes.io/docs/concepts/services-networking/service/) 
+
+**6/4/2019**
+
+**10:30am Pacific**
+
+New contributors 
+
+
+
+*   Chris Simpson (Open Bank, 6 months into K8s)
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: Cody Clark @cody-clark
+*   PR wrangler next week: Ryan McGinnis
+*   (Barnie) 1.15 updates?
+    *   Jennifer AI to find right resources to help with branch PR that merges from master
+
+Agenda
+
+
+
+*   Simon Forster is wondering how native English speakers can help to the localization efforts. After some brainstorming, we maybe can have a pool of native speakers to assist on complex localizations, doubts, helping to rephrase english, clarify concepts, etcetera.
+    *   Bilingual contributors are important to bridge those gaps
+    *   Also willing native-English only contributors to help l10n teams figure out original meaning
+        *   Contacts on other sigs too
+        *   Volunteers: Steve Perry, Simon Forster
+            *   Include useful changes in contribution/style guidelines
+            *   Develop a more formal role for this work?
+    *   What can we do after the first onboarding / commit?
+        *   Ongoing support of their journey (releases, branching, etc)
+            *   How to keep contributors interested, involved
+        *   Which concepts to translate -- prioritize, but also which need to stay in English. Glossary/word list of terms. Gender problems
+        *   Coordinate with effort to rework Concepts topics -- look at GH Projects for priorities -- Jennifer AI to reach out to l10n leads with this information, also look for external l10n expertise, resources
+        *   Working group?
+        *   Planning l10n retrospective
+    *   **Bring this topic up during the next 2 sig-docs meetings (APAC + regular post kubecon)**
+*   Onboarding new contributors: l10n a specific case, how to improve ongoing commitment
+*   Analytics data for specific translations? AI: make sure we have access all the time. Cody will also see what he has access to.
+
+**5/28/2019**
+
+**(APAC) 7pm Pacific**
+
+New contributors 
+
+
+
+*   Seth
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: Tim Zhang @zhangxiaoyu-zidif
+*   PR wrangler next week: Cody Clark @cody-clark
+*   (Barnie) 1.15 updates?
+    *   We are pushing people to continue creating placeholder PR by 30th here are the one opened [https://github.com/kubernetes/website/milestone/32](https://github.com/kubernetes/website/milestone/32)
+
+Agenda
+
+
+
+*   Simon Forster is wondering how native English speakers can help to the localization efforts. After some brainstorming, we maybe can have a pool of native speakers to assist on complex localizations, doubts, helping to rephrase english, clarify concepts, etcetera.
+    *   Bilingual contributors are important to bridge those gaps 
+    *   What can we do after the first onboarding / commit?
+        *   Ongoing support of their journey (releases, branching, etc)
+    *   **Bring this topic up during the next 2 sig-docs meetings (APAC + regular post kubecon)**
+*   (June Yi) Ko l10n update:
+    *   New Ko reviewer(Seokho), New K8s Member mainly contribute to Ko l10n(nowjean)
+    *   June 11 ~ 18: Pause Ko l10n PR merge, waiting for release-1.15(June 17)
+    *   June 19: Elect new Ko l10n leader who will be a single point of contact with upstream. (currently June Yi)
+
+    (@Qiming): Suggestion for PR wrangler: 200 PRs accumulated during the past 2 weeks, not good. Should contact the scheduled wrangler next time and see if he/she would be available. Someone else can step in if the schedule needs some fixes.
+
+
+    	AI: Jim: check with cody clark
+
+
+    (@Seth McCombs) PR merged causing dead links, what can we do to stop this? Seth offered to 
+
+*   
[https://github.com/kubernetes/website/issues/14220](https://github.com/kubernetes/website/issues/14220)

+*   
[https://github.com/kubernetes/website/pull/14442](https://github.com/kubernetes/website/pull/14442)

+*   [https://github.com/kubernetes/website/issues/14466](https://github.com/kubernetes/website/issues/14466)
+*   (@qiming) in general we should not have a lot links to the source code, right?
+*   Suggestions:
+    *   (Jim) Could try: Sig Docs Tools Slack Channel [https://kubernetes.slack.com/messages/sig-docs-tools/](https://kubernetes.slack.com/messages/sig-docs-tools/)
+    *   (Qiming) Raja started efforts to clean up dead links
+        *   **AI:** Seth to pair up to coordinate efforts
+
+**5/21/2019**
+
+**10:30am Pacific**
+
+New contributors 
+
+
+
+*   Simon Forster
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: Peter Zhao @xiangpengzhao
+*   PR wrangler next week: Tim Zhang @zhangxiaoyu-zidif
+*   (Barnie) 1.15 updates?
+    *   Nothing much we are still getting folks to open their draft PR as we are approaching the deadline for that.
+
+Agenda
+
+
+
+*   Simon Forster is wondering how native English speakers can help to the localization efforts. After some brainstorming, we maybe can have a pool of native speakers to assist on complex localizations, doubts, helping to rephrase english, clarify concepts, etcetera.
+    *   Bilingual contributors are important to bridge those gaps 
+    *   What can we do after the first onboarding / commit?
+        *   Ongoing support of their journey (releases, branching, etc)
+    *   **Bring this topic up during the next 2 sig-docs meetings (APAC + regular post kubecon)**
+*   Cody Crudgington: examples (tech preview)
+    *   Stricter guidelines when PRing tech examples to prevent a simple image/tag switch (vs full deployment test)
+    *   Dani_C gap in testing?
+        *   Could add testing - is it too heavy compared to # of issues? -Jim 
+*   Dani_C Naming node schemes in email
+    *   More folks with history jump in on thread on naming nodes
+    *   Link: [https://groups.google.com/forum/#!topic/kubernetes-sig-docs/tBtFGieqX7k](https://groups.google.com/forum/#!topic/kubernetes-sig-docs/tBtFGieqX7k) 
+
+**5/14/2019**
+
+**10:30am Pacific**
+
+New contributors 
+
+
+
+*   Erick Carty
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: @tfogo (?)
+*   PR wrangler next week: @xiangpengzhao
+*   (Barnie) 1.15 updates?
+    *   Zach can approve a PR to this file: [https://github.com/kubernetes/org/blob/master/config/kubernetes/sig-docs/teams.yaml#L258](https://github.com/kubernetes/org/blob/master/config/kubernetes/sig-docs/teams.yaml#L258)
+    *   Adding release leads/shadows to milestone team: great addition for handbook!
+
+Agenda
+
+
+
+*   Content
+    *   (Steve Perry, JD Palomino) Issues/PRs for every topic in Concepts/Overview: how’s that going?
+        *   How to add issues to repo project?
+    *   What is Kubernetes page: Shavi’s working on it
+    *   Adding “CRD” definitions, better definition for addons (they’re a form of operators)
+    *   Dani: Spoke with SIG Cluster Lifecycle about replacing “masters/workers” with “control plane/peer compute”
+*   Availability
+    *   Conference season is starting, so is summer
+    *   Jared B is out on sabbatical until 1 August,  \
+Zach C will be at conferences/on vacation until 22 Jul
+    *   Jennifer Rondeau and Jim Angel will lead weekly meetings
+        *   Jennifer is out at conferences/work offsites 21 May, 4 June
+*   Version Skew / Docs [Jim A.]
+    *   [https://github.com/kubernetes/website/issues/14307](https://github.com/kubernetes/website/issues/14307)
+    *   [https://github.com/kubernetes/sig-release/issues/626](https://github.com/kubernetes/sig-release/issues/626)
+    *   Example: [https://www.kernel.org/](https://www.kernel.org/) 
+    *   Track this for Q3 in the Q2 planning doc: [https://docs.google.com/document/d/16po48F83oaQGC_BxeB7_k_RlhMzCdJD6wKYq4kpE-P8/edit#heading=h.ghlki2544yp0](https://docs.google.com/document/d/16po48F83oaQGC_BxeB7_k_RlhMzCdJD6wKYq4kpE-P8/edit#heading=h.ghlki2544yp0) 
+*   (Rael) Are subprojects/hosted subdomains based out of SIG Docs?
+    *   Jennifer/Zach C: Nope, we can consult but we don’t own it
+
+**5/7/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: @rajakavitha1 
+*   PR wrangler next week: @tfogo (Zach C will reach out)
+*   (Barnie) 1.15 updates?
+    *   We met with team of last friday May 3rd may and update the team on the important dates for this release and what is expected from the team 
+    *   We have divided the enhancement for each member to help followup with owners of the enhancements to have placeholder PR by 30th so these coming 3 weeks is to make sure we have all enhancements that needs docs have placeholder PR ready.
+    *   Team members 
+        *   Tunde Oladipupo(simplytunde@gmail.com) Slack/ simplytunde Github: simplytunde
+        *   Damini Satya Kammakomati(daminisatya@gmail.com) Slack/@Damini satya Github/ daminisatya
+        *   Christian Hernandez(christian.hernandez@yahoo.com) Slack/ christianh814 Github: christianh814 
+    *   We have opened the official 1.15 docs PR that will be merged on release date([https://github.com/kubernetes/website/pull/14176](https://github.com/kubernetes/website/pull/14176))
+
+Agenda
+
+
+
+*   Content
+    *   Review all existing content: 
+        *   Work with SIGs to determine whether info is current
+        *   Refactor content, apply style guide
+    *   Need issues/PRs for every topic in Concepts/Overview: [https://kubernetes.io/docs/concepts/overview/](https://kubernetes.io/docs/concepts/overview/)
+    *   Who’s willing to open issues and assign them to a project? [https://github.com/kubernetes/website/projects/3](https://github.com/kubernetes/website/projects/3) 
+        *   JD Palomino & Steve Perry will open concepts, Steve will start in Object Management, JD will start with topics at the top
+*   New contributor ambassadors
+    *   Zach Arnold (@zparnold), Shawn (@zhangqx2010), Brad Topol (@bradtopol)
+    *   How’s that going so far?
+*   Issue triage leads
+    *   @chenrui333, @codyc, @zhangqx2010, @dani_c
+    *   How’s that going so far?
+*   Accessibility: Shavi has slides to share (Cody Clark and Rajie)
+*   Kube scheduler docs: (JD Palomino) 
+*   Zach C: follow up with Paris/contribex on docs presence at community day
+
+**4/30/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: @bradtopol 
+*   PR wrangler next week: @rajakavitha1
+*   (Barnie) 1.15 updates?
+
+Agenda
+
+
+
+*   Blog subproject:
+    *   PR open to make it official:
+        *   [https://github.com/kubernetes/community/pull/3640](https://github.com/kubernetes/community/pull/3640) 
+        *   It’s merged! Yay!
+    *   Still needs to be done:
+        *   (Kaitlyn Barnard) Set up OWNERS and optional team(s):
+            *   [content/en/blog/OWNERS](https://github.com/kubernetes/website/blob/master/content/en/blog/OWNERS)
+            *   If needed: [kubernetes/org/config/kubernetes/sig-docs/teams.yaml](https://github.com/kubernetes/org/blob/d272559f45b76b3bb4b0304cd7b0a9517e97bfc3/config/kubernetes/sig-docs/teams.yaml)
+*   New contributor ambassadors
+    *   Almost there!
+*   Issue triage captains
+    *   @chenrui333, @codyc, @zhangqx2010, @dani_c
+    *   Goal of issue triage captains is a list of open issues where everything is actionable
+*   Running meetings
+    *   We need folks to run meetings, both 10:30am slots and 7pm slots. SIG Docs chairs will be absent/partially available for most of the summer.
+        *   Willing to provide guidance, opportunities to shadow before leading
+    *   Reach out to Zach C on Slack
+*   Demographics survey
+    *   Thinking about doing a SIG Docs member survey: who we are, job titles
+    *   Goal is to gain data about what 
+    *   (Steve Perry) We need both technical writers and people to apply the style guides
+        *   But we need tech writers dedicated to K8s/open source, at least 50%
+        *   Zach C: Support CommunityBridge for “doc bounty”
+*   Content
+    *   (Jim A) Boost visibility on this issue: [https://github.com/kubernetes/website/issues/13904](https://github.com/kubernetes/website/issues/13904) 
+        *   Inquire about best org for refdocs: kubernetes or kubernetes-sigs
+            *   @cblecker can point in the right direction
+        *   Feedback from Qiming 
+    *   This issue needs attention (currently STALE): [https://github.com/kubernetes/website/issues/12333](https://github.com/kubernetes/website/issues/12333) 
+*   Localization teams: approval for specific files at root level/outside content path?
+    *   June Yi will open issue; Zach C will review
+*   Sig Docs security is going well, and this week we are going to focus our efforts on the CVE management process (building out a place for people to put CVE’s and have them visible on Kubernetes.io)
+
+Need feedback from a security/Kubernetes expert on
+
+**4/23/2019**
+
+**7pm Pacific - 4th Tuesday APAC**
+
+New contributors
+
+
+
+*   Dan Roscigno (Elastic)
+
+Updates/reminders
+
+
+
+*   PR wrangler this week: @jaredbhatti (maybe @cody-clark)
+*   PR wrangler next week: @bradtopol
+*   (Barnie) 1.15 updates?
+
+Agenda
+
+
+
+*   Blog subproject:
+    *   PR open to make it official:
+        *   [https://github.com/kubernetes/community/pull/3640](https://github.com/kubernetes/community/pull/3640) 
+    *   Still needs to be done:
+        *   (Kaitlyn Barnard) Set up OWNERS and optional team(s):
+            *   [content/en/blog/OWNERS](https://github.com/kubernetes/website/blob/master/content/en/blog/OWNERS)
+            *   If needed: [kubernetes/org/config/kubernetes/sig-docs/teams.yaml](https://github.com/kubernetes/org/blob/d272559f45b76b3bb4b0304cd7b0a9517e97bfc3/config/kubernetes/sig-docs/teams.yaml)
+*   New contributor ambassadors
+    *   Almost there!
+*   Issue triage
+    *   We need folks willing to work through the issue backlog and identify high-priority issues (Cody C, Rui, Shawn)
+    *   We also need folks to identify good first issues and apply the label. (/good-first-issue)
+        *   Good first issues are issues that describe all of the work that needs to be done in a PR: no guessing, investigation, or research required. 
+*   Running meetings
+    *   We need folks to run meetings, both 10:30am slots and 7pm slots. SIG Docs chairs will be absent/partially available for most of the summer.
+        *   Willing to provide guidance, opportunities to shadow before leading
+*   Demographics survey
+    *   
+*   Content
+    *   Contributor cheatsheet localization [https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet](https://github.com/kubernetes/community/tree/master/contributors/guide/contributor-cheatsheet) (Rui will open issue for English, need separate issues for each localization)
+    *   We need help with this issue (probably 2 weeks-1` month of work) [https://github.com/kubernetes/website/issues/12333](https://github.com/kubernetes/website/issues/12333)
+    *   Pick the Right Solution 
+*   Localization teams: approval for specific files at root level/outside content path?
+    *   June Yi will open issue; Zach C will review
+*   Jim A: Boost visibility on this issue: [https://github.com/kubernetes/website/issues/13904](https://github.com/kubernetes/website/issues/13904) 
+*   Jim A: EOL for Fedv1 refdocs [https://github.com/kubernetes/website/issues/13905](https://github.com/kubernetes/website/issues/13905) 
+
+**4/16/2019**
+
+**10:30am Pacific **
+
+New contributors
+
+
+
+*   Cody - Professional services @ Sysdig, Austin k8s meetup
+
+Updates/reminders
+
+
+
+*   PR Wranglers: 
+    *   This week: Jennifer (@bradamant3)
+    *   Next week: Jared (@jaredbhatti)
+
+Agenda
+
+
+
+*   New Contributor Ambassador Role (Jared, Jennifer, Zach C)
+    *   [Draft doc - Feedback welcome](https://docs.google.com/document/d/10snlue28FL-hjmCuw1UEFubcWk5PohH3gXIOCONqSBw/edit#)
+    *   Cody: I think this is a good idea - I’m struggling with the same thing
+    *   Any volunteers to be members of this group? 
+        *   Brad T, Zach A, Tim
+*   Integrating Blog process with SIG-Docs process - any updates? (Kaitlin, Zach C)
+    *   AI: Jared: Kaitlin and Zach need to update
+    *   Brad: Please document the process
+*   Sig-docs-es- Updates? @raelga
+*   Sig Docs Security Updates? - Zach A
+
+**4/9/2019**
+
+**10:30am Pacific **
+
+New contributors
+
+
+
+*   Barnabas (barnie): Leading the Docs release this cycle - shadow the past two releases
+
+Updates/reminders
+
+
+
+*   Qiming (@tengqm) is PR wrangler this week
+*   Jennifer (@bradamant3) is the PR wrangler for next week
+    *   Would like to switch weeks - please reach out to Jennifer on Slack. 
+
+Agenda
+
+
+
+*   (Paris, Kaitlyn) Blog becoming a sub-project of SIG-Docs: Create an editorial team for blog review with an owner and lead as a sub-project of SIG-Docs
+    *   Kaitlyn Barnard would be the lead
+    *   TODOs: 
+        *   Zach C will add a label for blog issues, make sure it can be manually assigned
+        *   Zach C will adjust OWNERS file for content/en/blog/ in k/website
+        *   Kaitlyn: Write a README.md for content/en/blog outlining blog process file, link to blog rolebook in k/community
+        *   Kaitlyn: Set standards around when SIG-Docs maintainers should approve changes. 
+        *   Kaitlyn: Write a Meta-Blog Post on how the new blog process will work. 
+    *   [Notes for the project planning meeting are here](https://docs.google.com/document/d/1-XWPHvd-Y141JnOurLD6pyk50rJ_fwPQgjmYomB8_9Q/edit#heading=h.kjkuct5152l0)
+*   sig-docs-es
+    *   Spanish localization of the website is live.
+    *   New contributors are starting to help on the localization of the documentation.
+    *   The Spanish team is working on a style guide for the Documentation.
+    *   The localization progress is being tracked with http[://bit.ly/k8s-sig-docs-es-track](http://bit.ly/k8s-sig-docs-es-track) at this point.
+    *   @raelga is working with Ben Hall from Katacoda to help in the localization the labs of the kubernetes.io tutorials.
+*   Sig Docs Security (Zach A.) (Can’t attend, double booked sorry)
+    *   We have analyzed current docs and created a framework for thought going forward
+    *   I am experiencing the “unknown unknown” issues for which we may need broader community insight. There are some topics in Kubernetes security I’m not sure about, so we may need some expert consults, and would love suggestions from the team here for how to proceed. 
+    *   Jennifer: Has some folks in mind who can help.
+    *   Jared: Maybe Steve Perry would be a good choice? (I know he’s currently swamped, though). 
+        *   More information needed on how we can help and what all the open issues are. 
+
+**4/2/2019**
+
+**10:30am Pacific **
+
+New contributors
+
+
+
+*   Rael Garcia (@raelga)
+*   Angel Guarisma (@angelg)
+*   Leslie Salazar (@lsalazar)	
+*   Nathan Melehan (@nmelehan)
+*   Andy Stevens (@astevens)
+
+Updates/reminders
+
+
+
+*   Ryan McGinnis (@ryanmcginnis) is PR wrangler this week
+*   Q2 planning video is up: [https://www.youtube.com/watch?v=uIlU2vFJyqw](https://www.youtube.com/watch?v=uIlU2vFJyqw)
+    *   Wins to highlight: 
+        *   1.2 million page views per week! Up from 1 mil last quarter!
+        *   1.14 Release (thanks Jim Angel and all the shadows!)
+        *   2x number of localizations (French, Italian, German have been added!)
+    *   [Notes from the planning session are here](https://docs.google.com/document/d/16po48F83oaQGC_BxeB7_k_RlhMzCdJD6wKYq4kpE-P8/edit)
+        *   Q1 goals graded, Q2 goals proposed
+*   Spanish localization of the website almost ready
+    *   New slack channel #kubernetes-docs-es created to start the Spanish localization of the Documentation
+    *   Init PR started and channel started
+        *   https://github.com/kubernetes/website/pull/13543
+
+Agenda
+
+
+
+*   (Paris Pittman) Editorial teams for blog review
+    *   Who owns the content of the blog? 
+    *   SIG-Docs didn’t call out the content, only the tooling in our charter
+    *   What is the blog process in general? Doesn’t seem transparent
+    *   PROPOSAL: Create an editorial team for blog review with an owner and lead as a sub-project of SIG-Docs
+        *   Kaitlyn Barnard would be the lead
+        *   Vision:
+            *   Put together a team of editors with clear blog guidelines
+            *   Rotations for blog editors
+            *   AI: Put out a call to folks in SIG-Docs and SIG-Contribx to help
+            *   AI: Create proposal for managing blog content, Jaredb, Katlyn, Paris, Cody, Zach  - Jared will set up initial meeting
+
+**3/26/2019**
+
+**7pm Pacific - Fourth Tuesday**
+
+New contributors
+
+
+
+*   
+
+Updates/reminders
+
+
+
+*   1.14 docs are live! Thanks and congratulations, Jim Angel (@jimangel), Barney Makonda (@MAKOSCAFEE), Cody Clark (@cody-clark), Jared Bhatti (@jaredbhatti), Naomi Pentrel (@npentrel), and Tunde Oladipupo (@simplytunde)!
+*   Misty Linville (@mistyhacks) is PR wrangler this week.
+*   Q2 planning meeting is Thursday, March 28, 6-9pm Pacific. [https://docs.google.com/document/d/16po48F83oaQGC_BxeB7_k_RlhMzCdJD6wKYq4kpE-P8/](https://docs.google.com/document/d/16po48F83oaQGC_BxeB7_k_RlhMzCdJD6wKYq4kpE-P8/) 
+
+Agenda
+
+
+
+*   (Zach C) New community role coming soon: New Contributor Ambassador
+    *   Do we need issue triage captains? Context: [https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md](https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md) 
+*   KubeCon Shanghai (June)
+    *   How many people planning to attend? (5)
+*   Doc Sprint 
+    *   (Rui) depends on the backlog tasks
+    *   (Zach) Will work with Julia to set questionnaire and find deadline for questionnaire
+    *   (Julia) Will the CNCF provide the same incentive for attendance as Nov 2018? Zach will confirm.
+    *   Zach: Will follow up with CNCF to make sure we’re funded for dev headcount for better refdoc generation: DEFER discussion for two weeks (April 9)
+        *   Loop in Qiming Teng (K8s community is great; challenge is some libraries, not a simple problem to solve)
+
+**3/19/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   David Watson (@dwat)
+*   Barnie (shadows releases 1.13, 1.14)
+*   Suresh Palemoni (joining from Dubai)
+
+Updates/reminders
+
+
+
+*   Jared Bhatti (@jaredbhatti) is PR wrangler this week
+    *   Cody (@cody-clark) will cover first two days
+*   New API review process: [https://github.com/kubernetes/community/blob/master/sig-architecture/api-review-process.md](https://github.com/kubernetes/community/blob/master/sig-architecture/api-review-process.md) 
+*   Feedback request for K8s community etiquette cheat sheet: [https://github.com/kubernetes/community/pull/3213](https://github.com/kubernetes/community/pull/3213) 
+
+Agenda
+
+
+
+*   (Jim A) Update on 1.14
+    *   Help needed?
+*   (Craig/Zach C) Where will Windows docs live?
+    *   What’s the best path? /Setup/
+*   (Zach C) KubeCon Barcelona: We’ve got an intro/deep dive scheduled; do we also want time at the community day? 
+    *   Deadline to decide is April 1
+*   (Zach C) New community role coming soon: new contributor ambassador
+    *   Do we need issue triage captains? Context: [https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md](https://github.com/kubernetes/community/blob/master/contributors/guide/issue-triage.md) 
+*   (Chen Rui) Relative links in the website repo \
+	[https://github.com/kubernetes/website/issues/13231](https://github.com/kubernetes/website/issues/13231)
+*   (Dominik/Andrew) RBAC
+    *   Blog post [Inside Kubernetes RBAC](https://medium.com/@dominik.tornow/inside-kubernetes-rbac-9988b08a738a)
+*   (Dani Comnea) discuss the path for [https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/celery-rabbitmq](https://github.com/kubernetes/kubernetes/tree/release-1.3/examples/celery-rabbitmq) example
+*   Zach C/Suresh/Dani: Link to Q2 planning doc: [https://docs.google.com/document/d/16po48F83oaQGC_BxeB7_k_RlhMzCdJD6wKYq4kpE-P8/edit?usp=sharing](https://docs.google.com/document/d/16po48F83oaQGC_BxeB7_k_RlhMzCdJD6wKYq4kpE-P8/edit?usp=sharing) 
+
+**3/12/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Lots of familiar faces :-) 
+
+Updates/reminders
+
+
+
+*   @cody-clark is PR wrangler this week
+    *   ...but check your assigned PRs! https://github.com/kubernetes/website/pulls
+*   Quarterly planning meeting on Thursday, 3/28, 6-9pm Pacific
+
+Agenda
+
+
+
+*   Q2 planning: co-chairs meeting this week to set agenda.
+    *   What should we talk about?
+    *   New stuff: new K8s features, docs coverage for new features, how new features fit in the big picture of docs (thanks, Brad and Jennifer!)
+*   Content review
+    *   SIG-level review, let’s talk about implementation details offline
+*   Use `feature-state` shortcodes in future releases
+    *   Context: [https://github.com/kubernetes/website/pull/12915#issuecomment-470768767](https://github.com/kubernetes/website/pull/12915#issuecomment-470768767)
+    *   Valid feature states: alpha, beta, deprecated, stable \
+[https://github.com/kubernetes/website/blob/master/layouts/shortcodes/feature-state.html#L1](https://github.com/kubernetes/website/blob/master/layouts/shortcodes/feature-state.html#L1) 
+    *   Where’s the best place to document that developers should use `feature-state`?
+        *   k/website PR template
+        *   k/enhancements repo PR template?
+        *   PR guideline checklist/cheatsheet
+    *   Add “introduced” to feature set
+*   Season of Docs (jaredb) - unfortunately, I can’t be at the meeting - but I want folks to know about this. 
+    *   Information launched here: [https://developers.google.com/season-of-docs/](https://developers.google.com/season-of-docs/)
+    *   Would be good for K8s to participate
+    *   2 Admins and 2 mentors are needed
+    *   Applications open in early april, close in late april
+*   SigDocsSec (Zach A.)
+    *   Our first meeting will be this week or next to get feedback on goals and set timelines...I am very excited!!!
+    *   Possibly get a channel in Slack maybe? I don’t know who to ping on this or if it’s even worth it
+    *   Starting with a survey of security concerns
+    *   Who’s the audience, how do you target them effectively?
+        *   (Jim Angel) Suggest adding actionable items (or links to them) to the end of each conceptual section
+*   No kube-scheduler documentation (#12609)? (JD)
+    *   Needed to run out early, but pls feel free to reach out to me if someone has some ideas. It’d be great just to be able to sit down with a sig-scheduling member to hammer something out
+    *   Steve: Kube-scheduler docs are autogenerated; if content is obsolete, place to fix it upstream in k/k
+*   Improving auto generation (Zach A)
+    *   Can we smooth out this process overall?
+    *   Build on Qiming’s existing work?
+*   We’re using the free version of Travis?!
+    *   Move to prow?
+    *   Dani will talk to sig-test-infra about migrating to Prow
+
+**3/5/2019**
+
+**10:30 am Pacific**
+
+New contributors
+
+
+
+*   Dani Comnea
+*   Suresh Kumar Palemoni
+
+Updates/reminders
+
+
+
+*   Zach C (@zacharysarah) is listed as PR wrangler this week -- Jennifer will check in when he's back (OOO today and tomorrow) and cover in the meantime
+*   [Write the Docs speakers announced](https://www.writethedocs.org/conf/portland/2019/news/announcing-speakers/). Time to buy your tickets if you plan to attend (note conflict with KubeCon Barcelona)
+*   U.S. is on Daylight time starting next week, so meeting times elsewhere around the globe that don't adjust (or don't adjust at the same time) will be an hour earlier
+*   (Zach A. can't attend) SIG-Docs security working group is still going on the sign up link is here: [https://goo.gl/forms/RE0bwxw3axH20y2P2](https://goo.gl/forms/RE0bwxw3axH20y2P2)
+    *   The goals of the group can be found in Slack, first meeting to hopefully occur this week
+
+Agenda
+
+
+
+*   (Dominik) Is Kubernetes really a declarative system? [[slides](https://docs.google.com/presentation/d/1ne0z2oH_x-ojQphLlxxT5EdjIx_pGp66ZaLR51rJZUg/edit?usp=sharing)]
+    *   Fundamental Modeling Working Group -- continue discussion of how we disrupt the terminology of "declarative" Kubernetes effectively in the docs
+    *   Working group meets Fridays @ 10 am Pacific, [Hangouts Meet](https://meet.google.com/spm-jota-twn) [[notes](https://docs.google.com/document/d/1VCMdsRGyCViWta7l1c7Hji77ha1_vSYqihrb4MrS96A/edit?usp=sharing)]
+*   (Jim Angel) 1.14 and docs
+    *   [http://bit.ly/k8s114-enhancements](http://bit.ly/k8s114-enhancements)
+*   (Steve) for next week, reminder/report on issues in [GH Project for the quarter](https://github.com/kubernetes/website/projects/3)
+
+**2/26/2019**
+
+**7pm Pacific**
+
+New contributors
+
+
+
+*   None yet :-( 
+
+Updates/reminders
+
+
+
+*   Zach A (@zparnold) is PR wrangler this week.
+
+Agenda
+
+
+
+*   (Zach C) Q2 planning meeting: 28 March, 6-9pm Pacific
+    *   I’ll send out invitations this week
+*   (Ben Elder) Update on kind docs subdomain: “the kind experiment is going excellently so far and that hopefully we can scale this out pretty easily”
+    *   Context: [https://github.com/kubernetes/k8s.io/issues/189#issuecomment-465884240](https://github.com/kubernetes/k8s.io/issues/189#issuecomment-465884240) 
+*   Chen Rui: How’s 1.14 going?
+    *   Cody gave an update, things are going well and according to plan.
+*   Chen Rui: Will there be a doc sprint at Shanghai?
+    *   Zach C: Yes, in the main track. But we can do a longer community day too.
+*   Brad: Getting started on [https://github.com/kubernetes/website/issues/12333](https://github.com/kubernetes/website/issues/12333)
+    *   Working on a PR, wants lots of feedback, will solicit feedback in Slack
+    *   Seeking help/collaboration for another PR
+*   June Yi: Local meetup next week
+    *   Working on 1.13 branching
+    *   Final iteration will be 8th (currently on 7th)
+*   Tamao: Interested in accessibility
+    *   Zach C: Will follow up with Rajie
+    *   Tamao: Will follow up with Rajie’s imminent draft
+
+        [Rajie] - Shared the draft with Cody Clark on Feb 27, 2019. Cody is helping in adding relevant examples to the guidelines for Level A compliance.
+
+
+**2/19/2019**
+
+**10:30am Pacific**
+
+New contributors
+
+
+
+*   Soheila (Munich)
+
+Updates/reminders
+
+
+
+*   Rajie is wrangling this week 
+
+Agenda
+
+
+
+*   Zach C: Set a date for our 2Q planning meeting: 3/28, 6-9pm
+    *   Check in with Brad
+*   Zach C: SIG Cloud Provider needs someone with good info architecture and organization skills to review their template for cloud provider information: [https://github.com/kubernetes/enhancements/pull/827](https://github.com/kubernetes/enhancements/pull/827)
+*   Rui: Interested in talking about Transifex (translation software) with other localization teams [https://docs.google.com/document/d/12vUq51yeeAPlldM4P_aEY3VUSi37YVeVfD_TfzzkGGQ/edit?usp=sharing](https://docs.google.com/document/d/12vUq51yeeAPlldM4P_aEY3VUSi37YVeVfD_TfzzkGGQ/edit?usp=sharing) 
+*   Zach A: Discuss potential for a sig docs security working group (I recall that I am carrying the flag for documenting security in more detail...and aggregating information related to KubeSec)
+    *   There is a lot of information here, and I wanted to open it up to other contributors who are interested in participation.
+    *   ng in security stuff. I have a rough implementation plan, but security is a team sport.
+    *   +1 from Luc: adding support for security is a high demand
+    *   +1 from Steve: there’s good security documentation, but it may be hard to find
+    *   +1 from Jennifer: We need a better story for securing a cluster, and for security as a whole
+*   Brad T: KubeCon Shanghai - Is anyone else besides me going? Are we doing a doc sprint or a main track intro/deep dive session, or a session at Contributor Day?
+    *   Action Item:: Zach will write the main track request for Shanghai by Feb 26.
+*   Jim Angel: Update on 1.14?
+    *   Docs release playbook will be ready for review soon, merge-ready PR due by end of next week (Mar 1)
+    *   Handbook WIP (to be “ready to merge” in the next few days): https://github.com/kubernetes/sig-release/pull/498
+    *   Release notes: Dave Strebel, Jeffrey Sica
+
+**2/12/2019**
+
+**10:30am Pacific**
+
+New contributors 
+
+
+
+*   Remy Leone (French!)
+
+Updates/reminders
+
+
+
+*   Zach Arnold (@zparnold) is PR wrangler this week, and Rajie (@rajakavitha1) is shadowing
+
+Agenda
+
+
+
+*   Craig Peters: Guidance for [Windows Container docs](https://drive.google.com/open?id=1a2bRd7PZXygIEm4cEcCeLXpEqJ7opakP_j4Pc6AJVYA) - best method to convert a GDoc to properly formatted md
+    *   Zach: Etherpad? Maybe, but GooDoc UX is really handy
+    *   Jennifer: There’s a useful plugin for GooDoc to Markdown ([GD2M](https://chrome.google.com/webstore/detail/export-as-markdown/hbojhdcnbcondcdfpfocpkjkfkbnbdad?hl=en-US))
+*   Juan Diego: Could we get some updated docs for the kube-scheduler?
+    *   JD will write up an issue
+    *   Zach will help boost signal to get 1:1 time with SIG Scheduling if needed
+*   [Zach C] Match PRs to Issues
+*   [Zach C] Issues in To Do project: https://github.com/kubernetes/website/projects/3
+
+**2/5/2019**
+
+New contributors
+
+
+
+*   
+
+Agenda
+
+
+
+*   Announcements: We are losing Andrew (not altogether, but still :-() But he is going to awesome OSS docs work.
+*   Mentorship (from last week)
+*   Updates to content projects: [Steve] I'll be late, around 11:00. This is the last time I need to be late.
+    *   @juandiegopalomino is updating the [ReplicaSet concept topic](https://kubernetes.io/docs/concepts/workloads/controllers/replicaset/). The [PR](https://github.com/kubernetes/website/pull/12409) is almost ready to be merged. This update brings several improvements to the topic, including an explanation of how owner references link Pods to a ReplicaSet. @codyclark has a [PR](https://github.com/kubernetes/website/pull/12409) that creates two new Ingress topics and updates one existing Ingress topic. @dtornow and I will work on an update to the [Deployment concept topic](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/). In the Deployment topic, we will include a prototype of a controller fact sheet. The idea is that each controller topic would have a fact sheet that gives the essence of the controller's behavior in a concise form.
+    *   Controller fact sheets [Dominik]
+*   Netlify [Jennifer] -- looks as though the Korean dev branch is now set up
+*   [Andrew, Dominik] WIP: "Kubernetes in 15 minutes" presentation. Kubernetes is a robot. Or a genie. Or both!
+
+**1/29/2019**
+
+**10:30am PST**
+
+New contributors
+
+
+
+*   Alex Ball (tech writer from Canada)
+*   Craig Peters, Microsoft PM (interested in docs, support for Windows containers/new node type)
+
+Updates/Reminders/Housekeeping
+
+
+
+*   Approvers, take a look at the [PR wrangler schedule](https://github.com/kubernetes/website/wiki/PR-Wranglers)
+
+Agenda
+
+
+
+*   [Steve] I'll be late to the meeting, around 11:00. If the meeting is still going when I connect, I'd like to ask about [this issue](https://github.com/kubernetes-incubator/reference-docs/issues/49). Also, I'd like to put in a request for people to take ownership of the issues in [this project](https://github.com/kubernetes/website/projects/3). Several of the issues have owners; thank you! We still need owners for these:
+*   [Need top-level Controllers concept guide](https://github.com/kubernetes/website/projects/3)
+*   [Update Deployment concept topic](https://github.com/kubernetes/website/issues/12082)
+*   Let’s consider mentorship--actively mentoring first and new contributors; let’s revisit this next week (2/5)
+*   [Zach] SIG chairs are looking at how to mentor our own replacements (for some eventual day). If you’re an approver who’s possibly interested in being a chair for SIG Docs, let us know!
+*   [Zach] Netlify: Still working on site setup for Korean dev branch
+*   [Craig] 
+
+**1/22/2019**
+
+**7pm PST - Fourth Tuesday **
+
+New contributors
+
+
+
+*   JD Palomino (joined us from KubeCon)
+*   Seokho Son (welcome back!)
+
+Updates/Reminders/Housekeeping
+
+
+
+*   [Zach C] I’m back! 
+    *   Creating new PR wrangler schedule this week (draft by Friday)
+*   [Jim A] 1.14 Release team update
+    *   Shadows selected (slack)
+        *   codyclark
+        *   jaredb
+        *   barnie
+        *   naomi
+        *   simplytunde
+    *   Main goal of creating playbook
+
+Agenda
+
+
+
+*   [Steve] Please take a look at these issues in [this project](https://github.com/kubernetes/website/projects/3). Several of the issues still need owners. (Brad will take #12081)
+*   [Jim] @tfogo recommended getting in touch with the l18n owners early as part of the release cycle - do we have a preferred / recommended contact list?
+    *   Owners file
+    *   Sig-docs channel
+    *   TODO [jim]: open issue, cc other localization members in advance.
+*   [Jim] @bentheelder is looking for direction on sig-docs involvement with sub projects that are still “k8s community projects.” The main outcome is for Ben to create his website in a sig-docs approved manor. This approach can be used for other sub projects in the future. Depending on availability this can be postponed until next week.
+    *   [Zach C] Loop in Alex Contini on theme development/portability
+    *   Talk about sharing netlify in sig-docs-tools
+    *   Can we create standards for standing up sig-specific project sites?
+*   [Andrew] @Rui reported some broken translation links. Wanted to follow up on this since he's at the meeting.
+*   [Seokho] Netlify Setup issue for dev-1.13-ko.*
+    *   Zach C will set up a Korean branch 
+    *   Look into granular permissions
+*   [Rajie] Persistence of language selection? 
+    *   Talk with sig-docs-tools about language persistence
+    *   Side issue: Who owns this site? [https://kubernetes-csi.github.io/docs/Home.html](https://kubernetes-csi.github.io/docs/Home.html)
+    *   [https://github.com/containernetworking/cni](https://github.com/containernetworking/cni) 
+    *   @chenopis will contact Saad Ali
+        *   Saad Ali said the content is still under development and needs to be rewritten, so it may make sense to leave them there for now. They need some help w/ content review and edits, so I suggested he come to one of the SIG Docs meetings.
+        *   FYI, Michelle Au ([msau@google.com](mailto:msau@google.com)) is also involved in the CSI effort.
+
+**1/15/2019**
+
+**10:30am PST**
+
+New contributors
+
+
+
+*   Seokho Son 
+*   Dan Roscigno 
+
+Updates / Reminders / Housekeeping
+
+
+
+*   [Jared] [PR Wranglers](https://kubernetes.io/docs/contribute/advanced/#be-the-pr-wrangler-for-a-week) needed - need to be an approver
+    *   1/15: Brad 
+    *   1/22: Tim
+    *   1/29: Based on rotations
+
+Agenda
+
+    New items:
+
+
+
+*   [Jim/Jared] 1.14 Launch kickoff
+    *   Finalizing the 1.14 list in the next week
+    *   Shadows - survey sent out - please respond!
+        *   [https://www.surveymonkey.com/r/k8s-114-rt-shadows](https://www.surveymonkey.com/r/k8s-114-rt-shadows) 
+*   Items from Q1 planning
+    *   [Steve] I will miss today's meeting. But I have listed the writing tasks that I think should be our focus for Q1. See [https://github.com/kubernetes/website/projects/3](https://github.com/kubernetes/website/projects/3). So far, two of the tasks have owners. Cody Clark will own updates to the Ingress topics. Jennifer will own updates to the kubeadm setup topic(s). The other four tasks are up for grabs. Of course, we can discuss and adjust the list.
+    *   [Jim] localization issues with predefined english shortcodes
+        *   [https://github.com/kubernetes/website/issues/12160](https://github.com/kubernetes/website/issues/12160)
+        *   AI: talk to Andrew re: option 0 (consensus) - Jared
+    *   [Jim] Can we merge the bump to the new hugo version? (.49 - .52)
+        *   [https://github.com/kubernetes/website/pull/11552](https://github.com/kubernetes/website/pull/11552)
+
+**1/8/2019**
+
+**10:30am PST**
+
+New contributors
+
+
+
+*   
+
+Updates and Reminders
+
+
+
+*   Welcome back and Happy New Year!
+
+Agenda
+
+    New items:
+
+
+
+*   [Jared] Meeting notes
+*   [Shavi] whitespace on user journeys pages
+    *   What's the status of entry pages redesign? (Andrew, Cody, ??) [PR 10795](https://github.com/kubernetes/website/pull/10795)
+    *   AI: Shavi - will sync with Andrew on CSS location. 
+    *   AI: Jared will sync with Andrew on User Journey pages, but will be looking at content 
+*   [Jennifer] OWNERS for l10n: how do we want to handle the need for translation teams to submit PRs for their languages to files at root of repo? See [PR #11581](https://github.com/kubernetes/website/pull/11581) for an example issue.
+*   [Dominik] ReplicaSet Controller model update
+    *   OwnerReferences!
+*   [Steve] I will miss today's meeting. But I have listed the writing tasks that I think should be our focus for Q1. See [https://github.com/kubernetes/website/projects/3](https://github.com/kubernetes/website/projects/3). So far, two of the tasks have owners. Cody Clark will own updates to the Ingress topics. Jennifer will own updates to the kubeadm setup topic(s). The other four tasks are up for grabs. Of course, we can discuss and adjust the list.
+*   [Jared] Who are the shadows for the upcoming launch? (Jim?)
+
+ 
+
+   Ongoing/previous items:
+
+
+
+*   [Misty] PR Wrangling, Configure stale issues bot
+    *   Bot’s current configuration needs to be improved.
+    *   Why do we stale-out issues after 90 days? Organization’s defaults
+    *   In GH: A PR is a type of issue, stale-bot shouldn’t close these
+    *   AI: We should create a doc that guides issue triage, response time, priorities
+*   [Jim] 1.14 release meister / shadow
+    *   Steven Augustus sent out last call for shadows: Cody Clark, Jared Bhatti are current shadows
+    *   Shadows: Working to write up a guide for future release meisters
+*   Community redesign: last call for feedback?  [https://cjyabraham.gitlab.io/community](https://cjyabraham.gitlab.io/community)
+*   [Andrew] Kubecon Planning and Feedback 
+    *   [Planning Document](https://docs.google.com/document/d/12lgT9usnk2vEKb9Fvnz2stXBZ35xvx8yEPTJDhwicic/edit#)
+        *   Q1 planning - let’s check in on these regularly during meetings starting next year - Steve volunteers to work on this.
+        *   AI: Jennifer will get an agenda up with the Q1 goals
+        *   Overall feedback: Felt more concrete, let’s do a short one again for Q2 and a longer one for Q3-4. 
+    *   Need to make a decision (in Jan) about pwittrock’s kubectl content. 
+        *   Make sure it aligns with our overall content strategy
+        *   It’s likely SIG-Docs will have some level of ownership in the future, let’s figure that out early. 
+    *   Paris/Misty: We welcome more help at the Diversity lunch next year
+        *   Jared: I’m interested in helping out at an upcoming conference
+*   AIs:
+    *   AI: We should create a doc that guides issue triage, response time, priorities
+    *   AI: Jennifer will get an agenda up with the Q1 goals for our first meeting of the year.
diff --git a/sig-docs/meeting-notes-archive/README.md b/sig-docs/meeting-notes-archive/README.md
new file mode 100644
index 00000000..333ec923
--- /dev/null
+++ b/sig-docs/meeting-notes-archive/README.md
@@ -0,0 +1,13 @@
+# Archiving meeting minutes
+
+At the beginning of each year, archive the old Google docs into this repo to improve the performance of the current doc.
+
+### Convert meeting minutes into markdown:
+
+1. Make sure you have a document (new or exisiting) with exactly the content you wish to store.
+2. Install [Docs2Markdown](https://github.com/evbacher/gd2md-html/wiki#using-docs-to-markdown)
+3. Open up Google Doc > Add-ons > Docs2Markdown > Convert [Markdown] (taking the unselected defaults)
+4. Select the output and paste into a document
+5. Add the new document to this repository
+
+> Message #sig-docs on slack if you need help!