Open Stack

That covered just about what I heard, sound wasn't great, as I expected from
previous experience.

 

I was encouraged by the points raised. I'm fine to skip elections for a
while with the interest of getting going. My worrying in nominating people
is if we 3 have enough knowledge of the significant users. The user group
representatives, we can identify or ask the user groups to define (via
whatever mechanism). Industry representation is more difficult, maybe we ask
the board/TC for proposals. Just asking on the community mailing list might
not yield the right profiles.

 

In particular, the encouragement to get on with the survey and work on
user/instance profiling is a priority, even if we don't have the full bylaw
details worked out by the summit.

 

Tim

 

 

From: Ryan Lane [mailto:rlane at wikimedia.org] 
Sent: 12 February 2013 21:17
To: user-committee at lists.openstack.org
Subject: [User-committee] Feedback from board on update

 

Here's some feedback we received:

 

* How are we going to include volunteers in the process? For instance, if a
volunteer from an organization wants to help bring in a large number of
end-users that are affiliated with them, how do they work with us?

* Should we be holding elections for additional committee members right now?
Feedback from this was that democracy, though preferred, is slow and we need
to get things set up and start getting feedback in quickly. Should we
appoint people now and handle elections later?

* We should be working closely with the infrastructure team for any
necessary tools.

 

Tim, is there anything I missed?

 

- Ryan

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20130212/99e8873f/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/20130212/99e8873f/attachment.bin>