kubernetes
/
community
mirror of https://github.com/kubernetes/community.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
community/sig-docs/meeting-notes-archive/2019_Weekly_Meeting_Minutes.md

97 KiB
Raw Blame History

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

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 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

Agenda

  • Release 1.17 update
  • 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
  • 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
  • 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
    • 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’. (Vanou Ishii)
  • Rob: I need some Hugo / how-is-this-table-generated help ? :-D
  • 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

Agenda

  • Release 1.17 update
  • 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 or 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

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

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

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

Agenda

  • Docs:
  • 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
  • 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
    • 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

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
  • 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

Agenda

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/
    • Better UX: Zach C is working with contractors to apply the Docsy Hugo template to the website. 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)?
      • We did, courtesy of @sftim: https://github.com/kubernetes/enhancements/pull/1327
      • Kubernetes Repository Guidelines 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
      • request for contributor patches for the speakers

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

Agenda

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
    • Zach C will ask in Slack for a replacement for @chenopis in week of October 27

Agenda

  • Docs:
  • 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
      • 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

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

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

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 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 - might be useful to include examples of each of these in our triage documentation for SIG-Docs. 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
      • 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
  • Layout(?)
    • [Rob K / Tim B] Sortable, filterable tables
      • Rob will update the issue with a summary
      • Zach suggested that @kbarnard10 might be able / willing to help
  • Community
  • Tooling

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
      • 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)
    • 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
      • 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 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/). 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
  • Community
  • Site engineering
  • 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
    • 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

8/13/2019

10:30am Pacific

New contributors

  • Savitha Raghunathan

Updates/reminders

  • This week’s PR wrangler is @xiangpengzhao (Peter)
  • Next week’s PR wrangler is @zhangxiaoyu-zidif (Tim)

Agenda

  • Docs
  • 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 is @zacharysarah
  • Next week’s PR wrangler is @xiangpengzhao (Peter)

Agenda

  • Docs
    • (Zach C) Pain point discovery
        1. Find pain points
        1. 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

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
    • 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
    • (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

Agenda

  • Docs
  • (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. 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

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
    • 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 - 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
    • 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
    • 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

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
    • 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
  • 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
  • Open PRs
  • 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?
  • 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:

  • (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
    • 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
    • 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

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

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?

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/pull/14442


  • https://github.com/kubernetes/website/issues/14466

  • (@qiming) in general we should not have a lot links to the source code, right?

  • Suggestions:

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

5/14/2019

10:30am Pacific

New contributors

  • Erick Carty

Updates/reminders

Agenda

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
    • We have opened the official 1.15 docs PR that will be merged on release date(https://github.com/kubernetes/website/pull/14176)

Agenda

  • Content
  • 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:
  • 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
  • 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

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
    • 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
  • 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 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

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/

Agenda

  • (Zach C) New community role coming soon: New Contributor Ambassador
  • 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

Agenda

3/12/2019

10:30am Pacific

New contributors

  • Lots of familiar faces :-)

Updates/reminders

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
  • Season of Docs (jaredb) - unfortunately, I can’t be at the meeting - but I want folks to know about this.
  • 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. 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
    • The goals of the group can be found in Slack, first meeting to hopefully occur this week

Agenda

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”
  • 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
    • 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
  • Rui: Interested in talking about Transifex (translation software) with other localization teams 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 - 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)
  • 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. The PR 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 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. 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

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. Also, I'd like to put in a request for people to take ownership of the issues in this project. Several of the issues have owners; thank you! We still need owners for these:
  • Need top-level Controllers concept guide
  • Update Deployment concept topic
  • 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. 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?

1/15/2019

10:30am PST

New contributors

  • Seokho Son
  • Dan Roscigno

Updates / Reminders / Housekeeping

  • [Jared] PR Wranglers needed - need to be an approver
    • 1/15: Brad
    • 1/22: Tim
    • 1/29: Based on rotations

Agenda

New items:

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
    • 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 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. 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
  • [Andrew] Kubecon Planning and Feedback
    • Planning Document
      • 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.