Draft community survey questions

Development
#1

Hi all,

Last year I rushed the community survey, and forgot to get feedback on
the questions it contained - I'm not making that mistake again :slight_smile:

Below is the draft question set - fair warning, its a big email :P. My
aim is to either make it shorter, or at least break it up into a couple
of logical pages. I've tried to indicate where the departures from last
year are (especially the dropped/potentially-dropped ones). Feedback on
what to change or things to add is very welcome - if you have a burning
question to ask, lets hear it!

Additionally, I may be able to fund some small incentive strategy to get
a larger sample size. I can see two ways to do that:

  • Some small reward for the first X people to fill out the survey (eg $5
    gift card or something)
  • All response go into a raffle for some nice (more expensive) things

Clearly this would require the user to identify themselves (an email is
probably all I'd need) - that would be optional, of course. Do people
support this? What would be your preferred option?

The plan is to gather feedback on this in the New Year, publish the
survey by mid January with a big push for early responders (hence the
swag incentive above) and then re-push in person at the conferences. We
then close it after about a month (mid Feb) and do the analysis.

Anyway, the questions:

To keep from last year - self-explanatory

How long have you been using Foreman?
[3m, 6m, 1yr, 2y, 3+yr]

How many people use Foreman in your organization
[1, 5, 10, 50+]

What Foreman version are you using?
[nightly, stable, old-stable, older]

How many nodes do you manage with Foreman?
[0, 10, 50, 200, 500, 1000, 10000, 20000+]

What operating system do most of your Foreman servers use?
[RHEL/CentOS/Fedora, Debian, Ubuntu, SUSE, Other]
(do we need to split this more, eg Fedora vs RHEL?)

Which Compute Resources do you use with Foreman?
Which Foreman plugins do you use?
these two need better structuring, the lists are long & stats were
skewed
last year due to missing options. See end of post for the actual
lists.

How would you rate our user support?
[mailing list, IRC, website, docs], 1-5 score

How well do major releases (e.g. 1.9, 1.10) meet your needs?
[frequency, features, bugs, stability], 1-5 score

Any other feedback about our support and documentation? [text]

Overall, how well does Foreman meets your requirements? [text]

What's the most important thing you'd like to see done next in Foreman?
[text]

Do you have any additional comments or special requests? [text]

New additions

Would you accept Foreman gathering anonymous usage stats to help improve
the
project? This would have an opt-out and a way to see the data before
sending
(see https://github.com/theforeman/rfcs/pull/31 for a proposed design -
comments
welcome!)
I really want to hear user feedback on this to avoid backlash later.
Not
sure if it should be a simple yes/no or text-field for comments.

What geographical area are you in?
[Europe, N America, S America, Africa, Asia, Oceania]
We don't really know where our userbase is, although we have a hunch.
I've
tried to keep it coarse, and it'll obviously be optional.

Dropped from last year

What do you use Foreman for at your organization?
I think our problem domain is fairly well specified, and knowledge of
specific plugins/CRs is more specific & valuable. Anything really
ugent will
end up in the "most important thing" or "additional comments" boxes

What are your top 3 from the following potential future features?
Basically the same thing as "what's most important to add", just ask
it once

Why did you choose it instead of alternatives?
I think I'd rather focus on Foreman than go off on a tangent. People
who
are switching away won't fill in the survey anyway.

Do you Use Locations / Organization features?
Could you tell us more about your usage of Locations/Organizations?
Any other feedback on your Locations/Organizations usage that you'd
share?
I think we've gathered all the feedback we can on this last year.

Would you be interested participating in a foreman community event?
Would you be willing to help organise Foreman events in your area?
We saw good responses to the birthday events, but these questions
don't work
on an anonymous survey. Potential to add back in if we ask for email
addrs

Optional from last year - comments welcome

Do you use the Foreman API or Hammer?
I guess people are more aware of this now? Could add back in, or
rephrase.
What things do these teams want to learn?

Are you aware of the existence of #theforeman IRC and the -user mailing
list?
I think we push this as hard as we can - if this is a low score we
can't
take any further action anyway

How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Frequency]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Support
dur.]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Fixing
bugs]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Stability]
Quite repetitive after the major release question, and broadly
produces the
same data, so removed to shorten the survey.

Contributor survey

Generally: Do we still think this is a good idea? We get a lot of
metrics from Redmine/GitHub etc, but I'm keen to learn where the pain
points are for new contributors.

Do you contribute to Foreman in some way?
[yes, no, would like to]

What areas of Foreman do you currently contribute to / want to get
started on?
[bugs, testing, translations, installer, core, proxy, plugins, none,
other]

Rate the following, for ease of use
[Finding docs, dev env, bugs, PRs, getting help, getting feedback]

Are you aware of the following development resources?
[handbook, wiki, deep dives, demos]

What's your biggest problem with contributing that we need to solve?
[text]

Any other contributing comments? [text]

··· ###

Thats the questions. Below are the current list of plugins. I think this
is a bit loo long - we could either

  • take the top 20 or so from the download metrics, or
  • Do plugins / CRs on their own survey page

CR list (wiki/List_of_Plugins + core)
Amazon EC2
Azure
DigitalOcean
Docker
Google Compute Engine
Libvirt
OpenNebula (foreman_one)
OpenStack
oVirt
Rackspace
VMware
Xen

Plugin list: (from wiki/List_of_Plugins)
foreman_abrt
foreman_ansible
foreman_audited_notifications
foreman_bootdisk
foreman_chef
foreman_cockpit
foreman_column_view
foreman_custom_banner
foreman_custom_parameters
foreman_default_hostgroup
foreman_dhcp_browser
foreman_discovery
foreman_epel_release
foreman_expire_hosts
foreman_graphite
foreman_hooks
foreman_host_extra_validator
foreman_host_overview
foreman_host_rundeck
foreman_memcache
foreman_monitoring
foreman_noenv
foreman_omaha
foreman_openscap
foreman_ovirt
foreman_param_lookup
foreman_pipeline
foreman_plugin_computeresource_
foreman_plugin_exec_cmd
foreman_radiator
foreman_remote_execution
foreman_reserve
foreman_resources
foreman_salt
foreman_sentry
foreman_setup
foreman_slack
foreman_templates
hostgroup_extra_validator_foreman
hubot_notify
katello
puppetdb_foreman

