Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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 rather big endeavor. You can view and amend the plan at the etherpad at: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! I'd like to confirm that we are all aware that this patch creates 16 new repos under the administration of horizon-ptl and horizon-core: https://review.openstack.org/#/c/95716/ 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 presumably part of the Horizon program, but yet the repos are under the stackforge/ namespace. Mark. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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 presumably part of the Horizon program, but yet the repos are under the stackforge/ namespace. What would you propose instead? Keeping them in repositories external to OpenStack, on github or bitbucket sounds wrong. Getting them under openstack/ doesn't sound good either, as the projects they are packaging are not related to OpenStack. Have them be managed by someone else? Who? -- 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][infra] Plan for the splitting of Horizon into two repositories
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 thing about this is that these repos are managed by horizon-core, so presumably part of the Horizon program, but yet the repos are under the stackforge/ namespace. What would you propose instead? Keeping them in repositories external to OpenStack, on github or bitbucket sounds wrong. Getting them under openstack/ doesn't sound good either, as the projects they are packaging are not related to OpenStack. Have them be managed by someone else? Who? If they're to be part of the Horizon program, I'd say they should be under openstack/. If not, perhaps create a new team to manage them. Mark. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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. These packages will be updated very sparingly, only when updating say bootstrap or jquery versions. [...] 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 Javascript library packages to help them participate in the distribution channels you need? This strikes me as similar to forking a Python library which doesn't publish to PyPI, just so you can publish it to PyPI. When some of these dependencies begin to publish xstatic packages themselves, do the equivalent repositories in Gerrit get decommissioned at that point? Standard way to publish javascript libraries these days is publish minified javascript file/s (usually in dist part of repository) and standard way to include it in the project is to use nodejs tools such as Bower to list the js dependencies and have them installed automatically. In our case it is more convinient to use xstatic packages, which we have to create if someone hasn't done it already. I think it might happen, that some of 'our' packages might turn into the official ones. Jirka ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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. These packages will be updated very sparingly, only when updating say bootstrap or jquery versions. [...] 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 Javascript library packages to help them participate in the distribution channels you need? There is nothing stopping us from doing that. On the other hand, I don't expect much success with that. Those are JavaScript and/or style/resources libraries, and the authors usually don't know or care about python packaging. Some of those libraries don't even have proper releases or versioning! We can reach out and ask them to include the packages in their releases (where they have them), but we need the packages now -- we are already using those libraries and we need to clean up how we bundle them. This strikes me as similar to forking a Python library which doesn't publish to PyPI, just so you can publish it to PyPI. There is no fork, as we are not modifying the source code. When some of these dependencies begin to publish xstatic packages themselves, do the equivalent repositories in Gerrit get decommissioned at that point? Yes, we will hand over the keys to the pypi entries, and get rid of the repositories on our side. -- 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][infra] Plan for the splitting of Horizon into two repositories
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 Javascript library packages to help them participate in the distribution channels you need? This strikes me as similar to forking a Python library which doesn't publish to PyPI, just so you can publish it to PyPI. When some of these dependencies begin to publish xstatic packages themselves, do the equivalent repositories in Gerrit get decommissioned at that point? we need those libraries installable or provided as a python package. Using xstatic solves this for us in a very nice way. I must admit, I'd prefer those (javascript) libraries installable as (rpm) packages, but that makes it even more complicated e.g gate. It seems, many folks here try to avoid distro packages at all. -- 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][infra] Plan for the splitting of Horizon into two repositories
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, only when updating say bootstrap or jquery versions. [...] 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 Javascript library packages to help them participate in the distribution channels you need? This strikes me as similar to forking a Python library which doesn't publish to PyPI, just so you can publish it to PyPI. When some of these dependencies begin to publish xstatic packages themselves, do the equivalent repositories in Gerrit get decommissioned at that point? -- Jeremy Stanley ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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 doing is wrong or could be improved. I think we should do whatever needs doing and not bother the PTL with every triviality. It would be great if you could do it, because I'm not good at this kind of stuff, and I just want to have the name. I do realize the choice is important as well as the way it was made, but I'm hopeless at it. It would be a great help if you could handle 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][infra] Plan for the splitting of Horizon into two repositories
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 discussions in Atlanta for those who didn't attend - as long as there are some new Web UI projects in OpenStack, it is a good reason to make a common web framework that to be used for all projects(something like a common layer on top of Django, to be used from different projects), which will need to only add their custom logic and views. Currently there is a lot of duplicate and similar code in different projects that could be unified. Also this will make it very easy to add new openstack-related dashboard sites, keeping it consistent to other sites, hence easier contribution from other project developers. Back on the naming thing - since Horizon from the very beginning keeps the common files(base templates and scripts), isn't it better to keep it's name?. Since Horizon is the base on which the different Dashboard projects will be built over, I'd propose a kind of broader naming concept - what comes on the horizon? A *Rainbow*? A *Storm*? This would allow the easy selection of new names when needed, and all will be related to Horizon in some way. I'm not sure if this makes sense, but I personally like when project names have something in common :) About the plan - it seems reasonable for me, count me in for the big rush. On Wed, May 28, 2014 at 11:03 PM, Gabriel Hurley gabriel.hur...@nebula.comwrote: 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 conventions to have the python import name be prefixed with django_. If the name horizon needs to stay with the reference implementation of the dashboard rather than keeping it with the framework as-is that's fine, but choose a new real name for the framework code. Just to get the ball rolling, and as a nod to the old-timers, I'll propose the runner up in the original naming debate: bourbon. ;-) If there are architectural questions I can help with in this process let me know. I'll try to keep an eye on the progress as it goes. All the best, - Gabriel -Original Message- From: Radomir Dopieralski [mailto:openst...@sheep.art.pl] Sent: Wednesday, May 28, 2014 5:55 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories 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: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! -- Radomir Dopieralski ___ 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 -- Regards, Tihomir Trifonov ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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 confusion, and it's against the Django community's conventions to have the python import name be prefixed with django_. Since the name is completely irrelevant from the technical point of view, and everybody will naturally have their own opinions about it, I would prefer to skip the whole discussion and just settle on the most mundane, boring, uninspired and obvious name that we can use, just to avoid bikeshedding and surprises. I didn't realize it would violate Django community's conventions, can you point to where they are documented? I don't think this is important, but since we have some time until the patches for static files and other stuff clear, we could have a poll for the name. Gabriel, would you like to run 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][infra] Plan for the splitting of Horizon into two repositories
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 the etherpad at: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! I'd like to confirm that we are all aware that this patch creates 16 new repos under the administration of horizon-ptl and horizon-core: https://review.openstack.org/#/c/95716/ 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. Thanks, Anita. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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 [mailto:ante...@anteaya.info] Sent: Thursday, May 29, 2014 12:30 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories 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 the etherpad at: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! I'd like to confirm that we are all aware that this patch creates 16 new repos under the administration of horizon-ptl and horizon-core: https://review.openstack.org/#/c/95716/ 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. Thanks, Anita. ___ 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][infra] Plan for the splitting of Horizon into two repositories
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 on all the new repositories require +A from horizon-core and tagging from horizon-ptl: https://review.openstack.org/#/c/95716/4/modules/openstack_project/files/gerrit/acls/stackforge/xstatic.config Anita. -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Thursday, May 29, 2014 12:30 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories 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 the etherpad at: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! I'd like to confirm that we are all aware that this patch creates 16 new repos under the administration of horizon-ptl and horizon-core: https://review.openstack.org/#/c/95716/ 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. Thanks, Anita. ___ 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 mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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 change encourages developers to fix bugs upstream at the source, rather than edit the static copies in the horizon repo. With the proposed repo split, both the existing horizon and openstack_dashboard components may have a common dependency on these static packages. 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, only when updating say bootstrap or jquery versions. We are certainly open to feedback. David On 5/29/14, 1:53 PM, Anita Kuno ante...@anteaya.info wrote: 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 on all the new repositories require +A from horizon-core and tagging from horizon-ptl: https://review.openstack.org/#/c/95716/4/modules/openstack_project/files/g errit/acls/stackforge/xstatic.config Anita. -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Thursday, May 29, 2014 12:30 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories 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 the etherpad at: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! I'd like to confirm that we are all aware that this patch creates 16 new repos under the administration of horizon-ptl and horizon-core: https://review.openstack.org/#/c/95716/ 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. Thanks, Anita. ___ 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 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][infra] Plan for the splitting of Horizon into two repositories
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 updates can be difficult to synchronize. This change encourages developers to fix bugs upstream at the source, rather than edit the static copies in the horizon repo. With the proposed repo split, both the existing horizon and openstack_dashboard components may have a common dependency on these static packages. 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, only when updating say bootstrap or jquery versions. We are certainly open to feedback. David All I needed to hear was that you and the rest of the core reviewers are aware of that you will be administering these new repos. That was my concern. I'll let the rest of the design discussions proceed. Thanks David, Anita. On 5/29/14, 1:53 PM, Anita Kuno ante...@anteaya.info wrote: 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 on all the new repositories require +A from horizon-core and tagging from horizon-ptl: https://review.openstack.org/#/c/95716/4/modules/openstack_project/files/g errit/acls/stackforge/xstatic.config Anita. -Original Message- From: Anita Kuno [mailto:ante...@anteaya.info] Sent: Thursday, May 29, 2014 12:30 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories 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 the etherpad at: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! I'd like to confirm that we are all aware that this patch creates 16 new repos under the administration of horizon-ptl and horizon-core: https://review.openstack.org/#/c/95716/ 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. Thanks, Anita. ___ 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 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 mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! -- 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][infra] Plan for the splitting of Horizon into two repositories
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 etherpad at: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! This high level overview looks quite reasonable to me. Count me in on helping out with this effort. Thanks for driving this, Radomir! -- Regards, Ana Krivokapic Software Engineer OpenStack team Red Hat Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories
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 conventions to have the python import name be prefixed with django_. If the name horizon needs to stay with the reference implementation of the dashboard rather than keeping it with the framework as-is that's fine, but choose a new real name for the framework code. Just to get the ball rolling, and as a nod to the old-timers, I'll propose the runner up in the original naming debate: bourbon. ;-) If there are architectural questions I can help with in this process let me know. I'll try to keep an eye on the progress as it goes. All the best, - Gabriel -Original Message- From: Radomir Dopieralski [mailto:openst...@sheep.art.pl] Sent: Wednesday, May 28, 2014 5:55 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into two repositories 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: https://etherpad.openstack.org/p/horizon-split-plan It's still a little vague, but I plan to gradually get it more detailed. All the points are up for discussion, if anybody has any good ideas or suggestions, or can help in any way, please don't hesitate to add to this document. We still don't have any dates or anything -- I suppose we will work that out soonish. Oh, and great thanks to all the people who have helped me so far with it, I wouldn't even dream about trying such a thing without you. Also thanks in advance to anybody who plans to help! -- Radomir Dopieralski ___ 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
