I agree that everyone's thoughts should be in it. I don't see why a representative vote does not allow for that. Sam put a text box on each use case to capture extra thoughts.
I would hope that no organization would be so confused as to have widely varying viewpoints on *what their customers want*, since that is the supposed purpose of all of this, right? We're supposed to be deciding which use-cases matter *to our customers*, so there should be no real variance for what I would vote versus what my teammates would vote, since we have the same customersÅ Also, if we are using this as a type of voting mechanism then interests of large/vocal organizations drown out smaller organizations. If this is being used as a voting mechanism then how do you suggest we weight votes for smaller companies so that we do not alienate them from further voting/discussions? Cheers, --Jorge On 5/6/14 1:52 PM, "Jay Pipes" <jaypi...@gmail.com> wrote: >On 05/06/2014 02:42 PM, Jorge Miramontes wrote: >> Sam, >> >> I'm assuming you want one person from each company to answer correct? >> I'm pretty sure people in each organization will vote the sameÅ at least >> I'd hope! > >I'd hope not! :) > >Even within the same organization or company, we all have different >ideas on use cases, the appropriateness of certain things "in the >cloud", and the role of a load balancer service in the general mix of >things. > >I certainly would hope that lots of Mirantis engineers other than myself >fill out the use case survey and offer their own insights. > >Best, >-jay > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev