Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 17/11/14 14:43, Yves-Gwenaël Bourhis wrote: Le 17/11/2014 14:19, Matthias Runge a écrit : There is already horizon on pypi[1] IMHO this will lead only to more confusion. Matthias [1] https://pypi.python.org/pypi/horizon/2012.2 Well the current horizon on Pypi is The OpenStack Dashboard + horizon(_lib) included If the future horizon on pypi is openstack_dashboard alone, it would still pull horizon_lib as a dependency, so it would not brake the existing. That would break expectations. When installing a software package named python-foo, I would expect a python package named foo in there, not a package named bar. Dependencies between packages are best defined in distribution packages. They solve dependencies since ages. For Fedora, there is a policy for package naming. I'd assume the same to be true for Debian. Matthias ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 30/10/14 13:13, Matthias Runge wrote: Hi, tl;dr: how to progreed in separating horizon and openstack_dashboard Options so far: horizon_lib/openstack_horizon horizon_lib/horizon_dashboard horizon_lib/horizon horizon/openstack_dashboard did I miss something? If not, I'll create a poll. Matthias ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
Le 11/11/2014 09:30, Jiri Tomasek a écrit : From what was discussed on contributors meetup, keeping the names 'horizon' for the lib (framework) and 'openstack_dashboard' for dashboard seemed most convenient. And I happen to aggree with that. +1 We also discussed the fact that we could keep the names to the modules, but rename only the packages. pip install horizon_lib - installs the horizon module pip install horizon - installs openstack_dashboard. This would allow using the new names for the packages without braking the existing code depending on the libraries which import them. -- Yves-Gwenaël Bourhis ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 17/11/14 13:28, Yves-Gwenaël Bourhis wrote: Le 11/11/2014 09:30, Jiri Tomasek a écrit : From what was discussed on contributors meetup, keeping the names 'horizon' for the lib (framework) and 'openstack_dashboard' for dashboard seemed most convenient. And I happen to aggree with that. +1 We also discussed the fact that we could keep the names to the modules, but rename only the packages. pip install horizon_lib - installs the horizon module pip install horizon - installs openstack_dashboard. This would allow using the new names for the packages without braking the existing code depending on the libraries which import them. There is already horizon on pypi[1] IMHO this will lead only to more confusion. Matthias [1] https://pypi.python.org/pypi/horizon/2012.2 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
Le 17/11/2014 14:19, Matthias Runge a écrit : There is already horizon on pypi[1] IMHO this will lead only to more confusion. Matthias [1] https://pypi.python.org/pypi/horizon/2012.2 Well the current horizon on Pypi is The OpenStack Dashboard + horizon(_lib) included If the future horizon on pypi is openstack_dashboard alone, it would still pull horizon_lib as a dependency, so it would not brake the existing. So indeed the horizon package itself in Pypi would not have horizon(_lib) in it anymore, but he pip install horizon would pull everything due to the dependency horizon will have with horizon_lib. I find this the least confusing issue and the horizon package on Pypi would still be seen as The OpenStack Dashboard like it is now. We would only add an horizon_lib package on Pypi. Therefore existing third-party requirements.txt would not brake because they would pull horizon_lib with horizon. and they would still import the proper module. Every backwards compatibility (requirements and module) is therefore preserved. -- Yves-Gwenaël Bourhis ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
+1 for Yves. On Mon, Nov 17, 2014 at 10:43 PM, Yves-Gwenaël Bourhis yves-gwenael.bour...@cloudwatt.com wrote: Le 17/11/2014 14:19, Matthias Runge a écrit : There is already horizon on pypi[1] IMHO this will lead only to more confusion. Matthias [1] https://pypi.python.org/pypi/horizon/2012.2 Well the current horizon on Pypi is The OpenStack Dashboard + horizon(_lib) included If the future horizon on pypi is openstack_dashboard alone, it would still pull horizon_lib as a dependency, so it would not brake the existing. So indeed the horizon package itself in Pypi would not have horizon(_lib) in it anymore, but he pip install horizon would pull everything due to the dependency horizon will have with horizon_lib. I find this the least confusing issue and the horizon package on Pypi would still be seen as The OpenStack Dashboard like it is now. We would only add an horizon_lib package on Pypi. Therefore existing third-party requirements.txt would not brake because they would pull horizon_lib with horizon. and they would still import the proper module. Every backwards compatibility (requirements and module) is therefore preserved. -- Yves-Gwenaël Bourhis ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Akihiro Motoki amot...@gmail.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
Le 17/11/2014 14:43, Yves-Gwenaël Bourhis a écrit : Well the current horizon on Pypi is The OpenStack Dashboard + horizon(_lib) included If the future horizon on pypi is openstack_dashboard alone, it would still pull horizon_lib as a dependency, so it would not brake the existing. So indeed the horizon package itself in Pypi would not have horizon(_lib) in it anymore, but he pip install horizon would pull everything due to the dependency horizon will have with horizon_lib. I find this the least confusing issue and the horizon package on Pypi would still be seen as The OpenStack Dashboard like it is now. We would only add an horizon_lib package on Pypi. Therefore existing third-party requirements.txt would not brake because they would pull horizon_lib with horizon. and they would still import the proper module. Every backwards compatibility (requirements and module) is therefore preserved. s/brake/break/g Sorry for the typo. -- Yves-Gwenaël Bourhis ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 11/17/2014 06:43 AM, Yves-Gwenaël Bourhis wrote: Le 17/11/2014 14:19, Matthias Runge a écrit : There is already horizon on pypi[1] IMHO this will lead only to more confusion. Matthias [1] https://pypi.python.org/pypi/horizon/2012.2 Well the current horizon on Pypi is The OpenStack Dashboard + horizon(_lib) included If the future horizon on pypi is openstack_dashboard alone, it would still pull horizon_lib as a dependency, so it would not brake the existing. So indeed the horizon package itself in Pypi would not have horizon(_lib) in it anymore, but he pip install horizon would pull everything due to the dependency horizon will have with horizon_lib. I find this the least confusing issue and the horizon package on Pypi would still be seen as The OpenStack Dashboard like it is now. We would only add an horizon_lib package on Pypi. Therefore existing third-party requirements.txt would not brake because they would pull horizon_lib with horizon. and they would still import the proper module. Every backwards compatibility (requirements and module) is therefore preserved. +1 to this solution -- Jason E. Rist Senior Software Engineer OpenStack Management UI Red Hat, Inc. openuc: +1.972.707.6408 mobile: +1.720.256.3933 Freenode: jrist github/identi.ca: knowncitizen ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 11/17/14, 10:00 AM, Jason Rist jr...@redhat.com wrote: On 11/17/2014 06:43 AM, Yves-Gwenaël Bourhis wrote: Le 17/11/2014 14:19, Matthias Runge a écrit : There is already horizon on pypi[1] IMHO this will lead only to more confusion. Matthias [1] https://pypi.python.org/pypi/horizon/2012.2 Well the current horizon on Pypi is The OpenStack Dashboard + horizon(_lib) included If the future horizon on pypi is openstack_dashboard alone, it would still pull horizon_lib as a dependency, so it would not brake the existing. So indeed the horizon package itself in Pypi would not have horizon(_lib) in it anymore, but he pip install horizon would pull everything due to the dependency horizon will have with horizon_lib. I find this the least confusing issue and the horizon package on Pypi would still be seen as The OpenStack Dashboard like it is now. We would only add an horizon_lib package on Pypi. Therefore existing third-party requirements.txt would not brake because they would pull horizon_lib with horizon. and they would still import the proper module. Every backwards compatibility (requirements and module) is therefore preserved. +1 to this solution +1 from me as well. smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 11/17/2014 06:43 AM, Yves-Gwenaël Bourhis wrote: Le 17/11/2014 14:19, Matthias Runge a écrit : There is already horizon on pypi[1] IMHO this will lead only to more confusion. Matthias [1] https://pypi.python.org/pypi/horizon/2012.2 Well the current horizon on Pypi is The OpenStack Dashboard + horizon(_lib) included If the future horizon on pypi is openstack_dashboard alone, it would still pull horizon_lib as a dependency, so it would not brake the existing. So indeed the horizon package itself in Pypi would not have horizon(_lib) in it anymore, but he pip install horizon would pull everything due to the dependency horizon will have with horizon_lib. I find this the least confusing issue and the horizon package on Pypi would still be seen as The OpenStack Dashboard like it is now. We would only add an horizon_lib package on Pypi. Therefore existing third-party requirements.txt would not brake because they would pull horizon_lib with horizon. and they would still import the proper module. Every backwards compatibility (requirements and module) is therefore preserved. +1 on this proposal as well On Mon, Nov 17, 2014 at 6:00 PM, Jason Rist jr...@redhat.com wrote: On 11/17/2014 06:43 AM, Yves-Gwenaël Bourhis wrote: Le 17/11/2014 14:19, Matthias Runge a écrit : There is already horizon on pypi[1] IMHO this will lead only to more confusion. Matthias [1] https://pypi.python.org/pypi/horizon/2012.2 Well the current horizon on Pypi is The OpenStack Dashboard + horizon(_lib) included If the future horizon on pypi is openstack_dashboard alone, it would still pull horizon_lib as a dependency, so it would not brake the existing. So indeed the horizon package itself in Pypi would not have horizon(_lib) in it anymore, but he pip install horizon would pull everything due to the dependency horizon will have with horizon_lib. I find this the least confusing issue and the horizon package on Pypi would still be seen as The OpenStack Dashboard like it is now. We would only add an horizon_lib package on Pypi. Therefore existing third-party requirements.txt would not brake because they would pull horizon_lib with horizon. and they would still import the proper module. Every backwards compatibility (requirements and module) is therefore preserved. +1 to this solution -- Jason E. Rist Senior Software Engineer OpenStack Management UI Red Hat, Inc. openuc: +1.972.707.6408 mobile: +1.720.256.3933 Freenode: jrist github/identi.ca: knowncitizen ___ 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
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 11/11/14 09:30, Jiri Tomasek wrote: On 11/10/2014 12:19 PM, Matthias Runge wrote: On Thu, Oct 30, 2014 at 01:13:48PM +0100, Matthias Runge wrote: Hi, tl;dr: how to progreed in separating horizon and openstack_dashboard About a year ago now we agreed, it makes sense to separate horizon and openstack_dashboard. At the past summit, we discussed this again. Currently, our repo contains two directories: horizon and openstack_dashboard, they both will need new names. We discussed a renaming in the past; the former consensus was: rename horizon to horizon_lib and rename openstack_dashboard to horizon. IMHO that doesn't make any sense and will confuse people a lot. I wouldn't object to rename horizon to horizon_lib, although any other name, e.g django-horizon should be fine as well. openstack_dashboard is our official name; people from outside refer to the Dashboard as Horizon, why not rename to openstack_horizon here? It is official name, but I disagree that people refer more to Dashboard than to Horizon. People mostly talk about Horizon and when they say Horizon they refer to the UI. Dashboard is not much used outside Horizon community and is a bit confusing (overloaded). Small example - when you want to add the general overview page - the actual dashboard, that should be the *dashboard* name how it should be used. Otherwise we are adding _Dashboard_ view into Project's _dashboard_ into OpenStack _Dashboard_ project. That's what I really see confusing :) My opinion and preference: * horizon_lib (framework) + horizon (UI) Thoughts? Opinions? Suggestions? From what was discussed on contributors meetup, keeping the names 'horizon' for the lib (framework) and 'openstack_dashboard' for dashboard seemed most convenient. And I happen to aggree with that. Jirka Not sure if it seemed the most convenient, I haven't seen agreement there. -- Jarda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 11/14/14, 4:24 AM, Jaromir Coufal jcou...@redhat.com wrote: On 11/11/14 09:30, Jiri Tomasek wrote: On 11/10/2014 12:19 PM, Matthias Runge wrote: On Thu, Oct 30, 2014 at 01:13:48PM +0100, Matthias Runge wrote: Hi, tl;dr: how to progreed in separating horizon and openstack_dashboard About a year ago now we agreed, it makes sense to separate horizon and openstack_dashboard. At the past summit, we discussed this again. Currently, our repo contains two directories: horizon and openstack_dashboard, they both will need new names. We discussed a renaming in the past; the former consensus was: rename horizon to horizon_lib and rename openstack_dashboard to horizon. IMHO that doesn't make any sense and will confuse people a lot. I wouldn't object to rename horizon to horizon_lib, although any other name, e.g django-horizon should be fine as well. openstack_dashboard is our official name; people from outside refer to the Dashboard as Horizon, why not rename to openstack_horizon here? It is official name, but I disagree that people refer more to Dashboard than to Horizon. People mostly talk about Horizon and when they say Horizon they refer to the UI. Dashboard is not much used outside Horizon community and is a bit confusing (overloaded). Small example - when you want to add the general overview page - the actual dashboard, that should be the *dashboard* name how it should be used. Otherwise we are adding _Dashboard_ view into Project's _dashboard_ into OpenStack _Dashboard_ project. That's what I really see confusing :) My opinion and preference: * horizon_lib (framework) + horizon (UI) I agree with both the concept behind these names and the name selections given here. People don¹t think of Nova as the framework, nor Neutron as the framework. That¹s the server/service that we make rest calls against. I like: (horizon_lib or horizon_framework) and horizon smime.p7s Description: S/MIME cryptographic signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 14/11/14 15:46, Wood, Matthew David (HP Cloud - Horizon) wrote: On 11/14/14, 4:24 AM, Jaromir Coufal jcou...@redhat.com wrote: My opinion and preference: * horizon_lib (framework) + horizon (UI) I agree with both the concept behind these names and the name selections given here. People don¹t think of Nova as the framework, nor Neutron as the framework. That¹s the server/service that we make rest calls against. I like: (horizon_lib or horizon_framework) and horizon The concern with this raised by Matthias is that application developers who currently do import horizon to build plug-ins will be surprised and completely broken once they upgrade. Changing both names would alleviate that a little. Julie ___ 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
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 30/10/14 13:13, Matthias Runge wrote: I tried that in [3], [4]. I renamed openstack_dashboard to openstack_horizon, rather than horizon to be sure, I really catched all imports etc., and to make sure, it's clear, what component is meant. During this process, the name horizon is a bit ambiguous. Thank you for doing this, it helps a lot! [snip] So, how do we proceed from here? - how do we block the gate I have no idea, in the past we just -2-ed all patches temporarily? - how to create a new repo - how to set up ci for the new project? That shouldn't be too complicated. Basically you send a patch to https://github.com/openstack-infra/project-config and have it accepted by the infra team. I suppose we will copy most of the current horizon setup. It will help to have someone from infra helping us on that. - how to integrate new horizon_lib and horizon (or openstack-horizon) to devstack I suppose we have to reach out to the devstack people for that. -- Radomir Dopieralski ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
Hi all, I'm agree with you Mathias, we should separate and rename. My suggestions: horizon - python-horizon openstack_dashboard - openstack-horizon Cheers, Marcos. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 11/10/2014 12:19 PM, Matthias Runge wrote: On Thu, Oct 30, 2014 at 01:13:48PM +0100, Matthias Runge wrote: Hi, tl;dr: how to progreed in separating horizon and openstack_dashboard About a year ago now we agreed, it makes sense to separate horizon and openstack_dashboard. At the past summit, we discussed this again. Currently, our repo contains two directories: horizon and openstack_dashboard, they both will need new names. We discussed a renaming in the past; the former consensus was: rename horizon to horizon_lib and rename openstack_dashboard to horizon. IMHO that doesn't make any sense and will confuse people a lot. I wouldn't object to rename horizon to horizon_lib, although any other name, e.g django-horizon should be fine as well. openstack_dashboard is our official name; people from outside refer to the Dashboard as Horizon, why not rename to openstack_horizon here? Thoughts? Opinions? Suggestions? From what was discussed on contributors meetup, keeping the names 'horizon' for the lib (framework) and 'openstack_dashboard' for dashboard seemed most convenient. And I happen to aggree with that. Jirka ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On Thu, Oct 30, 2014 at 01:13:48PM +0100, Matthias Runge wrote: Hi, tl;dr: how to progreed in separating horizon and openstack_dashboard About a year ago now we agreed, it makes sense to separate horizon and openstack_dashboard. At the past summit, we discussed this again. Currently, our repo contains two directories: horizon and openstack_dashboard, they both will need new names. We discussed a renaming in the past; the former consensus was: rename horizon to horizon_lib and rename openstack_dashboard to horizon. IMHO that doesn't make any sense and will confuse people a lot. I wouldn't object to rename horizon to horizon_lib, although any other name, e.g django-horizon should be fine as well. openstack_dashboard is our official name; people from outside refer to the Dashboard as Horizon, why not rename to openstack_horizon here? Thoughts? Opinions? Suggestions? -- Matthias Runge mru...@redhat.com ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On Thu, Oct 30, 2014 at 01:13:48PM +0100, Matthias Runge wrote: Hi, tl;dr: how to progreed in separating horizon and openstack_dashboard About a year ago now we agreed, it makes sense to separate horizon and openstack_dashboard. At the past summit, we discussed this again. Currently, our repo contains two directories: horizon and openstack_dashboard, they both will need new names. We discussed a renaming in the past; the former consensus was: rename horizon to horizon_lib and rename openstack_dashboard to horizon. IMHO that doesn't make any sense and will confuse people a lot. I wouldn't object to rename horizon to horizon_lib, although any other name, e.g django-horizon should be fine as well. openstack_dashboard is our official name; people from outside refer to the Dashboard as Horizon, why not rename to openstack_horizon here? Thoughts? Opinions? Suggestions? How about 'horizon_dashboard'? I think pairing that with 'horizon_lib' would make the purpose of each very clear. Mainn -- Matthias Runge mru...@redhat.com ___ 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
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 10/11/14 14:20, Tzu-Mainn Chen wrote: How about 'horizon_dashboard'? I think pairing that with 'horizon_lib' would make the purpose of each very clear. Wouldn't that imply, there exists an openstack_dashboard as well? Matthias ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Horizon] Separate horizon and openstack_dashboard
On 10/11/14 14:20, Tzu-Mainn Chen wrote: How about 'horizon_dashboard'? I think pairing that with 'horizon_lib' would make the purpose of each very clear. Wouldn't that imply, there exists an openstack_dashboard as well? Matthias Well, the original renaming idea of openstack_dashboard horizon was suggested because most people think of the openstack_dashboard when they say 'horizon', so I think it might be okay. But it's just an opinion! Mainn ___ 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
[openstack-dev] [Horizon] Separate horizon and openstack_dashboard
Hi, tl;dr: how to progreed in separating horizon and openstack_dashboard About a year ago now we agreed, it makes sense to separate horizon and openstack_dashboard. Thanks to Radomirs work in unbundling JavaScript libraries, we're finally there. It was decided to rename horizon to horizon_lib[1], and to rename openstack_dashboard to horizon. Now following[2]: The split: == code freeze -- no patches merged, except for the ones mentioned here, - rename horizon to horizon_lib, fix all corresponding imports, - rename openstack_dashboard to horizon, fix all corresponding imports, - clone the horizon repository using git-filter to skip the dashboard files, create an external repository on github for that, - add new project to openstack-infra/config called horizon_lib, with the new repo as the upstream, setup CI for the new project, - verify that the new repository works correctly, - remove the horizon_lib files from the old repository in one big commit, end of code freeze I tried that in [3], [4]. I renamed openstack_dashboard to openstack_horizon, rather than horizon to be sure, I really catched all imports etc., and to make sure, it's clear, what component is meant. During this process, the name horizon is a bit ambiguous. It was a somehow larger rework, just search and replace didn't do the job here, and I'm quite confident to have left one or the other thing untouched. There were quite a few additional code changes necessary, mostly due flake8 tests (renamed names are longer, breaking line length, horizon_lib and horizon are now separate, imports must be separated) So, how do we proceed from here? - how do we block the gate - how to create a new repo - how to set up ci for the new project? - how to integrate new horizon_lib and horizon (or openstack-horizon) to devstack Matthias [1] http://lists.openstack.org/pipermail/openstack-dev/2014-June/037996.html [2] https://etherpad.openstack.org/p/horizon-split-plan [3] https://github.com/mrunge/openstack_horizon [4] https://github.com/mrunge/horizon_lib ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
