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
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.
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
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.
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
+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]
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
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
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]
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
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
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
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
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
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
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
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
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.
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
___
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
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
21 matches
Mail list logo
