Re: [foreman-dev] Draft community survey questions

[Ori Rabin]

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 :)
>
> 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, 1, 2+]
>
> 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
>
> 

[foreman-dev] Example of how to extend the hostgroups action menu

[Daniel Kuffner]

Hi All,

Do we have somewhere an example of how to extend the hostgroups action menu 
item via foreman plugin? Is that possible?

thank you,
Daniel

-- 
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.

Re: [foreman-dev] undefined method `sub!' for nil:NilClass on foreman 1.14

[Karen Harutyunyan]

Hi Dominic

It has to be related with cockpit plugin, so if im using 
--enable-foreman-plugin-cockpit  option then foreman has error as shown 
above . Later on I`ll contact with cockpit plugin authors but for now at 
least you know where is the exact problem.)

Regards
Karen

-- 
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.