IMHO it's useful for prioritizing potential plug ins / toolkits for "cloud app" developers based on their preferred tools.
An example from the AWS world would be: http://aws.amazon.com/eclipse/ On Tue, Feb 4, 2014 at 1:37 PM, Sean Dague <s...@dague.net> wrote: > Out of curiosity, why is the development environment question an > interesting one? Is there some decision or action that an OpenStack > program or project would make based on that info? > > It is really easy to ask lots of questions, however, every additional > question causes a drop of in percentage responders. So every question > should have a clear reason for being asked other than general interest. > > And on a lighter note... how did vim make the list but not emacs? ;) > > -Sean > > On 02/05/2014 02:50 AM, Martin, JC wrote: > > For the development environment, more precisely, it may be PyCharm > instead of intelliJ. or to cover both : jetbrain IDEA. > > > > > > On Feb 3, 2014, at 2:42 PM, Everett Toews <everett.to...@rackspace.com> > wrote: > > > >> Some more potential questions. > >> > >> 1. What development environment do you use? > >> [ ] Eclipse > >> [ ] Intellij IDEA > >> [ ] Visual Studio > >> [ ] Sublime > >> [ ] vim > >> Other > >> > >> 2. What tools are you using to deploy/configure your application? > >> [ ] Ansible > >> [ ] Chef > >> [ ] Puppet > >> [ ] SaltStack > >> Other > >> > >> 3. What do you struggle with when developing and deploying applications > on OpenStack? > >> Free form answers. > >> > >> I'll try to aggregate all of the Q&A into one list this week. > >> > >> Thanks, > >> Everett > >> > >> > >> On Jan 21, 2014, at 11:55 AM, Everett Toews < > everett.to...@rackspace.com> wrote: > >> > >>> On Jan 21, 2014, at 10:29 AM, Dave Neary wrote: > >>> > >>>> On 01/21/2014 02:25 AM, Everett Toews wrote: > >>>>> There are a number of issues that stand out to me but before getting > >>>>> into them some quick definitions to be clear what I'm talking about. > >>>>> > >>>>> OpenStack developer = developer working on OpenStack itself > >>>>> OpenStack operator = operator deploying/maintaining an OpenStack > cloud > >>>>> application developer = developer working on application being > deployed > >>>>> on an OpenStack cloud > >>>>> application operator = operator deploying/maintaining an application > on > >>>>> an OpenStack cloud > >>>>> users = any of OpenStack operator, application developer, application > >>>>> operator > >>>> > >>>> It would be really useful, I think, to match these up with some of the > >>>> personas we have, so that we are all talking about the same thing > >>>> (there's a big difference between someone deploying a small private > >>>> cloud and someone operating a large public cloud, for example). > >>> > >>> I attended your session on personas at the HK Summit. I was the guy > ranting about SDKs from the back. ;) > >>> > >>> The personas are definitely useful and I think we could use them to > help inform the definitions of the above. Here's what I'm starting to > envision for the survey. > >>> > >>> On the About You page [1] we update the What best describes your > involvement with OpenStack? section as follows > >>> > >>> [ ] OpenStack cloud service provider - provides public or hosted > private cloud services for other organizations > >>> [ ] Ecosystem vendor - provides software or solutions that enable > others to build or run OpenStack clouds > >>> [ ] Private cloud operator - runs an OpenStack private cloud for their > own organization > >>> [ ] Application developer - has API or dashboard credentials and > deploys/maintains an application running on an OpenStack cloud > >>> [ ] Application operator - has API or dashboard credentials and > develops an application running on an OpenStack cloud > >>> > >>> If the survey taker checks Application developer or Application > operator then they are shown a survey page with the questions we are > formulating here instead of/in addition to the About Your OpenStack > Deployments page. > >>> > >>> I don't think we want to have the role definitions above too long but > anything can help. > >>> > >>> Can you link us to the personas work and how they might map to the > roles as above? > >>> > >>> [sidebar] > >>> It seems the About You page already makes the distinction between > someone deploying a small private cloud and someone operating a large > public cloud. However, I think the line between "...or hosted private cloud > services for other organizations" and "runs an OpenStack private cloud for > their own organization" is pretty thin. "hosted private cloud services for > other organizations" sounds like a small-scale public cloud to me. The real > distinction being whether you're doing it for your org or for others. The > questions on the About Your OpenStack Deployments page make the distinction > between scale. > >>> > >>> They could be reworded as > >>> > >>> [ ] OpenStack operator for a public cloud - provides public or hosted > private cloud services for other organizations > >>> [ ] OpenStack operator for a private cloud - runs an OpenStack private > cloud for their own organization > >>> > >>> This is apart from the app dev oriented discussion and hence the > sidebar. > >>> [/sidebar] > >>> > >>> Thanks, > >>> Everett > >>> > >>> [1] https://www.openstack.org/user-survey/OrgInfo > >>> _______________________________________________ > >>> User-committee mailing list > >>> user-commit...@lists.openstack.org > >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee > >> > >> > >> _______________________________________________ > >> User-committee mailing list > >> 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 > > > > > -- > Sean Dague > http://dague.net > > > _______________________________________________ > 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 > >
_______________________________________________ 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
