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 <greg.sutcli...@gmail.com> 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 :) > > 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: gwmngil...@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+unsubscr...@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+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.