Smart Proxy Plugin List (that aren’t already covered by a core plugin):
smart_proxy_dhcp_infoblox
smart_proxy_dns_infoblox
smart_proxy_dns_powerdns
smart_proxy_dns_route53
smart_proxy_pulp (covered by katello?)
smart_proxy_vault

Comments welcome!

Greg
IRC / Twitter: gwmngilfen
Diaspora: gwmngilfen@joindiaspora.com

#2

Some question in line below. Could we add some questions around smart
proxies? I don't know that I have any idea about:

  • how many smart proxies users deploy in their environments
  • what features of the smart proxy
  • what plugins to smart proxies users use

The plugin question would cover which configuration management project
users use, but it wouldn't indicate Puppet usage and Puppet 3 vs Puppet 4
usage in our ecosystem. A question around those two might be useful.

+! to splitting out the OS distros into versions (e.g. RHEL6, RHEL7, Fedora
24, CentOS 6, Debian Jessie) as that gives us a better idea of where to
focus and may help some plugins decide on what they want to focus their
support on.

Would it be worth asking an open ended question about what users pain
points are? I suppose the foreman-users post did this but still might be
worth it in the official survey.

Something to consider to help Katello developers would be a question around
how many users do not currently manage content but plan to in the future.
You could perhaps ask this more broadly about plugins that users plan to
add to their environments.

>
> Do you Use Locations / Organization features?
>

Why drop this question? Given how hotly some developers discuss this, I
think this is valuable data.

··· > Could you tell us more about your usage of Locations/Organizations? > Any other feedback on your Locations/Organizations usage that you'd share? > I think we've gathered all the feedback we can on this last year. > >
#3

I think plugins should be on a separate page or it should be an open
question because even a list on 20 is too long.
CRs can appear in the question itself, it's pushing it but the list is
still reasonable.

Maybe the question: How would you rate our user support? can have links
instead of bringing back the do you know our IRC question?

+1 for the contributor survey.

··· On Wed, Dec 21, 2016 at 10:04 PM, Greg Sutcliffe wrote:

Hi all,

Last year I rushed the community survey, and forgot to get feedback on the
questions it contained - I’m not making that mistake again :slight_smile:

Below is the draft question set - fair warning, its a big email :P. My aim
is to either make it shorter, or at least break it up into a couple of
logical pages. I’ve tried to indicate where the departures from last year
are (especially the dropped/potentially-dropped ones). Feedback on what to
change or things to add is very welcome - if you have a burning question to
ask, lets hear it!

Additionally, I may be able to fund some small incentive strategy to get a
larger sample size. I can see two ways to do that:

  • Some small reward for the first X people to fill out the survey (eg $5
    gift card or something)
  • All response go into a raffle for some nice (more expensive) things

Clearly this would require the user to identify themselves (an email is
probably all I’d need) - that would be optional, of course. Do people
support this? What would be your preferred option?

The plan is to gather feedback on this in the New Year, publish the survey
by mid January with a big push for early responders (hence the swag
incentive above) and then re-push in person at the conferences. We then
close it after about a month (mid Feb) and do the analysis.

Anyway, the questions:

To keep from last year - self-explanatory

How long have you been using Foreman?
[3m, 6m, 1yr, 2y, 3+yr]

How many people use Foreman in your organization
[1, 5, 10, 50+]

What Foreman version are you using?
[nightly, stable, old-stable, older]

How many nodes do you manage with Foreman?
[0, 10, 50, 200, 500, 1000, 10000, 20000+]

What operating system do most of your Foreman servers use?
[RHEL/CentOS/Fedora, Debian, Ubuntu, SUSE, Other]
(do we need to split this more, eg Fedora vs RHEL?)

Which Compute Resources do you use with Foreman?
Which Foreman plugins do you use?
these two need better structuring, the lists are long & stats were skewed
last year due to missing options. See end of post for the actual lists.

How would you rate our user support?
[mailing list, IRC, website, docs], 1-5 score

How well do major releases (e.g. 1.9, 1.10) meet your needs?
[frequency, features, bugs, stability], 1-5 score

Any other feedback about our support and documentation? [text]

Overall, how well does Foreman meets your requirements? [text]

What’s the most important thing you’d like to see done next in Foreman?
[text]

Do you have any additional comments or special requests? [text]

New additions

Would you accept Foreman gathering anonymous usage stats to help improve
the
project? This would have an opt-out and a way to see the data before
sending
(see https://github.com/theforeman/rfcs/pull/31 for a proposed design -
comments
welcome!)
I really want to hear user feedback on this to avoid backlash later. Not
sure if it should be a simple yes/no or text-field for comments.

What geographical area are you in?
[Europe, N America, S America, Africa, Asia, Oceania]
We don’t really know where our userbase is, although we have a hunch.
I’ve
tried to keep it coarse, and it’ll obviously be optional.

Dropped from last year

What do you use Foreman for at your organization?
I think our problem domain is fairly well specified, and knowledge of
specific plugins/CRs is more specific & valuable. Anything really ugent
will
end up in the “most important thing” or “additional comments” boxes

What are your top 3 from the following potential future features?
Basically the same thing as “what’s most important to add”, just ask it
once

Why did you choose it instead of alternatives?
I think I’d rather focus on Foreman than go off on a tangent. People who
are switching away won’t fill in the survey anyway.

Do you Use Locations / Organization features?
Could you tell us more about your usage of Locations/Organizations?
Any other feedback on your Locations/Organizations usage that you’d share?
I think we’ve gathered all the feedback we can on this last year.

Would you be interested participating in a foreman community event?
Would you be willing to help organise Foreman events in your area?
We saw good responses to the birthday events, but these questions don’t
work
on an anonymous survey. Potential to add back in if we ask for email
addrs

