forked from kubernetes/community
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathcontribex-survey-2018.csv
More file actions
161 lines (161 loc) · 155 KB
/
Copy pathcontribex-survey-2018.csv
File metadata and controls
161 lines (161 loc) · 155 KB
Edit and raw actions
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? |
|---|