Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2018 Kubernetes SIG Docs Summit #8116

Closed
zacharysarah opened this issue Apr 17, 2018 · 4 comments
Closed

2018 Kubernetes SIG Docs Summit #8116

zacharysarah opened this issue Apr 17, 2018 · 4 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/docs Categorizes an issue or PR as relevant to SIG Docs.

Comments

@zacharysarah
Copy link
Contributor

zacharysarah commented Apr 17, 2018

About the Summit

9 May 2018, 9:30am-4pm, 5-7pm dinner/drinks
Portland, OR, USA CENTRL Office Pearl (three blocks from Write the Docs)

Our first-ever summit for Kubernetes docs! Our goals for this summit are:

  • Get to know each other
  • Set our priorities for the rest of 2018

Why it matters

Setting shared priorities for the year helps us focus our time and energy effectively. Clear priorities let us say yes to the projects that move us closer to our goals.

While a globally distributed team has advantages and flexibility, this is an opportunity to get to know each other as more than faces on a screen.

Agenda

Time Activity
9:30am Kickoff at CENTRL Office Pearl
10am-11am Get to know each other
11am-12:00pm Set values, mission, strategy:
- Who we are
- What we do
- Why we do it
12:00pm-1:30pm Lunch
1:30pm-2:30pm Initiatives from CNCF:
- Specific projects that derive from these initiatives
3pm-4pm Start, Stop, Continue:
- What should the team start doing?
- What should the team stop doing?
- What should the team continue doing?
4pm-5pm Free time before dinner
5pm-7pm Dinner w/ Drinks @ Tilt
@zacharysarah zacharysarah added P2 sig/docs Categorizes an issue or PR as relevant to SIG Docs. labels Apr 17, 2018
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jul 29, 2018
@fejta-bot
Copy link

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Aug 28, 2018
@fejta-bot
Copy link

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

@k8s-ci-robot
Copy link
Contributor

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/docs Categorizes an issue or PR as relevant to SIG Docs.
Projects
None yet
Development

No branches or pull requests

3 participants