> -----Original Message----- > From: Akihiro Motoki [mailto:amot...@gmail.com] > Sent: Wednesday, May 31, 2017 6:13 AM > To: OpenStack Development Mailing List <email@example.com> > Subject: [openstack-dev] [neutron][horizon] FWaaS/VPNaaS dashboard split > out from horizon > > Hi all, > > As discussed last month , we agree that each neutron-related dashboard has > its own repository. > I would like to move this forward on FWaaS and VPNaaS as the horizon team > plans to split them out as horizon plugins. > > A couple of questions hit me. > > (1) launchpad project > Do we create a new launchpad project for each dashboard? > At now, FWaaS and VPNaaS projects use 'neutron' for their bug tracking from > the historical reason, it sometimes There are two choices: the one is to > accept > dashboard bugs in 'neutron' launchpad, and the other is to have a separate > launchpad project.
+1 for separating Launchpad we can one for each and each can cover all the issues related To it. > My vote is to create a separate launchpad project. > It allows users to search and file bugs easily. > > (2) repository name > > Are neutron-fwaas-dashboard / neutron-vpnaas-dashboard good repository > names for you? > Most horizon related projects use xxxx-dashboard or xxxx-ui as their repo > names. > I personally prefers to xxxx-dashboard as it is consistent with the OpenStack > dashboard (the official name of horizon). On the other hand, I know some folks > prefer to xxxx-ui as the name is shorter enough. > Any preference? Both looks good, but using ui will make it shorter so +1 for ui > (3) governance > neutron-fwaas project is under the neutron project. > Does it sound okay to have neutron-fwaas-dashboard under the neutron > project? > This is what the neutron team does for neutron-lbaas-dashboard before and > this model is adopted in most horizon plugins (like trove, sahara or others). IMO, we can have it under neutron project for now but for simplicity and maintenance I'd suggest to branch it out from neutron. > (4) initial core team > > My thought is to have neutron-fwaas/vpnaas-core and horizon-core as the > initial core team. > The release team and the stable team follow what we have for neutron- > fwaas/vpnaas projects. > Sounds reasonable? > > > Finally, I already prepare the split out version of FWaaS and VPNaaS > dashboards in my personal github repos. > Once we agree in the questions above, I will create the repositories under > git.openstack.org. > >  http://lists.openstack.org/pipermail/openstack-dev/2017- > April/thread.html#115200 > > _________________________________________________________________ > _________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev