+1 .... Full support from my side on this proposal...
We would need a new section for the end user questions... we currently have questions about the person (such as what should be the priorities) and the deployments (how many nodes, hypervisor etc.) so we'd need a new block on how you are using OpenStack (such as Everett's questions) Typical case would be if you are consuming OpenStack public cloud resources where Everett's questions would be directly relevant. Tim From: Anne Gentle [mailto:a...@openstack.org] Sent: 17 January 2014 02:49 To: Everett Toews Cc: openstack@lists.openstack.org; user-commit...@lists.openstack.org Subject: Re: [User-committee] Formulate application developer oriented questions for the user survey I definitely have questions I'd like to ask that are specific to documentation. Give us a week or so to discuss on our list and then we'll propose some. Thanks! Anne On Thu, Jan 16, 2014 at 4:01 PM, Everett Toews <everett.to...@rackspace.com<mailto:everett.to...@rackspace.com>> wrote: Hi All, Inspired by this thread [1], I think it's time we try to formulate some application developer oriented questions for the user survey. Having this information will help us guide OpenStack developers, SDK developers, and other tool developers. Sean Dague already proposed the following 3 questions. I've added some more answers to the first to flesh it out. I replaced the work toolkit with code in questions 2 and 3. 1. What toolkits do you use to interface with the OpenStack API? * OpenStack command line (i.e. nova cli) * OpenStack libraries (Python) * jclouds (Java) * fog (Ruby) * pkgcloud (node.js) * openstack.net<http://openstack.net> (C#) * php-opencloud (PHP) * deltacloud (HTTP API) * other - please specify * none - wrote our own 2. If you wrote your own code for accessing the OpenStack API, what wire format are you using? * JSON * XML 3. If you wrote your own code for accessing the OpenStack API, what programming language did you write it in? * Python * Java * Ruby * node.js * C# * PHP * Perl * C/C++ * Other (please specify) All of the answers would be multi-select. e.g. checkboxes instead of radio buttons. Do we need more questions? Do we need change the wording of the questions as if it's from the perspective of the OpenStack operators asking their users what tools they are using to develop applications on an OpenStack cloud? e.g. What toolkits *are your users using* to interface with the OpenStack API? If *your users wrote their* own code for accessing the OpenStack API, what wire format are *they* using? Regards, Everett [1] http://lists.openstack.org/pipermail/openstack/2014-January/004638.html _______________________________________________ User-committee mailing list user-commit...@lists.openstack.org<mailto:user-commit...@lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
