19:00:43 <SotK> #startmeeting storyboard
19:00:44 <openstack> 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 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:00:47 <openstack> The meeting name has been set to 'storyboard'
19:01:10 <diablo_rojo> I love story time :)
19:01:37 <fungi> gather 'round
19:01:38 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda-ish
19:02:09 <SotK> #topic Announcements
19:02:19 <SotK> we're having a repository rename!
19:02:38 <diablo_rojo> Woohoo!
19:02:56 <fungi> everybody loves those
19:03:09 <fungi> more of a namespace move really
19:03:17 <fungi> and also new hosting domain for the source code
19:03:34 <fungi> as well as a prettier git hosting platform at that domain
19:04:13 <SotK> yeah, gitea is very shiny, I like it
19:04:29 <SotK> I think the current plan for us is to basically do s/openstack-infra/opendev/
19:04:38 <fungi> 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 <diablo_rojo> Its all so shiny and new :)
19:05:02 <fungi> and some of the first services to move are code review and git source hosting/browsing
19:05:10 <diablo_rojo> +2 for s/openstack-infra/opendev/
19:05:15 <fungi> that's finally happening this friday, universe willing
19:05:46 <fungi> as part of that effort, major projects were asked what they wanted to do about namespacing
19:06:27 <fungi> the openstack project has decided that deliverable repositories for official openstack teams and related efforts go in the "openstack" namespace
19:06:53 <fungi> 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 <fungi> storyboard's repositories are deliverables of the openstack infra team
19:07:26 <fungi> so those would normally be expected to move from openstack-infra to openstack
19:07:50 <fungi> however the opendev effort has its own namespace for things it's extracting out of openstack governance
19:08:27 <fungi> so has given storyboard deliverables the option of moving out of the openstack namespace and into the opendev namespace
19:09:15 <fungi> 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 <diablo_rojo> I think opendev is good. Gives a better impression of not being solely used by openstack
19:09:41 <fungi> opendev is still supported by the openstack foundation and all the same sponsoring organizations
19:09:56 <SotK> diablo_rojo: +1
19:10:09 <fungi> but it's a way to indicate that storyboard is not really an openstack-specific application
19:10:26 <diablo_rojo> Yeah that is a HUGE benefit I think
19:10:36 <fungi> the governance for opendev isn't entirely fleshed out at this stage, though we do have a proposal floating around
19:10:37 <diablo_rojo> Maybe this is how we get some more hands to help us
19:11:01 <fungi> 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 <fungi> and hopefully a significant improvement in visibility
19:12:01 <fungi> 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 <fungi> 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 <fungi> there are redirects already prepped and tested so the old git urls will continue working as before
19:14:25 <fungi> we'll be pushing patches directly into all repositories (bypassing code review) to update git-review and zuul job configuration
19:15:19 <fungi> 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 <fungi> 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 <fungi> 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 <fungi> we don't currently have any redirecting solution in place though, so sb urls involving specific project names will need updating
19:18:50 <fungi> for example, https://storyboard.openstack.org/#!/project/openstack-infra/storyboard would need to become https://storyboard.openstack.org/#!/project/opendev/storyboard
19:20:12 <fungi> anyway, that's all i had on the namespace/hosting changes... any questions?
19:21:03 <SotK> 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 <SotK> we should probabl;y make storyboard support renaming projects with the ability to redirect at some point
19:21:55 <fungi> a lot hadn't converted to it yet, so are still using project id numbers which will keep working as before
19:22:19 <fungi> and yeah, i was thinking that would be a nifty feature in the future
19:22:52 <diablo_rojo> Agreed
19:22:56 <fungi> would probably want to do similar with renaming other things like project-groups and teams
19:23:29 <SotK> yeah, that would make sense
19:23:53 <SotK> I'll create a story for it after the meeting
19:24:15 <fungi> 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 <SotK> yeah I suspect that would be a sensible thing to do
19:27:25 <SotK> anything else on this?
19:27:30 <diablo_rojo> Nothing from me
19:27:47 <SotK> #topic Migration Updates
19:28:11 <fungi> i ran the test imports for all the openstack telemetry deliverables on storyboard-dev.openstack.org last week
19:28:20 <SotK> how did they go?
19:28:57 <fungi> 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 <fungi> 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 <fungi> 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 <fungi> hopefully next week though
19:31:10 <SotK> nice, hopefully its all sorted soon
19:32:09 <fungi> also in migration news, is seems like the ndsu interns are coming along with the lp blueprint importing implementation?
19:32:25 <fungi> diablo_rojo has been following that more closely than i have
19:32:55 <diablo_rojo> 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 <fungi> a bit of the delay was due to the incomplete api on launchpad around its blueprints feature
19:33:34 <fungi> the api actually calls them "specs"
19:34:26 <fungi> 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 <fungi> ugly, but gets the job done
19:35:05 <SotK> yeah I had a quick look at the patch and assumed that missing apis were the cause behind that
19:35:26 <SotK> I'll try to follow it more closely in the next week or two :)
19:35:30 <fungi> and at least once you have the name of a spec you can use the lp api to fetch details
19:36:07 <fungi> i don't have any other migration updates
19:37:14 <SotK> #topic Forum/PTG Planning
19:37:36 <SotK> do we have anything left that we should plan?
19:39:29 <SotK> and do we want to book a team photo slot? :D
19:40:14 <fungi> diablo_rojo seems to be a fan of photos
19:40:28 <diablo_rojo> I like taking them more than being in them
19:40:38 <diablo_rojo> but if you want a photo I can stand there awkwardly
19:41:07 <diablo_rojo> I created the etherpad for the forum session
19:41:28 <SotK> I don't have a strong desire for one, lets just not have one if you prefer taking them :)
19:41:43 <SotK> nice, do you have a link for it?
19:41:57 <diablo_rojo> #link https://etherpad.openstack.org/p/storyboard-pain-points Etherpad
19:42:19 <diablo_rojo> Its towards the end of the day Monday
19:42:31 <diablo_rojo> As for the massive bug triage we are planning at the PTG
19:42:45 <diablo_rojo> I think a corner of the infra room Thursday morning?
19:42:58 <fungi> 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 <diablo_rojo> #decision no photo :)
19:43:47 <SotK> diablo_rojo: corner of the infra room sounds good
19:44:00 <diablo_rojo> 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 <SotK> yeah we probably should
19:45:09 <SotK> would you like to do it or shall I?
19:45:19 <diablo_rojo> SotK, go for it ;)
19:45:40 <SotK> alright then, I'll get it sent sometime in the next day or two
19:45:52 <diablo_rojo> Sounds good.
19:46:50 <SotK> #topic In Progress Work
19:47:08 <SotK> I have about a million patches to review
19:47:19 <SotK> I'll try to get some of it done over the long weekend
19:47:59 <diablo_rojo> Heh yeah you do.
19:48:02 <SotK> I've been super busy elsewhere recently so have fallen rather behind on it again
19:48:06 <diablo_rojo> I also have a lot to review
19:48:19 <diablo_rojo> Its alright. I started single core approving the smaller ones
19:48:26 <diablo_rojo> I will probably do another round of that today.
19:48:31 <SotK> I noticed that, thanks :)
19:48:35 <diablo_rojo> Trying to leave the ones I think you might have an opinion on.
19:49:05 <mkarray> 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 <diablo_rojo> mkarray, awesome
19:49:44 <SotK> mkarray: thanks for your work!
19:50:05 <diablo_rojo> Yes thank you!
19:50:07 <mkarray> My pleasure :)  You guys have been very helpful
19:50:14 <diablo_rojo> We hope you'll stick around as much as you can
19:50:30 <fungi> your presence has been a huge help, even just answering folks questions in irc
19:50:30 <diablo_rojo> Maybe you can do the next round of outreachy after this summer round?
19:50:37 <diablo_rojo> That too
19:51:29 <SotK> +1, I really appreciate it :)
19:51:32 <mkarray> I'll definitely make the effort to apply, once again I had a great time helping out
19:52:59 <SotK> #topic Open Discussion
19:54:42 * diablo_rojo doesnt have anything
19:55:10 <fungi> yeah, i have to get back to scripting a few thousand git commits for friday
19:56:16 <diablo_rojo> Have fun with that :)
19:57:19 <SotK> heh, sounds exciting
19:57:25 <SotK> thanks for coming folks!
19:57:27 <SotK> #endmeeting