Optional from last year - comments welcome

Do you use the Foreman API or Hammer?
I guess people are more aware of this now? Could add back in, or
rephrase.
What things do these teams want to learn?

Are you aware of the existence of #theforeman IRC and the -user mailing
list?
I think we push this as hard as we can - if this is a low score we can’t
take any further action anyway

How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Frequency]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Support dur.]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Fixing bugs]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Stability]
Quite repetitive after the major release question, and broadly produces
the
same data, so removed to shorten the survey.

Contributor survey

Generally: Do we still think this is a good idea? We get a lot of metrics
from Redmine/GitHub etc, but I’m keen to learn where the pain points are
for new contributors.

Do you contribute to Foreman in some way?
[yes, no, would like to]

What areas of Foreman do you currently contribute to / want to get started
on?
[bugs, testing, translations, installer, core, proxy, plugins, none, other]

Rate the following, for ease of use
[Finding docs, dev env, bugs, PRs, getting help, getting feedback]

Are you aware of the following development resources?
[handbook, wiki, deep dives, demos]

What’s your biggest problem with contributing that we need to solve? [text]

Any other contributing comments? [text]

Thats the questions. Below are the current list of plugins. I think this
is a bit loo long - we could either

  • take the top 20 or so from the download metrics, or
  • Do plugins / CRs on their own survey page

CR list (wiki/List_of_Plugins + core)
Amazon EC2
Azure
DigitalOcean
Docker
Google Compute Engine
Libvirt
OpenNebula (foreman_one)
OpenStack
oVirt
Rackspace
VMware
Xen

Plugin list: (from wiki/List_of_Plugins)
foreman_abrt
foreman_ansible
foreman_audited_notifications
foreman_bootdisk
foreman_chef
foreman_cockpit
foreman_column_view
foreman_custom_banner
foreman_custom_parameters
foreman_default_hostgroup
foreman_dhcp_browser
foreman_discovery
foreman_epel_release
foreman_expire_hosts
foreman_graphite
foreman_hooks
foreman_host_extra_validator
foreman_host_overview
foreman_host_rundeck
foreman_memcache
foreman_monitoring
foreman_noenv
foreman_omaha
foreman_openscap
foreman_ovirt
foreman_param_lookup
foreman_pipeline
foreman_plugin_computeresource_
foreman_plugin_exec_cmd
foreman_radiator
foreman_remote_execution
foreman_reserve
foreman_resources
foreman_salt
foreman_sentry
foreman_setup
foreman_slack
foreman_templates
hostgroup_extra_validator_foreman
hubot_notify
katello
puppetdb_foreman

Smart Proxy Plugin List (that aren’t already covered by a core plugin):
smart_proxy_dhcp_infoblox
smart_proxy_dns_infoblox
smart_proxy_dns_powerdns
smart_proxy_dns_route53
smart_proxy_pulp (covered by katello?)
smart_proxy_vault

Comments welcome!

Greg
IRC / Twitter: gwmngilfen
Diaspora: gwmngilfen@joindiaspora.com

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

#4

> Hi all,
>
> Last year I rushed the community survey, and forgot to get feedback on the
> questions it contained - I'm not making that mistake again :slight_smile:
>
> Below is the draft question set - fair warning, its a big email :P. My aim
> is to either make it shorter, or at least break it up into a couple of
> logical pages. I've tried to indicate where the departures from last year
> are (especially the dropped/potentially-dropped ones). Feedback on what to
> change or things to add is very welcome - if you have a burning question to
> ask, lets hear it!
>
> Additionally, I may be able to fund some small incentive strategy to get a
> larger sample size. I can see two ways to do that:
>
> * Some small reward for the first X people to fill out the survey (eg $5
> gift card or something)
> * All response go into a raffle for some nice (more expensive) things

+1 for the raffle. It motivates you to respond even on the last day of
the survey. How about raffle for the foreman t-shirts? Or is it too
common and everybody already has one from conferences?

··· On Wed, Dec 21, 2016 at 9:04 PM, Greg Sutcliffe wrote:

Clearly this would require the user to identify themselves (an email is
probably all I’d need) - that would be optional, of course. Do people
support this? What would be your preferred option?

The plan is to gather feedback on this in the New Year, publish the survey
by mid January with a big push for early responders (hence the swag
incentive above) and then re-push in person at the conferences. We then
close it after about a month (mid Feb) and do the analysis.

Anyway, the questions:

To keep from last year - self-explanatory

How long have you been using Foreman?
[3m, 6m, 1yr, 2y, 3+yr]

How many people use Foreman in your organization
[1, 5, 10, 50+]

What Foreman version are you using?
[nightly, stable, old-stable, older]

How many nodes do you manage with Foreman?
[0, 10, 50, 200, 500, 1000, 10000, 20000+]

What operating system do most of your Foreman servers use?
[RHEL/CentOS/Fedora, Debian, Ubuntu, SUSE, Other]
(do we need to split this more, eg Fedora vs RHEL?)

Which Compute Resources do you use with Foreman?
Which Foreman plugins do you use?
these two need better structuring, the lists are long & stats were skewed
last year due to missing options. See end of post for the actual lists.

How would you rate our user support?
[mailing list, IRC, website, docs], 1-5 score

How well do major releases (e.g. 1.9, 1.10) meet your needs?
[frequency, features, bugs, stability], 1-5 score

Any other feedback about our support and documentation? [text]

Overall, how well does Foreman meets your requirements? [text]

What’s the most important thing you’d like to see done next in Foreman?
[text]

Do you have any additional comments or special requests? [text]

New additions

Would you accept Foreman gathering anonymous usage stats to help improve the
project? This would have an opt-out and a way to see the data before sending
(see https://github.com/theforeman/rfcs/pull/31 for a proposed design -
comments
welcome!)
I really want to hear user feedback on this to avoid backlash later. Not
sure if it should be a simple yes/no or text-field for comments.

What geographical area are you in?
[Europe, N America, S America, Africa, Asia, Oceania]
We don’t really know where our userbase is, although we have a hunch. I’ve
tried to keep it coarse, and it’ll obviously be optional.

