Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

user survey questions #2525

Closed
errordeveloper opened this issue Feb 8, 2018 · 13 comments
Closed

user survey questions #2525

errordeveloper opened this issue Feb 8, 2018 · 13 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. kind/ux lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@errordeveloper
Copy link
Member

It'd be good to create a survey, so that we have a better idea of how folks use minikube and why they use it that way.

One of the key questions would be about what drivers folks use, and why that driver is important to them, so that we can consider what drivers can be safely deprecated, and find out what alternative options can serve the same use case.

This issue is for the discussion of what questions we want to ask the users.

@afbjorklund
Copy link
Collaborator

What bootstrapper that people use, could also be of interest. And the Kubernetes version, I suppose.

@errordeveloper
Copy link
Member Author

And the Kubernetes version, I suppose.

Yes, I think we should have multiple questions about version, namely to identify how many folks would be okay with latest stable release and how many folks need some particular versions for some specific use-case.

@dlorenc
Copy link
Contributor

dlorenc commented Feb 14, 2018

How's this for a draft list:

  1. What driver(s) do you use regularly
  2. What platform do you run on (Windows, OSX, Linux)
  3. What Kubernetes versions do you use
  4. What --extra-config parameters do you use
  5. What addons do you use

@dlorenc
Copy link
Contributor

dlorenc commented Feb 14, 2018

cc @kimsterv

@afbjorklund
Copy link
Collaborator

Something semi-related, that is: more of a future possibility, but still interesting to ask to ask users, would be on the lines of:

  • are you interested in having a multi-node minikube (beyond current single-node)

@afbjorklund
Copy link
Collaborator

Should also ask about: container runtime

@r2d4 r2d4 added kind/documentation Categorizes issue or PR as related to documentation. priority/P0 kind/ux labels Mar 5, 2018
@errordeveloper
Copy link
Member Author

From wg-app-def survey:

  • How would you describe your usage of Minikube
    • I regularly use Minikube
    • I use a competitor to Minikube instead
    • I do not use Minikube or any of its competitors
  • What do you like about Minikube? (if they use minikube)
  • What would you like to see added or change in Minikube? (if they use minikube)
  • Which competitor to Minikube do you use and why do you use it? (if they use a competitor)
  • What platform do you run on (Windows, OSX, Linux)
  • What driver(s) do you use regularly with Minikube?
  • What bootstrapper do you use with Minikube?
  • What version of Kubernetes are up you using? Do you need support for older version or is the latest stable release enough?
  • What --extra-config parameters do you use?
  • What addons do you use?
  • Are you interested in having a multi-node minikube (beyond current single-node)?

@errordeveloper
Copy link
Member Author

Do we think we have enough here to sketch a basic survey form or there is anything we should add?

I think wg-app-def has a good number of questions, but participants have to answer more questions, and it seems like a rather better option to have more short and targeted surveys... so perhaps we could ask wg-app-def to relay some of the deeper questions onto this survey?

@r2d4
Copy link
Contributor

r2d4 commented Mar 8, 2018

Did this go out already? I changed up some of the wording to not be so harsh (alternative rather than competitor) and added the question about container-runtime

@errordeveloper
Copy link
Member Author

@r2d4 no, I don't think it went out yet. Last time I checked with @mattfarina, he said they were going to come back to it after Helm Summit (which was just over a week ago).

@fejta-bot
Copy link

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

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

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

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

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

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

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

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

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

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

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

No branches or pull requests

6 participants