Foreman community survey 2016

Hi all,

I've just finished preparing the community survey for this year:

There's a new section this year on how we meet the needs of our dev
community as well as our users, so please do respond and help us help you :slight_smile:

Feel free to use this link in any presentations you may be preparing for
next week, or for circulating to anyone you think needs to see it. I'll be
sending it on the the foreman-users list in just a moment.

Cheers

路路路 -- Greg IRC: gwmngilfen

Is it possible to fill that out without filling out the user bit? Most
of the questions are required but not really applicable to me (and
presumably some others).

Thanks for doing it, but any chance you can put it up for discussion
first? There are some points I'd have liked to include or perhaps change.

路路路 On 28/01/16 15:33, Greg Sutcliffe wrote: > Hi all, > > I've just finished preparing the community survey for this year: > > https://docs.google.com/forms/d/1nIsFBur1ABb3fawfz5xLEXJfPZ9MnZyCMtcWMil9e7I > > There's a new section this year on how we meet the needs of our dev > community as well as our users, so please do respond and help us help you :)


Dominic Cleal
dominic@cleal.org

>
> > Hi all,
> >
> > I've just finished preparing the community survey for this year:
> >
> >


> >
> > There's a new section this year on how we meet the needs of our dev
> > community as well as our users, so please do respond and help us help
you :slight_smile:
>
> Is it possible to fill that out without filling out the user bit? Most
> of the questions are required but not really applicable to me (and
> presumably some others).

Once I'm in Brussels with a decent WiFi connection, I can see what I can do
about changing it.

> Thanks for doing it, but any chance you can put it up for discussion
> first? There are some points I'd have liked to include or perhaps change.

I'll bear that in mind - it was an oversight rather than intentional
exclusion. If there's any additions you'd like that don't invalidate
existing answers, I'd be happy to consider them.

Greg

路路路 On 29 Jan 2016 8:14 am, "Dominic Cleal" wrote: > On 28/01/16 15:33, Greg Sutcliffe wrote:

I'm a bit disappointed that katello didn't rate well enough to get some questions on its usage. Remember, we closed down #katello and other resources to merge with foreman.

路路路 ----- Original Message ----- > On 29 Jan 2016 8:14 am, "Dominic Cleal" wrote: > > > > On 28/01/16 15:33, Greg Sutcliffe wrote: > > > Hi all, > > > > > > I've just finished preparing the community survey for this year: > > > > > > > https://docs.google.com/forms/d/1nIsFBur1ABb3fawfz5xLEXJfPZ9MnZyCMtcWMil9e7I > > > > > > There's a new section this year on how we meet the needs of our dev > > > community as well as our users, so please do respond and help us help > you :) > > > > Is it possible to fill that out without filling out the user bit? Most > > of the questions are required but not really applicable to me (and > > presumably some others). > > Once I'm in Brussels with a decent WiFi connection, I can see what I can do > about changing it. > > > Thanks for doing it, but any chance you can put it up for discussion > > first? There are some points I'd have liked to include or perhaps change. > > I'll bear that in mind - it was an oversight rather than intentional > exclusion. If there's any additions you'd like that don't invalidate > existing answers, I'd be happy to consider them. > > 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. >

questions on its usage. Remember, we closed down #katello and other
resources to merge with foreman.

That's not entirely true, but it does show my total failure at
communication this week. Let me explain鈥

The aim was to (a) circulate a first draft to Eric, Daniel, Ohad, etc for
question input and to spot glaring errors, (b) circulate more widely for
feedback, and then 漏 publish. The problem was that in all the rush, (b)
got totally missed, and as I've said, lesson learned for next year.
However, I did at least get some input from some people - it's not
completely unilateral.

I can make the same offer as I did to Dominic - what questions would you
have asked? If suitable, there's still time to include them (currently
we're at about 1/4 of last year's total reponses). If not, at least I learn
something for next time. That said, I'm concious there are other large
plugins that might feel left out, so perhaps we could look at
plugin-specific (and skippable) sections for next time? It's possible, but
I'd be concious of making the survey too long鈥 any one else have thoughts
on that?

Dominic, you should be able to skip the user survey now - hopefully Google
Forms can cope with the additional question. It's an interesting test
anyway - if yes, we can potentially add other things. If not, well, I have
a backup of the responses so far.

路路路 On 29 January 2016 at 12:42, Tom McKay wrote: > > I'm a bit disappointed that katello didn't rate well enough to get some

>
>>
>> > Hi all,
>> >
>> > I've just finished preparing the community survey for this year:
>> >
>> >
> https://docs.google.com/forms/d/1nIsFBur1ABb3fawfz5xLEXJfPZ9MnZyCMtcWMil9e7I
>> >
>> > There's a new section this year on how we meet the needs of our dev
>> > community as well as our users, so please do respond and help us
> help you :slight_smile:
>>
>> Is it possible to fill that out without filling out the user bit? Most
>> of the questions are required but not really applicable to me (and
>> presumably some others).
>
> Once I'm in Brussels with a decent WiFi connection, I can see what I can
> do about changing it.

Thanks, that looks better.

>> Thanks for doing it, but any chance you can put it up for discussion
>> first? There are some points I'd have liked to include or perhaps change.
>
> I'll bear that in mind - it was an oversight rather than intentional
> exclusion. If there's any additions you'd like that don't invalidate
> existing answers, I'd be happy to consider them.

No worries, cheers. A couple of ideas:

  1. Areas of Foreman to contribute to could include: documentation,
    packaging, and testing.

  2. OSes should include FreeBSD. (Actually, I think I misread this last
    year as OSes being managed by Foreman, not where Foreman was installed.)

  3. Compute resources is missing Rackspace.

  4. Compute resources includes one plugin (Docker), but not others - Xen,
    OpenNebula and CloudStack.

  5. The lower bound for "Overall, how well does Foreman meets your
    requirements?" starts at "It's OK", but should perhaps be "Badly" or
    something?

路路路 On 29/01/16 11:34, Greg Sutcliffe wrote: > On 29 Jan 2016 8:14 am, "Dominic Cleal" > wrote: >> On 28/01/16 15:33, Greg Sutcliffe wrote:


Dominic Cleal
dominic@cleal.org