Skip to content

Instantly share code, notes, and snippets.

💭
Catching up and prepping for Kubecon Shanghai

Josh Berkus jberkus

💭
Catching up and prepping for Kubecon Shanghai
Block or report user

Report or block jberkus

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile
@jberkus
jberkus / draft-mc-questions.md
Last active Oct 4, 2019
Draft SIG-MC Survey Questions
View draft-mc-questions.md

This survey is intended to gauge the level of interest and adoption in current and prospective SIG-Multicluster tools and projects. Your answer here will help SIG-Multicluster determine future plans and decide on deprecation schedules. Your identifying information will be shared only with the SIG-Multicluster chairs, the survey administrators at the CNCF, and the survey assistant (Josh Berkus). Other answers will be shared in anonymized, aggregate form in SIG meetings. You may ask for your data to be deleted at any time by contacting the SIG-Multicluster chairs.

  • *Your Name [ short answer ]
  • *Your Email
  • Organization Name
  • *Organization Type Please select the type of organization that most closely matches what yours does, or (for large organizations) what the part of the organization that you work in does.
    • End-User: run Kubernetes for our own internal use
    • Provider/Host: run Kubernetes clusters for customers to use
@jberkus
jberkus / survey-questions-2019-c.txt
Created Sep 25, 2019
Draft survey questions for 2019 Contributor Survey
View survey-questions-2019-c.txt
It would be useful to have this list of questions in a GiST or other doc
ok - i modified and left comments for all of the questions we asked last year. Please take a look.
1- How long have you been contributing to Kubernetes?
* less than one year
* one to two years
@jberkus
jberkus / ask-sigs.md
Last active Aug 19, 2019
SIG solicitation for 2019 CS SD
View ask-sigs.md

Hi, I'm ____ and I'm a member of the Event Team for the upcoming Contributor Summit in San Diego, on November 18th. I wanted to make sure that your SIG/WG knew about it, because there are several things we'd like you to participate in.

First, we're looking for Session and Workshop submissions for pre-programmed sessions. These are sessions for three of the rooms that will be submitted and picked in advance; we're looking not just for presentations, but for discussions, and hands-on workshops or code reviews. Submit them through this form, before September 9th:

https://forms.gle/6tgMmJ4sYHJ4CDxy9

We need your SIG/WG to send some folks to talk to contributors about participating in your SIG/WG. Please have your group's representative(s) complete the form below so that we can send them additional details closer to the date.

https://forms.gle/hxx1qz8XtwtXEBMm8

View gist:1967d98314e45e86b45a2138b1f6cf6d
* Explain in detail what "joining a SIG" means. Differentiate formal org membership from informal SIG membership. Sig Leadership is official.
* Can't have SIG meet-and-greet in China, Barcelona
* SIG buttons -- have them.
* Testgrid confusing? We need full end-to-end build, local test, push PR, testgrid. Do demo walkthrough. Verify that Sen Lu will be in China. Build & Test container, figure out how to distributed.
* Better Labels & Owners content?
* Listing of contributor resources/Tour
* Chinese communitcations: Chinese Discuss, Wechat? Not much activity, so people don't participate.
* GoPath troubleshooting session? Peer-to-Peer timeslot for troubleshooting in China? Would need a couple people to commit. Peer-to-peer VPN setup for China?
* Create USB distribution of many things, like Pulp files. Also ask maybe about Harbor portlable? Jorge to get Harbor folks from China. Josh to check with CNCF.
* translate the contributor docs -- contact Zack? Cheatsheet/contributor guide, maybe translate it
@jberkus
jberkus / Kubernetes-Shanghai-Cihinese.pdf
Last active Dec 1, 2018
Gist to hold PDF copies of the new contributor workshop
View Kubernetes-Shanghai-Cihinese.pdf
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
@jberkus
jberkus / gist:087289b542a12b76693b171ccf25a453
Created Jul 18, 2018
Notes from NIST Container Security Standards Talk: OSCON 2018
View gist:087289b542a12b76693b171ccf25a453
Elsie Philips and Paul Burt, CoreOS/RedHat
NIST container security standards
=================================
Elsie & Paul
in 2017 NIST issued a report on containers
wanted to explain security concerns and make recommendations
63 pages long
@jberkus
jberkus / gist:807fcf4d4d484dca02079f29aa4a3865
Created Jul 18, 2018
Notes from VM Brasseur's Open Sourcing Internal Projects talk OSCON 2018
View gist:807fcf4d4d484dca02079f29aa4a3865
Open Sourcing an Internal Project
VM
Author of fossforge.com (book in beta)
Releasing software is just the start. If you want to get stuff, throwing code over the wall won't get you it. Guides you find for "how companies OSS" are too generic, you need to figure out what's specific to your company.
Slides: archive.org/details/oscon2018-internalproject
View 111sched.md
What Who APR MAY JUN JUL DEV WEEK TEST GATES
Start of Release Cycle Lead 2 week 1
Finalize Schedule Lead 4
Begin collecting planned work from SIGs Lead, Features Lead 9 week 2
Begin weekly release team meetings Lead 10
Begin weekly status reports at Community Lead, Shadow 12
Finalize Release Team Lead 15
Start Release Notes Draft Release Notes Lead 17 week 3
@jberkus
jberkus / bug_triage.md
Last active Jan 18, 2018
Very Draft Bug Triage Role Description
View bug_triage.md

Bug Wrassler Release Team Role

Your job for the release is to make sure that bugs (issues) and their related PRs which affect the release are dealt with in a timely fashion. In general, you will be polling bugs, checking status, sending reminders and questions to contributors and SIG leads, and publishing summary reports.

Secondarily, you will be helping improve automation around issue management and release tagging.

How this works depends on where you are in the release cycle. There are five relevant periods where your workload changes:

  1. Early Release: between Feature Freeze and a week before Code Slush.
@jberkus
jberkus / kube_dev_summit.md
Last active Dec 5, 2017
Kube Dev Summit Notes
View kube_dev_summit.md

Steering Committee Update

Showed list of Steering Committee backlog.

We had a meeting, and the two big items we'd been pushing on hard were:

  • votining in the proposals in the bootstrap committee
  • how we're going to handle incubator and contrib etc.
You can’t perform that action at this time.