> Yes, and it's been 4 days since last message in this thread and no > objections, so it seems > that Pecan in now our framework-of-choice for Nailgun and future > apps/projects.
We still need some research to do about technical issues and how easy we can move to Pecan. Thanks to Ryan, we now have multiple links to solutions and docs on discussed issues. I guess we'll dedicate some engineer(s) responsible for doing such a research and then make all our decisions on subject. On Mon, Dec 8, 2014 at 11:07 AM, Sebastian Kalinowski <skalinow...@mirantis.com> wrote: > 2014-12-04 14:01 GMT+01:00 Igor Kalnitsky <ikalnit...@mirantis.com>: >> >> Ok, guys, >> >> It became obvious that most of us either vote for Pecan or abstain from >> voting. > > > Yes, and it's been 4 days since last message in this thread and no > objections, so it seems > that Pecan in now our framework-of-choice for Nailgun and future > apps/projects. > >> >> >> So I propose to stop fighting this battle (Flask vs Pecan) and start >> thinking about moving to Pecan. You know, there are many questions >> that need to be discussed (such as 'should we change API version' or >> 'should be it done iteratively or as one patchset'). > > > IMHO small, iterative changes are rather obvious. > For other questions maybe we need (draft of ) a blueprint and a separate > mail thread? > >> >> >> - Igor > > > > _______________________________________________ > OpenStack-dev mailing list > OpenStackemail@example.com > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Best regards, Nick Markov _______________________________________________ OpenStack-dev mailing list OpenStackfirstname.lastname@example.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev