[tc][horizon][all] Horizon plugins maintenance
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help: - new Django versions - dependencies updates - Horizon API changes - etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
I added horizon-core to zun-ui core. Feel free to exercice the +2 privilegae whenever it is necessary.
On Wed., Oct. 23, 2019, 8:51 a.m. Ivan Kolodyazhny e0ne@e0ne.info wrote:
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help:
- new Django versions
- dependencies updates
- Horizon API changes
- etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
I believe this is totally reasonable and will raise it with the ironic team during our next meeting.
Thanks for bringing this up!
-Julia
On Wed, Oct 23, 2019 at 5:43 AM Ivan Kolodyazhny e0ne@e0ne.info wrote:
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help:
- new Django versions
- dependencies updates
- Horizon API changes
- etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
While I totally forgot to bring this up during the ironic meeting today, I was able to bring it up with the cores present shortly after the meeting. Everyone was good with granting this access.
As such I've added horizon-core to ironic-ui-core. The only ask from the ironic team is that we try to have one core review from the ironic team as well. If we run into any visibility issues, please don't hesitate to reach out to the team in IRC.
I hope this is just the beginning of a new age of cross-project collaboration in OpenStack!
Thanks again!
-Julia
On Wed, Oct 23, 2019 at 11:14 AM Julia Kreger juliaashleykreger@gmail.com wrote:
I believe this is totally reasonable and will raise it with the ironic team during our next meeting.
Thanks for bringing this up!
-Julia
On Wed, Oct 23, 2019 at 5:43 AM Ivan Kolodyazhny e0ne@e0ne.info wrote:
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help:
- new Django versions
- dependencies updates
- Horizon API changes
- etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
Hi,
I have added horizon-core to sahara-dashboard-core. Thanks for your help.
Best, Jeremy
On Wed, Oct 23, 2019 at 2:44 PM Ivan Kolodyazhny e0ne@e0ne.info wrote:
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help:
- new Django versions
- dependencies updates
- Horizon API changes
- etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
Hi Ivan and Horizon team,
thanks a lot for your help. It's greatly appreciated. I've submitted a change[1] granting +2 permissions for Monasca UI.
[1] https://review.opendev.org/690918
Best greetings Witek
On 10/23/19 2:41 PM, Ivan Kolodyazhny wrote:
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help:
- new Django versions
- dependencies updates
- Horizon API changes
- etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
On Wed, Oct 23, 2019 at 5:46 AM Ivan Kolodyazhny e0ne@e0ne.info wrote:
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help:
- new Django versions
- dependencies updates
- Horizon API changes
- etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
+1, the horizon team has been extremely helpful in reviewing, finding, fixing issues in manila-ui. We certainly appreciate the proactive approach you folks take, Ivan! It's invaluable to teams that have lesser number of core reviewers/contributors who are familiar with the framework or the dependencies. If anyone needs a testimony, we've had the horizon core team have access to merge changes in manila-ui for several releases now, and they've been nothing but responsible and responsive!
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
Hi,
We really appreciate the help! I've submitted a change adding +2/+1 permissions for horizon-core on cloudkitty-dashboard [1].
Cheers,
[1] https://review.opendev.org/#/c/691263/
Hi Ivan,
Thank you for your offer and support. I raised this topic at the weekly Octavia meeting and we agreed to add the horizon core team to octavia-dashboard-core. I have updated the access on gerrit.
Michael
On Wed, Oct 23, 2019 at 5:44 AM Ivan Kolodyazhny e0ne@e0ne.info wrote:
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help:
- new Django versions
- dependencies updates
- Horizon API changes
- etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
Hi,
As discussed in PTG, I had added horizon-core into tacker-horizon-core team. Thanks for your support.
Thanks & Regards Dharmendra Kushwaha
On Wed, Oct 23, 2019 at 6:20 PM Ivan Kolodyazhny e0ne@e0ne.info wrote:
Hi team,
As you may know, we've got a pretty big list of Horizon Plugins [1]. Unfortunately, not all of them are in active development due to the lack of resources in projects teams.
As a Horizon team, we understand all the reasons, and we're doing our best to help other teams to maintain plugins.
That's why we're proposing our help to maintain horizon plugins. We raised this topic during the last Horizon weekly meeting [2] and we'll have some discussion during the PTG [3] too.
There are a lot of Horizon changes which affect plugins and horizon team is ready to help:
- new Django versions
- dependencies updates
- Horizon API changes
- etc.
To get faster fixes in, it would be good to have +2 permissions for the horizon-core team for each plugin.
We helped Heat team during the last cycle adding horizon-core to the heat-dashboard-core team. Also, we've got +2 on other plugins via global project config [4] and via Gerrit configuration for (neutron-*aas-dashboard, tuskar-ui).
Vitrage PTL agreed to do the same for vitrage-dashboard during the last meeting [5].
Of course, it's up to each project to maintain horizon plugins and it's responsibilities but I would like to raise this topic to the TC too. I really sure, that it will speed up some critical fixes for Horizon plugins and makes users and operators experience better.
[1] https://docs.openstack.org/horizon/latest/install/plugin-registry.html [2] http://eavesdrop.openstack.org/meetings/horizon/2019/horizon.2019-10-16-15.0... [3] https://etherpad.openstack.org/p/horizon-u-ptg [4] http://codesearch.openstack.org/?q=horizon-core&i=nope&files=&re... [5] http://eavesdrop.openstack.org/meetings/vitrage/2019/vitrage.2019-10-23-08.0...
Regards, Ivan Kolodyazhny, http://blog.e0ne.info/
participants (9)
-
Dharmendra Kushwaha
-
Goutham Pacha Ravi
-
Hongbin Lu
-
Ivan Kolodyazhny
-
Jeremy Freudberg
-
Julia Kreger
-
Luka Peschke
-
Michael Johnson
-
Witek Bedyk