19:22:08 #startmeeting storyboard 19:22:09 Meeting started Wed May 29 19:22:08 2019 UTC and is due to finish in 60 minutes. The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:22:10 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:22:12 The meeting name has been set to 'storyboard' 19:22:20 o/ 19:22:26 #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda 19:22:55 #topic Announcements 19:23:07 any announcements that aren't agenda'd? 19:24:12 fungi test migrated swift? 19:24:19 But that kinda goes in the next topic 19:24:21 not sure if that's an announcement 19:24:33 #topic Migration Updates 19:24:36 there :) 19:24:54 fungi test migrated swift 19:25:12 finished fine once it was finally working? 19:25:36 yeah, the only revelation is that the import script is now py3k-only 19:26:19 so if we want to use the natively-installed copy i need to rebuild the servers with sb installed via python3 19:26:41 that's somewhat my fault, I thought we were already using python 3.x on our servers when I approved the patch which caused it 19:26:57 related, the lp blueprint import feature from our ndsu capstone interns got tested and some improvements, but is still in need of additional love before it's usable 19:27:29 I'm a bit surprised that https://review.opendev.org/#/c/660701/ didn't do anything to help though 19:28:40 possible that was a problem with a transitive dependency, would need to revisit diablo_rojo_phon's traceback 19:29:14 i've already paged out that problem and assumed we should be planning to redo the servers with python3 anyway 19:29:44 yeah it would be nice to be using python 3 I think 19:30:12 is someone planning to finish off that blueprint patch or is it waiting for anyone with a bit of time? 19:30:35 i think it's waiting for someone with a bit more time than i had on hand, though hogepodge may have ideas 19:30:46 Anyone with a bit of time. 19:31:11 i tried to leave a fairly explicit checklist of what it still needs in the comments 19:31:21 in review comments i mean, not code comments 19:31:53 Much appreciated :) 19:32:47 thanks for that, hopefully someone will have time soonish 19:33:12 It's on my radar but if someone else gets there first I won't be offended ;) 19:33:31 probably the hardest bit will be the idempotency problem 19:33:53 that will need some design work to figure out how to be able to tell whether a bp has already been imported 19:34:21 Yeah. Some sort of check it's not already there. 19:34:24 the rest of the problems with it are probably fairly easy to solve 19:34:36 well, how to tell whether it's already there is the hard part 19:35:16 for imported bugs we just update the story number matching the bug number. there is no similar unique number for an lp blueprint 19:35:40 maybe doing something like adding an html comment to the description of the story that we can then filter by to check would be good enough 19:35:52 There aren't any ids? 19:36:03 so we need to pick a unique identifier (perhaps part of the bp url?) and then embed that somewhere we can query for (description, initial task name, comment, something) 19:36:04 assuming we don't really want something more user-visible like tagging the story 19:36:45 yeah, the path part of the url sounds sensible to me if its unique 19:37:01 and in a comment is probably the best place, since that way its hard for folk to accidentally get rid of it 19:38:46 though one of my other suggestions was to note in the description that it was imported from a lp blueprint so we could maybe just have that also be the way we check to find one which was previously imported but... would require a subtext match on the description which could be costly... then again, the number of them being imported is probably not that great and it's an infrequent performance hit 19:39:09 ahh, yeah comment might make it easier since we could do an exact text match 19:39:23 no sibstring/wildcard mess 19:39:30 Yeah comment makes sense to me 19:39:30 er, substring 19:39:52 Haha and you have a full size keyboard ;) 19:40:13 but terrible inaccurate fingers 19:41:23 anything more about migration? 19:42:06 nope! 19:42:13 #topic Releasing 19:42:34 so we had a chat about doing a release at the PTG 19:42:54 I think it'd be nice to start doing some 19:43:01 sounds great 19:43:28 right now anyone in https://review.opendev.org/#/admin/groups/storyboard-release can push tags to the repo in gerrit 19:43:45 which is kinda sparse (only has the infra-core team as included) 19:44:39 #link https://review.opendev.org/#/admin/groups/storyboard-release release team 19:45:13 we have some basic instructions on how to create and push a tag to gerrit... 19:45:23 #link https://docs.openstack.org/infra/manual/drivers.html#tagging-a-release Tagging a release in OpenDev 19:46:08 probably want to make sure we include the publish-to-pypi template in our zuul config 19:46:20 (per the first note in that manual section) 19:46:47 anyway, i'm happy to push releases or to add someone to the storyboard-release team who wants to give it a go 19:47:10 hardest part will be... deciding on version numbers ;) 19:48:00 there's also a minor complication in that `storyboard` is the name of someone else's project on pypi, so we need to change our dist name 19:48:13 yeah, i saw a change up for review to do that 19:48:37 #link https://review.opendev.org/#/c/661663/ Change for updating the dist name 19:49:02 #link https://pypi.org/project/storyboard/ someone else's project 19:49:24 I might want to bikeshed on the name a little though, as well as version numbers 19:49:32 I think it's like.. not been used in like two years? 19:49:42 We were gonna try to get the name from them I think? 19:50:22 diablo_rojo_phon: yeah, but someone could be pip installing it for something else 19:50:24 I dont remember what exactly we said at the PTG 19:50:30 That's fair. 19:50:34 according to that patch they still want to use it 19:50:39 I feel like we came up with a backup name. 19:50:52 Opende-storyboard or something 19:51:06 Opendev-storyboard 19:51:07 yeah, the patch changes it to opendev-storyboard 19:51:17 Yeah that's fine with me. 19:51:42 looks like sboard is available if we want something shorter 19:52:10 SB? 19:52:41 sb is squatted, we *might* be able to convnice teh warehouse maintainers to hand it over to us 19:52:56 That would be pretty cool 19:53:09 But I'm also fine with opendev-storyboard 19:53:17 ahh, actually no it has a release 19:53:29 described as "a simple printer of neaster lists" 19:53:40 Booo 19:53:55 * SotK has also briefly considered its-storyboard like the name of our gerrit plugin, but that could get confusing 19:54:15 we could also rename the project... drastic ;) 19:54:30 Please no 19:54:33 Lol 19:54:40 boarystord 19:55:18 also, we're about to the end of the meeting slot and still have stuff on the agenda 19:55:22 Boarttysword 19:55:29 the next topic looks important 19:55:34 indeed 19:55:48 #topic Outreachy 19:55:59 we got an intern! 19:56:11 * fungi cheers inaudibly on the other end of the internet 19:57:03 Yay! 19:57:08 We even talked to her today. 19:57:36 i guess ankita isn't on irc at the moment, but... welcome anyway ankita! 19:58:29 indeed, welcome! 19:58:42 \o/ 19:59:05 #info Welcome to our Outreachy intern, Ankita! 19:59:50 and we're about out of time, sorry for the late start 20:00:04 thanks for coming folks 20:00:06 #endmeeting