<div dir="ltr"><div>Hello all,<br></div><div><br>What is the current situation with choosing web framework? Was there any<br>progress in the topic? I would like to avoid forgetting about it.<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2014-12-08 15:47 GMT+01:00 Ryan Petrello <span dir="ltr"><<a href="mailto:ryan.petrello@dreamhost.com" target="_blank">ryan.petrello@dreamhost.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Feel free to ask any questions you have in #pecanpy on IRC; I can answer a lot<br>
more quickly than researching docs, and if you have a special need, I can<br>
usually accommodate with changes to Pecan (I've done so with several OpenStack<br>
projects in the past).<br>
<div class="HOEnZb"><div class="h5">On 12/08/14 02:10 PM, Nikolay Markov wrote:<br>
> > Yes, and it's been 4 days since last message in this thread and no<br>
> > objections, so it seems<br>
> > that Pecan in now our framework-of-choice for Nailgun and future<br>
> > apps/projects.<br>
><br>
> We still need some research to do about technical issues and how easy<br>
> we can move to Pecan. Thanks to Ryan, we now have multiple links to<br>
> solutions and docs on discussed issues. I guess we'll dedicate some<br>
> engineer(s) responsible for doing such a research and then make all<br>
> our decisions on subject.<br>
><br>
> On Mon, Dec 8, 2014 at 11:07 AM, Sebastian Kalinowski<br>
> <<a href="mailto:skalinowski@mirantis.com">skalinowski@mirantis.com</a>> wrote:<br>
> > 2014-12-04 14:01 GMT+01:00 Igor Kalnitsky <<a href="mailto:ikalnitsky@mirantis.com">ikalnitsky@mirantis.com</a>>:<br>
> >><br>
> >> Ok, guys,<br>
> >><br>
> >> It became obvious that most of us either vote for Pecan or abstain from<br>
> >> voting.<br>
> ><br>
> ><br>
> > Yes, and it's been 4 days since last message in this thread and no<br>
> > objections, so it seems<br>
> > that Pecan in now our framework-of-choice for Nailgun and future<br>
> > apps/projects.<br>
> ><br>
> >><br>
> >><br>
> >> So I propose to stop fighting this battle (Flask vs Pecan) and start<br>
> >> thinking about moving to Pecan. You know, there are many questions<br>
> >> that need to be discussed (such as 'should we change API version' or<br>
> >> 'should be it done iteratively or as one patchset').<br>
> ><br>
> ><br>
> > IMHO small, iterative changes are rather obvious.<br>
> > For other questions maybe we need (draft of ) a blueprint and a separate<br>
> > mail thread?<br>
> ><br>
> >><br>
> >><br>
> >> - Igor<br>
> ><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > OpenStack-dev mailing list<br>
> > <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
> ><br>
><br>
><br>
><br>
> --<br>
> Best regards,<br>
> Nick Markov<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</div></div><span class="im HOEnZb">--<br>
Ryan Petrello<br>
Senior Developer, DreamHost<br>
<a href="mailto:ryan.petrello@dreamhost.com">ryan.petrello@dreamhost.com</a><br>
<br>
</span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div>