I'd suggest openstack@lists.openstack.org. The user committee mailing list is fine if you want to discuss the details of survey confidentiality but it is not the route to reach the average busy users/operators. There is a clear need for a body that can translate user/operator needs and work with the developers to define the right blueprints/bugs. Not an easy job, especially to find those with some time but volunteers are welcome. Tim
-----Original Message----- From: Stefano Maffulli [mailto:stefano@openstack.org] Sent: 16 December 2013 20:25 To: John Dickinson; Tristan Goode Cc: community@lists.openstack.org Subject: Re: [openstack-community] Bringing focus to the Operators and Users at the next summit
[not sure the 'community' list is the most appropriate one where to have this conversation. I think it's more appropriate for the User Committee. Shall we move it there?]
On 12/15/2013 08:09 AM, John Dickinson wrote:
When considering any OpenStack project in production system, many factors must be considered. These are the sort of questions that come up every day as part of a sales process (even if that sales process is simply convincing other internal people to use something).
Indeed, your comment confirms that one way to close the loop is to establish a formal forum for product and project managers to talk and bring to the OpenStack developer their expertise. I think that product managers should be able to speak more fluently in terms that developers can understand and these conversations lead to improvements faster. Thoughts?
/stef
-- Ask and answer questions on https://ask.openstack.org
_______________________________________________ Community mailing list Community@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/community