<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000">
<blockquote style="border: 0px none;"
cite="mid:5D7F9996EA547448BC6C54C8C5AAF4E5010298C114@CERNXCHG43.cern.ch"
type="cite">
<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;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">April 1, 2015 at
1:03 AM</span></font></div></div></div>
<div style="color: rgb(136, 136, 136); 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;
font-family:"Calibri",sans-serif;
color:#1F497D;}
span.EmailStyle18
{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: 11pt; font-family:
"Calibri",sans-serif; color: rgb(31, 73, 125);">Can you
explain what normalisation you would like to do ?</span></p></div></div>
</blockquote>
<span>Happy to :) Currently the survey questions are hard coded into
the PHP. What we'd like to do first off is make all of the questions and
answers dynamic, served from relational tables. This would allow any
Survey Admin to CRUD the questions without touching the code. This
should save lots of time in the long term as it would eliminate
development hours year over year.<br>
<br>
For the data output, everything is being stored in two tables. Questions
that have options for multiple answers are stored in an array, which is
generally bad practice. While it's not impossible to work around, it
makes it much more difficult to analyze the data. We'd like to set up
relational tables with questions and answers so we can reference
everything by ID. In addition, we would tag all questions/answers with a
survey ID.<br>
<br>
Which brings me to us losing tons of historical data because we're
writing over the same records every year. I propose that we snapshot the
survey for all companies by using the SurveyID. Combined with the
relational data for past surveys, we would be able to look historically
at all data that companies are submitting for each survey. This has
obvious advantages for spotting trends, improving responses to questions
that are historically getting incorrect/no answers, etc...<br>
<br>
If you'd like me to provide some specific examples or a blueprint for
our proposal, we're happy to do that. However, wanted to make sure we
had input from the community before we even started down that road.<br>
<br>
Thank you!<br>
Jimmy<br>
<br>
<br>
</span>
<blockquote style="border: 0px none;"
cite="mid:5D7F9996EA547448BC6C54C8C5AAF4E5010298C114@CERNXCHG43.cern.ch"
type="cite">
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<div class="WordSection1">
<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"><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 18:10<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> Re: [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"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div
style="margin-left:18.75pt;margin-top:22.5pt;margin-right:18.75pt;margin-bottom:7.5pt">
<div style="border:none;border-top:solid #EDEEF0 1.0pt;padding:4.0pt 0cm
0cm 0cm;display:table">
<div>
<p style="vertical-align:middle" class="MsoNormal"><span
style="color:#9FA2A5">March 31, 2015 at 8:12 AM</span><o:p></o:p></p>
</div>
</div>
</div>
<div style="margin-left:18.0pt;margin-right:18.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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.</span><o:p></o:p></p>
</div></blockquote>
<p class="MsoNormal">Right now we're maintaining the deployment ID and
re-populating questions from the past survey, where appropriate. That
way users have a head start on the survey and can update data where
appropriate.
<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div
style="margin-left:18.0pt;margin-right:18.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"> </span><o:p></o:p></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">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.</span><o:p></o:p></p>
</div></blockquote>
<p class="MsoNormal">This year was a bigger lift than previous years,
but you're right it's not a big shift from survey to survey. The driving
force IMO is to normalize the data.<br>
<br>
Thanks!<br>
Jimmy<br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt"><div
style="margin-left:18.0pt;margin-right:18.0pt">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"> </span><o:p></o:p></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 moz-do-not-send="true"
href="mailto:jimmy@tipit.net">mailto:jimmy@tipit.net</a>]
<br>
<b>Sent:</b> 31 March 2015 00:49<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:user-committee@lists.openstack.org">user-committee@lists.openstack.org</a><br>
<b>Subject:</b> [User-committee] OpenStack Surveys moving forward</span><o:p></o:p></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></blockquote>
</div>
</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="jimmy@tipit.net" photoname="Jimmy Mcarthur"
src="cid:part1.06090507.01050404@tipit.net"
name="compose-unknown-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:jimmy@tipit.net"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Jimmy Mcarthur</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
11:09 AM</span></font></div></div></div>
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<br>
<blockquote type="cite"
cite="mid:5D7F9996EA547448BC6C54C8C5AAF4E50102989651@CERNXCHG43.cern.ch"
style="border: 0px none;"><div class="__pbConvHr" style="margin:30px
25px 10px 25px;"><div style="display:table;width:100%;border-top:1px
solid
#EDEEF0;padding-top:5px"><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 class="__pbConvBody" __pbrmquotes="true" style="color: rgb(136,
136, 136); margin-left: 24px;
margin-right: 24px;">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<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: 11pt; font-family:
"Calibri",sans-serif; color: rgb(31, 73, 125);">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.</span></p></div></div></blockquote>
Right now we're maintaining the deployment ID and re-populating
questions from the past survey, where appropriate. That way users have a
head start on the survey and can update data where appropriate. <br>
<blockquote type="cite"
cite="mid:5D7F9996EA547448BC6C54C8C5AAF4E50102989651@CERNXCHG43.cern.ch"
style="border: 0px none;">
<div class="__pbConvBody" __pbrmquotes="true" style="color: rgb(136,
136, 136); margin-left: 24px;
margin-right: 24px;">
<div class="WordSection1">
<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"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size: 11pt; font-family:
"Calibri",sans-serif; color: rgb(31, 73, 125);">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.</span></p></div>
</div></blockquote>
This year was a bigger lift than previous years, but you're right it's
not a big shift from survey to survey. The driving force IMO is to
normalize the data.<br>
<br>
Thanks!<br>
Jimmy<br>
<blockquote type="cite"
cite="mid:5D7F9996EA547448BC6C54C8C5AAF4E50102989651@CERNXCHG43.cern.ch"
style="border: 0px none;">
<div class="__pbConvBody" __pbrmquotes="true"
style="color:#888888;margin-left:24px;margin-right:24px;">
<div class="WordSection1">
<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"><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 moz-do-not-send="true"
href="mailto:jimmy@tipit.net" class="moz-txt-link-freetext">mailto:jimmy@tipit.net</a>]
<br>
<b>Sent:</b> 31 March 2015 00:49<br>
<b>To:</b> <a moz-do-not-send="true"
href="mailto:user-committee@lists.openstack.org"
class="moz-txt-link-abbreviated">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 href="http://Tipit.net"
moz-do-not-send="true"><span style="color:black">Tipit.net</span></a>
<
<a href="mailto:jimmy@tipit.net" moz-do-not-send="true">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 class="MsoNormal" style="margin-bottom:12.0pt"> <o:p></o:p></p>
</div>
</div>
</div>
</div></blockquote>
</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:part2.04040405.02000701@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>
<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="jimmy@tipit.net" photoname="Jimmy Mcarthur"
src="cid:part1.06090507.01050404@tipit.net"
name="compose-unknown-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:jimmy@tipit.net"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Jimmy Mcarthur</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">March 30, 2015 at
5:49 PM</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">
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>
</div>
</blockquote>
</body></html>