Open Stack

Ryan,

 

I would like to be able to get to the following

 

Framework

 

-          Defined mandate/scope for the user committee

-          Agreed structure and schedule for reporting to TC/MB

-          Initial set of additional members filling out the committee to
cover market segment and user geography representation

 

User Input

-          A simple user survey/poll to identify to profile the users/start
off the feedback and assemble it for the summit. Ideally, we'd be able to
get to something where we can see the production/test/development stages,
size of installations, components used, version run, pain points, etc. but
this may be ambitious. a CRM would allow some structure to avoid that we get
multiple responses per deployment

-          Have a panel session / discussion group at the summit presenting
the survey results and areas where we need input such as how to gather user
requirements and track deployments

 

Tim

 

From: Ryan Lane [mailto:rlane at wikimedia.org] 
Sent: 09 January 2013 00:24
To: user-committee at lists.openstack.org
Subject: [User-committee] Targets for OpenStack summit

 

The next summit is only a few months away. What should our targets for the
user committee be for that time period? Do we want to finalize the committee
at the summit, where we can get direct user feedback? Do we want to have it
up and running so that we can start pulling in user information and be able
to provide some feedback to the foundation and developers?

 

My vote is having it up and running and having some method of collecting
user information (sugarcrm? civicrm?) before the summit.

 

Thoughts?

 

- Ryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20130109/fd0b8261/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5215 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20130109/fd0b8261/attachment.bin>