Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-06-05 Thread Mark McLoughlin
On Thu, 2014-05-29 at 15:29 -0400, Anita Kuno wrote: On 05/28/2014 08:54 AM, Radomir Dopieralski wrote: Hello, we plan to finally do the split in this cycle, and I started some preparations for that. I also started to prepare a detailed plan for the whole operation, as it seems to be a

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-06-05 Thread Radomir Dopieralski
On 06/05/2014 10:59 AM, Mark McLoughlin wrote: If I'm late to the party and the only one that this is news to, that is fine. Sixteen additional repos seems like a lot of additional reviews will be needed. One slightly odd thing about this is that these repos are managed by horizon-core, so

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-06-05 Thread Mark McLoughlin
On Thu, 2014-06-05 at 11:19 +0200, Radomir Dopieralski wrote: On 06/05/2014 10:59 AM, Mark McLoughlin wrote: If I'm late to the party and the only one that this is news to, that is fine. Sixteen additional repos seems like a lot of additional reviews will be needed. One slightly odd

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-06-04 Thread Jiri Tomasek
On 05/31/2014 11:13 PM, Jeremy Stanley wrote: On 2014-05-29 20:55:01 + (+), Lyle, David wrote: [...] There are several more xstatic packages that horizon will pull in that are maintained outside openstack. The packages added are only those that did not have existing xstatic packages.

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-06-03 Thread Radomir Dopieralski
On 05/31/2014 11:13 PM, Jeremy Stanley wrote: On 2014-05-29 20:55:01 + (+), Lyle, David wrote: [...] There are several more xstatic packages that horizon will pull in that are maintained outside openstack. The packages added are only those that did not have existing xstatic packages.

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-06-02 Thread Matthias Runge
On Sat, May 31, 2014 at 09:13:35PM +, Jeremy Stanley wrote: I'll admit that my Web development expertise is probably almost 20 years stale at this point, so forgive me if this is a silly question: what is the reasoning against working with the upstreams who do not yet distribute needed

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-31 Thread Jeremy Stanley
On 2014-05-29 20:55:01 + (+), Lyle, David wrote: [...] There are several more xstatic packages that horizon will pull in that are maintained outside openstack. The packages added are only those that did not have existing xstatic packages. These packages will be updated very sparingly,

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-30 Thread Radomir Dopieralski
On 05/29/2014 08:40 PM, Gabriel Hurley wrote: we could have a poll for the name. Gabriel, would you like to run that? I can run that if you like, though it might be more official coming from the PTL. ;-) I'm sure that David is reading this and that he will tell us when anything we are

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-29 Thread Tihomir Trifonov
Hi Gabriel, thanks for joining the conversation. It is a quite old discussion that was also discussed at the Atlanta design summit, and it seems that the moment this to happen had finally come. It is always nice to hear the opinion of a real Django core developer. Just a follow-up from the

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-29 Thread Radomir Dopieralski
On 05/28/2014 10:03 PM, Gabriel Hurley wrote: It's sort of a silly point, but as someone who would likely consume the split-off package outside of the OpenStack context, please give it a proper name instead of django_horizon. The module only works in Django, the name adds both clutter and

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-29 Thread Anita Kuno
On 05/28/2014 08:54 AM, Radomir Dopieralski wrote: Hello, we plan to finally do the split in this cycle, and I started some preparations for that. I also started to prepare a detailed plan for the whole operation, as it seems to be a rather big endeavor. You can view and amend the plan at

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-29 Thread Gabriel Hurley
Forgive me if I'm misunderstanding, but those all look like repositories that are strictly tracking upstreams. They're not maintained by the Horizon/OpenStack developers whatsoever. Is this intentional/necessary? - Gabriel -Original Message- From: Anita Kuno

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-29 Thread Anita Kuno
On 05/29/2014 03:45 PM, Gabriel Hurley wrote: Forgive me if I'm misunderstanding, but those all look like repositories that are strictly tracking upstreams. They're not maintained by the Horizon/OpenStack developers whatsoever. Is this intentional/necessary? - Gabriel The permissions

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-29 Thread Lyle, David
The idea here is to decouple 3rd party static files from being embedded in the Horizon repo. There are several reasons for this move. With embedded 3rd party static files upgrading the static files is cumbersome, versions can be difficult to track and updates can be difficult to synchronize. This

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-29 Thread Anita Kuno
On 05/29/2014 04:55 PM, Lyle, David wrote: The idea here is to decouple 3rd party static files from being embedded in the Horizon repo. There are several reasons for this move. With embedded 3rd party static files upgrading the static files is cumbersome, versions can be difficult to track and

[openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-28 Thread Radomir Dopieralski
Hello, we plan to finally do the split in this cycle, and I started some preparations for that. I also started to prepare a detailed plan for the whole operation, as it seems to be a rather big endeavor. You can view and amend the plan at the etherpad at:

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-28 Thread Ana Krivokapic
On 05/28/2014 02:54 PM, Radomir Dopieralski wrote: Hello, we plan to finally do the split in this cycle, and I started some preparations for that. I also started to prepare a detailed plan for the whole operation, as it seems to be a rather big endeavor. You can view and amend the plan at the

Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories

2014-05-28 Thread Gabriel Hurley
It's sort of a silly point, but as someone who would likely consume the split-off package outside of the OpenStack context, please give it a proper name instead of django_horizon. The module only works in Django, the name adds both clutter and confusion, and it's against the Django community's