Dropped from last year

What do you use Foreman for at your organization?
I think our problem domain is fairly well specified, and knowledge of
specific plugins/CRs is more specific & valuable. Anything really ugent
will
end up in the “most important thing” or “additional comments” boxes

What are your top 3 from the following potential future features?
Basically the same thing as “what’s most important to add”, just ask it
once

Why did you choose it instead of alternatives?
I think I’d rather focus on Foreman than go off on a tangent. People who
are switching away won’t fill in the survey anyway.

Do you Use Locations / Organization features?
Could you tell us more about your usage of Locations/Organizations?
Any other feedback on your Locations/Organizations usage that you’d share?
I think we’ve gathered all the feedback we can on this last year.

Would you be interested participating in a foreman community event?
Would you be willing to help organise Foreman events in your area?
We saw good responses to the birthday events, but these questions don’t
work
on an anonymous survey. Potential to add back in if we ask for email
addrs

Optional from last year - comments welcome

Do you use the Foreman API or Hammer?
I guess people are more aware of this now? Could add back in, or rephrase.
What things do these teams want to learn?

Are you aware of the existence of #theforeman IRC and the -user mailing
list?
I think we push this as hard as we can - if this is a low score we can’t
take any further action anyway

How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Frequency]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Support dur.]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Fixing bugs]
How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Stability]
Quite repetitive after the major release question, and broadly produces
the
same data, so removed to shorten the survey.

Contributor survey

Generally: Do we still think this is a good idea? We get a lot of metrics
from Redmine/GitHub etc, but I’m keen to learn where the pain points are for
new contributors.

Do you contribute to Foreman in some way?
[yes, no, would like to]

What areas of Foreman do you currently contribute to / want to get started
on?
[bugs, testing, translations, installer, core, proxy, plugins, none, other]

Rate the following, for ease of use
[Finding docs, dev env, bugs, PRs, getting help, getting feedback]

Are you aware of the following development resources?
[handbook, wiki, deep dives, demos]

What’s your biggest problem with contributing that we need to solve? [text]

Any other contributing comments? [text]

Thats the questions. Below are the current list of plugins. I think this is
a bit loo long - we could either

  • take the top 20 or so from the download metrics, or
  • Do plugins / CRs on their own survey page

CR list (wiki/List_of_Plugins + core)
Amazon EC2
Azure
DigitalOcean
Docker
Google Compute Engine
Libvirt
OpenNebula (foreman_one)
OpenStack
oVirt
Rackspace
VMware
Xen

Plugin list: (from wiki/List_of_Plugins)
foreman_abrt
foreman_ansible
foreman_audited_notifications
foreman_bootdisk
foreman_chef
foreman_cockpit
foreman_column_view
foreman_custom_banner
foreman_custom_parameters
foreman_default_hostgroup
foreman_dhcp_browser
foreman_discovery
foreman_epel_release
foreman_expire_hosts
foreman_graphite
foreman_hooks
foreman_host_extra_validator
foreman_host_overview
foreman_host_rundeck
foreman_memcache
foreman_monitoring
foreman_noenv
foreman_omaha
foreman_openscap
foreman_ovirt
foreman_param_lookup
foreman_pipeline
foreman_plugin_computeresource_
foreman_plugin_exec_cmd
foreman_radiator
foreman_remote_execution
foreman_reserve
foreman_resources
foreman_salt
foreman_sentry
foreman_setup
foreman_slack
foreman_templates
hostgroup_extra_validator_foreman
hubot_notify
katello
puppetdb_foreman

Smart Proxy Plugin List (that aren’t already covered by a core plugin):
smart_proxy_dhcp_infoblox
smart_proxy_dns_infoblox
smart_proxy_dns_powerdns
smart_proxy_dns_route53
smart_proxy_pulp (covered by katello?)
smart_proxy_vault

Comments welcome!

Greg
IRC / Twitter: gwmngilfen
Diaspora: gwmngilfen@joindiaspora.com

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

#5

