Open Stack

> I'd agree though if we're reworking the database side to maintain
> history (which seems a very good idea to me), perhaps the incremental
> cost isn't so much now. That rather depends on how much work it would
> be to keep the current frontend while switching out the back &
> honestly I have no clue how that's all plumbed together.
No question. It's not a small project. The big lift is just building the 
survey builder itself. Fortunately, there is already a plugin for 
Silverstripe (https://github.com/silverstripe/silverstripe-userforms) 
for at least some of this. We might have to do a bit of customization.

IMO, the ability to track growth / changes to deployments over time 
would seem to be extremely valuable data. With only the changes we made 
this year, we can start doing some of that. However, if we fully 
normalized the data, it would be much, much easier to run analytics on 
the data.

That said, we could just see how the next rev of the survey goes and see 
if there are continued pain points.

Thanks,
Jimmy
>
> -Jon
>
>
> :Tim
> :
> :From: Jimmy Mcarthur [mailto:jimmy at tipit.net]
> :Sent: 31 March 2015 00:49
> :To: user-committee at lists.openstack.org
> :Subject: [User-committee] OpenStack Surveys moving forward
> :
> :Hello all -
> :
> :We've been working on the development side of the user survey for 
> OpenStack Foundation for the last two years. During that time, I've 
> noticed a few issues which we'd like to address with the help of the 
> stakeholders.
> :
> :* Because of some earlier limitations with Silverstripe, the data 
> isn't normalized. I'd like to propose a true relational data model. 
> This is a problem for many reasons: data analysis, ease of updates, 
> year over year changes, etc...
> :* Users are updating the same Deployment and Survey rows year over 
> year. Literally we're writing over historical data, which eliminates 
> our ability to track data trends for companies and deployments.
> :* Due to the current data model, updating the survey must be done by 
> someone familiar with Silverstripe. I would propose a survey builder, 
> built around the needs of the most current survey. This should allow 
> the User Committee to create/edit their own questions and answers, 
> including the style of the question (e.g. radio buttons, checkbox 
> list, ranking of answers, etc...)
> :
> :We would be happy to put together a blueprint of what we're thinking, 
> but I'd like to first get general feedback from you all. You're much 
> more familiar with both the data and what you want to do with it than 
> we could ever be, so we welcome any input you might have in improving 
> the process of both creating the surveys and managing the data.
> :
> :Thank you!
> :--
> :Jimmy McArthur / Tipit.net<http://Tipit.net> < 
> jimmy at tipit.net<mailto:jimmy at tipit.net>>
> :m: 512.965.4846
> :o: 512.481.1161
> :
>
> :_______________________________________________
> :User-committee mailing list
> :User-committee at lists.openstack.org
> :http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
>
>
> Tim Bell <mailto:Tim.Bell at cern.ch>
> March 31, 2015 at 8:12 AM
>
> If we create new rows for new data entry for an existing deployment, 
> can we keep the same deployment id ? It is useful to have a unique 
> identified for each deployment, especially if we eventually get to an 
> automated way of reporting the current deployment state.
>
> We're not adding a huge number of questions each year so if it is easy 
> to change the technology, that's OK but it would seem like a lot of 
> work only for the delegation rights on its own.
>
> Tim
>
> *From:*Jimmy Mcarthur [mailto:jimmy at tipit.net]
> *Sent:* 31 March 2015 00:49
> *To:* user-committee at lists.openstack.org
> *Subject:* [User-committee] OpenStack Surveys moving forward
>
> Hello all -
>
> We've been working on the development side of the user survey for 
> OpenStack Foundation for the last two years. During that time, I've 
> noticed a few issues which we'd like to address with the help of the 
> stakeholders.
>
> * Because of some earlier limitations with Silverstripe, the data 
> isn't normalized. I'd like to propose a true relational data model. 
> This is a problem for many reasons: data analysis, ease of updates, 
> year over year changes, etc...
> * Users are updating the same Deployment and Survey rows year over 
> year. Literally we're writing over historical data, which eliminates 
> our ability to track data trends for companies and deployments.
> * Due to the current data model, updating the survey must be done by 
> someone familiar with Silverstripe. I would propose a survey builder, 
> built around the needs of the most current survey. This should allow 
> the User Committee to create/edit their own questions and answers, 
> including the style of the question (e.g. radio buttons, checkbox 
> list, ranking of answers, etc...)
>
> We would be happy to put together a blueprint of what we're thinking, 
> but I'd like to first get general feedback from you all. You're much 
> more familiar with both the data and what you want to do with it than 
> we could ever be, so we welcome any input you might have in improving 
> the process of both creating the surveys and managing the data.
>
> Thank you!
>
> -- 
>
> Jimmy McArthur / Tipit.net <http://Tipit.net> < jimmy at tipit.net 
> <mailto:jimmy at tipit.net>>
> m: 512.965.4846
>
> o: 512.481.1161
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20150331/5b80e43f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1142 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20150331/5b80e43f/attachment-0001.jpg>