<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<blockquote style="border: 0px none;"
cite="mid:20150331140045.GA780@csail.mit.edu" type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><div>I'd
agree though if we're reworking the database side to maintain<br>history
(which seems a very good idea to me), perhaps the incremental<br>cost
isn't so much now. That rather depends on how much work it would<br>be
to keep the current frontend while switching out the back &<br>honestly
I have no clue how that's all plumbed together.<br></div></div>
</blockquote>
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 (<a class="moz-txt-link-freetext" href="https://github.com/silverstripe/silverstripe-userforms">https://github.com/silverstripe/silverstripe-userforms</a>)
for at least some of this. We might have to do a bit of customization. <br>
<br>
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.<br>
<br>
That said, we could just see how the next rev of the survey goes and see
if there are continued pain points. <br>
<br>
Thanks,<br>
Jimmy<br>
<blockquote style="border: 0px none;"
cite="mid:20150331140045.GA780@csail.mit.edu" type="cite">
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<div><br>-Jon<br><br><br>:Tim<br>:<br>:From: Jimmy Mcarthur
[<a class="moz-txt-link-freetext" href="mailto:jimmy@tipit.net">mailto:jimmy@tipit.net</a>]<br>:Sent: 31 March 2015 00:49<br>:To:
<a class="moz-txt-link-abbreviated" href="mailto:user-committee@lists.openstack.org">user-committee@lists.openstack.org</a><br>:Subject: [User-committee]
OpenStack Surveys moving forward<br>:<br>:Hello all -<br>:<br>: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.<br>:<br>:*
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...<br>:* 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.<br>:* 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...)<br>:<br>: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.<br>:<br>:Thank you!<br>:--<br>:Jimmy
McArthur / Tipit.net<a class="moz-txt-link-rfc2396E" href="http://Tipit.net"><http://Tipit.net></a> <
<a class="moz-txt-link-abbreviated" href="mailto:jimmy@tipit.net">jimmy@tipit.net</a><a class="moz-txt-link-rfc2396E" href="mailto:jimmy@tipit.net"><mailto:jimmy@tipit.net></a>><br>:m: 512.965.4846<br>:o:
512.481.1161<br>:<br><br>:_______________________________________________<br>:User-committee
mailing list<br>:User-committee@lists.openstack.org<br>:<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><br><br><br></div>
</div>
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="Tim.Bell@cern.ch" photoname="Tim Bell"
src="cid:part1.05030708.07070104@tipit.net" name="postbox-contact.jpg"
height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:Tim.Bell@cern.ch"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Tim Bell</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">March 31, 2015 at
8:12 AM</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<meta content="Microsoft Word 15 (filtered medium)" name="Generator">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">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.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Tim<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm
4.0pt">
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm
0cm 0cm">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"
lang="EN-US">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"
lang="EN-US"> Jimmy Mcarthur [<a class="moz-txt-link-freetext" href="mailto:jimmy@tipit.net">mailto:jimmy@tipit.net</a>]
<br>
<b>Sent:</b> 31 March 2015 00:49<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:user-committee@lists.openstack.org">user-committee@lists.openstack.org</a><br>
<b>Subject:</b> [User-committee] OpenStack Surveys moving forward<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hello all -<br>
<br>
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.<br>
<br>
* 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...<br>
* 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.<br>
* 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...)<br>
<br>
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.<br>
<br>
Thank you!<o:p></o:p></p>
<div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div style="margin-right:18.0pt;color:rgb(136,
136, 136)">
<p class="MsoNormal">Jimmy McArthur / <a moz-do-not-send="true"
href="http://Tipit.net"><span style="color:black">Tipit.net</span></a>
<
<a moz-do-not-send="true" href="mailto:jimmy@tipit.net">jimmy@tipit.net</a>><br>
m: 512.965.4846 <o:p></o:p></p>
<div>
<p class="MsoNormal">o: 512.481.1161<o:p></o:p></p>
</div>
</div>
<p style="margin-bottom:12.0pt" class="MsoNormal"> <o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</body></html>