Open Stack

For this user survey cycle, we offered each PTL the opportunity to add one question under the “current issues” heading, which was intended to cover a hot issue or discussion going into the design summit. Ideally, the “current issues” questions do not need to become permanent fixtures in the survey for trending over time, and might be swapped out each survey cycle. 

I would support continuing to include a reasonable number of "current issues" questions within the main survey, and then offering an optional link or tick box to receive more in-depth questions around a particular project or issue. For example, we included a tick box for those who were interested in learning more and participating in RefStack this time around. Operators (and other types of users) who really care about those projects or issues are more likely to participate.


> On Sep 28, 2015, at 2:55 PM, Barrett, Carol L <carol.l.barrett at intel.com> wrote:
> 
> I like the idea of having optional sections to the User Survey. I think there is per-project info that PTLs are looking for that apply to different Operators, so allowing them to choose makes sense.
> 
> I would also be interested in including a couple of questions on future usage models/capabilities that they don't need today, but can see them becoming important over the horizon.
> 
> Carol
> -----Original Message-----
> From: Bruno Morel [mailto:bmorel at internap.com] 
> Sent: Monday, September 28, 2015 12:14 PM
> To: Jonathan Proulx; Tim Bell
> Cc: user-committee at lists.openstack.org
> Subject: Re: [User-committee] Per-project surveys
> 
> 
> I agree with Jonathan, in detail :
> 
> * making it a regular, scheduled thing : everybody in the community would know and expect every 6 month (or 3 month ?) to have the opportunity to give feedback, especially if it is pre / post cycle (ex. : January -> July -> January …)
> * Making it a community wide effort and consolidated in one ‘interaction’ / survey : having the ability to check/uncheck which project you want to give feedback about would be very useful and probably help focus each set of question to each project goals / needs
> * A main section would be, in my opinion, the right place to get all the general project-independant information we want to gather and any related question to the community efforts
> 
> Bruno
> 
> 
> 
> 
> 
> 
> 
> On 2015-09-28, 15:06, "Jonathan Proulx" <jon at csail.mit.edu> wrote:
> 
>> 
>> I'm thinking we try (next round) to wrap this into the user survey.
>> 
>> If we can organized the PTL surveys as optional and at the end 
>> hopefully we can retain the short general overview an relatively high 
>> response.
>> 
>> If the survey is arranged so PTLs can send deeper links to say 'update 
>> your Neuron usage survey' that go directly to that sub part we may not 
>> completely solve the survey over load but we can at least eliminate the 
>> duplication and bring all the data under the same privacy model.
>> 
>> I'm thinking an "optional tab" at the end of the survey, after we thank 
>> you for your responses, with a list of links to project specific 
>> sections.
>> 
>> -Jon
>> 
>> 
>> On Mon, Sep 28, 2015 at 05:03:49PM +0000, Tim Bell wrote:
>> : 
>> :
>> :There have been a couple of project surveys of OpenStack users in the 
>> past :week (Neutron and Ceilometer).
>> :
>> : 
>> :
>> :They tend to duplicate the standard questions (industry, size of 
>> deployment, :release levels, .) and also some of the questions we are 
>> currently asking in :the survey (nova network, metering feedback). The 
>> commitment to anonymity is :also not always clear.
>> :
>> : 
>> :
>> :The difficulty I see is that we reach survey limits, where people are 
>> not :sure what is official and whether the questions/audience may lead to a bias.
>> :
>> : 
>> :
>> :On the other hand, the PTLs often want more detailed information and 
>> the :user survey needs to be kept to a reasonable length (to avoid we 
>> lose :everything because people bailed out before finishing).
>> :
>> : 
>> :
>> :Any suggestions on how to proceed ? 
>> :
>> : 
>> :
>> :Tim
>> :
>> : 
>> :
>> 
>> 
>> 
>> :_______________________________________________
>> :User-committee mailing list
>> :User-committee at lists.openstack.org
>> :http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>> 
>> 
>> --
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee