Friday, 2020-06-26

*** jamesmcarthur has joined #openstack-tc00:00
*** jamesmcarthur_ has joined #openstack-tc00:18
*** jamesmca_ has joined #openstack-tc00:21
*** jamesmcarthur has quit IRC00:22
*** jamesmcarthur_ has quit IRC00:23
*** jamesmca_ has quit IRC00:24
*** tetsuro has joined #openstack-tc00:25
*** ricolin has joined #openstack-tc00:37
*** jamesmcarthur has joined #openstack-tc00:39
*** jamesmcarthur has quit IRC00:42
*** ricolin has quit IRC00:42
*** jamesmcarthur has joined #openstack-tc00:44
*** markvoelker has joined #openstack-tc00:54
*** markvoelker has quit IRC00:59
*** markvoelker has joined #openstack-tc01:09
*** markvoelker has quit IRC01:14
openstackgerritGhanshyam Mann proposed openstack/governance master: Add storyboard link to migrate-to-focal goal  https://review.opendev.org/73812901:42
*** ricolin has joined #openstack-tc01:46
*** jamesmcarthur has quit IRC01:58
*** jamesmcarthur has joined #openstack-tc01:59
*** jamesmcarthur has quit IRC02:04
*** jamesmcarthur has joined #openstack-tc02:32
*** jamesmcarthur has quit IRC02:42
*** ricolin has quit IRC03:02
*** markvoelker has joined #openstack-tc03:10
*** markvoelker has quit IRC03:14
*** jamesmcarthur has joined #openstack-tc03:17
*** jamesmcarthur has quit IRC03:22
*** jamesmcarthur has joined #openstack-tc03:50
*** camelCaser has quit IRC04:33
*** evrardjp has quit IRC04:33
*** ccamel has joined #openstack-tc04:33
*** evrardjp has joined #openstack-tc04:33
*** jamesmcarthur has quit IRC04:52
*** jamesmcarthur has joined #openstack-tc04:52
*** jamesmcarthur has quit IRC04:58
*** jamesmcarthur has joined #openstack-tc05:26
*** jamesmcarthur has quit IRC05:33
*** diablo_rojo has quit IRC05:50
*** ralonsoh has joined #openstack-tc06:17
*** dklyle has quit IRC06:20
*** rpittau|afk is now known as rpittau06:29
*** slaweq has joined #openstack-tc06:56
*** e0ne has joined #openstack-tc07:31
*** tosky has joined #openstack-tc07:35
*** markvoelker has joined #openstack-tc08:49
*** markvoelker has quit IRC08:54
*** rpittau is now known as rpittau|bbl10:04
*** tetsuro has quit IRC10:08
*** slaweq has quit IRC10:40
*** slaweq has joined #openstack-tc10:42
*** markvoelker has joined #openstack-tc10:50
*** markvoelker has quit IRC10:54
*** rpittau|bbl is now known as rpittau12:12
*** ijolliffe has joined #openstack-tc12:26
*** markvoelker has joined #openstack-tc12:51
*** markvoelker has quit IRC12:56
*** cloudnull has quit IRC13:17
mnasertc-members: eyes on https://review.opendev.org/#/c/737590/ if possible, please? :)13:21
mnaserand let us start gathering votes on https://review.opendev.org/#/c/738105/ for gouthamr =]13:21
openstackgerritMerged openstack/governance master: No longer track refstack repos in governance  https://review.opendev.org/73796213:32
njohnstonaye aye captain13:33
openstackgerritMerged openstack/governance master: TC Guide Follow Ups  https://review.opendev.org/73765013:34
openstackgerritMerged openstack/governance master: Add storyboard link to migrate-to-focal goal  https://review.opendev.org/73812913:34
*** mordred has quit IRC13:34
*** cloudnull has joined #openstack-tc13:40
*** cloudnull has quit IRC13:44
*** cloudnull has joined #openstack-tc13:45
*** jamesmcarthur has joined #openstack-tc13:49
gmanno/13:50
*** dklyle has joined #openstack-tc14:08
knikollao/14:30
gmannclarkb: fungi AJaeger does these renaming applies for 'openstack/' -> 'x/' namespace also https://docs.opendev.org/opendev/infra-manual/latest/creators.html#project-renames14:38
gmanni remember we talked it earlier but making sure14:39
fungigmann: i don't understand the question14:40
gmannnetworking-l2gw has active maintainer and they want to continue the development under x/ namespace. and it is under openstack/ now but retired so we have to complete the retirement for it.14:40
fungimakes sense so far14:40
gmannfungi: instead of deleting the code just rename to keep history etc - https://review.opendev.org/#/c/738035/14:40
gmanntill now we use to retire (means delete code from openstack/) as there were no maintainer but in this case repo is active but cannot stay under openstack/ as it is not official project14:41
fungigmann: that's precisely the sort of situation which prompted us to enact https://governance.openstack.org/tc/resolutions/20190711-mandatory-repository-retirement.html14:42
fungidoesn't matter whether there are active maintainers14:42
gmannhumm14:42
fungiwe need a retired copy of the repository in the openstack namespace and to not redirect the old repository to the new name specifically so that people who are consuming the source code know it's no longer an official part of openstack14:43
fungiwe've had too many cases in the past where a project left openstack governance, we renamed them, then later they became defunct, but users continued trying to use it because they never found out it wasn't an official part of openstack, and since it was by that time no longer under the tc's jurisdiction there was no way to properly signal that the project was dead/abandoned/unmaintained14:44
toskynow I shouldn't ask this, but this didn't happen for refstack, just moved under osf14:44
gmannfor dead/abandoned/unmaintained it make sense.14:45
fungiwe've made exceptions for repositories which are managed by the osf board of directors, because we have some leverage to get them to cleanly retire such projects when they're no longer maintaining them14:45
fungi(the openstack tc is granted certain jurisdiction directly within the osf bylaws)14:46
gmannyeah, osf is taken that way,14:47
toskyre users who continued to use the software because they didn't notice it wasn't official: does it mean the lack of the project under openstack/ namespace wasn't enough?14:47
gmannand no way for them to keep the history with new repo creation.14:47
fungibut the whole point of the mandatory retirement resolution was about projects which leave tc control when they're still actively maintained14:47
toskygmann: can't they import from github or other sources when creating a repository?14:48
fungithe idea is that they history from when they were an official part of openstack remains in openstack, and retired. the project which continues outside openstack tc jurisdiction is a new project, a fork of the previous openstack project14:48
toskyI think I've seen that in the past; if that's still the case, they can push the clone to an external source with the full history14:48
toskyand get that imported14:48
fungithey can import directly from the openstack copy of the repository when creating the new repository in some other namespace14:48
toskyeven easier14:48
AJaegertosky, fungi, want to followup to my email on openstack-discuss in case it's not clear?14:49
fungijust set "upstream: https://opendev.org/openstack/whatever" in the gerrit/projects.yaml entry they create and our project management automation will import the original git history14:49
*** cloudnull has quit IRC14:50
gmannyeah let's go that way only instead of any exception here14:50
fungithen their first change proposed to the fork can be `git revert HEAD`14:50
*** cloudnull has joined #openstack-tc14:51
fungialong with an edit to the .gitreview file for the new repository namespace14:51
fungiand then proceed to propose new changes as usual14:51
*** markvoelker has joined #openstack-tc14:52
AJaegerfungi: or - as I proposed on openstack-discuss: Import current state as is without the README change - and then close under openstack14:54
*** markvoelker has quit IRC14:57
fungiAJaeger: sure, that works too, all depends on whether they get around to creating the projects in the new namespace before or after they're retired from the openstack namespace15:00
fungiif it happens after, then they'll need to propose reverts in the new repos, but otherwise the process is essentially the same15:00
gmannwe can hold the openstack namespace for few days, anyways lajoskatona is going to start it on Monday15:01
fungialso if they have in-repo job definitions, forking that before the zuul configs are removed through retirement could prove problematic15:01
AJaegerfungi: oh, yes - we won't be able to import that...15:20
fungiwhich is why importing the retired state and then reverting might be better. that way the zuul config gets reintroduced as a proposed change in gerrit and can be tested normally15:21
AJaegerindeed15:22
AJaegerfungi: or remove .zuul.yaml, import, retire; we'll figure it out next week ;)15:24
*** mordred has joined #openstack-tc15:36
*** ricolin has joined #openstack-tc15:39
*** rpittau is now known as rpittau|afk15:59
*** e0ne has quit IRC16:05
*** ricolin has quit IRC16:13
*** mordred has quit IRC16:33
*** mordred has joined #openstack-tc16:38
*** markvoelker has joined #openstack-tc16:53
*** markvoelker has quit IRC16:58
*** jamesmcarthur has quit IRC17:23
*** jamesmcarthur has joined #openstack-tc17:23
*** jamesmcarthur has quit IRC17:27
*** jamesmcarthur has joined #openstack-tc17:50
*** jamesmcarthur has quit IRC18:08
*** ralonsoh has quit IRC18:25
*** markvoelker has joined #openstack-tc18:49
*** markvoelker has quit IRC18:54
*** slaweq has quit IRC20:02
*** slaweq has joined #openstack-tc20:06
*** slaweq has quit IRC20:10
*** markvoelker has joined #openstack-tc20:35
*** markvoelker has quit IRC20:39
openstackgerritLance Bragstad proposed openstack/governance master: Update policy in code goal for glance  https://review.opendev.org/73827820:47
*** markvoelker has joined #openstack-tc22:35
*** markvoelker has quit IRC22:40
*** tosky has quit IRC23:00
openstackgerritMerged openstack/governance master: Update policy in code goal for glance  https://review.opendev.org/73827823:37
openstackgerritMerged openstack/governance master: Add deprecated cycle for deprecated deliverables  https://review.opendev.org/73759023:41

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!