| *** cody-somerville has quit IRC | 05:27 | |
| *** cody-somerville has joined #storyboard | 05:43 | |
| Zara | morning, storyboard! | 10:26 |
|---|---|---|
| pedroalvarez | o/ | 10:31 |
| * pedroalvarez is starting to dislike storyboard dependency on mysql | 10:43 | |
| pedroalvarez | :( | 10:43 |
| pedroalvarez | latest mariadb seems to support what storyboard needs, but the version check from the alembic migration script don't work | 10:45 |
| pedroalvarez | I guess it would be possible to check also for maria db versions | 10:46 |
| pedroalvarez | I wonder if a good solution would be to ask forgiveness instead of asking permission in the scripts | 10:49 |
| persia | Or to ask in -infra if anyone has a good reason not to support mariadb | 10:56 |
| * persia remembers some old ML threads about mariadb, but not the conclusions | 10:56 | |
| Zara | yeah, I've assumed that mysql was chosen to ensure that things fit in with the rest of openstack, but it sounds like it doesn't need to be a dependency... it may be that people don't want to commit to supporting too many things. | 11:03 |
| Zara | there were some comments in infra yesterday along those lines (someone was asking about postgresql) | 11:05 |
| * paulsherwood wants postgresql too | 11:05 | |
| persia | One of the points of the postgresql discussion yesterday was that it was impolitic to speak of "hating", "killing" or "stabbing" postgresql. | 11:06 |
| persia | There seemed no objection to dropping yet more support for it. | 11:06 |
| Zara | I was referring to the discussion that starts around here: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2015-11-17.log.html#t2015-11-17T18:42:47 | 11:08 |
| Zara | though I'm not sure how much refers to the specific project and how much to infra in general | 11:09 |
| * paulsherwood thought postgresql to be less 'hated' than other solns in general | 11:11 | |
| persia | Zara: Yes, it started from SpamapS at 18:40. | 11:13 |
| persia | paulsherwood: Very much not: the problem is that supporting more than one thing is hard, from a testing/gating perspective. mysql was the original default, and remains the default, so all !mysql suffers and is irritating to developers. | 11:14 |
| pedroalvarez | it is indeed irritating me | 11:27 |
| paulsherwood | pedroalvarez: postgres? how? | 11:29 |
| * persia read that as !mysql being irritating, rather than specifically postgres | 11:30 | |
| pedroalvarez | the lack of support for !mysql | 11:30 |
| paulsherwood | pedroalvarez: let's add pg to sb, then :) | 11:54 |
| pedroalvarez | heh :) | 11:55 |
| pedroalvarez | given that my infra is using a mariadb instance, I don't really want to go that way | 11:55 |
| paulsherwood | ack | 11:55 |
| pedroalvarez | in other news, storyboard doesn't quite work with openstackid | 11:57 |
| pedroalvarez | although I guess I'm not configuring it properly | 11:58 |
| Zara | following questions in another channel, here are some general links to useful storyboard resources: | 12:47 |
| Zara | developer docs: http://docs.openstack.org/infra/storyboard/ | 12:47 |
| Zara | wiki: https://wiki.openstack.org/wiki/StoryBoard | 12:47 |
| Zara | github mirror for the api (I just find things easier to read on github): https://github.com/openstack-infra/storyboard | 12:48 |
| Zara | and the webclient: https://github.com/openstack-infra/storyboard-webclient | 12:49 |
| Zara | the api is the python backend stuff; the webclient is the angularjs browser UX stuff. (I didn't realise that when I first came to this project, so might as well mention it) | 12:50 |
| Zara | api story list here: https://storyboard.openstack.org/#!/project/456 | 12:51 |
| Zara | webclient story list here: https://storyboard.openstack.org/#!/project/457 | 12:51 |
| Zara | if anything is out of date in the docs, please flag it up (or better, send a patch! :)) | 12:52 |
| Zara | and a repeat of the list of patches waiting for review: https://review.openstack.org/#/q/status:open+(project:openstack-infra/storyboard+OR+project:openstack-infra/storyboard-webclient)+-owner:self+(-label:Code-Review%3D2%2Cuser%3Dself+AND+-label:Code-Review%3D1%2Cuser%3Dself)++label:Verified%3D1,n,z | 12:54 |
| Zara | hm, the link breaks in my terminal, but copy and paste should still work | 12:55 |
| Zara | there are some specs here: https://github.com/openstack-infra/infra-specs/tree/master/specs | 12:56 |
| Zara | (and also some in the corresponding gerrit project, but some of those may be out of date by now; they've been waiting a while.) | 12:57 |
| Zara | let me know if there's anything else! :) | 12:57 |
| betherly | great thanks Zara | 12:58 |
| Zara | and now I'll try and sort out an agenda for today's meeting... | 12:59 |
| betherly | :) | 12:59 |
| Zara | what used to happen was that we would do all the discussion in this channel over the week, and the meeting would end up just being a summary, but this channel has been much busier since the summit! | 13:07 |
| Zara | So I think we'll start using the meeting more as a place to decide things as time goes on. | 13:08 |
| *** openstackgerrit has quit IRC | 14:31 | |
| *** openstackgerrit has joined #storyboard | 14:32 | |
| Zara | meeting in ten! | 14:50 |
| Zara | meeting in #openstack-meeting btw | 15:01 |
| Zara | it has just occured to me that I set the topics all wrong | 15:43 |
| Zara | should make the logs interesting | 15:43 |
| Zara | oh no, I think it worked | 15:44 |
| Zara | cool | 15:44 |
| betherly | thanks for leading the meeting Zara it was great | 15:44 |
| Zara | aw, thanks! :) | 15:44 |
| Zara | I should probably learn how to delete actions in future, though... | 15:45 |
| Zara | right, priority features | 15:45 |
| Zara | should we discuss it now or would another time suit people better? (if so, when?) | 15:45 |
| betherly | now works for me for about 30mins | 15:46 |
| Zara | okay, great | 15:46 |
| Zara | so priority number 1 has to be email notifications | 15:46 |
| Zara | we've got as far as patches to say '$subscribedresource was updated' | 15:47 |
| Zara | so once those are merged | 15:47 |
| betherly | can we narrow that even further. ie subpoinnts | 15:47 |
| betherly | ie what does that involve work wise and what will we include feature wise | 15:47 |
| Zara | yeah, was about to say, we can stop at that point if something else seems like a better priority, or we can continue to refine them-- where those questions come in | 15:48 |
| betherly | :) | 15:48 |
| Zara | this is the patch where the discussion heads toward that: https://review.openstack.org/#/c/240346/ | 15:49 |
| Zara | So, re: refining or moving on-- I'm not sure there's anything that's ready to move on to. My gut feeling is that this affects people more than any bugs in search. | 15:54 |
| persia | Lack of subscription makes it not worthwhile to put anything in storyboard: you can't have a conversation, and your stories get lost. | 15:55 |
| Zara | or at least it will, once it's merged and people start getting lots of emails-- and for as long as it isn't merged, nobody can use storyboard to track tasks without putting in a *lot* of effort. | 15:55 |
| persia | With subscription, search isn't important for any story you are already following (because you have notifications), and it encourages folk to share story URLs to others so they can subscribe. | 15:56 |
| Zara | we should distinguish between subscriptions themselves and notifications when things happen to subscribed resources | 15:56 |
| Zara | subscriptions are up. | 15:56 |
| Zara | notifications do come up in recent events | 15:57 |
| Zara | email notifications aren't up yet. | 15:57 |
| Zara | and I think the notifications that come up in 'recent events' don't apply to every change one can make to the subscribed resource | 15:59 |
| Zara | I'm wondering if we should say that 'notification' is the main thing to focus on, or if we're best just looking at emails specifically | 15:59 |
| Zara | I think the goal matters more and we'd be better off looking at notification in general. | 16:00 |
| Zara | (I think this is currently recent events on the dashboard and email notifications) | 16:02 |
| *** wuhg has quit IRC | 16:11 | |
| Zara | so my vague map for notifications would be: 1) email notifications when subscribed resources update-- these should be configurable to avoid spam (configuration options need to be decided). 2) recent events should update in a useful way when subscribed resources update (this needs fleshing out-- what time period is 'recent'? (ie: how long should an event display for? presumably we want multiple events to display... under what conditions | 16:12 |
| Zara | I suspect the code for these is quite entwined atm. | 16:12 |
| Zara | lots of brackets because I am a terrible person | 16:13 |
| Zara | I don't know where to start with configuration options for emails, but it seems like the sensible place to start. | 16:14 |
| Zara | I suppose we would need to decide what got configured, make the filters functional, and have a way for a user to choose them. | 16:15 |
| betherly | sorry for disappearing for a while there | 16:16 |
| Zara | as far as the last point goes, there's already a 'preferences' area in the UX for timeline events, so that seems like the place to put the options. | 16:16 |
| Zara | no worries | 16:16 |
| Zara | I just rambled | 16:16 |
| betherly | that all seems good to me tbh | 16:16 |
| betherly | do you want to write that up in an etherpad or something? | 16:17 |
| persia | Let's use the StoryBoard wiki. | 16:17 |
| betherly | ah yes sorry persia you mentioned that earlier my bad | 16:17 |
| betherly | #memoryissues #oldbeforemytime | 16:18 |
| persia | betherly: No worries: I just find the proliferation of etherpads increasingly hard to follow :) | 16:18 |
| persia | They are great for live sessions because it supports multiple simultaneous edits better, but less ideal for longer-lived things. | 16:18 |
| Zara | heh, I was just working things out on paper (well, irc) but recording it will stop things from getting lost in the meantime | 16:18 |
| betherly | yep :) | 16:19 |
| Zara | I work things out by discussing them with myself at length on irc and distracting everyone, it's great | 16:19 |
| betherly | haha :D | 16:20 |
| Zara | is this enough to be getting on with, or is it worth rambling some more before we put it up? | 16:21 |
| persia | I think that's enough for notifications. | 16:23 |
| persia | I also want tags to work: the mess a few days ago when a tag was added making the story unreadable was very unfortunate. Even if tags don't work right, making them not dangerous would be good. | 16:24 |
| Zara | okay, I think we'll find the first step to getting there (re: notifications) is to work out how timeline events currently work, where they intersect with email notifications atm. | 16:24 |
| Zara | persia: I agree with you but I can't focus on lots of things at a time. so if I look at making tags not-dangerous, I can't look at notifications. | 16:26 |
| Zara | so deciding on a priority between those two things would be good, or allocating different people to different areas. | 16:27 |
| persia | Fair. Go with proximate objectives :) | 16:27 |
| Zara | this is the whole trouble, hahaha. everything needs doing! :) | 16:28 |
| Zara | worklists and boards work will still be ongoing in the background, but the requirements are relatively clear so I'm less concerned about that. | 16:30 |
| Zara | ideally I'd love to have everyone focussed on one feature at a time, together, but I think that's unrealistic. | 16:30 |
| persia | Everyone does things for their own motivations, but yes, alignment can help make milestones get hit faster. | 16:33 |
| * Zara wonders where to put discussion so far on the wiki | 16:34 | |
| Zara | there's a roadmap but it's very longterm and high-level | 16:34 |
| Zara | (eg: 'feature: tags' | 16:34 |
| Zara | notifications were listed under 'final polish' in there. | 16:36 |
| Zara | that also maps changes to versions of storyboard, so we should probably get back to versioning it (I think that got lost) | 16:36 |
| persia | Just rearrange the page to map more closely to reality | 16:37 |
| persia | And put the details either as sub-points or on detail pages. | 16:37 |
| Zara | okay, I've started by putting hte irc conversation so far into other docs/notifications so we don't lose it | 16:40 |
| Zara | I should be able to work it into something resembling a spec. | 16:40 |
| persia | Don't forget the potential to link to eavesdrop :) | 16:41 |
| Zara | one reason I haven't altered the roadmap so far is that it's a good source of 'who knows about what' (eg: it suggests that Nikita knows about tags) | 16:42 |
| Zara | it's possible he might be able to help with a quick fix there where none of the rest of us could. | 16:43 |
| persia | 1) Wikis have history, 2) it may be useful to encode that information in a different way anyway | 16:43 |
| *** jtomasek has quit IRC | 20:12 | |
| *** openstack has joined #storyboard | 21:04 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!