14:00:41 #startmeeting sahara 14:00:42 Meeting started Thu Apr 25 14:00:41 2019 UTC and is due to finish in 60 minutes. The chair is jeremyfreudberg. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:00:43 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 14:00:45 The meeting name has been set to 'sahara' 14:01:01 o/ 14:01:28 tosky probably won't be joining today 14:01:30 he is on PTO 14:01:47 yep 14:02:16 #topic News/Updates 14:02:42 nothing new on my side, still not doing much work on sahara lately 14:02:46 o/ 14:02:55 hi tosky 14:03:21 (public holiday here, but I'm unsurprisingly using my computer right now) 14:05:22 i've been busy with non-sahara (and non-openstack) things, not much to report either. i was keeping an eye on the ipv6 goal (offering the sahara perspective as i did for previously proposed goals) 14:05:26 i also did https://review.opendev.org/#/c/655527/ to clean up our repo descriptions (interestingly enough the change has only made it to github so far, not to opendev.org) 14:05:47 I hopefully fixed most of the opendev references , but I have few questions 14:06:05 yes, i saw your sahara-specs question, i'll make it a topic here 14:07:00 anyway 14:07:11 #topic Virtual PTG (may 6 or 7) 14:07:32 i'd still like to have a virtual ptg may 6 or 7 14:07:38 people seem to be around https://www.when2meet.com/?7751227-lVJDN 14:07:47 works for me 14:08:12 i've forgotten to create the etherpad and stuff but i will do that soon and send to the lst 14:08:17 list 14:08:21 my schedule changed a bit, so I updated by availability times 14:09:11 sorry, but this days intercepts a lot of holidays, vacations or other planned duties 14:10:17 in any case, according to a random number generator, i've selected may 6 14:11:06 we might as well do 15 utc (the earliest time that we are all available) but i know telles likes to eat his lunch at that time 14:11:40 that is no problem at all 14:11:52 I can eat a bit earlier and stay for the meeting 14:12:10 count me in 14:12:14 cool 14:12:20 tosky? 15 utc may 6? 14:13:13 yes, fine by me 14:13:35 cool, i will send an email with the etherpad and such 14:14:11 moving on 14:14:16 #topic pike-em tag 14:14:31 there is this patch to create the pike-em tag: https://review.opendev.org/#/c/652891/ 14:14:54 not sure why it is failing, but i just wanted to mention it to our release liasion (tosky) 14:15:27 oh, another one? Right, I tought that the "create the last pike version" was enough 14:15:42 but the tag is a different story 14:16:33 uhm, given that the change is managed by the release team, I guess they will probably figure out the reason for the failure 14:16:57 yes, i guess the same 14:17:50 good 14:18:16 #topic gitdev migration 14:18:30 tosky raised some points about changing some links to gitdev 14:18:34 he can fill us in some more 14:19:42 gitea migration :) 14:19:55 ah, right 14:20:02 mushing my words together 14:20:04 opendev, gitea 14:21:23 the status is: all the links have been fixed in master; there is just an open follow-up for sahara to fix few addresses 14:21:29 (let me find the link) 14:22:18 https://review.opendev.org/654619 14:22:48 i mean the other one, your sahara-specs question 14:22:52 regarding the idea of backporting the changes, I sent few backports for the plugin repositories, but then I asked -infra, and the idea is that it's not worth doing it 14:23:08 the sahara-spec question is the *last* question of the series :) 14:23:52 -infra answer about the backports: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2019-04-22.log.html#t2019-04-22T16:31:03 14:24:29 so up to you: should I abandon the stein backports, or should we backport everything (so also the other repositories) back to stein? 14:24:40 about sahara-spec 14:24:54 sahara-specs* 14:25:32 I sent out an initial patch to replace git.openstack.org with opendev.org, but I may also fix few review.openstack.org->review.opendev.org references 14:25:36 see https://review.opendev.org/#/c/655115/ 14:26:00 if it's all just doc/readme stuff then it's not really necessary 14:26:19 at least for the stable branches and old specs, the churn doesn't seem worth it 14:26:20 the question is: should we go back and fix the old specs? If so, we should probably resurrect also https://review.opendev.org/#/c/568119/, where the link was really broken iirc (or anyway with a redirect which may go away at some point) 14:26:47 i remember someone saying that the redirects will stay in place on the order of years 14:26:53 but it's true, redirects aren't forever 14:27:26 but we also assume it's easy enough for people to understand the meaning of dead link and know how to reconstruct it for whatever new thing is out there 14:30:07 so... :) 14:31:05 i'm in favor of https://review.opendev.org/#/c/654619/ certainly 14:31:11 might as well fix it on the new stuff, for the future 14:31:17 stable branches and old specs -- meh 14:31:28 that is my thought as well 14:32:20 okidoki; I will drop the stein backports of the opendev fixes, and update the sahara-specs review 14:32:33 cool 14:33:14 oh, sorry, I misread 14:33:40 I guess I need to also drop the sahara-specs review 14:33:49 yes 14:34:31 ok -- anything else for today? 14:34:39 not from me 14:36:32 tosky? anything else? 14:36:36 not from me 14:36:42 ok, lets close 14:36:45 bye all 14:36:48 thank you 14:36:48 bye o/ 14:37:33 #endmeeting