<div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">Hi Gabriel,</div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">
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.</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">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.</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">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 <b>Rainbow</b>? A <b>Storm</b>? 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 :)</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div><div class="gmail_default" style="font-family:trebuchet ms,sans-serif">About the plan - it seems reasonable for me, count me in for the big rush.</div>
<div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 28, 2014 at 11:03 PM, Gabriel Hurley <span dir="ltr"><<a href="mailto:Gabriel.Hurley@nebula.com" target="_blank">Gabriel.Hurley@nebula.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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_".<br>
<br>
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.<br>
<br>
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". ;-)<br>
<br>
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.<br>
<br>
All the best,<br>
<br>
- Gabriel<br>
<div class="HOEnZb"><div class="h5"><br>
> -----Original Message-----<br>
> From: Radomir Dopieralski [mailto:<a href="mailto:openstack@sheep.art.pl">openstack@sheep.art.pl</a>]<br>
> Sent: Wednesday, May 28, 2014 5:55 AM<br>
> To: OpenStack Development Mailing List (not for usage questions)<br>
> Subject: [openstack-dev] [horizon][infra] Plan for the splitting of Horizon into<br>
> two repositories<br>
><br>
> Hello,<br>
><br>
> we plan to finally do the split in this cycle, and I started some preparations for<br>
> that. I also started to prepare a detailed plan for the whole operation, as it<br>
> seems to be a rather big endeavor.<br>
><br>
> You can view and amend the plan at the etherpad at:<br>
> <a href="https://etherpad.openstack.org/p/horizon-split-plan" target="_blank">https://etherpad.openstack.org/p/horizon-split-plan</a><br>
><br>
> It's still a little vague, but I plan to gradually get it more detailed.<br>
> All the points are up for discussion, if anybody has any good ideas or<br>
> suggestions, or can help in any way, please don't hesitate to add to this<br>
> document.<br>
><br>
> We still don't have any dates or anything -- I suppose we will work that out<br>
> soonish.<br>
><br>
> Oh, and great thanks to all the people who have helped me so far with it, I<br>
> wouldn't even dream about trying such a thing without you. Also thanks in<br>
> advance to anybody who plans to help!<br>
><br>
> --<br>
> Radomir Dopieralski<br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Regards,<br>Tihomir Trifonov
</div>