19:01:13 <SotK> #startmeeting storyboard
19:01:13 <zara_the_lemur__> aw, that was a good reason to not have a meeting xD
19:01:14 <openstack> Meeting started Wed Jun 28 19:01:13 2017 UTC and is due to finish in 60 minutes.  The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot.
19:01:15 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
19:01:17 <openstack> The meeting name has been set to 'storyboard'
19:01:27 <zara_the_lemur__> they're going to have some long logs...
19:01:45 <SotK> heh
19:01:58 <SotK> somewhere there is an agenda, I am unprepared today
19:02:15 <SotK> #link https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting Agenda
19:02:29 <zara_the_lemur__> :) dw, I'm mainly attending because I feel chatty
19:02:45 <SotK> I don't think we have any announcements or urgent items, so...
19:02:51 <SotK> #topic In Progress Work
19:03:03 <zara_the_lemur__> I fail at review :(
19:03:15 <zara_the_lemur__> I have it on my todo list for tonight
19:03:48 <zara_the_lemur__> I know diablo_rojo sent an update for the branches patch
19:03:51 <zara_the_lemur__> which I have not yet looked at
19:04:01 <zara_the_lemur__> and I have my usual pile of boards patches to look at :)
19:04:33 * SotK intends to write a response to the email from AJaeger tonight, and also look at how much work it will be to provide useful functionality there
19:04:38 <zara_the_lemur__> \o/
19:04:42 <SotK> since I think it will solve some other problems too
19:04:50 <zara_the_lemur__> yeah, 'bug templates', right?
19:04:54 <SotK> indeed
19:05:17 <zara_the_lemur__> I like the idea of it and am not volunteering to do it because I'm already behind with my commitments
19:05:23 <zara_the_lemur__> so I'm pleased that you want to work on it
19:05:33 <SotK> :)
19:06:22 <zara_the_lemur__> (for my own part, I'm not going to look at coding anything until I get more on top of review)
19:06:40 <SotK> (the logic with bug templates being, a similar feature will let people provide links to a pre-filled story submission modal, which is basically a template)
19:06:59 <zara_the_lemur__> yep
19:07:12 <fungi> #link http://lists.openstack.org/pipermail/openstack-dev/2017-June/119016.html Report a bug and storyboard
19:07:22 <zara_the_lemur__> thanks
19:07:25 <SotK> thanks fungi
19:07:38 <fungi> took me a moment to dig it back out of my history
19:09:06 <fungi> thanks for following up there
19:09:43 <zara_the_lemur__> I don't have any other in-progress things to note myself
19:09:47 <SotK> yw :)
19:09:48 <diablo_rojo> Hello
19:09:54 <SotK> hey diablo_rojo
19:09:55 <diablo_rojo> Multitasking
19:10:02 <zara_the_lemur__> hi!
19:10:39 <fungi> a more generalized option might be to allow story creation to take an arbitrary title and description and whatnot provided via get parameters, and just expect the client to get prompted to athenticate to sb via openid first or something
19:11:17 <fungi> but not worry about making it possible to specify arbitrary subfields within the description and just leave that up to the caller
19:12:33 <fungi> granted the templates stuff would be more elegant and reusable within the webui for new story submissions which come in without such prior context
19:13:28 <SotK> yeah, the ability to have reuse there was what I was hoping for
19:13:41 <SotK> though, I see how both approaches could be useful
19:13:53 * SotK may look at both
19:14:02 <persia> Continuing to allow the API to submit arbitrary description content (regardless of subfields), even if the webui allows subfield templating seems safer to me, especially for folk who are already using alternate clients and may be surprised by new validation changes on description input from the API.
19:15:11 <SotK> I wasn't planning on any change to validation, just the ability to pre-fill the description field for folk who use a particular URL to create a story
19:15:28 <SotK> this could have the issue of a bunch of stories with useless content in the description though
19:15:57 <fungi> if people don't edit them before saving, i guess
19:16:29 <persia> That's a natural side effect of the template clients (and has widely been seen in other trackers).  That a later triager could edit it to be less verbose makes this less painful than some systems that hardcode all the possible subfields.
19:17:06 <SotK> yeah, I expect it would be rare, but I can see it not being impossible someone would see the field with words in and be like "oh automatic description, *submit*"
19:19:39 <SotK> anything else in progress?
19:21:07 <SotK> #topic Open Discussion
19:21:09 <diablo_rojo> SotK, just that patch I've had around forever. I updated things. It should be good to go I think..
19:21:33 <SotK> oh yeah, I saw you updated that and was meaning to take a look, thanks!
19:21:56 <diablo_rojo> SotK, thank you!
19:22:26 <diablo_rojo> Stil haven't heard the 'go ahead' from the projects I've reached out to. Kind of waiting to hear back from them currently.
19:23:11 <diablo_rojo> I replied to one email with questions with some help from the wonderful fungi but that's all I've seen.
19:23:42 * zara_the_lemur__ hasn't looked at the etherpads; wonders if there's anything there
19:24:02 * diablo_rojo never had the links to them in the first place
19:24:28 <diablo_rojo> I have been listening in on Tripleo's meetings and answering questions where I can with them
19:24:40 <zara_the_lemur__> iirc someone linked one on the list once, will see if I can dig them up.
19:25:38 <zara_the_lemur__> #link https://etherpad.openstack.org/p/watcher-storyboard
19:26:33 <diablo_rojo> Doesn't look like anything new
19:26:40 <diablo_rojo> Thanks for the link zara_the_lemur__ !
19:27:07 <zara_the_lemur__> yw :)
19:28:14 <zara_the_lemur__> yeah, I see nothing dramatic there
19:28:25 * SotK neither
19:32:50 <SotK> anything else or shall we end this meeting here?
19:33:33 <diablo_rojo> I dont think so but to plead for reviews :)
19:34:14 * SotK will get on it :)
19:34:25 <SotK> #endmeeting