Welcome!

Once again, the Foreman team would like to collect information about our user-base in order to find out more about the needs of the community and how well we're doing in meeting them. This helps us direct our efforts over the coming year.

Since the multi-page format seemed to work last year, we've used it again, and again all question responses are optional. If you're uncomfortable with any part of it, just skip that one!

Your responses are only visible to the Foreman Community Team, and will be used solely to help improve the Foreman community. If you've submitted anything in error, or would like to have your data deleted, you can contact mcorr AT redhat DOT com for help.

Lets get started! First, let's cover some basic metrics on Foreman itself

Question Title

* 1. How long have you been using Foreman? Think about the first time you opened the dashboard, even if it was not a production installation

Question Title

* 2. What Foreman version are you using?

Question Title

* 3. How many people use Foreman in your organization?

Question Title

* 4. How many hosts do you manage with Foreman?

Question Title

* 5. How many Smart Proxies do you have?

Question Title

* 6. In your Foreman deployment, which operating system(s) are your Foreman server and smart proxies deployed on?

Question Title

* 7. In your Foreman deployment, what are the main operating systems that most of your Hosts use?

Question Title

* 8. How do you install and upgrade your Foreman server and proxies?

Question Title

* 9. How would you rate our user support?

  1 (awful) 2 3 (neutral) 4 5 (excellent)
Forum
IRC
Manual
Website

Question Title

* 10. How satisfied are you with the Foreman web UI?

Question Title

* 11. Overall, how well does Foreman meet your requirements?

Question Title

* 12. What changes would you like to see in the project?
We'll ask this now in case you don't make it to the end :P - this could be the most important feature you'd like to see added next, or pain points you are currently fighting with, or changes to the project structure itself. Fire away!

0 of 34 answered
 

T