155 KiB
155 KiB
| 1 | Respondent ID | Collector ID | End Date | Contributing Length | Level of Contributor Laddor | Interested in next level? | World Region | Time Zone | Contribute to other OSS? | Blocker: Code/Doc review | Blocker: Communication | Blocker: GH tools&processes (not our customized tooling) | Blocker: Finding a/the right SIG | Blocker: Our CI, labels, and crafted customized automation | Blocker: Debugging test failures | Blocker: Finding issues to work on | Blocker: Setting up dev env | Blocker: Having PRs rejected | Useful: /retest of flakes (fejta-bot) | Useful: labeling of stale issues (fejta-bot) | Useful: issue commands like /assign, /kind bug (k8s-ci-robot) | Useful: PR commands like /approve, /lint (k8s-ci-robot) | Useful: merging of approved PRs (k8s-merge-robot and k8s-ci-bot) | Least Useful Tool/Something that needs to be automated | current notification volume and utility | Which areas could use additional automation? | Upstream supported at employer? | How often do you contribute upstream (code, docs, issue triage, etc.)? | Contribute: code to k/k | Contribute: code in a k/* GH org | Contribute: Docs | Contribute: Testing and CI | Contribute: Events&Advocacy | Contribute: Community & PM; SIG Chair etc. | Contribute: Plugins & Drivers (CSI, CNI, cloud providers) | Contribute: Related projects (Kubeadm, Helm, container runtimes, etc.) | Contribute: Not yet | Contribute: Other | Make project easier to contribute? | Attended: KC EU 2017 | Attended: KC NA 17 | Attended: KC EU 18 | Attending: KC CN 18 | Attending: KC NA 18 | Attending: KC EU 19 | Attended: Ecosystem events, eg. Helm Summit | Attended: Other confs with a Kubernetes track (like DockerCon or ContainerDay) | Does not attend conferences | How to make ContribSummits more valuable? | Attended: # of ContribSummits | Useful@ThursMtg: Demo | Useful@ThursMtg: KEP | Useful@ThursMtg: DevStats | Useful@ThursMtg: Release | Useful@ThursMtg: SIG Updates | Useful@ThursMtg: Announcements | Useful@ThursMtg: Shoutouts | Misc Thurs Mtg feedback | Most Important Project: Mentoring programs | Most Important Prj: GH Mgmt | Most Important Proj: Contributor Summits | Most Important Proj: Contributor Site | Most Important Proj: CommPlatform Consolidation/other options | Most Important Proj: DevStats | Most Important Proj: Keeping community safe | What projects are missing? | Generic Project Groupings from BN | Use freq: Google Groups/Mailing Lists | Use freq: Slack | Use freq: discuss.kubernetes.io | Use freq: Zoom Mtgs | Use freq: GH (comments, issues, prs) | Use freq: Unofficial(Twitter, Reddit, etc.) | Use freq: SO | Use freq: YT Recordings | Use freq: GDocs/Forms/Sheets, etc (meeting agendas, etc) | Check for news: k-dev ML | Check for news: discuss.kubernetes.io | Check for news: contribex ML | Check for news: Slack | Check for news: Twitter read first | Check for news: A dedicated contributor site read first | Check for news: Kubernetes blog read first | Check for news: k/community repo in GH (Issues and/or PRs) read first | Check for news: Other | Value in Slack? | HelpWanted &/or GoodFirstIssue label usage? | HelpWanted&GoodFirstIssue Other Comments | Interetested in mentoring GSoC or Outreachy? | Watched or participated in MoC? | Is MoC useful? | Mentoring Blocker? |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2 | 10249522900 | 216437765 | 10/01/2018 2:16:15 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+03:00 | 2-4 | 1 | 4 | 1 | 1 | 1 | 1 | 5 | 2 | 2 | 1 | n/a | 1 | n/a | n/a | So far haven't been able to use most of the commands, since org membership process has met some issues. | Lots of notifications but they are useful | Pinging reviewers to either approve or disapprove PRs and issues. | Yes, it’s part of my job | Several times a month | Core code inside of kubernetes/kubernetes | n/a | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | I would have time to contribute, but so far me asking for things to do has met only silence on Slack channels. Would be nice if mentoring would be set up. | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 1 | 1 | 4 | 2 | 4 | 4 | 4 | 2 | N/A | 1 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 4 | 5 | 2 | 3 | 5 | 1 | 1 | 3 | 5 | n/a | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Other (please specify): | At SIG Node the labels aren't really used. | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 3 | 10248186342 | 216437765 | 09/30/2018 10:00:19 AM | Just started | I’m not an org member yet, but working on it | Yes, but not sure I have time. | Europe | UTC+01:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 4 | 10247634817 | 216437765 | 09/29/2018 9:53:32 PM | 1-2 years | Approver | Yes, but not sure I have time. | North America | UTC-08:00 | 2-4 | 3 | 1 | 4 | 4 | 2 | 2 | 3 | 4 | 2 | 1 | 1 | 1 | n/a | 1 | /lgtm triggers /approve if I’m an approved? Madness! A weaker action should not trigger a stronger action based on my social status. | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | Don’t know | Yes, it’s part of my job | Several times a month | n/a | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | Use Gerrit | Kubecon Europe 2017 | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 1 | 2 | 4 | 4 | 4 | 4 | 5 | 5 | N/A | n/a | 2 | n/a | 4 | n/a | n/a | 7 | Better, clearer documentation that’s organized | Better contributor documentation | 3 | 5 | 1 | 5 | 4 | 2 | 1 | 1 | 5 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week |
| 5 | 10247081052 | 216437765 | 09/29/2018 7:54:55 AM | 2-3 years | Approver | Yes, doing it on my own. | North America | UTC+06:00 | 2-4 | 2 | 4 | 2 | 1 | 4 | 2 | 1 | 1 | 1 | n/a | n/a | n/a | 1 | 1 | fejta-bot, I have never seen it respark conversation | Way too many notifications with no benefits | Automation onboarding | No, but I’m able to use “free” time at work | A few times a week | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | n/a | 0 | 3 | 5 | 3 | 4 | 5 | 5 | 3 | No | n/a | n/a | n/a | 4 | n/a | n/a | n/a | N/A | 2 | 5 | 1 | 5 | 5 | 3 | 2 | 5 | 5 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 2 | Employer doesn't support spending time mentoring | |
| 6 | 10246592845 | 216437765 | 09/28/2018 11:06:00 PM | Just started | I’m not an org member yet, but working on it | Yes, but not sure I have time. | Asia | UTC+05:30 | None, Kubernetes is my first one! | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | NA | Lots of notifications but they are useful | An issue can have multiple PRs. But with current automation, issue gets closed if only one PR is closed. Need automation to check if all associated issues are closed and keep track of count. | No, but I’m able to use “free” time at work | A few times a week | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Could not think of any... | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | N/A | 1 | 2 | n/a | 4 | 5 | n/a | n/a | N/A | 3 | 3 | 1 | 1 | 5 | 2 | 2 | 5 | 3 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | A dedicated contributor site | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Other (please specify): | Didn't create issue | A - Yes, I would love to mentor one or both programs | No | 3 | Don't know enough to mentor | |
| 7 | 10246539346 | 216437765 | 09/28/2018 10:23:01 PM | 3+ years | Subproject Owner | Yes, but would like mentorship. | North America | UTC-05:00 | One more | 2 | 4 | 2 | 4 | 2 | 2 | 4 | 1 | 2 | 1 | n/a | 1 | 1 | 1 | n/a | Right notifications at the right frequency | non cloud infrastructure | Yes, it’s part of my job | A few times a year | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | n/a | n/a | n/a | 5 | 5 | 5 | n/a | It is already better. :) | n/a | n/a | n/a | n/a | 5 | n/a | 7 | N/A | 4 | 4 | 1 | 3 | 4 | 1 | 2 | 2 | 2 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) | |
| 8 | 10246240889 | 216437765 | 09/28/2018 8:03:43 PM | 3+ years | Approver | No, I'm already an owner | North America | UTC-03:30 | 4+ | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 9 | 10246162130 | 216437765 | 09/28/2018 7:29:33 PM | Less than 6 months | Approver | Yes, but not sure I have time. | North America | UTC-05:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 10 | 10246160102 | 216437765 | 09/28/2018 7:53:04 PM | Less than 6 months | Org Member | Yes, but would like mentorship. | North America | UTC-08:00 | None, Kubernetes is my first one! | 2 | 4 | 1 | 2 | 1 | 1 | 4 | 1 | 3 | 1 | n/a | 1 | n/a | 1 | n/a | Lots of notifications but they are useful | e2e tests | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | n/a | n/a | Testing & Infrastructure | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon China 2018 | Kubecon North America 2018 | n/a | n/a | n/a | n/a | i have to experience it first | 0 | 5 | 5 | 3 | 3 | 4 | 2 | 2 | have more feedback/discussion on PR, Pull request | 1 | n/a | 3 | n/a | n/a | 6 | n/a | deep dive of all components is needed | Deep Dives and Code Base Tour Videos/Content | 1 | 2 | 1 | 4 | 4 | 1 | 2 | 3 | 4 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | Kubernetes blog | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | A - Yes, I would love to mentor one or both programs | No | 1 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) |
| 11 | 10245935128 | 216437765 | 09/28/2018 6:25:08 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Asia | UTC+08:00 | One more | 4 | 5 | 4 | 3 | 4 | 3 | 3 | 5 | 3 | n/a | n/a | 1 | 1 | n/a | N/A | Right notifications at the right frequency | N/A | It’s entirely on my own time | Don’t know yet | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Don’t contribute yet, hoping to start soon | n/a | N/A | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | N/A | 1 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 3 | 3 | 3 | 3 | 3 | 1 | 3 | 2 | 3 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | A - Yes, I would love to mentor one or both programs | Yes | 3 | Other (please specify): | |
| 12 | 10243938380 | 216437765 | 09/27/2018 9:17:45 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+02:00 | One more | 3 | 3 | 2 | 3 | 2 | 4 | 4 | 2 | 4 | 1 | n/a | 1 | 1 | 1 | Auto target release assignment to PRs (to provide a priority in review/merge process) | Lots of notifications but they are useful | Dashboards | Finding a mentor | Navigating code base / dependencies -> documentation or visualization. | No, but I’m able to use “free” time at work | Several times a month | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | N/A | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | I did not participate in one yet. Happy to help during the next one in Europe. | 0 | 4 | 4 | 5 | 4 | 5 | 5 | 4 | At the beginning I thought there should be more context for new comers. Now I have mixed feelings, because that would promote being inclusive at the risk of becoming boring for regulars | 1 | 2 | n/a | 4 | n/a | n/a | n/a | A place where I can find the list of items contrib-experience is working on, a bit more detailed plans and scopes as well as the priorities driving their execution. | ContribEx proj mgmt | 4 | 5 | 2 | 4 | 3 | 2 | 2 | 3 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) |
| 13 | 10243887058 | 216437765 | 09/27/2018 8:34:56 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-07:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 14 | 10243855578 | 216437765 | 09/27/2018 8:22:50 PM | Just started | Had no idea this was even a thing | Not really | North America | UTC-04:00 | 4+ | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 15 | 10243848503 | 216437765 | 09/27/2018 8:37:14 PM | Less than 6 months | Org Member | Yes, doing it on my own. | North America | UTC-07:00 | None, Kubernetes is my first one! | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 1 | 2 | 1 | n/a | 1 | n/a | 1 | I think they're all useful. | Lots of notifications but they are useful | Can we have a tool to smartly detect whether a PR has unnecessary un-squashed commits? Like this one https://github.com/kubernetes/kubernetes/pull/68289 has 3 commits, but should be squashed into 1. It will make people question k8s's code quality (or process) when they see those non-sense commits in the main branch history. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | Advocacy and events | n/a | n/a | n/a | n/a | n/a | I think it's friendly enough to new contributors. | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 4 | 5 | 5 | 4 | 2 | 3 | 3 | No at this moment. | n/a | n/a | n/a | 4 | n/a | n/a | n/a | N/A | 2 | 5 | 1 | 2 | 5 | 2 | 1 | 1 | 2 | n/a | n/a | n/a | Slack | A dedicated contributor site | Kubernetes blog | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | Yes | 4 | Not enough time in the week | ||
| 16 | 10243846001 | 216437765 | 09/27/2018 8:39:44 PM | Less than 6 months | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-08:00 | 2-4 | 2 | 2 | 4 | 3 | 3 | 3 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | the /assign is a bit confusing. In here you need to assign to someone who is a org member.. However, in generic terms if i am working on a Issue then I would think I would /assign it to myself. I think the overall github workflow is my least favorite part. I would rather prefer something like gerrit frontend for reviews and merges. A lot of other open source projects use that mechanism. for .e.g openstack. And I think that is surely a much better way to do the review/rebase/merge process. | Right notifications at the right frequency | I think the current set of automation is fine. | Yes, it’s part of my job | A few times a week | n/a | n/a | n/a | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | no suggestions at the moment | n/a | Kubecon North America 2017 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Based on the one conference I did attend, I loved it | 1 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | nothing now | n/a | n/a | n/a | n/a | 5 | n/a | n/a | not sure at the moment | 3 | 5 | 1 | 4 | 4 | 1 | 1 | 3 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | Yes | 4 | Don't know enough to mentor | |
| 17 | 10243783540 | 216437765 | 09/27/2018 8:08:16 PM | 2-3 years | Subproject Owner | Yes, but not sure I have time. | North America | UTC-07:00 | 4+ | 5 | 5 | 3 | 3 | 4 | 5 | 4 | 5 | 1 | 1 | 1 | n/a | 1 | 1 | Disagreement on what some of the labels and process are, and the difference in how they are per project. | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | suggesting people to add as reviewers and approvers. We cannot bottleneck on the same 7 or so people. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | Make it easier to get permissions to do things. Make it easy to have people help other people and get to the point where the have the permissions. We're having massive sprawl because it's easier to do things outside of the project than it is to do it inside. | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | I think they're good. | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | I stopped showing up after the 40th version of "here's how we at XYZ company install kubernetes" | 1 | 2 | n/a | n/a | n/a | 6 | n/a | GETTING MORE PEOPLE INTO REVIEWERS/APPROVERS. | Reviewer and Approver Growth | 5 | 5 | 2 | 4 | 5 | 3 | 2 | 3 | 5 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | likely that this never reaches me | no value for anyone | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) |
| 18 | 10243694700 | 216437765 | 09/27/2018 8:01:24 PM | 1-2 years | Org Member | Yes, but not sure I have time. | North America | UTC-04:00 | None, Kubernetes is my first one! | 2 | 2 | 2 | 2 | 2 | 3 | 3 | 4 | 2 | 1 | 1 | 1 | 1 | 1 | For reasons that are currently being debated, we've had trouble in sig-multicluster with the coupling of /approve /lgtm labels that have lead to unexpected merging of PRs. It seems that a better system is being developed through the conversation currently taking place. Otherwise, all of these tools have been very useful in my experience. | Right notifications are being made, but too frequently | I'm not sure | I’m a student | Several times a month | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | I have been lucky to have great support in getting to a point where I have a working development environment, introductions into the community and mentoring during my ramp up to contributing regularly to kubernetes (which was far more frequent than currently) so at this point, I don't feel like there are ways the project could make contributing easier for me. | Kubecon Europe 2017 | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 1 | 4 | 4 | 4 | 4 | 4 | 4 | 5 | No, I think it's useful. | 1 | n/a | n/a | n/a | n/a | n/a | 7 | New Contributor playground. I'm not sure why it's not there but I think it's important to make sure there is support for new contributors to get up and running. | New contributor playground | 4 | 5 | 2 | 4 | 4 | 2 | 1 | 3 | 4 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | Yes | 5 | Not enough time in the week |
| 19 | 10243216424 | 216437765 | 09/27/2018 4:26:23 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-08:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 20 | 10243001543 | 216437765 | 09/27/2018 2:53:40 PM | Less than 6 months | Had no idea this was even a thing | Yes, but not sure I have time. | North America | UTC-05:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 21 | 10242890962 | 216437765 | 09/27/2018 2:31:05 PM | 6 months -1 year | Org Member | Yes, doing it on my own. | Europe | UTC+02:00 | One more | 3 | 3 | 2 | 2 | 1 | 1 | 3 | 3 | 3 | 1 | n/a | 1 | 1 | 1 | N/A | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | Ability to subscribe for certain PRs, issues and test failures | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Test automation (CI/CD) is just awful right now. Its UX is bad and I can hardly find why a test is failing. The flakyness of tests is an issue too. | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 3 | 1 | 1 | 3 | 3 | 3 | 3 | N/A | 1 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 2 | 5 | 1 | 4 | 5 | 1 | 1 | 4 | 4 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | Zoom meetings | yes, for both users and contributors | Yes | n/a | A - Yes, I would love to mentor one or both programs | No | 3 | Don't know enough to mentor | |
| 22 | 10242540704 | 216437765 | 09/27/2018 10:51:38 AM | 6 months -1 year | Org Member | Yes, but would like mentorship. | Asia | UTC+08:00 | 2-4 | 1 | 1 | 1 | 1 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | I hope we can send a email or notification to assigners if the PR n/a for some days. | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | I often absences from the SIG meetings due to the time zone. So I hope I can receive an email or notification of the meeting summary document or video. | Yes, it’s part of my job | A few times a week | Core code inside of kubernetes/kubernetes | n/a | n/a | Testing & Infrastructure | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon China 2018 | n/a | n/a | n/a | n/a | n/a | I hope we can have more Contributor Summits in China. | n/a | 5 | 5 | 4 | 4 | 5 | 5 | 4 | I hope we can output a summary document of each meeting. | n/a | n/a | n/a | 4 | n/a | n/a | n/a | Nothing | 5 | 5 | 3 | 3 | 5 | 1 | 5 | 3 | 5 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | A - Yes, I would love to mentor one or both programs | Yes | 5 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) | |
| 23 | 10241906398 | 216437765 | 09/27/2018 2:12:15 AM | 3+ years | Subproject Owner | No, I'm already an owner | North America | UTC-07:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 24 | 10241687270 | 216437765 | 09/27/2018 12:29:17 AM | 2-3 years | Org Member | Yes, but would like mentorship. | North America | UTC-07:00 | One more | 2 | 4 | 4 | 2 | 5 | 5 | 5 | 5 | 5 | 1 | 1 | 1 | 1 | 1 | /lint I never knew it existed. hence did not know how to use it offline. | Way too many notifications with no benefits | - Ability to build and test as a developer the way current test-infra is building. | Yes, it’s part of my job | Don’t know yet | n/a | n/a | n/a | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | Better release management and compatibility matrix of components involved around the project (such as compatiblity matrix for kubernetes, containerd and CRI plugins, CSI, CNI, helm, docker) etc., | Kubecon Europe 2017 | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | Last year the mentors were helping in career mentoring. Not mentoring people in being a better contributor summit. I think we need to focus more on helping people be a better contributor. | 2 | 1 | 2 | 3 | 1 | 2 | 1 | 1 | The notes writing is sometimes vague if you miss the meeting. You have to watch the recordings. May be we could do a better job at pre-writing some sections that the speaker wants to cover in the notes section so that we have more time while write live notes. | 1 | 2 | 3 | n/a | 5 | n/a | 7 | Offline communities such as meetups need better guidelines and toolset. | Meetups | 3 | 1 | 3 | 1 | 2 | 2 | 3 | 2 | 1 | n/a | n/a | n/a | Slack | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | Yes | 2 | Employer doesn't support spending time mentoring | |
| 25 | 10241675978 | 216437765 | 09/27/2018 12:06:28 AM | 2-3 years | Org Member | Yes, but would like mentorship. | North America | UTC-07:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 26 | 10241578617 | 216437765 | 09/26/2018 11:58:02 PM | 1-2 years | Reviewer | Yes, doing it on my own. | North America | UTC-08:00 | 4+ | 2 | 3 | 2 | 1 | 1 | 5 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | "/retest" why is this needed SOOOO OFTEN? Also could it self report when manually run ten times in a row on PR that there's a bug somewhere? | Right notifications at the right frequency | Noting which line(s) in which OWNERS file(s) are seeming overworked...ie: if somebody's getting 5000 notifications via GitHub each day maybe it's not the notifications that's the problem but rather ownership and delegation? Acknowledging that individuals are buried in notifications, how does one go about understanding how to raise a priority interrupt on somebody or some SIG? Email address for direct email, Slack ID for ping, timezone, vacation/presence, etc. are reasonably obfuscated. A message of "can anybody help with issue XX or PR YY" in a SIG's slack channel seems in my experience to have less 50% chance of triggering action. Adding the SIG leaders or appropriate OWNERS to a @mention there similarly find low rate of success, but perhaps this is inactivity in specific SIGs. Are SIG leads using the https://k8s-gubernator.appspot.com/pr dashboard for their own queue or is it also too full of to-do items? Could a similar dashboard show thing things for example priority/critical-urgent, especially if they're "languishing" for some metric thereof? Could "active contributor in area, but not in reviewer or approver list" be tracked and suggested quarterly to SIG leadership for promotion, for example around the same time as their SIG update at The Community Meeting, where they can then announce how they're pro-actively growing their contributor base and solving "The Approver Problem"? | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | While there is undeniably friction (and important focus on continual improvement), for a project as large and complex as kubernetes I just want to say a huge kudos to those who've done work to make contributing generally easy. The number one pain point I hear about from experienced developers newly coming to k8s is confusion about the state of presubmit test automation and why things feel so flakey in CI. Things like joining groups/channels/meetings, reading docs, make a GitHub account, sign the CLA, and even the custom labeling are sufficiently clear to a newcomer who has done some development before and reads what the bot tells them in response to their actions. But when they make a first even trivial docs or code fix to validate they understood the process enough to get a PR merged...and it all fails, they don't know what to do and they can't be expected (yet) as newcomers to go triage cross-project infrastructure flakes. Overall improving CI signal so it more consistently yields true positives and true negatives is a need. | Kubecon Europe 2017 | Kubecon North America 2017 | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | Kubecon Europe 2019 | Ecosystem events, eg. Helm Summit | n/a | n/a | continue to hone the content toward being completely pre-canned and reusable, modulo some small bits of annual updating to capture changes in community process, repo layout, etc. | 1 | 4 | 4 | 4 | 3 | 5 | 3 | 3 | Bring more consistency to the SIG updates and up the quality by requiring the SIG leadership presenting to have materials pre-shared instead of talking rapidly off the cuff with a volunteer trying to scribe on a topic for which they're not a subject matter expert. | 1 | n/a | 3 | n/a | n/a | n/a | n/a | A corporate focus, but pragmatic. As the project grows, one dimension of its next level growth will be more corporate involvement from the 70+(?!) vendors/distributors/hosting providers. Many of these newcomers will have little open source experience, yet they will have been tasked with accomplishing some product related goal (implement a feature, enable platform specific CI, measure conformance, etc.). They may need special guidance so they do not overwhelm or undermine the project an instead can constructively and pragmatically help their sponsor companies navigate deeper kubernetes engagement. It's also important to not become OpenStack. | Onboarding vendor contributors in a nondisruptive way | 4 | 5 | 3 | 5 | 5 | 2 | 1 | 4 | 5 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | Yes | 5 | Not enough time in the week | |
| 27 | 10241229093 | 216437765 | 09/26/2018 9:10:35 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+02:00 | None, Kubernetes is my first one! | 2 | 1 | 2 | 3 | 1 | 2 | 2 | 1 | 1 | n/a | n/a | 1 | 1 | 1 | /lint | Right notifications at the right frequency | don't know yet | I’m a student | Don’t know yet | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | N/A | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | n/a | n/a | n/a | 3 | 3 | 3 | n/a | N/A | n/a | 2 | 3 | n/a | n/a | n/a | n/a | N/A | 2 | 5 | 1 | 2 | 4 | 1 | 4 | 3 | 2 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Other (please specify): | Only contributed | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 28 | 10241066609 | 216437765 | 09/26/2018 8:13:49 PM | 2-3 years | Subproject Owner | No, I'm already an owner | Europe | UTC+03:00 | One more | 5 | 3 | 2 | 3 | 3 | 4 | 4 | 2 | 2 | 1 | n/a | 1 | 1 | 1 | On a day-to-day basis I benefit the least from the automatic labeling of stale issues, but on a project level it's a good thing so I don't mind it. | Lots of notifications but they are useful | I don't know at the moment | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | Kubecon Europe 2017 | Kubecon North America 2017 | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | n/a | n/a | N/A, I think the current format is good | 3 | 3 | 4 | 3 | 4 | 5 | 4 | 3 | N/A | 1 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 3 | 5 | 2 | 4 | 5 | 3 | 2 | 4 | 5 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Yes | n/a | A - Yes, I would love to mentor one or both programs | No | 3 | Nothing, am already a mentor | |
| 29 | 10240775393 | 216437765 | 09/26/2018 6:31:08 PM | 1-2 years | Subproject Owner | Yes, but not sure I have time. | North America | UTC-08:00 | 2-4 | 2 | 3 | 1 | 3 | 2 | 2 | 4 | 4 | 2 | 1 | 1 | 1 | 1 | 1 | All the tooling mentioned above is useful. I wish process/tooling for development was better/faster. For example, faster build and release. | Way too many notifications with no benefits | Local - build, release, and test - faster, requiring less resources, more automated. | Yes, it’s part of my job | A few times a year | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | n/a | n/a | n/a | n/a | n/a | Find better ways to leverage new community member's desire to contribute. | n/a | n/a | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | Coordinate with events, perhaps have it the same day as tutorials - in the afternoon. I like it when sig-updates/meetings are paired with the conference. For example, kubecon EU. | 1 | 4 | 2 | 2 | 3 | 3 | 4 | 2 | Email agenda or at least sig-updates to a list, so that I can determine whether to attend or watch the session later without requiring me to go check the agenda. | 1 | 2 | 3 | n/a | n/a | n/a | 7 | Improving build times or local development. More tests, which should probably have its own track. More on how users (not developers) can contribute. | Better contributor documentation | 5 | 4 | 3 | 3 | 4 | 1 | 3 | 3 | 3 | kubernetes-dev mailing list | Dedicated discuss.k8s.io forum for contributors | Contributor Experience mailing list | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week |
| 30 | 10240715265 | 216437765 | 09/26/2018 6:01:32 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Asia | UTC-05:00 | None, Kubernetes is my first one! | 1 | 2 | 3 | 4 | 5 | 2 | 1 | 2 | 2 | 1 | n/a | n/a | n/a | n/a | n/a | Way too many notifications with no benefits | n/a | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | as | Kubecon Europe 2017 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | as | as | 1 | 2 | 2 | 2 | 1 | 1 | 1 | as | 1 | n/a | n/a | n/a | n/a | n/a | n/a | as | 1 | 2 | 2 | 2 | 2 | 2 | 1 | 2 | 2 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | n/a | n/a | n/a | n/a | n/a | n/a | |
| 31 | 10240539297 | 216437765 | 09/30/2018 6:13:18 AM | 2-3 years | Approver | Yes, doing it on my own. | Asia | UTC+08:00 | 4+ | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 32 | 10240281768 | 216437765 | 09/26/2018 3:09:56 PM | Less than 6 months | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+02:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 33 | 10240177938 | 216437765 | 09/26/2018 2:37:07 PM | 3+ years | Approver | Yes, but not sure I have time. | Europe | UTC+02:00 | 2-4 | 5 | 3 | 2 | 2 | 2 | 4 | 2 | 1 | 2 | 1 | n/a | 1 | 1 | 1 | all tool are resonably useful | Way too many notifications with no benefits | Cross-repo e2e tests ("stable" kubernetes/kubernetes with another kubernetes/repo master, "stable" kubernetes/repo with kubernetes/kubernetes master, both master and so on). | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | Faster reviews! In my SIG, I can find a reviewer easily, but anything cross-SIG is really painful to me. Even as a seasoned Kubernetes contributor I need to beg for reviews and approvals. | Kubecon Europe 2017 | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | n/a | 2 | 4 | 3 | 3 | 3 | 3 | 3 | 3 | n/a | n/a | n/a | 3 | n/a | n/a | n/a | n/a | Some "developer news" - often I find out that the way we did things in the past does not work any longer and a new process was established. These changes should be documented somewhere and announced on kubernetes-devel. Examples from 1.12: - CRD is now preferred for new API objects - coordination.k8s.io/Lease is now preferred for leader-election | Contributor / Dev Announcement News | 5 | 4 | 1 | 4 | 5 | 5 | 1 | 3 | 5 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week |
| 34 | 10239891071 | 216437765 | 09/26/2018 11:25:00 AM | Just started | Org Member | Yes, but would like mentorship. | Europe | UTC+01:00 | One more | 2 | 2 | 2 | 2 | 2 | 1 | 3 | 3 | 3 | 1 | 1 | 1 | 1 | 1 | Not clear what permissions are needed to issue commands like /assign, /labels, /milestone etc | Lots of notifications but they are useful | - Consolidation of stale/frozen issues - Better issue visualisation based on SIG areas - More automation on sig-release process overall | It’s entirely on my own time | Every day | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 1 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | n/a | 1 | 2 | n/a | 4 | n/a | n/a | n/a | Code tour of the Kubernetes repo, but very detailed / deep dive. A tree of directories with text around them, a series of videos. | Deep Dives and Code Base Tour Videos/Content | 5 | 5 | 2 | 4 | 4 | 1 | 1 | 2 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 3 | Don't know enough to mentor |
| 35 | 10239602078 | 216437765 | 09/26/2018 6:31:38 AM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-07:00 | One more | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | n/a | n/a | n/a | n/a | 1 | N/A | Lots of notifications but they are useful | N/A | Yes, it’s part of my job | Don’t know yet | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Don’t contribute yet, hoping to start soon | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | N/A | 1 | 2 | n/a | n/a | n/a | n/a | n/a | N/A | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | no value for anyone | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 1 | Don't know enough to mentor | |
| 36 | 10239376480 | 216437765 | 09/26/2018 3:55:33 AM | 1-2 years | Subproject Owner | No, I'm already an owner | Asia | UTC+08:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 37 | 10239217297 | 216437765 | 09/26/2018 2:20:46 AM | 2-3 years | I’m not an org member yet, but working on it | Yes, doing it on my own. | North America | UTC-08:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 38 | 10239165899 | 216437765 | 09/26/2018 2:02:08 AM | 3+ years | Subproject Owner | No, I'm already an owner | North America | UTC-08:00 | None, Kubernetes is my first one! | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | n/a | n/a | n/a | 1 | n/a | Right notifications are being made, but too frequently | management of github notifications | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | 2 | 2 | 2 | 3 | 5 | 4 | 5 | 1 | n/a | n/a | 2 | 3 | n/a | n/a | n/a | n/a | n/a | 4 | 5 | 1 | 4 | 4 | 1 | 2 | 2 | 4 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 1 | Not enough time in the week | ||
| 39 | 10239107208 | 216437765 | 09/26/2018 1:37:53 AM | 1-2 years | Subproject Owner | No, I'm already an owner | North America | UTC-07:00 | One more | 2 | 1 | 3 | 2 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | n/a | n/a | 1 | Maybe /approve, /lint is least useful, but they are all useful in their own ways. | Way too many notifications with no benefits | None comes to my mind | Yes, it’s part of my job | A few times a week | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Github notifications can be improved. For example, right now github sends almost 1 email per test failure for PRs. An email for test failure of PR that I review is not important for me, but when there is comment or a new commit, I want to be notified. There is no good way of distinguishing these notifications. Github diff tool is not good. It does not show diffs compared to the previously reviewed code either. I think improvements to Github could possibly be one of the most useful areas of improvement. | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 1 | 3 | 2 | 2 | 4 | 3 | 3 | 3 | N/A | n/a | 2 | n/a | 4 | n/a | n/a | n/a | - | 4 | 5 | 2 | 3 | 5 | 1 | 1 | 3 | 4 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | SIG mailing list | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Nothing, am already a mentor | |
| 40 | 10239063862 | 216437765 | 09/26/2018 1:06:40 AM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-07:00 | One more | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | n/a | n/a | n/a | 1 | 1 | Allow cc of non-k8s members (for PRs integrating with other environments or projects) | Lots of notifications but they are useful | Testing | Yes, it’s part of my job | Don’t know yet | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 4 | 4 | 3 | 4 | 3 | 3 | 3 | N/A | 1 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | no value for anyone | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 1 | Don't know enough to mentor | |
| 41 | 10239007975 | 216437765 | 09/26/2018 12:40:37 AM | 2-3 years | Subproject Owner | No, I'm already an owner | North America | UTC-08:00 | 4+ | 4 | 4 | 3 | 2 | 3 | 4 | 3 | 4 | 3 | n/a | 1 | n/a | n/a | n/a | In general all of the custom k8s bot stuff is confusing and frustrating. I’ve noticed my contributions have gone down because I just don’t understand it or trust it. Just seems really over engineered. | Lots of notifications but they are useful | Creating new repositories | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | Advocacy and events | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Lose the monorepo | Kubecon Europe 2017 | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | Less presentations more productivity - nobody wants another lecture from elite Googlers | 4 | 2 | 2 | 1 | 4 | 4 | 4 | 1 | Nope it’s really good | n/a | n/a | n/a | n/a | n/a | n/a | 7 | All the technical things that are wrong with k8s | 5 | 5 | 1 | 5 | 4 | 5 | 1 | 1 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 3 | Not enough time in the week | ||
| 42 | 10238882946 | 216437765 | 09/25/2018 11:54:10 PM | Less than 6 months | Org Member | Yes, doing it on my own. | North America | UTC-07:00 | One more | 1 | 1 | 1 | 1 | 1 | 3 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | I find the toolset absolutely amazing!! I wish other projects can borrow these tools and bots :-) | Lots of notifications but they are useful | Some sort of reminder to reviewers/approvers beyond say 72 hrs if they have not had a chance to look/leave comments/LGTM/Approve | No, but I’m able to use “free” time at work | Several times a month | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | Nothing right now | n/a | 3 | 3 | 3 | 3 | 3 | 3 | 3 | n/a | n/a | n/a | 3 | 4 | n/a | n/a | n/a | Nothing that I can think of | 5 | 3 | 1 | 2 | 4 | 1 | 1 | 1 | 2 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 43 | 10238632679 | 216437765 | 09/25/2018 10:10:18 PM | 1-2 years | Org Member | Yes, but would like mentorship. | North America | UTC-05:00 | 2-4 | 2 | 2 | 1 | 3 | 2 | 3 | 3 | 1 | 1 | n/a | n/a | 1 | 1 | 1 | fejta-bot looks a bit too chatty | Right notifications at the right frequency | n/a | No, but I’m able to use “free” time at work | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | maybe not easier but definitely more interesting lihe sig-apimachinery | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | n/a | n/a | maybe better sig representation? | 3 | 1 | 2 | 2 | 1 | 1 | 2 | 2 | n/a | 1 | n/a | 3 | 4 | n/a | n/a | n/a | n/a | 2 | 1 | 2 | 1 | 1 | 2 | 2 | 2 | 2 | kubernetes-dev mailing list | Dedicated discuss.k8s.io forum for contributors | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 44 | 10238560621 | 216437765 | 09/25/2018 9:41:43 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+02:00 | 2-4 | 3 | 4 | 3 | 5 | 2 | 3 | 5 | 4 | 4 | 1 | 1 | 1 | 1 | 1 | Na | Lots of notifications but they are useful | Na | It’s entirely on my own time | A few times a week | n/a | n/a | n/a | Testing & Infrastructure | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Well explained issues if is lookong for first contribution. | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2019 | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | I would like to attend if have in some key cities like berlin. Ad hoc not only in kubercon. I can help to organize | 0 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | Na | 1 | 2 | 3 | 4 | n/a | n/a | 7 | Na | 2 | 3 | 2 | 3 | 3 | 1 | 3 | 4 | 2 | n/a | n/a | Contributor Experience mailing list | Slack | n/a | A dedicated contributor site | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 45 | 10238483974 | 216437765 | 09/25/2018 9:14:16 PM | 2-3 years | Org Member | No, I'm already an owner | North America | UTC-07:00 | One more | 3 | 1 | 2 | 2 | 1 | 4 | 3 | 1 | 1 | n/a | n/a | 1 | 1 | 1 | retest bot might be spammy | Lots of notifications but they are useful | hunt down issue owners :-) | Yes, it’s part of my job | Every day | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | n/a | n/a | n/a | n/a | some sort of open discussions? | 1 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | n/a | n/a | 2 | 3 | n/a | n/a | n/a | n/a | n/a | 3 | 5 | 1 | 3 | 5 | 3 | 1 | 2 | 2 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | Yes | 4 | Not enough time in the week | |
| 46 | 10238478706 | 216437765 | 09/25/2018 9:27:19 PM | 6 months -1 year | Reviewer | Yes, but would like mentorship. | North America | UTC+08:00 | One more | 4 | 4 | 3 | 2 | 2 | 3 | 4 | 4 | 3 | n/a | n/a | 1 | 1 | 1 | fejta-bot. The few issues I've seen have been a thread of it marking an issue as stale, someone removing that designation, then it marking the issue as stale again (and sometimes repeat). It'd be great if the Netlify previews would link to the pages that had been changed instead of just linking to the homepage. | Way too many notifications with no benefits | See 9 | Yes, it’s part of my job | A few times a week | n/a | n/a | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 1 | 3 | 3 | 3 | 4 | 4 | 3 | 2 | Some demos drag on a little too much, but at the same time, there are others I think are too short. Maybe a stronger vetting process? | n/a | n/a | 3 | n/a | 5 | n/a | 7 | More doc contributions from CNCF members. It's not on the list. | Help get doc contributors from CNCF | 5 | 5 | 1 | 3 | 4 | 2 | 2 | 3 | 5 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, just users | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor |
| 47 | 10238468406 | 216437765 | 09/25/2018 8:59:31 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Asia | UTC-04:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 48 | 10237728459 | 216437765 | 09/25/2018 4:26:18 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+02:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 49 | 10237255415 | 216437765 | 09/25/2018 12:20:10 PM | Less than 6 months | Org Member | Not really | Europe | UTC+01:00 | 4+ | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 50 | 10237216533 | 216437765 | 09/25/2018 12:07:13 PM | Less than 6 months | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-05:00 | None, Kubernetes is my first one! | 5 | 5 | 3 | 3 | 3 | 5 | 5 | 3 | 1 | 1 | n/a | 1 | 1 | 1 | The /retest command could be better. Incorporating additional signals that can be used to inform contributors when something is likely flaky or not could improve the DX. This is especially relevant to folks who are new to the ecosystem like myself and haven't figured out how to navigate our way yet. | Way too many notifications with no benefits | Not sure; too new to the community. | Yes, it’s part of my job | Don’t know yet | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | N/A | 1 | n/a | n/a | 4 | n/a | n/a | 7 | N/A | 1 | 1 | 1 | 3 | 3 | 1 | 1 | 1 | 3 | n/a | n/a | n/a | n/a | n/a | A dedicated contributor site | n/a | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 1 | Don't know enough to mentor | |
| 51 | 10236778977 | 216437765 | 09/25/2018 5:26:19 AM | 6 months -1 year | Org Member | Yes, doing it on my own. | North America | UTC-05:00 | One more | 1 | 1 | 2 | 2 | 3 | 4 | 1 | 4 | 1 | n/a | 1 | 1 | 1 | 1 | It would be great in k/website if you could regen netlify test with /retest or similar | Way too many notifications with no benefits | Not sure | Yes, it’s part of my job | Several times a month | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Easier instructions for building the latest k/k master for testing. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/a | 0 | 3 | 3 | 2 | 5 | 4 | 4 | 3 | I think it's great! Maybe a tips and tricks section for better contributing / involvement / using k8s | 1 | n/a | 3 | n/a | 5 | n/a | n/a | Make onboarding and helping out easier, training, videos etc | Better contributor documentation | 2 | 5 | 3 | 4 | 4 | 2 | 1 | 3 | 2 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 4 | Don't know enough to mentor | |
| 52 | 10236642556 | 216437765 | 09/25/2018 3:29:34 AM | Just started | Had no idea this was even a thing | Yes, but not sure I have time. | North America | UTC-07:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 53 | 10236528658 | 216437765 | 09/25/2018 2:24:53 AM | 6 months -1 year | Reviewer | Not really | North America | UTC-07:00 | 2-4 | 5 | 4 | 3 | 1 | 2 | 3 | 3 | 2 | 1 | n/a | n/a | 1 | 1 | 1 | Stale issues | Lots of notifications but they are useful | Cherry-picking a fix into multiple target branches Figuring out how to add Netlify to /retest | Yes, it’s part of my job | A few times a week | n/a | n/a | Documentation | n/a | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | Other | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 2 | 2 | 2 | 5 | 4 | 4 | 5 | Maybe a SIG of the week | 1 | n/a | 3 | 4 | n/a | n/a | 7 | I can't think of anything. | 5 | 5 | 1 | 3 | 4 | 1 | 1 | 2 | 3 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, just contributors | Yes | n/a | B - No, I can’t/don’t want to | Yes | 3 | Not enough time in the week | |
| 54 | 10236308069 | 216437765 | 09/25/2018 12:20:21 AM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC±00:00 | One more | 5 | 3 | 1 | 1 | 1 | 4 | 4 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | I don't like the noise that people create by posting comments that only contain bot commands. I wish I could turn notifications for these comments off | Right notifications are being made, but too frequently | I don't know yet | It’s entirely on my own time | Several times a month | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 5 | 5 | 4 | 5 | 4 | 3 | 4 | N/A | 1 | n/a | n/a | n/a | n/a | n/a | n/a | Need better guides for contributors who just start their dive into the project | Better contributor documentation | 5 | 4 | 1 | 2 | 4 | 1 | 2 | 2 | 2 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | Yes | 3 | Don't know enough to mentor |
| 55 | 10236209837 | 216437765 | 09/24/2018 11:24:06 PM | Less than 6 months | I’m not an org member yet, but working on it | Yes, but not sure I have time. | North America | UTC-07:00 | 2-4 | 2 | 4 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | n/a | Right notifications at the right frequency | not enough context for an opinion | Yes, it’s part of my job | A few times a year | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | n/a | 0 | 3 | 3 | 3 | 4 | 4 | 4 | 4 | zoom does not work on my computer. Is there an alternative? | n/a | n/a | n/a | 4 | n/a | n/a | n/a | not sure yet | 3 | 3 | 2 | 3 | 3 | 1 | 4 | 4 | 3 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 56 | 10236079987 | 216437765 | 09/24/2018 10:25:30 PM | 1-2 years | Org Member | Yes, doing it on my own. | North America | UTC-07:00 | None, Kubernetes is my first one! | 3 | 3 | 2 | 2 | 2 | 3 | 2 | 2 | 2 | 1 | n/a | 1 | 1 | n/a | N/A | Right notifications are being made, but too frequently | N/A | Yes, it’s part of my job | Several times a month | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | N/A | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 4 | 4 | 5 | 4 | 4 | 5 | 4 | N/A | 1 | 2 | n/a | n/a | 5 | n/a | n/a | n/a | 2 | 2 | 1 | 2 | 5 | 3 | 1 | 1 | 5 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | n/a | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Employer doesn't support spending time mentoring | |
| 57 | 10235937400 | 216437765 | 09/24/2018 9:47:42 PM | 1-2 years | Org Member | Yes, but not sure I have time. | North America | UTC-08:00 | One more | 3 | 3 | 4 | 1 | 3 | 3 | 3 | 4 | 3 | n/a | n/a | 1 | 1 | 1 | Sometimes the stale issue robot is a bit annoying. | Way too many notifications with no benefits | N/A | Yes, it’s part of my job | Several times a month | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | Testing & Infrastructure | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | Make notifications better. Fixing https://github.com/kubernetes/test-infra/issues/1723 should help | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | Instead of having just one track, like we had in EU 2018, have a lot of tracks, like we had in NA 2017. | 2 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | I don't attend it. | n/a | 2 | n/a | n/a | n/a | n/a | n/a | N/A | 5 | 2 | 1 | 2 | 4 | 3 | 2 | 2 | 4 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 1 | Not enough time in the week | ||
| 58 | 10235874254 | 216437765 | 09/24/2018 9:04:03 PM | 1-2 years | Had no idea this was even a thing | Yes, doing it on my own. | North America | UTC-08:00 | One more | 5 | 3 | 3 | 3 | 3 | 1 | 2 | 4 | 3 | 1 | n/a | n/a | n/a | n/a | /lint maybe? I've never used it. | Way too many notifications with no benefits | Feels like more could be done to make sure we have the right owners (ensure files are kept up-to-date w/r/t to who is actually most involved in code and review) throughout the tree | Yes, it’s part of my job | A few times a week | Core code inside of kubernetes/kubernetes | n/a | n/a | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon China 2018 | Kubecon North America 2018 | n/a | n/a | n/a | n/a | n/a | 0 | 4 | 2 | 2 | 3 | 4 | 4 | 3 | More discussion of sig arch leads on project direction and key issues | 1 | 2 | n/a | n/a | n/a | n/a | 7 | don't know | 2 | 2 | 1 | 3 | 5 | 2 | 1 | 1 | 4 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week | |
| 59 | 10235813487 | 216437765 | 09/24/2018 8:38:52 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-07:00 | 4+ | 1 | 1 | 1 | 2 | 2 | 4 | 4 | 2 | 2 | 1 | n/a | 1 | n/a | 1 | Stale issue labeler | Way too many notifications with no benefits | More help in identifying issues for various groups (docs, core, etc.) | No, but I’m able to use “free” time at work | A few times a week | n/a | n/a | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Easier path to becoming a member of the community to vote, shape structure, etc. Right now it's too exclusive. | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | More time with core members | 0 | 5 | 4 | 4 | 5 | 3 | 2 | 1 | Make it a bit longer with better segmentation between topics | 1 | n/a | 3 | 4 | 5 | 6 | n/a | Team check-in to see how everyone is doing in a psychological sense (are you stressed, was this a productive week, etc.) Having this data might help to identify burnout and what causes the community stress. | Burnout education | 2 | 5 | 3 | 2 | 5 | 5 | 5 | 2 | 2 | n/a | n/a | n/a | Slack | A dedicated contributor site | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Yes | n/a | A - Yes, I would love to mentor one or both programs | Yes | 5 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) | |
| 60 | 10235772397 | 216437765 | 09/24/2018 8:20:24 PM | 3+ years | Subproject Owner | No, I'm already an owner | North America | UTC-07:00 | 2-4 | 4 | 4 | 2 | 2 | 2 | 5 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | Automatically notifying test owners that their tests are breaking, kicking out their tests if they don't fix them | Way too many notifications with no benefits | Better filtering of notifications | Yes, it’s part of my job | Every day | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | A better notification dashboard | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | n/a | Ecosystem events, eg. Helm Summit | n/a | n/a | I'm happy with where it's at | 3 | 3 | 4 | 3 | 4 | 5 | 4 | 5 | Updates on releases other than the release currently under development: what is the schedule for patch releases? | 1 | 2 | 3 | n/a | 5 | 6 | 7 | Can't think of anything right now | 4 | 5 | 1 | 4 | 5 | 1 | 1 | 2 | 3 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | Slack | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 4 | Not enough time in the week | |
| 61 | 10235761961 | 216437765 | 09/24/2018 8:12:31 PM | 1-2 years | Had no idea this was even a thing | Yes, but not sure I have time. | North America | UTC-08:00 | 4+ | 2 | 3 | 4 | 2 | 2 | 3 | 2 | 5 | 1 | 1 | 1 | 1 | n/a | n/a | ci-robot | Lots of notifications but they are useful | Not sure. | Yes, it’s part of my job | Every day | n/a | n/a | n/a | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | Kubecon Europe 2019 | n/a | n/a | n/a | N/A | 1 | 4 | 3 | 2 | 4 | 3 | 3 | 2 | Not sure. | n/a | n/a | 3 | n/a | 5 | n/a | n/a | Not sure. | 4 | 1 | 1 | 2 | 4 | 3 | 2 | 1 | 4 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | no value for anyone | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week | |
| 62 | 10235755196 | 216437765 | 09/24/2018 8:04:47 PM | 6 months -1 year | Org Member | Yes, but not sure I have time. | North America | UTC-08:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 63 | 10235714842 | 216437765 | 09/24/2018 7:56:56 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-07:00 | 2-4 | 1 | 1 | 1 | 1 | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | issue/PR command | Right notifications at the right frequency | list all issues/pr that relates to me | Yes, it’s part of my job | A few times a year | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon China 2018 | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | N/A | 1 | 2 | 3 | n/a | n/a | n/a | n/a | N/A | 5 | 1 | 1 | 5 | 5 | 1 | 1 | 5 | 1 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 64 | 10235691040 | 216437765 | 09/24/2018 7:43:41 PM | 2-3 years | Subproject Owner | Yes, doing it on my own. | North America | UTC-07:00 | 4+ | 3 | 3 | 5 | 4 | 2 | 3 | 2 | 1 | 3 | 1 | 1 | n/a | n/a | 1 | PR Commands | Way too many notifications with no benefits | Notifications/Communication | Yes, it’s part of my job | A few times a week | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | Advocacy and events | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | More breakout sessions | 1 | 1 | 3 | 3 | 2 | 3 | 1 | 1 | N/A | 1 | 2 | 3 | n/a | 5 | n/a | 7 | N/A | 5 | 5 | 5 | 4 | 5 | 4 | 1 | 2 | 5 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, just users | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 4 | Not enough time in the week | ||
| 65 | 10235587169 | 216437765 | 09/24/2018 7:04:12 PM | Less than 6 months | I’m not an org member yet, but working on it | Yes, doing it on my own. | North America | UTC-05:00 | 2-4 | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | n/a | n/a | 1 | 1 | Haven't needed the stale issues bot. | Right notifications at the right frequency | Automated PR assignment | Yes, it’s part of my job | Don’t know yet | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | No | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 5 | 3 | 3 | 4 | 3 | 4 | 4 | N/A | n/a | 2 | n/a | n/a | n/a | n/a | 7 | N/A | 1 | 1 | 1 | 3 | 5 | 1 | 5 | 4 | 2 | n/a | n/a | n/a | n/a | n/a | n/a | Kubernetes blog | k/community repo in GH (Issues and/or PRs) | n/a | yes, just contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 66 | 10235454962 | 216437765 | 09/24/2018 6:05:38 PM | Less than 6 months | Org Member | Yes, doing it on my own. | Europe | UTC+02:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 67 | 10235434280 | 216437765 | 09/24/2018 6:13:43 PM | 6 months -1 year | I’m not an org member yet, but working on it | Not really | North America | UTC-07:00 | 4+ | 3 | 5 | 1 | 5 | 2 | 2 | 1 | 1 | 1 | 1 | n/a | n/a | 1 | 1 | /kind and /assign are presented as mandatory to a new contributor while they have no way of understanding how to make good use of it. I wish the process had a sense of how green a contributor is, and would fallback to a more guided experience for newcomers. | Way too many notifications with no benefits | code quality metrics: coverage, complexity, security, ... | Yes, it’s part of my job | Several times a month | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | responding to communication attempts like design discussions and proposals on github. | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 1 | 4 | 2 | 1 | 4 | 3 | 4 | 1 | no | 1 | n/a | 3 | n/a | 5 | n/a | 7 | N/A | 5 | 2 | 1 | 1 | 4 | 1 | 2 | 1 | 4 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | Kubernetes blog | n/a | n/a | no value for anyone | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 1 | Don't know enough to mentor | |
| 68 | 10235423189 | 216437765 | 09/24/2018 6:09:18 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but not sure I have time. | Europe | UTC+02:00 | 4+ | 4 | 4 | 1 | 1 | 1 | 2 | 5 | 1 | 1 | 1 | n/a | 1 | 1 | 1 | Retesting for flakes is great | Way too many notifications with no benefits | detecting which PR broke build and revert | Yes, it’s part of my job | A few times a week | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | n/a | n/a | More organized networking, e.g. Open Space like picking topics to discuss and selecting by majority and discussing in groups etc | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | Been once | 1 | 2 | 3 | n/a | n/a | n/a | n/a | Don't know | 1 | 5 | 3 | 1 | 2 | 1 | 1 | 4 | 2 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, just users | Not as much as I should because I forget | n/a | A - Yes, I would love to mentor one or both programs | No | 3 | Not enough time in the week | ||
| 69 | 10234448880 | 216437765 | 09/24/2018 4:43:28 AM | 3+ years | Had no idea this was even a thing | Yes, but not sure I have time. | North America | UTC-08:00 | 4+ | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 70 | 10234376003 | 216437765 | 09/24/2018 3:10:32 AM | Just started | Had no idea this was even a thing | Not really | South America | UTC+14:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 71 | 10234309100 | 216437765 | 09/24/2018 1:46:04 AM | Just started | I’m not an org member yet, but working on it | Yes, doing it on my own. | North America | UTC-07:00 | 2-4 | 3 | 1 | 1 | 2 | 1 | 5 | 4 | 5 | 2 | 1 | 1 | 1 | 1 | 1 | They are all super useful. | Right notifications at the right frequency | Not sure | It’s entirely on my own time | A few times a year | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | For my first contribution, I could not for the life of me find instructions on how to run tests on the source code. Running the `make` file was failing. I found no documentation to get me unstuck. After much looking I found the `testing.md` file. Ran the commands and got failures, and again not finding any documentation that would help me move on. I'm aware that we have the Slack channel. I propose, however, that running make files and tests on the fresh source code should be a slam dunk (with proper documentation). | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | Have material for newcomers. But I haven't attended on yet so this might be true already. | 0 | 4 | 4 | 4 | 4 | 4 | 3 | No | 1 | n/a | n/a | 4 | n/a | n/a | n/a | Not sure. | 2 | 5 | 4 | 4 | 4 | 5 | 3 | 4 | 3 | n/a | n/a | n/a | Slack | A dedicated contributor site | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 4 | Not enough time in the week | |||
| 72 | 10232672428 | 216437765 | 09/22/2018 5:41:11 AM | Just started | I’m not an org member yet, but working on it | Yes, but not sure I have time. | Europe | UTC+02:00 | 4+ | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | automatic merging, i think a human review is more important | Right notifications at the right frequency | deployment | No, but I’m able to use “free” time at work | Several times a month | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Don’t contribute yet, hoping to start soon | n/a | i don't known | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | n/a | 0 | 3 | 3 | 3 | 5 | 3 | 5 | 4 | n.a | 1 | 2 | n/a | 4 | 5 | 6 | 7 | i don't know | 2 | 2 | 3 | 1 | 4 | 2 | 4 | 3 | 2 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | no value for anyone | Yes | n/a | A - Yes, I would love to mentor one or both programs | No | 2 | Not enough time in the week | |
| 73 | 10231145970 | 216437765 | 09/21/2018 2:48:58 PM | Less than 6 months | I’m not an org member yet, but working on it | Yes, but not sure I have time. | Europe | UTC+01:00 | One more | 1 | 1 | 1 | 1 | 2 | 3 | 1 | 3 | 1 | 1 | n/a | n/a | n/a | 1 | I have not had chance yet to explore all the tools. | Lots of notifications but they are useful | I was fine with the level of automation. | Yes, it’s part of my job | Haven’t contributed in a while | Core code inside of kubernetes/kubernetes | n/a | Documentation | n/a | Advocacy and events | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Not really. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 5 | 4 | 5 | 5 | 5 | 5 | 5 | No | 1 | 2 | n/a | n/a | n/a | n/a | n/a | Nothing | 2 | 5 | 1 | 2 | 5 | 5 | 3 | 3 | 3 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | ||
| 74 | 10230167769 | 216437765 | 09/21/2018 1:38:45 AM | Just started | Had no idea this was even a thing | Yes, doing it on my own. | North America | UTC-06:00 | 2-4 | 1 | 2 | 2 | 2 | 2 | 3 | 2 | 1 | 1 | 1 | n/a | n/a | n/a | 1 | N\A | Lots of notifications but they are useful | not enough experience to answer this question | No, but I’m able to use “free” time at work | Several times a month | n/a | n/a | n/a | n/a | Advocacy and events | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 4 | 4 | 1 | 4 | 4 | 5 | 3 | thank you for the notes and recordings: they're really useful. | n/a | n/a | 3 | 4 | 5 | n/a | n/a | not sure. | 5 | 4 | 1 | 4 | 2 | 2 | 1 | 3 | 3 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 75 | 10229628055 | 216437765 | 09/20/2018 8:43:23 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Asia | UTC+05:30 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 76 | 10229617568 | 216437765 | 09/20/2018 8:59:11 PM | 2-3 years | Reviewer | Yes, doing it on my own. | North America | UTC-07:00 | 2-4 | 2 | 3 | 1 | 3 | 2 | 4 | 2 | 5 | 1 | 1 | n/a | 1 | 1 | 1 | I wish there was some way we could auto-assign issues/PRs to SIGs | Way too many notifications with no benefits | See above. | Yes, it’s part of my job | Every day | n/a | n/a | n/a | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Better build/test env instructions, tools, for my own build env. | Kubecon Europe 2017 | Kubecon North America 2017 | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | Kubecon Europe 2019 | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | no | 4 | 2 | 5 | 3 | 5 | 5 | 4 | 5 | We might consider changing the time; current 10am time is very hard for some timezones. | 1 | n/a | n/a | 4 | n/a | n/a | 7 | NA | 3 | 5 | 5 | 5 | 5 | 4 | 2 | 2 | 4 | n/a | Dedicated discuss.k8s.io forum for contributors | n/a | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, just contributors | Not as much as I should because I forget | n/a | A - Yes, I would love to mentor one or both programs | Yes | 4 | Not enough time in the week | |
| 77 | 10229456886 | 216437765 | 09/20/2018 7:39:15 PM | 2-3 years | Org Member | Yes, but not sure I have time. | North America | UTC-08:00 | 4+ | 4 | 2 | 3 | 2 | 4 | 4 | 2 | 3 | 3 | n/a | n/a | 1 | 1 | n/a | NA | Lots of notifications but they are useful | Not sure | It’s entirely on my own time | Haven’t contributed in a while | n/a | n/a | Documentation | n/a | Advocacy and events | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Add extra hours to the day | n/a | Kubecon North America 2017 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | More people able to attend | 2 | 4 | 2 | 1 | 5 | 4 | 4 | 3 | NA | 1 | n/a | 3 | n/a | n/a | n/a | 7 | Better onboarding for new users to become contributors. | Better contributor documentation | 5 | 4 | 4 | 2 | 2 | 5 | 3 | 2 | 2 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, just users | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 1 | Employer doesn't support spending time mentoring | |
| 78 | 10228000437 | 216437765 | 09/20/2018 4:31:04 AM | 2-3 years | I’m not an org member yet, but working on it | Yes, doing it on my own. | North America | UTC-05:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 79 | 10227941733 | 216437765 | 09/20/2018 3:59:48 AM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Asia | UTC+08:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 80 | 10227903504 | 216437765 | 09/20/2018 8:14:19 PM | 3+ years | Subproject Owner | No, I'm already an owner | North America | UTC-07:00 | One more | 5 | 3 | 3 | 1 | 2 | 3 | 1 | 2 | 1 | 1 | n/a | n/a | 1 | 1 | Automatic labeling of stale issues - I undo the bot's changes more often than not. | Way too many notifications with no benefits | Concept of "PR attention set". I often find that PRs with 2+ approvers assigned are less likely to get approved, than when there is a single approver. My theory is that people opt to wait for the other person to take a first pass, or want to give them an opportunity to give an opinion before giving a final approval. If instead there were multiple people assigned, but only 1 person was "up to bat" at a time, it might help move PRs forward. Likewise, once I've approved something, I don't necessarily want to follow up on every review comment after. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | Community & Project management; SIG Chair etc. | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | Other | PR reviews are currently my biggest pain point, both as a code contributor (receiving reviews) and a reviewer. One of the challenges is growing our reviewer pool while still maintaining a high quality bar. To that end, I think we could do a much better job with staged reviews. For example, more junior members do a first pass review before handing off to senior members for final review & approval. I believe this was the intention with the reviewer & approver split, but in my experience this hasn't panned out, and needs more automation to work (see above suggestion about assigning a single reviewer). Another way to do staged reviews is have reviewers who focus on different aspects, such as: go readability & language idioms, comment language (we have many non-native english speakers), testing, etc. However, I don't want to need 7 different reviewers to sign off on my 10 line PR, so this approach would need more careful consideration. | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | n/a | n/a | n/a | n/a | Focus more on community & contributor issues. The kubecon EU 2018 summit had a lot of technical content, which while great is what the main conference is for. I would prefer to spend more time discussing the problems & challenges our community faces. This probably means heavy involvement by the steering committee & sig-contribex | 2 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | I never attend the community meeting unless I'm presenting, so please disregard my answers to the previous question. Why do I never attend? I simply have too many meetings, and need to draw the line somewhere. The community meeting is less likely to be directly relevant to me, compared with sig & working group meetings. | n/a | 2 | n/a | 4 | 5 | n/a | 7 | Not to be a broken record, but more emphasis on improving the review bottleneck. | Reviewer and Approver Growth | 5 | 4 | 1 | 4 | 5 | 5 | 2 | 1 | 4 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | Word of mouth | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week |
| 81 | 10227754132 | 216437765 | 09/20/2018 2:10:48 AM | 6 months -1 year | Approver | Yes, doing it on my own. | North America | UTC-07:00 | None, Kubernetes is my first one! | 3 | 2 | 3 | 2 | 3 | 4 | 2 | 5 | 2 | 1 | 1 | 1 | 1 | 1 | Stale issues feel least useful, because I often wish there were a better way of being notified an issue I created was stale. | Way too many notifications with no benefits | Org membership in all k8s orgs, including k8s-sigs | It’s complicated | Every day | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | Other | I'm very outgoing and outspoken and it has been easy for me to find at least someone willing to show me the path. I often wonder if that has been the experience for others. | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | I am no sure about me, but I'm hoping to be able to roll out a "speed dating" event between potential contributors and SIGs to help people connect with opportunities. | 1 | 3 | 4 | 2 | 4 | 4 | 4 | 5 | I wish the demos were less "product show-and-tell" and more "general tutorials/walkthroughs"! For example, a testgrid walk through, a "how to set up your dev env" walkthrough, a minikube tutorial walkthrough, etc. Not every week but some weeks? | 1 | 2 | 3 | n/a | 5 | n/a | 7 | Detangling aspects of Kubernetes from the monorepo and greater repo cross-reference | 2 | 5 | 1 | 4 | 5 | 2 | 1 | 2 | 4 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | Yes | 4 | Other (please specify): | |
| 82 | 10227655092 | 216437765 | 09/20/2018 12:53:42 AM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+02:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 83 | 10227633920 | 216437765 | 09/20/2018 12:42:18 AM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, doing it on my own. | Europe | UTC+02:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 84 | 10227498388 | 216437765 | 09/20/2018 12:23:37 AM | 1-2 years | Org Member | Yes, doing it on my own. | Europe | UTC+01:00 | One more | 1 | 2 | 1 | 1 | 1 | 4 | 3 | 1 | 3 | n/a | n/a | 1 | 1 | 1 | Fejta-bot for flakes can flood you when having /approve /lgtm | Right notifications at the right frequency | Nothing i can think of | No, but I’m able to use “free” time at work | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | More cross-SIG discussions and brainstorming | 1 | 3 | 3 | 5 | 5 | 5 | 5 | 4 | One of the best communities I’ve seen in the OSS landscape | 1 | n/a | n/a | 4 | 5 | n/a | n/a | Nothing | 3 | 5 | 2 | 5 | 5 | 4 | 1 | 5 | 5 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | Yes | 5 | Not enough time in the week | |
| 85 | 10227329768 | 216437765 | 09/19/2018 10:29:58 PM | 2-3 years | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+02:00 | 2-4 | 3 | 2 | 2 | 2 | 4 | 3 | 4 | 2 | 3 | n/a | n/a | n/a | 1 | n/a | Fejta-bot | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | N/a | Yes, it’s part of my job | Several times a month | n/a | n/a | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | Kubecon Europe 2019 | n/a | n/a | n/a | N/A | 0 | 4 | 3 | 3 | 4 | 4 | 4 | 3 | Too many groups, picking the right groups could be difficult sometime | 1 | 2 | n/a | n/a | n/a | n/a | 7 | N/A | 2 | 5 | 4 | 2 | 3 | 2 | 2 | 3 | 2 | n/a | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 86 | 10227062641 | 216437765 | 09/19/2018 9:00:11 PM | Less than 6 months | Approver | Yes, but not sure I have time. | Europe | UTC+01:00 | One more | 2 | 1 | 1 | 1 | 2 | 2 | 3 | 2 | 1 | 1 | 1 | n/a | n/a | 1 | /assign and /kind are mostly abused, /approve could be integrated with GitHub reviews. | Right notifications at the right frequency | Infra (I'm talking specifically for Kubernetes/ingress-nginx) | No, but I’m able to use “free” time at work | Several times a month | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | Advocacy and events | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | n/a (haven't attended yet) | 0 | 4 | 5 | 3 | 3 | 5 | 4 | 3 | Nothing that comes to my mind, need to attend more. | 1 | n/a | 3 | 4 | n/a | n/a | 7 | n/a | 1 | 5 | 1 | 3 | 4 | 5 | 3 | 2 | 1 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 3 | Employer doesn't support spending time mentoring | ||
| 87 | 10227015112 | 216437765 | 09/19/2018 8:08:51 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but not sure I have time. | Europe | UTC+01:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 88 | 10226936255 | 216437765 | 09/19/2018 7:50:29 PM | 2-3 years | Reviewer | Yes, doing it on my own. | North America | UTC-07:00 | None, Kubernetes is my first one! | 1 | 3 | 3 | 1 | 4 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | I wish reviewers were not assigned until after tests pass. | Way too many notifications with no benefits | Is it possible to get email notifications for specific test failures? | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | N/A | n/a | n/a | n/a | n/a | n/a | 6 | n/a | Nothing | 2 | 5 | 1 | 3 | 5 | 5 | 1 | 2 | 5 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 2 | Not enough time in the week | |
| 89 | 10226800235 | 216437765 | 09/19/2018 6:59:36 PM | 1-2 years | Had no idea this was even a thing | Not really | North America | UTC-08:00 | 2-4 | 3 | 3 | 1 | 2 | 2 | 3 | 3 | 3 | 2 | 1 | n/a | n/a | n/a | 1 | All are pretty useful | Right notifications at the right frequency | None I know of | No, but I’m able to use “free” time at work | Haven’t contributed in a while | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 4 | 4 | 2 | 5 | 5 | 3 | 1 | Haven't attended enough to give good feedback | n/a | n/a | n/a | 4 | 5 | n/a | n/a | n/a | 1 | 4 | 1 | 1 | 3 | 1 | 2 | 2 | 1 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 90 | 10226795801 | 216437765 | 09/19/2018 6:51:29 PM | 1-2 years | Org Member | Yes, but not sure I have time. | Europe | UTC+01:00 | 4+ | 3 | 2 | 1 | 1 | 1 | 1 | 4 | 1 | 1 | n/a | n/a | n/a | 1 | 1 | automated issue closing | Way too many notifications with no benefits | listing related issues | No, but I’m able to use “free” time at work | A few times a year | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | Kubecon Europe 2017 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | not sure | 1 | 1 | 3 | 1 | 3 | 3 | 2 | 1 | n/a | 1 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | 3 | 5 | 2 | 3 | 5 | 1 | 2 | 2 | 5 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 1 | Not enough time in the week | |
| 91 | 10224032912 | 216437765 | 09/18/2018 6:48:35 PM | Just started | I’m not an org member yet, but working on it | Yes, doing it on my own. | North America | UTC-08:00 | 4+ | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 92 | 10223696648 | 216437765 | 09/18/2018 4:44:00 PM | Less than 6 months | Org Member | Yes, but would like mentorship. | Asia | UTC+05:30 | 2-4 | 2 | 4 | 3 | 4 | 3 | 3 | 5 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | N/A | Right notifications are being made, but too frequently | Issue labeling could benefit from additional automation. | It’s entirely on my own time | Every day | Core code inside of kubernetes/kubernetes | n/a | Documentation | n/a | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | I'd really like some mentorship to get started. K8s is a beast and it's very easy to get lost. I've been looking for stuff to work on for a while now, but it gets very confusing very quickly! | n/a | n/a | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | n/a | n/a | n/a | n/a | I attended the beginner track last time, this time I'm planning to attend the more experienced track as I've been familiar with it for a while! I'll make sure to reach out post that :) | 1 | 2 | 4 | 3 | 4 | 3 | 3 | 4 | N/A | 1 | n/a | 3 | 4 | n/a | n/a | 7 | I'd really like to see some focus on the developer guide. It feels like it's all over the place atm. | Better contributor documentation/developer guide | 2 | 5 | 3 | 3 | 5 | 3 | 1 | 3 | 3 | n/a | Dedicated discuss.k8s.io forum for contributors | n/a | Slack | A dedicated contributor site | n/a | n/a | n/a | yes, for both users and contributors | Other (please specify): | I've not filed too many issues to be able to answer this correctly | A - Yes, I would love to mentor one or both programs | No | 3 | Don't know enough to mentor | |
| 93 | 10223602767 | 216437765 | 09/18/2018 3:50:36 PM | Less than 6 months | Org Member | Yes, but would like mentorship. | Asia | UTC+05:30 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 94 | 10222598172 | 216437765 | 09/18/2018 1:57:57 AM | Just started | I’m not an org member yet, but working on it | Yes, but not sure I have time. | North America | UTC-06:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 95 | 10222294684 | 216437765 | 09/17/2018 11:12:38 PM | 3+ years | Approver | No, I'm already an owner | North America | UTC-08:00 | 4+ | 2 | 4 | 4 | 1 | 1 | 5 | 2 | 4 | 2 | 1 | 1 | 1 | 1 | 1 | n/a | Way too many notifications with no benefits | n/a | Yes, it’s part of my job | A few times a week | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | Kubecon Europe 2017 | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | n/a | 1 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | n/a | n/a | 2 | n/a | n/a | n/a | n/a | n/a | n/a | 5 | 2 | 1 | 3 | 5 | 2 | 1 | 1 | 5 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | A - Yes, I would love to mentor one or both programs | Yes | 4 | Not enough time in the week | |
| 96 | 10222070141 | 216437765 | 09/17/2018 9:27:34 PM | Just started | I’m not an org member yet, but working on it | Yes, but not sure I have time. | North America | UTC-04:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 97 | 10222067162 | 216437765 | 09/17/2018 9:35:53 PM | 2-3 years | I’m not an org member yet, but working on it | Yes, but not sure I have time. | North America | UTC-08:00 | 2-4 | 1 | 3 | 3 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | n/a | 1 | 1 | 1 | The automatic stale is a but tough to deal with sometimes. As it feels like issues are being railroaded out of sight. | Lots of notifications but they are useful | Not Sure. | Yes, it’s part of my job | Several times a month | n/a | n/a | Documentation | n/a | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | Other | n/a | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 5 | 5 | 3 | 3 | 3 | 4 | 5 | It's actually pretty great. | 1 | n/a | 3 | 4 | n/a | n/a | 7 | N/A | 2 | 5 | 2 | 4 | 4 | 1 | 3 | 2 | 3 | n/a | n/a | n/a | Slack | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | Yes | 4 | Nothing, am already a mentor | ||
| 98 | 10222048043 | 216437765 | 09/17/2018 9:25:18 PM | 6 months -1 year | Reviewer | Not really | North America | UTC-04:00 | None, Kubernetes is my first one! | 2 | 3 | 4 | 2 | 3 | 4 | 1 | 2 | 2 | 1 | n/a | 1 | n/a | 1 | I've never seen the flakes retested automatically, I just wish they would be | Way too many notifications with no benefits | Flake reporting is very manual, so I almost never do it. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | n/a | 0 | 4 | 3 | 2 | 2 | 1 | 2 | 2 | I don't usually attend, if I'm honest. | 1 | n/a | n/a | n/a | n/a | n/a | 7 | Managing the firehose of notifications | Notification control (communication pipelines) | 3 | 5 | 1 | 3 | 4 | 1 | 1 | 1 | 3 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 2 | Not enough time in the week |
| 99 | 10222047195 | 216437765 | 09/17/2018 9:37:34 PM | Just started | Had no idea this was even a thing | Yes, but would like mentorship. | North America | UTC+13:00 | None, Kubernetes is my first one! | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | n/a | n/a | n/a | n/a | 1 | - | Lots of notifications but they are useful | - | It’s complicated | Don’t know yet | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Don’t contribute yet, hoping to start soon | n/a | I am someone who has never contributed but would like to. Overall, I think something like Google's Summer of Code except on a part time level for full time employees where people can get support and some hand holding through processes / targeting issues would be immensely useful. Its one thing to say "documentation is useful" and that's great. But even after understanding the processes of merging a PR there's a HUGE leap to contribute to actual Kuberenetes code. There's historical context on why things are implemented the way they are. Then gaining enough context on which issues to target is difficult. And even further then tackling the actual code. This needs a lot of initial investment on individual contributors. | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | I would love contributor workshops for people who haven't contributed to kubernetes yet. Not sure if this is under the realm of contributor summit or not. | 0 | n/a | 5 | n/a | n/a | n/a | n/a | n/a | - | 1 | n/a | n/a | 4 | n/a | n/a | 7 | I don't think this is missing per se. But I'd love to be paired with someone in the open source community that has sort of a project manager role. I have the competency to jump into a code base. What I lack is the context on what in the community is prioritized, what issues aren't time sensitive for new contributors, what issues I can take my time on, and someone to ask technical questions. | Issue Triage | 1 | 4 | 1 | 3 | 5 | 3 | 1 | 1 | 5 | n/a | n/a | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Other (please specify): | I don't file issues | B - No, I can’t/don’t want to | No | 3 | Other (please specify): | |
| 100 | 10221989907 | 216437765 | 09/17/2018 8:53:16 PM | 6 months -1 year | Had no idea this was even a thing | Yes, but would like mentorship. | North America | UTC-06:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 101 | 10221978535 | 216437765 | 09/17/2018 8:48:12 PM | Just started | Had no idea this was even a thing | Yes, but not sure I have time. | North America | UTC-05:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 102 | 10221960887 | 216437765 | 09/17/2018 8:40:25 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-05:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 103 | 10221836566 | 216437765 | 09/17/2018 8:22:05 PM | 1-2 years | Reviewer | Yes, doing it on my own. | North America | UTC-04:00 | 4+ | 2 | 2 | 1 | 2 | 2 | 3 | 5 | 2 | 1 | n/a | 1 | 1 | 1 | 1 | i think the retest is the least useful because I've never actually seen it work and I've had to manually re-run flakes...but knowing there is something that *should* rerun flakes makes me think I could do this better. | Lots of notifications but they are useful | Github emails, maybe some kind of gmail filter creator that asks you what you want to hear about and then generates a filter for you? Too many emails from github though. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | n/a | Documentation | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Being able to find good first issues to help new folks with on boarding is by far, in my opinion, the biggest problem with contributing to kubernetes today. | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 2 | 3 | 3 | 2 | 1 | 3 | 1 | It's nice when I get time to attend it | 1 | n/a | n/a | n/a | n/a | n/a | 7 | Ways to identify new issues. There was talk of a `good-first-issue` label, but that hasn't taken off yet. In order to get more people into the community we need to make it much easier for folks to find areas of interest that need improving. Maybe each sig could have a standard way of identifying good first issues. Maybe I'm looking for a sig trello board. I'm not sure, but joining a sig takes a long time to get up to speed. I usually have to attend several weeks of meetings before I can really figure out what's going on/what area of focus a sig has, etc. | Issue Triage | 2 | 5 | 1 | 5 | 5 | 2 | 2 | 2 | 4 | n/a | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Employer doesn't support spending time mentoring |
| 104 | 10221816526 | 216437765 | 09/17/2018 7:44:51 PM | Less than 6 months | Had no idea this was even a thing | Yes, but would like mentorship. | North America | UTC-07:00 | None, Kubernetes is my first one! | 2 | 3 | 3 | 3 | 1 | 3 | 4 | 4 | 1 | 1 | 1 | 1 | 1 | 1 | N/A | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | N/A | Yes, it’s part of my job | Every day | n/a | n/a | Documentation | n/a | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | n/a | 3 | 2 | 1 | 3 | 3 | 3 | 3 | n/a | 1 | 2 | n/a | n/a | n/a | n/a | n/a | N/A | 3 | 5 | 1 | 5 | 5 | 1 | 1 | 4 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | n/a | n/a | no value for anyone | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 105 | 10221801147 | 216437765 | 09/17/2018 8:27:52 PM | 2-3 years | Subproject Owner | No, I'm already an owner | North America | UTC-05:00 | 4+ | 3 | 3 | 5 | 3 | 3 | 5 | 3 | 3 | 2 | 1 | 1 | 1 | 1 | 1 | N/A | Way too many notifications with no benefits | unsure | Yes, it’s part of my job | A few times a week | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Improve the ability to triage test failures and be able to easily reproduce locally. | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 3 | 4 | 4 | 5 | 5 | 5 | 3 | No, I think that it does a good job of balancing information sharing and being respectful of people's time. | n/a | 2 | 3 | 4 | 5 | n/a | 7 | Improving the ability to identify the cause of test failures and the ability to reproduce test failures locally. | 4 | 5 | 1 | 4 | 4 | 2 | 1 | 3 | 5 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week | |
| 106 | 10221794836 | 216437765 | 09/17/2018 7:38:40 PM | 3+ years | Approver | No, I'm already an owner | North America | UTC-05:00 | 4+ | 4 | 2 | 3 | 1 | 2 | 4 | 2 | 1 | 4 | n/a | n/a | n/a | n/a | 1 | The automation is byzantine and UX is not simple. | Way too many notifications with no benefits | Reassign reviewers/approvers on a timeout of a couple of weeks and no feedback. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | Other | Flowchart on the process for new contributors. | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | 1/2 updates, 1/2 free form sig discussions. | All of them | 5 | 4 | 1 | 4 | 3 | 4 | 4 | Please don't monopolize folks time talking about byzantine automation changes unless there is a UX change that would affect their day 2 day lives. | 1 | n/a | n/a | 4 | n/a | n/a | n/a | N/A | 3 | 4 | 3 | 4 | 5 | 2 | 1 | 2 | 3 | kubernetes-dev mailing list | Dedicated discuss.k8s.io forum for contributors | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 2 | Not enough time in the week | |
| 107 | 10221534874 | 216437765 | 09/24/2018 5:42:59 PM | 1-2 years | Org Member | Yes, doing it on my own. | North America | UTC+03:00 | 2-4 | 1 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | They'all are useful. | Lots of notifications but they are useful | n/a | Yes, it’s part of my job | A few times a week | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2017 | Kubecon North America 2017 | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | n/a | n/a | n/a | n/a | n/a | 1 | 1 | 2 | 2 | 1 | 2 | 2 | 2 | n/a | n/a | n/a | n/a | 4 | n/a | n/a | n/a | n/a | 1 | 2 | 2 | 2 | 1 | 3 | 3 | 2 | 2 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 4 | Not enough time in the week | ||
| 108 | 10221178738 | 216437765 | 09/17/2018 3:21:02 PM | 2-3 years | Approver | Yes, but would like mentorship. | Asia | UTC+08:00 | None, Kubernetes is my first one! | 3 | 2 | 1 | 1 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | automatic labeling of stale issues. Just close issues, not really help solving problems. | Way too many notifications with no benefits | NA | Yes, it’s part of my job | Several times a month | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | Advocacy and events | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2017 | n/a | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | Make the planning part more visible. | 1 | 3 | n/a | n/a | 3 | 3 | n/a | n/a | Have more Asia time-zone friendly meeting. | 1 | n/a | 3 | 4 | 5 | n/a | n/a | na | 4 | 3 | 2 | 2 | 4 | 2 | 1 | 4 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, just contributors | No, because I don't think my issues qualify | n/a | A - Yes, I would love to mentor one or both programs | No | 2 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) | |
| 109 | 10221032938 | 216437765 | 09/17/2018 1:09:01 PM | 3+ years | Subproject Owner | Yes, doing it on my own. | Europe | UTC+02:00 | 2-4 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | - | Lots of notifications but they are useful | The problem itself is on the gh side, dealing with their notifications is cumbersome at the level k8s currently is. I have multiple filters in my inbox, but still the volume of emails is significantly large. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | n/a | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2017 | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | - | 1 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | - | 1 | n/a | 3 | n/a | 5 | n/a | 7 | - | 5 | 5 | 1 | 4 | 5 | 2 | 2 | 3 | 3 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week | |
| 110 | 10216867455 | 216437765 | 09/14/2018 9:31:24 AM | 6 months -1 year | Reviewer | Yes, but would like mentorship. | Asia | UTC+05:30 | One more | 1 | 1 | 1 | 1 | 1 | 3 | 2 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | n/a | Lots of notifications but they are useful | n/a | It’s entirely on my own time | A few times a week | n/a | n/a | Documentation | n/a | n/a | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | None. | n/a | n/a | n/a | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | n/a | n/a | N/A | n/a | 5 | 5 | 4 | 5 | 5 | 5 | 4 | none | 1 | n/a | 3 | 4 | n/a | n/a | n/a | not that i can think of. | 3 | 5 | 2 | 3 | 2 | 2 | 2 | 3 | 4 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | A - Yes, I would love to mentor one or both programs | No | 4 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) | |
| 111 | 10216171567 | 216437765 | 09/14/2018 12:09:37 AM | 1-2 years | Org Member | Yes, but not sure I have time. | North America | UTC-07:00 | One more | 2 | 3 | 2 | 2 | 1 | 2 | 2 | 2 | 2 | 1 | 1 | n/a | n/a | 1 | I've found /approve to not be that useful since GitHub's improved review features duplicate that. | Lots of notifications but they are useful | n/a | Yes, it’s part of my job | A few times a week | n/a | n/a | Documentation | n/a | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Perhaps greater discoverability for sub-projects, e.g. those in kubernetes-sigs/ repo | Kubecon Europe 2017 | n/a | n/a | n/a | Kubecon North America 2018 | n/a | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | The unconference style SIG sessions (deep-dive) were much later in the evening at the last KubeCon in Copenhagen. We find these sessions particularly useful for SIG Apps due to the large amount of things it covers. It would be good to have these at a more accessible time. | 2 | 5 | 4 | 3 | 4 | 4 | 5 | 4 | n/a | 1 | 2 | 3 | n/a | 5 | n/a | 7 | n/a | 4 | 5 | 2 | 4 | 5 | 5 | 3 | 4 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | A - Yes, I would love to mentor one or both programs | No | 3 | Just not getting around to it | ||
| 112 | 10215312899 | 216437765 | 09/13/2018 5:44:35 PM | 3+ years | Subproject Owner | No, I'm already an owner | North America | UTC-05:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 113 | 10214900593 | 216437765 | 09/13/2018 3:05:12 PM | 1-2 years | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-05:00 | None, Kubernetes is my first one! | 4 | 3 | 1 | 5 | 3 | 4 | 5 | 5 | 2 | n/a | n/a | 1 | 1 | n/a | N/A | Right notifications at the right frequency | Unsure right now | Yes, it’s part of my job | Several times a month | n/a | n/a | Documentation | n/a | Advocacy and events | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | More guided mentorship | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 5 | 3 | 3 | 4 | 5 | 5 | 4 | none | 1 | n/a | 3 | 4 | n/a | n/a | n/a | none | 4 | 5 | 5 | 4 | 5 | 3 | 4 | 4 | 4 | n/a | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | Yes | 5 | Don't know enough to mentor | |
| 114 | 10214567885 | 216437765 | 09/13/2018 11:40:39 AM | Less than 6 months | Had no idea this was even a thing | Yes, but not sure I have time. | Europe | UTC+01:00 | 4+ | 2 | 3 | 1 | 3 | 1 | 4 | 4 | 4 | 1 | 1 | 1 | 1 | 1 | 1 | Don't know | Right notifications at the right frequency | Don't know | It’s complicated | A few times a year | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Don't know | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | Kubecon Europe 2019 | n/a | n/a | n/a | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | No | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 115 | 10213539213 | 216437765 | 09/12/2018 11:17:55 PM | 2-3 years | Org Member | Not really | North America | UTC+08:00 | 4+ | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 116 | 10213442456 | 216437765 | 09/12/2018 11:09:23 PM | 1-2 years | Approver | Yes, but would like mentorship. | Europe | UTC+02:00 | None, Kubernetes is my first one! | 3 | 1 | 2 | 2 | 1 | 4 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | Sometimes the amount of GitHub notification is overhelming. It will be great to have an enhanced gubernetor PR/issue dashboard to keep things under control with less effort | Lots of notifications but they are useful | Integration test, build and packaging, hacks/validation | No, but I’m able to use “free” time at work | A few times a week | Core code inside of kubernetes/kubernetes | n/a | Documentation | Testing & Infrastructure | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Help me find a work where I can works OSS full time | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Contributor summit is really valuable and deserve more space into the kubeconf Circus. Helps/Facilitation should be provided to contributors not backed by companies | 1 | 4 | 4 | 5 | 5 | 4 | 5 | 5 | You are doing a great work! | 1 | 2 | 3 | n/a | n/a | 6 | 7 | Cncf ambassador program, I have no news about it Job boards, marching contributors careers and companies needs | 2 | 5 | 1 | 3 | 5 | 1 | 1 | 4 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | n/a | Sig meetings | yes, for both users and contributors | Yes | n/a | A - Yes, I would love to mentor one or both programs | No | 3 | Employer doesn't support spending time mentoring | |
| 117 | 10212981609 | 216437765 | 09/12/2018 7:31:19 PM | 6 months -1 year | Org Member | Yes, doing it on my own. | North America | UTC-07:00 | One more | 2 | 1 | 3 | 4 | 4 | 2 | 2 | 3 | 2 | n/a | n/a | 1 | 1 | 1 | N/A | Right notifications are being made, but too frequently | N/A | No, but I’m able to use “free” time at work | Several times a month | n/a | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 3 | 3 | 2 | 5 | 5 | 5 | 3 | N/A | 1 | 2 | n/a | 4 | 5 | n/a | n/a | N/A | 4 | 5 | 1 | 3 | 4 | 1 | 2 | 2 | 3 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week | |
| 118 | 10212885572 | 216437765 | 09/12/2018 7:24:05 PM | Just started | Had no idea this was even a thing | Not really | Asia | UTC+05:30 | 2-4 | 1 | 1 | 2 | 2 | 2 | 3 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | No one at the moment | Right notifications at the right frequency | Test failure guidance maybe | It’s entirely on my own time | A few times a week | Core code inside of kubernetes/kubernetes | n/a | n/a | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | More hands-on workshops | 1 | 1 | 1 | 1 | 1 | 1 | 1 | Nope | 1 | n/a | 3 | 4 | 5 | n/a | n/a | Nothing I can think of | 3 | 5 | 2 | 1 | 4 | 1 | 3 | 4 | 1 | kubernetes-dev mailing list | n/a | n/a | Slack | A dedicated contributor site | Kubernetes blog | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 2 | Don't know enough to mentor | |||
| 119 | 10212715497 | 216437765 | 09/12/2018 6:02:27 PM | 1-2 years | Subproject Owner | No, I'm already an owner | North America | UTC-06:00 | 4+ | 4 | 4 | 1 | 3 | 3 | 2 | 4 | 2 | 2 | 1 | n/a | n/a | 1 | 1 | I need help sometimes as a maintainer identifying pull requests that have stalled out and need intervention or more attention. Maybe normalizing that things need help by adding a /bump command and making it super clear for new contributors, and in our bots first reply (the approve bot comment that you see immediately after a PR is submitted) saying "Hey if this gets stuck or you are confused, just reply /bump" so that people don't worry over how to find a nice way to get help? | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | More comments on 10. I need help watching for: * New PRs and issues (without watching the entire repo and every . single . comment) * Separating out replies to an issue that I commented on once, or was mentioned on once, vs notifications for when someone is actually mentioning my name _right now_. Basically GH's email notifications are a fire hose and the noise is much higher than the signal. So I'm losing a lot of important things because my email filtering foo isn't strong enough. | Yes, it’s part of my job | Every day | n/a | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | I'd really appreciate help getting email notifications for relevant events without getting emailed for every single comment. GH is letting me down, octobox doesn't quite help either, I use the PR dashboard but that requires me to check, and it still pops things up for my attention that don't really need any action on my part. | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | Ecosystem events, eg. Helm Summit | n/a | n/a | I wanted more interaction with the SIGs. At KubeCon EU '18 it was in a presenter format which wasn't at all what I was hoping for. | 1 | 2 | 4 | 1 | 5 | 4 | 4 | 2 | N/A | 1 | 2 | n/a | 4 | n/a | n/a | N/A | 2 | 5 | 2 | 4 | 5 | 2 | 1 | 1 | 4 | n/a | n/a | n/a | n/a | A dedicated contributor site | n/a | n/a | Something that is announcements only | yes, just users | Yes | n/a | A - Yes, I would love to mentor one or both programs | Yes | 3 | Not enough time in the week | |||
| 120 | 10212675874 | 216437765 | 09/12/2018 5:32:07 PM | Just started | Had no idea this was even a thing | Yes, but not sure I have time. | Europe | UTC+01:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 121 | 10212308706 | 216437765 | 09/12/2018 9:33:55 PM | Less than 6 months | Had no idea this was even a thing | Yes, but would like mentorship. | Europe | UTC±00:00 | 4+ | 1 | 2 | 3 | 3 | 3 | 2 | 2 | 2 | 2 | n/a | n/a | 1 | n/a | n/a | automatic stale issues | Lots of notifications but they are useful | e2e testing | No, but I’m able to use “free” time at work | A few times a year | n/a | n/a | Documentation | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | Don’t contribute yet, hoping to start soon | n/a | Nope | Kubecon Europe 2017 | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | It does feel sometimes that the contributor community is pretty insular at the conferences. | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | N/A | 1 | n/a | 3 | n/a | n/a | n/a | n/a | Overall SIG processes for new or people on the periphery | 1 | 3 | 1 | 1 | 4 | 1 | 2 | 3 | 1 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 2 | Just not getting around to it | ||
| 122 | 10212242335 | 216437765 | 09/12/2018 2:21:53 PM | 3+ years | Approver | Yes, doing it on my own. | Europe | UTC+02:00 | 4+ | 1 | 4 | 4 | 2 | 1 | 3 | 1 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | /label by far. There is no autocompletion. I am lucky to have the permission to use the Github UI directly instead. | Way too many notifications with no benefits | Escalation of approval requests. Approver often do not read all Github notifications. Often it is not clear whether the didn't see the notification, have no time, are out of office or simply don't like the PR but hesitate to comment. Especially from Europe this can be very frustrating with US approvers because pinging them directly is often in evening hours. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | Advocacy and events | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2017 | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | Ecosystem events, eg. Helm Summit | n/a | n/a | Unconference style instead of talks. Less steering commitee. Less Sig-Lead mini presentations. More discussion about core topics (to be collected in advance and voted for). | 3 | 1 | 4 | 2 | 2 | 3 | 4 | 4 | - | n/a | 2 | 3 | n/a | 5 | n/a | 7 | - | 2 | 5 | 1 | 3 | 5 | 4 | 2 | 3 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | A - Yes, I would love to mentor one or both programs | Yes | 5 | Nothing, am already a mentor | |
| 123 | 10212214310 | 216437765 | 09/12/2018 1:53:46 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but not sure I have time. | Europe | UTC±00:00 | 4+ | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 124 | 10212010909 | 216437765 | 09/12/2018 11:47:01 AM | 1-2 years | Org Member | Yes, but not sure I have time. | Europe | UTC+02:00 | 2-4 | 2 | 1 | 2 | 2 | 1 | 2 | 4 | 3 | 1 | 1 | n/a | 1 | 1 | 1 | Labeling stale issues is useful if people care about them... most of the time I think they don't have enough time to do so. | Lots of notifications but they are useful | Squash commits (I think it's coming...) | It’s entirely on my own time | A few times a week | n/a | Code inside of another repo in the kubernetes/* GitHub organization | n/a | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2017 | n/a | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 4 | 5 | 3 | 5 | 5 | 5 | 5 | I like them like that, I only wish I had more time to attend. | 1 | n/a | n/a | n/a | 5 | n/a | n/a | N/A | 2 | 5 | 1 | 4 | 4 | 1 | 1 | 3 | 3 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | Yes | 3 | Don't know enough to mentor | |
| 125 | 10212003967 | 216437765 | 09/12/2018 11:49:00 AM | 6 months -1 year | Org Member | Yes, doing it on my own. | Europe | UTC+01:00 | 2-4 | 3 | 3 | 2 | 2 | 3 | 2 | 4 | 2 | 1 | 1 | 1 | 1 | 1 | 1 | I hate it, when my PR fails on "stupid" ./hack/verify-* issues ... but I don't have a solution for that ... | Way too many notifications with no benefits | - | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Make prow / test-infra / kubetest / ... easier to understand, extend, and use. Make vendoring stuff easier (how can my repo vendor in parts of k/k, then itself be vendored into k/k without being a stagung repo) | n/a | n/a | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 5 | 4 | 3 | 4 | 5 | 4 | 3 | - | 1 | n/a | n/a | 4 | 6 | 7 | One thing that is also important to me: Not only focus on US (e.g. timezone wise) but also other regions | Globalization | 4 | 5 | 1 | 4 | 5 | 2 | 1 | 3 | 4 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | random SIG meeting where this is brought up | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 126 | 10211956716 | 216437765 | 09/12/2018 11:00:02 AM | Less than 6 months | I’m not an org member yet, but working on it | Yes, doing it on my own. | Europe | UTC+02:00 | One more | 4 | 3 | 2 | 1 | 2 | 1 | 1 | 2 | 1 | n/a | n/a | 1 | 1 | 1 | Automatic retesting of flakes didn't seem to trigger on my PRs | Right notifications at the right frequency | IDK | Yes, it’s part of my job | A few times a week | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | No | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 127 | 10211906690 | 216437765 | 09/12/2018 10:25:40 AM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, doing it on my own. | Europe | UTC+01:00 | 2-4 | 2 | 1 | 5 | 3 | 3 | 3 | 3 | 2 | 2 | 1 | 1 | n/a | 1 | 1 | - | Lots of notifications but they are useful | - | Yes, it’s part of my job | Several times a month | n/a | n/a | Documentation | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | less SIGs | n/a | n/a | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | n/a | n/a | walk through real code contributions in groups, come prepared with real issues suitable for that | 1 | 5 | 4 | 3 | 3 | 3 | 2 | 2 | - | 1 | 2 | 3 | 4 | 5 | n/a | n/a | - | 4 | 4 | 3 | 3 | 4 | 1 | 3 | 3 | 4 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | n/a | n/a | n/a | n/a | n/a | n/a | yes, just contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week | |
| 128 | 10211899789 | 216437765 | 09/12/2018 10:20:12 AM | 6 months -1 year | Org Member | Yes, doing it on my own. | Asia | UTC+08:00 | 2-4 | 1 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | fejta-bot is too slow. | Way too many notifications with no benefits | The membership process. | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | n/a | n/a | Testing & Infrastructure | n/a | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | No, i think the contributing process is clear to me. | n/a | n/a | n/a | Kubecon China 2018 | n/a | n/a | n/a | n/a | n/a | N/A | N/A | 2 | 2 | 3 | 3 | 3 | 2 | N/A | 1 | 2 | 3 | n/a | n/a | n/a | 7 | N/A | 2 | 2 | 2 | 3 | 5 | 1 | 3 | 1 | 3 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | Kubernetes blog | k/community repo in GH (Issues and/or PRs) | n/a | no value for anyone | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week | ||
| 129 | 10211823751 | 216437765 | 09/12/2018 9:31:07 AM | 1-2 years | Reviewer | Yes, doing it on my own. | Europe | UTC+01:00 | 4+ | 5 | 2 | 1 | 2 | 1 | 1 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | none | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | if a sig is labeled on a PR, members should get notification (e.g. auto mention sig-xxx-pr-reviews) sice sigs should be autolabeled by touching the code this would lead to better transparency | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | get rid of Bazel - it is unnecessary barrier causing most merge conflicts on PRs forcing rebases (loosing lgtms and waiting for someone to re-review) | n/a | n/a | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | n/a | n/a | make it 2 days :) | 1 | 1 | 3 | 1 | 4 | 4 | 5 | 4 | none | n/a | 2 | 3 | n/a | n/a | n/a | 7 | n/a | 4 | 4 | 1 | 3 | 5 | 1 | 1 | 2 | 3 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 2 | Not enough time in the week | |
| 130 | 10211753707 | 216437765 | 09/12/2018 7:58:03 AM | Less than 6 months | I’m not an org member yet, but working on it | Yes, doing it on my own. | North America | UTC-08:00 | 2-4 | 3 | 2 | 1 | 1 | 1 | 4 | 2 | 2 | 1 | 1 | n/a | n/a | n/a | 1 | Automatic labeling of stale issues is the least useful feature. | Lots of notifications but they are useful | n/a | Yes, it’s part of my job | A few times a week | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Better responsiveness from reviewers of PRs Reduce test flakiness | n/a | n/a | n/a | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | N/A | n/a | n/a | 3 | 4 | n/a | n/a | n/a | N/A | 3 | 5 | 2 | 4 | 5 | 1 | 2 | 2 | 3 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 131 | 10211648722 | 216437765 | 09/12/2018 6:24:52 AM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Asia | UTC+05:30 | 2-4 | 1 | 3 | 1 | 4 | 4 | 4 | 4 | 2 | 3 | n/a | 1 | 1 | 1 | 1 | User need to remember each command, it could have been a bit easier if UI buttons were also present | Lots of notifications but they are useful | not aware much of such other areas.. will share later on if come across.. | Yes, it’s part of my job | Every day | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Don’t contribute yet, hoping to start soon | Other | I came across a form to ask for mentor which was filled in.. but still I could not find any response for same.. it could have been better if someone can give a brief details on how to start contribution. different sig... their environment setup requirement. Actually these details would have helped me to choose the right SIG for me and have helped me to head start things... Looking forward for some response for form which I filled in regarding mentor.. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 5 | 4 | 4 | 4 | 3 | 4 | 3 | I have started looking into it a couple of weeks ago.. will share these feedback in future.. | 1 | 2 | 3 | n/a | n/a | n/a | 7 | There must be some spoc person for each SIG where we can ask for just some basic question(answers may be in form of email/docs etc) | 3 | 5 | 3 | 4 | 2 | 1 | 3 | 4 | 3 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | Slack | n/a | A dedicated contributor site | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | Yes | 3 | Other (please specify): | |
| 132 | 10211508705 | 216437765 | 09/12/2018 4:47:00 AM | 2-3 years | Subproject Owner | Yes, but would like mentorship. | Asia | UTC+08:00 | 2-4 | 4 | 4 | 1 | 1 | 1 | 3 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | All above tools are useful, but it's better have a bot to ping approvers automatically if the PR hasn't got reviewed for a period. | Way too many notifications with no benefits | ping approvers | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | Advocacy and events | n/a | Plugins & Drivers (CSI, CNI, cloud providers) | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon China 2018 | n/a | n/a | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 1 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | Timezone is a main blocker for me. Maybe hold the meeting in multiple times? | 2 | 3 | 4 | 5 | n/a | n/a | N/A | 3 | 5 | 3 | 2 | 5 | 2 | 2 | 3 | 4 | n/a | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Yes | n/a | A - Yes, I would love to mentor one or both programs | Yes | 4 | Not enough time in the week | ||
| 133 | 10211308450 | 216437765 | 09/12/2018 2:18:54 AM | Less than 6 months | I’m not an org member yet, but working on it | Not really | Europe | UTC+01:00 | 2-4 | 2 | 2 | 2 | 3 | 3 | 3 | 4 | 4 | 3 | n/a | n/a | 1 | 1 | n/a | I do not have much experience with these tools yet | Way too many notifications with no benefits | I am too inexperienced to really say. The notifications are many, still trying to grasp it. | No, but I’m able to use “free” time at work | A few times a year | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | N/A | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 134 | 10211251973 | 216437765 | 09/12/2018 2:17:31 AM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Asia | UTC+08:00 | 4+ | 2 | 1 | 1 | 2 | 3 | 1 | 3 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | k8s-ci-bot so simple and useful. Perhaps we need a document auto generate tool from source code comment, like Sphinx. | Right notifications at the right frequency | Messages archive? Maybe. I wish we can archive message about projects. | Yes, it’s part of my job | Every day | n/a | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | It feels great now. | n/a | n/a | n/a | Kubecon China 2018 | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | Not currently, can learn a lot of content. | 2 | 4 | 3 | 4 | 5 | 4 | 2 | 4 | Not yet. | 1 | 2 | n/a | n/a | 5 | n/a | n/a | Not yet. Thanks. | 5 | 3 | 2 | 3 | 5 | 3 | 4 | 3 | 4 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | n/a | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | A - Yes, I would love to mentor one or both programs | Yes | 3 | Don't know enough to mentor | |
| 135 | 10211204730 | 216437765 | 09/12/2018 1:21:13 AM | 1-2 years | Had no idea this was even a thing | Yes, but would like mentorship. | Europe | UTC±00:00 | 4+ | 2 | 5 | 3 | 3 | 3 | 4 | 3 | 2 | 3 | 1 | 1 | n/a | n/a | 1 | some issue commands may be something that could be done manually with less noise | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | Some push to reviewers before coming stale | Yes, it’s part of my job | A few times a year | n/a | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | More information I guess | 0 | 4 | 3 | 2 | 5 | 4 | 4 | 2 | Nope | 1 | n/a | 3 | n/a | 5 | n/a | 7 | N/A | 2 | 3 | 4 | 1 | 5 | 1 | 5 | 3 | 4 | n/a | n/a | n/a | n/a | A dedicated contributor site | Kubernetes blog | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week | ||
| 136 | 10211174308 | 216437765 | 09/12/2018 1:06:14 AM | Less than 6 months | Reviewer | Yes, but not sure I have time. | Europe | UTC+01:00 | 4+ | 3 | 4 | 1 | 2 | 1 | 4 | 3 | 3 | 3 | 1 | n/a | 1 | 1 | 1 | Commands provide visibility | Way too many notifications with no benefits | no opinion | No, but I’m able to use “free” time at work | Every day | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | I just want to say that the community is very friendly and welcoming - and that is a great start to get people on board! | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 0 | 3 | 3 | 3 | 3 | 2 | 2 | 3 | Give the scale at question 19 - is 1 good or bad? | 2 | n/a | 4 | n/a | n/a | n/a | N/A | 5 | 5 | 1 | 3 | 5 | 3 | 2 | 1 | 3 | n/a | Dedicated discuss.k8s.io forum for contributors | n/a | Slack | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 1 | Don't know enough to mentor | |||
| 137 | 10211083820 | 216437765 | 09/12/2018 12:31:46 AM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but not sure I have time. | Europe | UTC+02:00 | 2-4 | 1 | 2 | 1 | 2 | 2 | 3 | 4 | 3 | 2 | 1 | n/a | n/a | 1 | n/a | Automatic labeling is a bit misleading, but I think that's because the labels were changed recently. I'd like that if you close one issues all PR related to that issues will closed | Lots of notifications but they are useful | I think that some kind of automatic standardization checks for all the related repos to the project should be useful. | No, but I’m able to use “free” time at work | Every day | n/a | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other | I think that's impossible for newbie and part time contributors to catch up with the pace of the core products, however, I see lot of opportunities handling the low hanging fruit on new/incubator projects, helping with the bug triage and system administrations | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 0 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | Continue to iterate and listen to the community | 1 | 2 | n/a | 4 | 5 | 6 | 7 | Centralize all that information | Better documentation | 5 | 4 | 2 | 2 | 3 | 1 | 1 | 1 | 3 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor |
| 138 | 10210970675 | 216437765 | 09/11/2018 11:26:17 PM | Just started | Reviewer | Yes, but would like mentorship. | Asia | UTC+05:30 | None, Kubernetes is my first one! | 3 | 2 | 3 | 1 | 4 | 4 | 3 | 4 | 1 | n/a | 1 | 1 | n/a | n/a | - | Right notifications at the right frequency | - | Yes, it’s part of my job | Several times a month | n/a | n/a | Documentation | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | Need more easy test environment deployment | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | - | 4 | 3 | 4 | 4 | 4 | 4 | 5 | - | 1 | n/a | n/a | 4 | 5 | n/a | n/a | - | 1 | 1 | 3 | 2 | 4 | 2 | 3 | 4 | 1 | n/a | Dedicated discuss.k8s.io forum for contributors | n/a | n/a | n/a | n/a | Kubernetes blog | n/a | n/a | no value for anyone | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | Yes | 3 | Not enough time in the week | ||
| 139 | 10210741104 | 216437765 | 09/11/2018 9:32:40 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-08:00 | One more | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 140 | 10210700667 | 216437765 | 09/11/2018 9:22:02 PM | 3+ years | Subproject Owner | No, I'm already an owner | North America | UTC-07:00 | 2-4 | 1 | 1 | 3 | 1 | 1 | 1 | 1 | 4 | 5 | 1 | 1 | 1 | 1 | 1 | Requiring this survey question | Way too many notifications with no benefits | Fewer survey requirements | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | No | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | No | 2 | 3 | 3 | 3 | 3 | 3 | 3 | 5 | No | n/a | n/a | n/a | n/a | n/a | 6 | n/a | Making 1 mean I like the tool is extremely odd | 3 | 5 | 1 | 3 | 5 | 1 | 2 | 1 | 5 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Other (please specify): | Sometimes but don't think they work well | B - No, I can’t/don’t want to | Yes | 4 | Wasn't connected with mentoring opportunities (reach out to us to get engaged!) | |
| 141 | 10210653661 | 216437765 | 09/11/2018 8:55:20 PM | 2-3 years | Org Member | Not really | North America | UTC-05:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 142 | 10210647774 | 216437765 | 09/11/2018 9:03:27 PM | 1-2 years | Had no idea this was even a thing | Yes, but would like mentorship. | North America | UTC-06:00 | 2-4 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | n/a | 1 | 1 | 1 | 1 | Not sure | Lots of notifications but they are useful | Not sure | Yes, it’s part of my job | A few times a year | n/a | n/a | Documentation | n/a | Advocacy and events | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | Other | Not sure | n/a | Kubecon North America 2017 | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | N/A | 1 | 5 | 4 | 3 | 3 | 3 | 4 | 2 | N/A | 1 | 2 | 3 | n/a | n/a | n/a | n/a | N/A | 4 | 4 | 4 | 2 | 2 | 5 | 3 | 4 | 4 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | A - Yes, I would love to mentor one or both programs | No | 3 | Don't know enough to mentor | |
| 143 | 10210583897 | 216437765 | 09/11/2018 8:26:56 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-07:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 144 | 10210532937 | 216437765 | 09/11/2018 8:17:59 PM | 3+ years | Approver | No, I'm already an owner | North America | UTC+08:00 | None, Kubernetes is my first one! | 2 | 2 | 2 | 2 | 2 | 3 | 2 | 2 | 2 | 1 | 1 | 1 | 1 | 1 | I'd like a /squash command that would take a PR and squash it for me. This would remove the one blocker from contributing to docs and KEPs purely from the Github UI. | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | Squashing via github command. | Yes, it’s part of my job | Several times a month | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | Other | n/a | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | no | 4 | 5 | 4 | 3 | 2 | 2 | 2 | 2 | no | n/a | 2 | n/a | n/a | n/a | n/a | n/a | nope | 3 | 1 | 1 | 3 | 3 | 3 | 2 | 1 | 5 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | no value for anyone | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 1 | Not enough time in the week | |
| 145 | 10210530309 | 216437765 | 09/11/2018 8:20:07 PM | 3+ years | Approver | Not really | Europe | UTC+02:00 | One more | 3 | 2 | 2 | 2 | 1 | 4 | 3 | 3 | 2 | 1 | n/a | 1 | 1 | 1 | I wish cherrypicks were automated | Way too many notifications with no benefits | Cherrypick process | Yes, it’s part of my job | Several times a month | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | Automate cherrypicking | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | No opinion | 1 | 4 | 5 | 3 | 4 | 3 | 3 | 3 | No opinion. | 1 | 2 | n/a | 4 | n/a | n/a | n/a | Nothing | 3 | 2 | 1 | 3 | 5 | 1 | 1 | 3 | 3 | n/a | n/a | n/a | n/a | n/a | n/a | Kubernetes blog | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Nothing, am already a mentor | |
| 146 | 10210524466 | 216437765 | 09/11/2018 8:11:33 PM | Just started | Had no idea this was even a thing | Yes, but not sure I have time. | North America | UTC-08:00 | None, Kubernetes is my first one! | 1 | 2 | 2 | 1 | 1 | 1 | 2 | 2 | 1 | 1 | n/a | n/a | n/a | n/a | - | Lots of notifications but they are useful | - | It’s entirely on my own time | Don’t know yet | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Don’t contribute yet, hoping to start soon | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | - | 0 | 5 | 5 | 4 | 3 | 3 | 3 | 3 | - | n/a | n/a | n/a | n/a | n/a | 6 | n/a | - | 2 | 3 | 3 | 1 | 2 | 2 | 2 | 2 | 2 | n/a | n/a | n/a | n/a | n/a | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | Yes | 4 | Don't know enough to mentor | |
| 147 | 10210517563 | 216437765 | 09/11/2018 8:01:32 PM | Just started | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-07:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 148 | 10210505379 | 216437765 | 09/11/2018 8:11:10 PM | 3+ years | Approver | No, I'm already an owner | North America | UTC-05:00 | 4+ | 2 | 3 | 1 | 2 | 2 | 5 | 1 | 2 | 1 | n/a | n/a | 1 | 1 | 1 | automatic retest is frequently overaggressive, continuously testing a PR that has never passed tests automated tooling around cherry-pick and release branch management would be very helpful | Lots of notifications but they are useful | release branch management (cherry-picks, tracking when a fix needs to be backported, when backport is complete, etc) | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | Plugins & Drivers (CSI, CNI, cloud providers) | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | clarify the intent of each session (information distribution, brainstorming, feedback gathering, etc). each type of session is valuable, but confusing the intent often leads to competing emphases between presenters/attendees | 4 | 2 | 2 | 2 | 4 | 3 | 4 | 2 | n/a | 1 | n/a | n/a | n/a | 5 | n/a | n/a | making common contributor pain points visible to owning sigs and ensuring that feedback loop informs sig actions | 3 | 5 | 1 | 3 | 5 | 2 | 4 | 2 | 4 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | Yes | 3 | Not enough time in the week | |
| 149 | 10210487075 | 216437765 | 09/11/2018 8:04:00 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, doing it on my own. | North America | UTC-05:00 | None, Kubernetes is my first one! | 3 | 1 | 2 | 2 | 3 | 3 | 4 | 4 | 1 | n/a | n/a | n/a | n/a | 1 | N/A | Lots of notifications but they are useful | N/A | Yes, it’s part of my job | A few times a week | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | N/A | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 5 | 4 | 2 | 4 | 4 | 4 | 4 | N/A | 1 | n/a | n/a | n/a | n/a | n/a | 7 | N/A | 4 | 5 | 2 | 3 | 4 | 1 | 1 | 1 | 4 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I didn't know they were there | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 150 | 10210482937 | 216437765 | 09/11/2018 7:57:46 PM | 1-2 years | Reviewer | Yes, but would like mentorship. | Asia | UTC+05:30 | None, Kubernetes is my first one! | 4 | 2 | 2 | 2 | 1 | 4 | 5 | 3 | 4 | 1 | 1 | 1 | 1 | 1 | NA | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | NA | It’s entirely on my own time | Every day | Core code inside of kubernetes/kubernetes | n/a | Documentation | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | More hallway discussions, round table discussions and explanations about overall project architecture, goals, etc | 1 | 2 | 5 | 4 | 5 | 4 | 5 | 5 | I think it's been mentioned previously but if SIG updates could include places where the SIG is looking for contributions or if they could point out good first issues, that would really awesome! | 1 | 2 | 3 | 4 | 5 | 6 | 7 | NA | 5 | 5 | 4 | 4 | 5 | 4 | 3 | 4 | 5 | kubernetes-dev mailing list | Dedicated discuss.k8s.io forum for contributors | Contributor Experience mailing list | Slack | n/a | Kubernetes blog | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | Yes | 5 | Nothing, am already a mentor | ||
| 151 | 10210478715 | 216437765 | 09/11/2018 7:54:05 PM | 3+ years | Approver | Not really | North America | UTC-04:00 | 2-4 | 3 | 3 | 2 | 1 | 1 | 2 | 1 | 1 | 2 | 1 | 1 | 1 | 1 | 1 | If I had to choose, automatic labeling of stale issues. They're all useful, but the others are more important IMHO. | Lots of notifications but they are useful | Not sure | Yes, it’s part of my job | A few times a year | Core code inside of kubernetes/kubernetes | n/a | n/a | n/a | n/a | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | n/a | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | Have more dedicated face to face time with other community members (hackathon style) | 2 | 4 | 4 | 2 | 3 | 3 | 4 | 4 | N/A - I don't regularly attend | 1 | 2 | n/a | n/a | n/a | n/a | 7 | Not sure | 2 | 5 | 2 | 3 | 3 | 1 | 1 | 2 | 2 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Nothing, am already a mentor | |
| 152 | 10210468433 | 216437765 | 09/11/2018 7:57:49 PM | Less than 6 months | Org Member | Yes, doing it on my own. | North America | UTC-08:00 | None, Kubernetes is my first one! | 4 | 3 | 1 | 2 | 5 | 2 | 1 | 1 | 1 | 1 | n/a | n/a | n/a | n/a | Issue commands are noisy, awkward, and sometimes unintuitive. | Lots of notifications but they are useful | ¯\_(ツ)_/¯ | Yes, it’s part of my job | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | Testing & Infrastructure | n/a | n/a | n/a | n/a | n/a | n/a | Tests that don't flake repeatedly on every PR. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | None | N/A | 0 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | I've not gone (and there was no N/A option, and the question as mandatory). | n/a | n/a | n/a | 4 | n/a | n/a | n/a | Reducing test flakes! | 5 | 5 | 1 | 3 | 4 | 1 | 1 | 1 | 3 | kubernetes-dev mailing list | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | No, because I don't think my issues qualify | n/a | B - No, I can’t/don’t want to | No | 3 | Don't know enough to mentor | |
| 153 | 10208654544 | 216437765 | 09/11/2018 12:30:19 AM | Less than 6 months | Org Member | Yes, but not sure I have time. | Europe | UTC+02:00 | 2-4 | 1 | 1 | 2 | 2 | 1 | 3 | 4 | 2 | 2 | n/a | n/a | 1 | 1 | 1 | Mailing test failures is way too spammy. If you have a PR with failing tests, you can easily get way too much emails and it becomes hard to navigate. | Right notifications are being made, but too frequently | Nothing at all. All the most frequent task are automated. | Yes, it’s part of my job | Several times a month | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Easier to find issues to work on. Looking by the issue tracker, it can be find to hard a right one by yourself. Usually, you first need to get in contact with SIG members and to see what you can help with with. Some "automation" around that part could be useful. | n/a | n/a | Kubecon Europe 2018 | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | Not sure :) I liked the format of contributor summer we had this year on KubeCon EU, and would definitely love something similar on upcoming conferences. | 1 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | Community meeting is the best meeting :D | 1 | n/a | 3 | 4 | n/a | n/a | 7 | Nothing at all, I think it covers the most important points. | 2 | 5 | 3 | 4 | 4 | 5 | 1 | 3 | 5 | n/a | n/a | n/a | Slack | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 5 | Don't know enough to mentor | |
| 154 | 10208576582 | 216437765 | 09/11/2018 8:25:13 AM | 1-2 years | Reviewer | Yes, but not sure I have time. | North America | UTC-04:00 | None, Kubernetes is my first one! | 5 | 5 | 1 | 2 | 5 | 2 | 2 | 3 | 3 | n/a | n/a | 1 | n/a | n/a | n/a | Lots of notifications but they are useful | n/a | I’m a student | A few times a week | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon Europe 2017 | Kubecon North America 2017 | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | n/a | 1 | 3 | 2 | 4 | 3 | 3 | 4 | 5 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 155 | 10208225442 | 216437765 | 09/28/2018 9:09:36 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | Europe | UTC+01:00 | None, Kubernetes is my first one! | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 156 | 10208136069 | 216437765 | 09/10/2018 8:39:41 PM | 6 months -1 year | I’m not an org member yet, but working on it | Yes, but would like mentorship. | North America | UTC-07:00 | None, Kubernetes is my first one! | 1 | 1 | 5 | 3 | 4 | 1 | 4 | 4 | 1 | n/a | 1 | 1 | n/a | n/a | Since all my contribution is documentation, I don't find any use in retesting, though I'm confident it would be if I was writing code. | Right notifications are being made, but too frequently | Maybe importing and correlation of documentation from outside sources | It’s complicated | Don’t know yet | n/a | n/a | Documentation | n/a | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | I'd love some review-able tutorials on github usage. It comes up just often enough for me to be rusty every time I use it. | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | Kubecon China 2018 | Kubecon North America 2018 | Kubecon Europe 2019 | n/a | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | Maybe some active mentoring/pairing of new contributors with veterans to provide color during the contributor summits. | 1 | 4 | 4 | 3 | 4 | 5 | 5 | 4 | no | 1 | 2 | 3 | 4 | 5 | n/a | n/a | Maybe even more diversity and outreach programs? | Diversity Initatives | 2 | 5 | 4 | 5 | 1 | 4 | 1 | 2 | 5 | n/a | n/a | Contributor Experience mailing list | Slack | n/a | n/a | n/a | n/a | yes, for both users and contributors | Other (please specify): | No, because I'm not really filing many issues. | B - No, I can’t/don’t want to | Yes | 5 | Employer doesn't support spending time mentoring | |
| 157 | 10208101835 | 216437765 | 09/10/2018 8:05:32 PM | 6 months -1 year | Org Member | Yes, but not sure I have time. | Europe | UTC+02:00 | 2-4 | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 158 | 10208029121 | 216437765 | 09/10/2018 7:44:22 PM | 2-3 years | Subproject Owner | No, I'm already an owner | North America | UTC-08:00 | 4+ | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | N/A | Lots of notifications but they are useful | n/a | No, but I’m able to use “free” time at work | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | n/a | Testing & Infrastructure | n/a | Community & Project management; SIG Chair etc. | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | n/a | Nope | n/a | n/a | n/a | n/a | Kubecon North America 2018 | n/a | n/a | n/a | n/a | N/A | 0 | 1 | 3 | 2 | 5 | 3 | 5 | 5 | Nope | n/a | 2 | n/a | 4 | 5 | n/a | n/a | N/A | 5 | 5 | 2 | 4 | 5 | 1 | 1 | 3 | 4 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | n/a | n/a | n/a | n/a | n/a | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | Yes | 4 | Not enough time in the week | |
| 159 | 10208020798 | 216437765 | 09/26/2018 4:25:29 AM | 3+ years | Subproject Owner | Yes, but not sure I have time. | South America | UTC-04:00 | 4+ | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 1 | n/a | 1 | 1 | n/a | . | Not enough notifications and I frequently miss important things (e.g when my review/approval is needed) | . | Yes, it’s part of my job | Every day | n/a | Code inside of another repo in the kubernetes/* GitHub organization | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Other | n/a | n/a | Kubecon North America 2017 | Kubecon Europe 2018 | n/a | n/a | n/a | n/a | n/a | n/a | N/A | 2 | 4 | 3 | 3 | 3 | 3 | 3 | 3 | N/A | n/a | 2 | n/a | n/a | n/a | 6 | n/a | N/A | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| 160 | 10204125563 | 216437765 | 09/08/2018 6:20:19 AM | 1-2 years | Subproject Owner | Yes, doing it on my own. | North America | UTC-05:00 | One more | 3 | 2 | 3 | 2 | 1 | 3 | 3 | 3 | 2 | 1 | 1 | 1 | 1 | 1 | n/a | Lots of notifications but they are useful | KEP / Features / requests for new features, specifically for new Contributors or passerbys | Yes, it’s part of my job | Every day | n/a | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | Community & Project management; SIG Chair etc. | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | Kubecon North America 2018 | Kubecon Europe 2019 | Ecosystem events, eg. Helm Summit | Other conferences with a Kubernetes track (like DockerCon or ContainerDay) | n/a | Haven't been to one yet, but a strong focus on all types of Contributors (e.g., non-code) and having leaders from those segments available is key. | 0 | 4 | 5 | 4 | 5 | 5 | 5 | 5 | I think it's pretty great. Would like to see more around product roadmap from SIGs | 1 | 2 | 3 | 4 | 5 | 6 | 7 | Process around creating a better feedback loop for non-contributors requesting improvements. Triage to delivery. | 5 | 5 | 3 | 5 | 5 | 3 | 1 | 3 | 5 | kubernetes-dev mailing list | n/a | n/a | Slack | n/a | n/a | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Not as much as I should because I forget | n/a | B - No, I can’t/don’t want to | Yes | 5 | Not enough time in the week | ||
| 161 | 10203989035 | 216437765 | 09/08/2018 4:15:43 AM | 1-2 years | Org Member | Yes, doing it on my own. | Europe | UTC+03:00 | 2-4 | 3 | 3 | 3 | 1 | 4 | 5 | 1 | 3 | 2 | n/a | 1 | 1 | 1 | 1 | n/a | Right notifications at the right frequency | n/a | n/a | Every day | Core code inside of kubernetes/kubernetes | Code inside of another repo in the kubernetes/* GitHub organization | Documentation | Testing & Infrastructure | Advocacy and events | n/a | n/a | Related projects (Kubeadm, Helm, container runtimes, etc.) | n/a | Other | less test flakes, faster code reviews | n/a | n/a | Kubecon Europe 2018 | n/a | n/a | Kubecon Europe 2019 | n/a | n/a | n/a | n/a | n/a | 4 | 3 | 2 | 4 | 3 | 3 | 3 | n/a | n/a | 2 | n/a | n/a | n/a | n/a | n/a | n/a | 5 | 5 | 3 | 5 | 5 | 1 | 1 | 5 | 5 | kubernetes-dev mailing list | n/a | Contributor Experience mailing list | Slack | n/a | n/a | Kubernetes blog | k/community repo in GH (Issues and/or PRs) | n/a | yes, for both users and contributors | Yes | n/a | B - No, I can’t/don’t want to | No | 3 | Not enough time in the week |