> Hi all,
>
> Last year I rushed the community survey, and forgot to get feedback on the
> questions it contained - I'm not making that mistake again :slight_smile:
>
> Below is the draft question set - fair warning, its a big email :P. My aim
> is to either make it shorter, or at least break it up into a couple of
> logical pages. I've tried to indicate where the departures from last year
> are (especially the dropped/potentially-dropped ones). Feedback on what to
> change or things to add is very welcome - if you have a burning question to
> ask, lets hear it!
>
> Additionally, I may be able to fund some small incentive strategy to get a
> larger sample size. I can see two ways to do that:
>
> * Some small reward for the first X people to fill out the survey (eg $5
> gift card or something)
> * All response go into a raffle for some nice (more expensive) things
>
> Clearly this would require the user to identify themselves (an email is
> probably all I'd need) - that would be optional, of course. Do people
> support this? What would be your preferred option?
>
> The plan is to gather feedback on this in the New Year, publish the survey
> by mid January with a big push for early responders (hence the swag
> incentive above) and then re-push in person at the conferences. We then
> close it after about a month (mid Feb) and do the analysis.
>
> Anyway, the questions:
>
> ### To keep from last year - self-explanatory
>
> How long have you been using Foreman?
> [3m, 6m, 1yr, 2y, 3+yr]
>
> How many people use Foreman in your organization
> [1, 5, 10, 50+]
>
> What Foreman version are you using?
> [nightly, stable, old-stable, older]
>
> How many nodes do you manage with Foreman?
> [0, 10, 50, 200, 500, 1000, 10000, 20000+]
>
> What operating system do most of your Foreman servers use?
> [RHEL/CentOS/Fedora, Debian, Ubuntu, SUSE, Other]
> (do we need to split this more, eg Fedora vs RHEL?)
>
> Which Compute Resources do you use with Foreman?
> Which Foreman plugins do you use?
> these two need better structuring, the lists are long & stats were skewed
> last year due to missing options. See end of post for the actual lists.
>
> How would you rate our user support?
> [mailing list, IRC, website, docs], 1-5 score
>
> How well do major releases (e.g. 1.9, 1.10) meet your needs?
> [frequency, features, bugs, stability], 1-5 score
>
> Any other feedback about our support and documentation? [text]
>
> Overall, how well does Foreman meets your requirements? [text]
>
> What's the most important thing you'd like to see done next in Foreman?
> [text]
>
> Do you have any additional comments or special requests? [text]
>
> ### New additions
>
> Would you accept Foreman gathering anonymous usage stats to help improve
> the
> project? This would have an opt-out and a way to see the data before
> sending
> (see https://github.com/theforeman/rfcs/pull/31 for a proposed design -
> comments
> welcome!)
> I really want to hear user feedback on this to avoid backlash later. Not
> sure if it should be a simple yes/no or text-field for comments.
>
> What geographical area are you in?
> [Europe, N America, S America, Africa, Asia, Oceania]
> We don't really know where our userbase is, although we have a hunch.
> I've
> tried to keep it coarse, and it'll obviously be optional.
>
> ### Dropped from last year
>
> What do you use Foreman for at your organization?
> I think our problem domain is fairly well specified, and knowledge of
> specific plugins/CRs is more specific & valuable. Anything really ugent
> will
> end up in the "most important thing" or "additional comments" boxes
>
> What are your top 3 from the following potential future features?
> Basically the same thing as "what's most important to add", just ask it
> once
>
> Why did you choose it instead of alternatives?
> I think I'd rather focus on Foreman than go off on a tangent. People who
> are switching away won't fill in the survey anyway.
>
> Do you Use Locations / Organization features?
> Could you tell us more about your usage of Locations/Organizations?
> Any other feedback on your Locations/Organizations usage that you'd share?
> I think we've gathered all the feedback we can on this last year.
>
> Would you be interested participating in a foreman community event?
> Would you be willing to help organise Foreman events in your area?
> We saw good responses to the birthday events, but these questions don't
> work
> on an anonymous survey. Potential to add back in if we ask for email
> addrs
>
> ### Optional from last year - comments welcome
>
> Do you use the Foreman API or Hammer?
> I guess people are more aware of this now? Could add back in, or
> rephrase.
> What things do these teams want to learn?
>
> Are you aware of the existence of #theforeman IRC and the -user mailing
> list?
> I think we push this as hard as we can - if this is a low score we can't
> take any further action anyway
>
> How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Frequency]
> How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Support dur.]
> How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Fixing bugs]
> How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Stability]
> Quite repetitive after the major release question, and broadly produces
> the
> same data, so removed to shorten the survey.
>
> ### Contributor survey
>
> Generally: Do we still think this is a good idea? We get a lot of metrics
> from Redmine/GitHub etc, but I'm keen to learn where the pain points are
> for new contributors.
>
> Do you contribute to Foreman in some way?
> [yes, no, would like to]
>
> What areas of Foreman do you currently contribute to / want to get started
> on?
> [bugs, testing, translations, installer, core, proxy, plugins, none, other]
>
> Rate the following, for ease of use
> [Finding docs, dev env, bugs, PRs, getting help, getting feedback]
>
> Are you aware of the following development resources?
> [handbook, wiki, deep dives, demos]
>
> What's your biggest problem with contributing that we need to solve? [text]
>
> Any other contributing comments? [text]
>
> ###
>
> Thats the questions. Below are the current list of plugins. I think this
> is a bit loo long - we could either
>
> * take the top 20 or so from the download metrics, or
> * Do plugins / CRs on their own survey page
>
> CR list (wiki/List_of_Plugins + core)
> Amazon EC2
> Azure
> DigitalOcean
> Docker
> Google Compute Engine
> Libvirt
> OpenNebula (foreman_one)
> OpenStack
> oVirt
> Rackspace
> VMware
> Xen
>
> Plugin list: (from wiki/List_of_Plugins)
> foreman_abrt
> foreman_ansible
> foreman_audited_notifications
> foreman_bootdisk
> foreman_chef
> foreman_cockpit
> foreman_column_view
> foreman_custom_banner
> foreman_custom_parameters
> foreman_default_hostgroup
> foreman_dhcp_browser
> foreman_discovery
> foreman_epel_release
> foreman_expire_hosts
> foreman_graphite
> foreman_hooks
> foreman_host_extra_validator
> foreman_host_overview
> foreman_host_rundeck
> foreman_memcache
> foreman_monitoring
> foreman_noenv
> foreman_omaha
> foreman_openscap
> foreman_ovirt
> foreman_param_lookup
> foreman_pipeline
> foreman_plugin_computeresource_
> foreman_plugin_exec_cmd
> foreman_radiator
> foreman_remote_execution
> foreman_reserve
> foreman_resources
> foreman_salt
> foreman_sentry
> foreman_setup
> foreman_slack
> foreman_templates
> hostgroup_extra_validator_foreman
> hubot_notify
> katello
> puppetdb_foreman
>
> Smart Proxy Plugin List (that aren't already covered by a core plugin):
> smart_proxy_dhcp_infoblox
> smart_proxy_dns_infoblox
> smart_proxy_dns_powerdns
> smart_proxy_dns_route53
> smart_proxy_pulp (covered by katello?)
> smart_proxy_vault
>
> Comments welcome!

can we take back the input from Shlomi's tread about what people are
annoyed by, break it into categories, and have a question like:

over the next few releases, I would be happier if you first work on:
[x] provisioning
[x] UI/UX
[x] no new features, just stabilization
[x] fix the damn operating system/templates issue
…

obviously, the categories needs to make sense.

thanks,
Ohad

··· On Wed, Dec 21, 2016 at 10:04 PM, Greg Sutcliffe wrote:

–
Greg
IRC / Twitter: gwmngilfen
Diaspora: gwmngilfen@joindiaspora.com

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

#6

As a content person, I'm interested in what Katello users are doing in that
area. Some ideas that could be valuable to know:

  • Do you manage content with Katello?

  • If not, what do you use?

  • Select all of the ways you want to manage content with Foreman:
    ** mirror content from 3rd parties
    ** lifecycle management for 3rd party content
    ** host content my organization creates
    ** lifecycle management for content my organization creates

  • Select all of the repository types you manage with Katello:
    ** RPM (Red Hat, Fedora, CentOS, and similar)
    ** SUSE
    ** Puppet
    ** Docker
    ** ISO

  • Which of the following content types would you manage with Katello if it
    supported them?
    ** Python
    ** Ruby Gem
    ** NPM
    ** Debian
    ** Java (there's probably a better word to use here)

I'm sure those questions could be improved and clarified, but those are
some general areas where insight could help us prioritize. Feel free to
adjust, mangle, exapand, or discard as you see fit.

#7

+1 for raffle and contributor survey. (I don't have a t-shirt… Yet…)

Plugins should definitely be on their own page, as well as having CRs on
their own page.

In general, it's been my experience that people who are going to complete
surveys will complete them regardless of length. By that I mean most people
won't be swayed into doing a survey because it's short unless they already
planned on completing it going in. I know everyone is busy, but 15 minutes
for something most users probably use multiple times a day isn't really
that much to ask.

> Hi all,
>
> Last year I rushed the community survey, and forgot to get feedback on the
> questions it contained - I'm not making that mistake again :slight_smile:
>
> Below is the draft question set - fair warning, its a big email :P. My aim
> is to either make it shorter, or at least break it up into a couple of
> logical pages. I've tried to indicate where the departures from last year
> are (especially the dropped/potentially-dropped ones). Feedback on what to
> change or things to add is very welcome - if you have a burning question
to
> ask, lets hear it!
>
> Additionally, I may be able to fund some small incentive strategy to get a
> larger sample size. I can see two ways to do that:
>
> * Some small reward for the first X people to fill out the survey (eg $5
> gift card or something)
> * All response go into a raffle for some nice (more expensive) things

+1 for the raffle. It motivates you to respond even on the last day of
the survey. How about raffle for the foreman t-shirts? Or is it too
common and everybody already has one from conferences?

>
> Clearly this would require the user to identify themselves (an email is
> probably all I'd need) - that would be optional, of course. Do people
> support this? What would be your preferred option?
>
> The plan is to gather feedback on this in the New Year, publish the survey
> by mid January with a big push for early responders (hence the swag
> incentive above) and then re-push in person at the conferences. We then
> close it after about a month (mid Feb) and do the analysis.
>
> Anyway, the questions:
>
> ### To keep from last year - self-explanatory
>
> How long have you been using Foreman?
> [3m, 6m, 1yr, 2y, 3+yr]
>
> How many people use Foreman in your organization
> [1, 5, 10, 50+]
>
> What Foreman version are you using?
> [nightly, stable, old-stable, older]
>
> How many nodes do you manage with Foreman?
> [0, 10, 50, 200, 500, 1000, 10000, 20000+]
>
> What operating system do most of your Foreman servers use?
> [RHEL/CentOS/Fedora, Debian, Ubuntu, SUSE, Other]
> (do we need to split this more, eg Fedora vs RHEL?)
>
> Which Compute Resources do you use with Foreman?
> Which Foreman plugins do you use?
> these two need better structuring, the lists are long & stats were
skewed
> last year due to missing options. See end of post for the actual lists.
>
> How would you rate our user support?
> [mailing list, IRC, website, docs], 1-5 score
>
> How well do major releases (e.g. 1.9, 1.10) meet your needs?
> [frequency, features, bugs, stability], 1-5 score
>
> Any other feedback about our support and documentation? [text]
>
> Overall, how well does Foreman meets your requirements? [text]
>
> What's the most important thing you'd like to see done next in Foreman?
> [text]
>
> Do you have any additional comments or special requests? [text]
>
> ### New additions
>
> Would you accept Foreman gathering anonymous usage stats to help improve
the
> project? This would have an opt-out and a way to see the data before
sending
> (see https://github.com/theforeman/rfcs/pull/31 for a proposed design -
> comments
> welcome!)
> I really want to hear user feedback on this to avoid backlash later. Not
> sure if it should be a simple yes/no or text-field for comments.
>
> What geographical area are you in?
> [Europe, N America, S America, Africa, Asia, Oceania]
> We don't really know where our userbase is, although we have a hunch.
I've
> tried to keep it coarse, and it'll obviously be optional.
>
> ### Dropped from last year
>
> What do you use Foreman for at your organization?
> I think our problem domain is fairly well specified, and knowledge of
> specific plugins/CRs is more specific & valuable. Anything really ugent
> will
> end up in the "most important thing" or "additional comments" boxes
>
> What are your top 3 from the following potential future features?
> Basically the same thing as "what's most important to add", just ask it
> once
>
> Why did you choose it instead of alternatives?
> I think I'd rather focus on Foreman than go off on a tangent. People who
> are switching away won't fill in the survey anyway.
>
> Do you Use Locations / Organization features?
> Could you tell us more about your usage of Locations/Organizations?
> Any other feedback on your Locations/Organizations usage that you'd share?
> I think we've gathered all the feedback we can on this last year.
>
> Would you be interested participating in a foreman community event?
> Would you be willing to help organise Foreman events in your area?
> We saw good responses to the birthday events, but these questions don't
> work
> on an anonymous survey. Potential to add back in if we ask for email
> addrs
>
> ### Optional from last year - comments welcome
>
> Do you use the Foreman API or Hammer?
> I guess people are more aware of this now? Could add back in, or
rephrase.
> What things do these teams want to learn?
>
> Are you aware of the existence of #theforeman IRC and the -user mailing
> list?
> I think we push this as hard as we can - if this is a low score we can't
> take any further action anyway
>
> How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Frequency]
> How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Support
dur.]
> How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Fixing bugs]
> How well do minor releases (e.g. 1.9.1, .2) meet your needs? [Stability]
> Quite repetitive after the major release question, and broadly produces
> the
> same data, so removed to shorten the survey.
>
> ### Contributor survey
>
> Generally: Do we still think this is a good idea? We get a lot of metrics
> from Redmine/GitHub etc, but I'm keen to learn where the pain points are
for
> new contributors.
>
> Do you contribute to Foreman in some way?
> [yes, no, would like to]
>
> What areas of Foreman do you currently contribute to / want to get started
> on?
> [bugs, testing, translations, installer, core, proxy, plugins, none,
other]
>
> Rate the following, for ease of use
> [Finding docs, dev env, bugs, PRs, getting help, getting feedback]
>
> Are you aware of the following development resources?
> [handbook, wiki, deep dives, demos]
>
> What's your biggest problem with contributing that we need to solve?
[text]
>
> Any other contributing comments? [text]
>
> ###
>
> Thats the questions. Below are the current list of plugins. I think this
is

··· On Dec 22, 2016 4:37 AM, "Tomas Strachota" wrote: On Wed, Dec 21, 2016 at 9:04 PM, Greg Sutcliffe wrote: > a bit loo long - we could either > > * take the top 20 or so from the download metrics, or > * Do plugins / CRs on their own survey page > > CR list (wiki/List_of_Plugins + core) > Amazon EC2 > Azure > DigitalOcean > Docker > Google Compute Engine > Libvirt > OpenNebula (foreman_one) > OpenStack > oVirt > Rackspace > VMware > Xen > > Plugin list: (from wiki/List_of_Plugins) > foreman_abrt > foreman_ansible > foreman_audited_notifications > foreman_bootdisk > foreman_chef > foreman_cockpit > foreman_column_view > foreman_custom_banner > foreman_custom_parameters > foreman_default_hostgroup > foreman_dhcp_browser > foreman_discovery > foreman_epel_release > foreman_expire_hosts > foreman_graphite > foreman_hooks > foreman_host_extra_validator > foreman_host_overview > foreman_host_rundeck > foreman_memcache > foreman_monitoring > foreman_noenv > foreman_omaha > foreman_openscap > foreman_ovirt > foreman_param_lookup > foreman_pipeline > foreman_plugin_computeresource_ > foreman_plugin_exec_cmd > foreman_radiator > foreman_remote_execution > foreman_reserve > foreman_resources > foreman_salt > foreman_sentry > foreman_setup > foreman_slack > foreman_templates > hostgroup_extra_validator_foreman > hubot_notify > katello > puppetdb_foreman > > Smart Proxy Plugin List (that aren't already covered by a core plugin): > smart_proxy_dhcp_infoblox > smart_proxy_dns_infoblox > smart_proxy_dns_powerdns > smart_proxy_dns_route53 > smart_proxy_pulp (covered by katello?) > smart_proxy_vault > > Comments welcome! > -- > Greg > IRC / Twitter: gwmngilfen > Diaspora: gwmngilfen@joindiaspora.com > > -- > You received this message because you are subscribed to the Google Groups > "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

#8

Thanks all, and sorry for the delay. Some inline comments and the final
draft attached separately :stuck_out_tongue:

Ori Rabin wrote:
> Maybe the question: How would you rate our user support? can have links
> instead of bringing back the do you know our IRC question?

I like that, added.

Tomas Strachota wrote:
> +1 for the raffle. It motivates you to respond even on the last day of
the survey.

Good point.

> How about raffle for the foreman t-shirts? Or is it too
common and everybody already has one from conferences?

They (and stickers) are what we give out for free, and seems somewhat
stingy :slight_smile:

I have a budget for a couple of decent items, 2 or 3 depending on price.
The question is what? It needs to be something available in multiple
countries (because that is likely cheaper than shipping from elsewhere),
a nice thing to win, and relevant to us. My current thinking is
something like a RaspberyyPi3 / oDroid / etc for running your own ARM
Foreman server on :stuck_out_tongue: - thoughts?

Neil Hanlon wrote:
> +1 for raffle and contributor survey. (I don't have a t-shirt…
> Yet…)

Let me fix that for you - ping me an address and size :slight_smile:

> In general, it's been my experience that people who are going
> to complete surveys will complete them regardless of length. By
> that I mean most people won't be swayed into doing a survey because
> it's short unless they already planned on completing it going in.
> I know everyone is busy, but 15 minutes for something most users
> probably
> use multiple times a day isn't really that much to ask.

That's a great point. I've converted the draft to a multi-page format,
and tidied up the group to something which I hope is logical. It's also
enabled me to re-add many of the things I dropped due to trying to be
brief.

Ohad Levy wrote:
> can we take back the input from Shlomi's tread about what people are
> annoyed by, break it into categories, and have a question

Originally I wanted to leave this as an open text field ("what needs
fixing?") but I think we can combine it. I've added a few suggestions
from the thread and an Other box too.

Eric D Helms wrote:
> Some question in line below. Could we add some questions around smart
> proxies? I don't know that I have any idea about:

Great point. Page added for Proxies, and since it's short I put the
Hammer and API questions there too.

> The plugin question would cover which configuration management project
> users use, but it wouldn't indicate Puppet usage and Puppet 3 vs
> Puppet 4 usage in our ecosystem. A question around those two might be
> useful.

I added just one, but if there's more sing out.
> +! to splitting out the OS distros into versions (e.g. RHEL6, RHEL7,
> Fedora 24, CentOS 6, Debian Jessie) as that gives us a better idea of
> where to focus and may help some plugins decide on what they want to
> focus their support on.

Done.

> Would it be worth asking an open ended question about what users pain
> points are? I suppose the foreman-users post did this but still might
> be worth it in the official survey.

Added as part of the final "What else would you like add?" question to
highlight pain points are definitely worth mentioning.

> Something to consider to help Katello developers would be a question
> around how many users do not currently manage content but plan to in
> the future. You could perhaps ask this more broadly about plugins that
> users plan to add to their environments.

That's a good question. The plugin page is already huge, so I wonder if
it makes more sense in the "wrap-up" section? For now, I've added an
open question to the main first page.

>> Do you Use Locations / Organization features?
>
> Why drop this question? Given how hotly some developers discuss this,
> I think this is valuable data.

I don't think there's anything new here. We gathered good feedback which
(to me) confirmed that moving to a tag-based system wouldn't break many
(if any) setups. Simply asking the same broad question again won't
extend that, I don't think - but if you've got something more specific
you'd like to ask, I can add it.

I'm mocking this up in Google Forms at the moment, but the markdown is
attached. I'll publish next week if there are no major concerns :slight_smile:

Gre

survey-draft.md (5.68 KB)

··· -- IRC / Twitter: gwmngilfen Diaspora: gwmngilfen@joindiaspora.com
#9

> Also "Smart proxy, Hammer & API" page - I think maybe adding "Katello"
> in parens next to smart_proxy_pulp might help people know what it's
> for. I doubt most Katello users are aware of the plugin name on the
> smart proxy side.

Good point, done.

> > The 1 to 5 selectors don't seem to be working correctly, it's not a
> > preference order right?

Yes, stupid mistake. Thanks!

> As a content person, I'm interested in what Katello users are doing in that
> area. Some ideas that could be valuable to know:

I did think about Katello input, but cut it in the first round due to survey
length. Now that we're multi-page, I think it's fine to include. Thanks for
reminding me :slight_smile:

I've restructured it so that it's more generally applicable to people who
manage content in other ways (for example, I manage Puppet with puppet-
librarian and DEBs with Aptly). My aim is to answer your questions about the
content we do support, but also to try and gain some more understanding about
areas we could look to including in future work.

This really needs to go out today so the initial rush can ebb a little before
DevConf, where we'll push it again (and again a week later). I've filled it
out once myself to test the questions this time… (oops :P) and unless
anything major comes up, I'll wipe the replies and publish the survey to the
users-list later on tonight.

Cheers for the input guys!
Greg

··· On Friday, 20 January 2017 15:51:28 GMT Stephen Benjamin wrote: > On Fri, Jan 20, 2017 at 3:49 PM, Stephen Benjamin wrote: On Sunday, 22 January 2017 19:04:58 GMT Michael Hrivnak wrote:
#10

Ok, the Google Form is done - I've added one or two more good suggestions I
got privately (thanks Ewoud and Dmitri :P). The link is:

I consider this to be a "beta" - have a play with it, but expect the responses
to be wiped before we announce it as "live". If no-one has any major concerns,
then I'll announce it early next week.

Greg

#11

On page 4, I can only select one Compute Resource when question asks
"select all that apply". Same for selecting which features I use on my
Smart Proxies and which Smart Proxy plugins I use on page 5.

Should't these three inputs be checkboxes instead of radio buttons?

··· On Friday, 20 January 2017 13:22:25 UTC, Greg Sutcliffe wrote: > > Ok, the Google Form is done - I've added one or two more good suggestions > I > got privately (thanks Ewoud and Dmitri :P). The link is: > > https://goo.gl/forms/i5Gu2o31vbuQLToh1 > > I consider this to be a "beta" - have a play with it, but expect the > responses > to be wiped before we announce it as "live". If no-one has any major > concerns, > then I'll announce it early next week. > > Greg >
#12

You are correct - the dangers of cut'n'paste. Should be fixed now, thanks!

Greg

··· On Friday, 20 January 2017 06:45:16 GMT Duncan Innes wrote: > On page 4, I can only select one Compute Resource when question asks > "select all that apply". Same for selecting which features I use on my > Smart Proxies and which Smart Proxy plugins I use on page 5. > > Should't these three inputs be checkboxes instead of radio buttons?
#13

For the question 'How would you rate our user support system' I can't
choose the same number twice. So I can't give the manual and IRC the
same rating.

Same for the next question.

··· On Fri, Jan 20, 2017 at 01:22:19PM +0000, Greg Sutcliffe wrote: > Ok, the Google Form is done - I've added one or two more good suggestions I > got privately (thanks Ewoud and Dmitri :P). The link is: > > https://goo.gl/forms/i5Gu2o31vbuQLToh1 > > I consider this to be a "beta" - have a play with it, but expect the responses > to be wiped before we announce it as "live". If no-one has any major concerns, > then I'll announce it early next week.
#14

The 1 to 5 selectors don't seem to be working correctly, it's not a
preference order right?

Screenshot from 2017-01-20 15-47-53.png822×502 12.2 KB

··· On Fri, Jan 20, 2017 at 11:56 AM, Greg Sutcliffe wrote: > On Friday, 20 January 2017 06:45:16 GMT Duncan Innes wrote: >> On page 4, I can only select one Compute Resource when question asks >> "select all that apply". Same for selecting which features I use on my >> Smart Proxies and which Smart Proxy plugins I use on page 5. >> >> Should't these three inputs be checkboxes instead of radio buttons? > > You are correct - the dangers of cut'n'paste. Should be fixed now, thanks! > > Greg > > -- > You received this message because you are subscribed to the Google Groups "foreman-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com. > For more options, visit https://groups.google.com/d/optout.
#15

Also "Smart proxy, Hammer & API" page - I think maybe adding "Katello"
in parens next to smart_proxy_pulp might help people know what it's
for. I doubt most Katello users are aware of the plugin name on the
smart proxy side.

··· On Fri, Jan 20, 2017 at 3:49 PM, Stephen Benjamin wrote: > The 1 to 5 selectors don't seem to be working correctly, it's not a > preference order right? > > On Fri, Jan 20, 2017 at 11:56 AM, Greg Sutcliffe > wrote: >> On Friday, 20 January 2017 06:45:16 GMT Duncan Innes wrote: >>> On page 4, I can only select one Compute Resource when question asks >>> "select all that apply". Same for selecting which features I use on my >>> Smart Proxies and which Smart Proxy plugins I use on page 5. >>> >>> Should't these three inputs be checkboxes instead of radio buttons? >> >> You are correct - the dangers of cut'n'paste. Should be fixed now, thanks! >> >> Greg >> >> -- >> You received this message because you are subscribed to the Google Groups "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com. >> For more options, visit https://groups.google.com/d/optout.