19:00:43 #startmeeting storyboard 19:00:44 Meeting started Wed Apr 17 19:00:43 2019 UTC and is due to finish in 60 minutes. The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:00:45 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:00:47 The meeting name has been set to 'storyboard' 19:01:10 I love story time :) 19:01:37 gather 'round 19:01:38 #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda-ish 19:02:09 #topic Announcements 19:02:19 we're having a repository rename! 19:02:38 Woohoo! 19:02:56 everybody loves those 19:03:09 more of a namespace move really 19:03:17 and also new hosting domain for the source code 19:03:34 as well as a prettier git hosting platform at that domain 19:04:13 yeah, gitea is very shiny, I like it 19:04:29 I think the current plan for us is to basically do s/openstack-infra/opendev/ 19:04:38 the long and short of it is that the openstack infra team has been spinning off some of its core services into a new hosting platform it calls "opendev" at opendev.org 19:04:38 Its all so shiny and new :) 19:05:02 and some of the first services to move are code review and git source hosting/browsing 19:05:10 +2 for s/openstack-infra/opendev/ 19:05:15 that's finally happening this friday, universe willing 19:05:46 as part of that effort, major projects were asked what they wanted to do about namespacing 19:06:27 the openstack project has decided that deliverable repositories for official openstack teams and related efforts go in the "openstack" namespace 19:06:53 but anything not official has to go somewhere else (projects who don't pick a new namespace are going in one called "x") 19:07:11 storyboard's repositories are deliverables of the openstack infra team 19:07:26 so those would normally be expected to move from openstack-infra to openstack 19:07:50 however the opendev effort has its own namespace for things it's extracting out of openstack governance 19:08:27 so has given storyboard deliverables the option of moving out of the openstack namespace and into the opendev namespace 19:09:15 this does however also imply a governance change, that storyboard efforts would cease being part of the openstack project and become an opendev infrastructure project 19:09:18 I think opendev is good. Gives a better impression of not being solely used by openstack 19:09:41 opendev is still supported by the openstack foundation and all the same sponsoring organizations 19:09:56 diablo_rojo: +1 19:10:09 but it's a way to indicate that storyboard is not really an openstack-specific application 19:10:26 Yeah that is a HUGE benefit I think 19:10:36 the governance for opendev isn't entirely fleshed out at this stage, though we do have a proposal floating around 19:10:37 Maybe this is how we get some more hands to help us 19:11:01 i think the end result is at least no worse than remaining part of openstack (same benefits extended by osf and sponsors) 19:11:23 and hopefully a significant improvement in visibility 19:12:01 in the not too distant future, the storyboard instance hosted at storyboard.openstack.org would also start redirecting to a new storyboard.opendev.org name, or something along those lines 19:12:52 as far as the actual maintenance happening on friday, we're trying to make it as seamless as possible, but still expect some bumps 19:13:42 there are redirects already prepped and tested so the old git urls will continue working as before 19:14:25 we'll be pushing patches directly into all repositories (bypassing code review) to update git-review and zuul job configuration 19:15:19 however, you will likely need to pull that commit locally, remove any existing gerrit remote in your repositories, and rerun `git review -s` to get it to reread that configuration so you can push new patches to review 19:16:07 blowing away your local repo and re-cloning is another option of course, if you don't have any local commits you need to save 19:17:02 one other note, specific for the storyboard.openstack.org instance... when we rename projects or their namespaces, we do update the storyboard database to reflect that 19:17:49 we don't currently have any redirecting solution in place though, so sb urls involving specific project names will need updating 19:18:50 for example, https://storyboard.openstack.org/#!/project/openstack-infra/storyboard would need to become https://storyboard.openstack.org/#!/project/opendev/storyboard 19:20:12 anyway, that's all i had on the namespace/hosting changes... any questions? 19:21:03 I don't think so, thanks for the heads up on the configuration changes 19:21:35 * SotK wonders how many projects are using that style of project URL in docs and so on 19:21:54 we should probabl;y make storyboard support renaming projects with the ability to redirect at some point 19:21:55 a lot hadn't converted to it yet, so are still using project id numbers which will keep working as before 19:22:19 and yeah, i was thinking that would be a nifty feature in the future 19:22:52 Agreed 19:22:56 would probably want to do similar with renaming other things like project-groups and teams 19:23:29 yeah, that would make sense 19:23:53 I'll create a story for it after the meeting 19:24:15 in our deployment, i foresee wanting to also start namespacing project-groups and teams the same way we do with projects, but that doesn't really need any change to the software just how we're using it 19:26:02 yeah I suspect that would be a sensible thing to do 19:27:25 anything else on this? 19:27:30 Nothing from me 19:27:47 #topic Migration Updates 19:28:11 i ran the test imports for all the openstack telemetry deliverables on storyboard-dev.openstack.org last week 19:28:20 how did they go? 19:28:57 their ptl gave the results a thumbs-up but we're holding off merging the change and doing the final import until he can arrange to get control of the corresponding launchpad projects so they can have their bug reporting closed down at the same time 19:29:58 there was a bit of a takeover of those projects as they were mostly orphaned by their previous maintainers and some new users have adopted them 19:30:37 so it's taking a bit of time for the new ptl to track down someone with admin privs on those (they had never correctly ceded ownership of the lp teams to the openstack admins team) 19:31:01 hopefully next week though 19:31:10 nice, hopefully its all sorted soon 19:32:09 also in migration news, is seems like the ndsu interns are coming along with the lp blueprint importing implementation? 19:32:25 diablo_rojo has been following that more closely than i have 19:32:55 Yeah a bit. Its still got some work but I think their semester is going to be done in a couple weeks so they have to be done with it by then lol 19:33:29 a bit of the delay was due to the incomplete api on launchpad around its blueprints feature 19:33:34 the api actually calls them "specs" 19:34:26 but at any rate, there's no obvious way to query for "specs" which match a particular project on lp, so they're having to resort to scraping the web content for searches through its webui 19:34:52 ugly, but gets the job done 19:35:05 yeah I had a quick look at the patch and assumed that missing apis were the cause behind that 19:35:26 I'll try to follow it more closely in the next week or two :) 19:35:30 and at least once you have the name of a spec you can use the lp api to fetch details 19:36:07 i don't have any other migration updates 19:37:14 #topic Forum/PTG Planning 19:37:36 do we have anything left that we should plan? 19:39:29 and do we want to book a team photo slot? :D 19:40:14 diablo_rojo seems to be a fan of photos 19:40:28 I like taking them more than being in them 19:40:38 but if you want a photo I can stand there awkwardly 19:41:07 I created the etherpad for the forum session 19:41:28 I don't have a strong desire for one, lets just not have one if you prefer taking them :) 19:41:43 nice, do you have a link for it? 19:41:57 #link https://etherpad.openstack.org/p/storyboard-pain-points Etherpad 19:42:19 Its towards the end of the day Monday 19:42:31 As for the massive bug triage we are planning at the PTG 19:42:45 I think a corner of the infra room Thursday morning? 19:42:58 yeah, i was a photographer's assistant for years, not really that into being in front of the camera but happy to jump i a photo if folks want 19:43:27 #decision no photo :) 19:43:47 diablo_rojo: corner of the infra room sounds good 19:44:00 I didnt think we needed an etherpad for the PTG activities, but I think we should email the discuss list with the plan 19:45:03 yeah we probably should 19:45:09 would you like to do it or shall I? 19:45:19 SotK, go for it ;) 19:45:40 alright then, I'll get it sent sometime in the next day or two 19:45:52 Sounds good. 19:46:50 #topic In Progress Work 19:47:08 I have about a million patches to review 19:47:19 I'll try to get some of it done over the long weekend 19:47:59 Heh yeah you do. 19:48:02 I've been super busy elsewhere recently so have fallen rather behind on it again 19:48:06 I also have a lot to review 19:48:19 Its alright. I started single core approving the smaller ones 19:48:26 I will probably do another round of that today. 19:48:31 I noticed that, thanks :) 19:48:35 Trying to leave the ones I think you might have an opinion on. 19:49:05 I am currently no longer working on making new features as my term has come to a close, though I'll still be around until my patches get pushed to completion 19:49:19 mkarray, awesome 19:49:44 mkarray: thanks for your work! 19:50:05 Yes thank you! 19:50:07 My pleasure :) You guys have been very helpful 19:50:14 We hope you'll stick around as much as you can 19:50:30 your presence has been a huge help, even just answering folks questions in irc 19:50:30 Maybe you can do the next round of outreachy after this summer round? 19:50:37 That too 19:51:29 +1, I really appreciate it :) 19:51:32 I'll definitely make the effort to apply, once again I had a great time helping out 19:52:59 #topic Open Discussion 19:54:42 * diablo_rojo doesnt have anything 19:55:10 yeah, i have to get back to scripting a few thousand git commits for friday 19:56:16 Have fun with that :) 19:57:19 heh, sounds exciting 19:57:25 thanks for coming folks! 19:57:27 #endmeeting