Monday, 2014-11-24

*** MaxV has joined #storyboard01:46
*** MaxV has quit IRC01:51
*** mase_x200 has joined #storyboard02:58
*** MaxV has joined #storyboard02:58
*** MaxV has quit IRC03:02
*** mase_x200 has quit IRC04:03
*** k4n0 has joined #storyboard06:00
*** alexismonville has joined #storyboard07:22
*** mrmartin has joined #storyboard07:38
*** jtomasek has joined #storyboard07:42
*** alexismonville has quit IRC07:43
*** alexismonville has joined #storyboard07:53
*** miqui_ has quit IRC08:05
*** wdutch has joined #storyboard08:06
*** jcoufal has joined #storyboard08:31
*** MaxV has joined #storyboard08:41
*** jedimike has joined #storyboard09:13
*** alexismonville has quit IRC09:13
*** alexismonville has joined #storyboard09:13
*** jcoufal has quit IRC09:51
*** mase_x200 has joined #storyboard10:20
*** mase_x200 has quit IRC10:29
*** mase_x200 has joined #storyboard10:32
*** mase_x200 has quit IRC10:38
*** jcoufal has joined #storyboard10:54
*** petefoth has quit IRC11:01
*** petefoth has joined #storyboard11:05
*** MaxV has quit IRC11:08
*** MaxV has joined #storyboard11:12
*** alexismonville has quit IRC11:20
*** MaxV has quit IRC11:27
*** alexismonville has joined #storyboard11:47
*** mase_x200 has joined #storyboard12:22
*** MaxV has joined #storyboard12:27
*** mase_x200 has quit IRC12:29
*** mase_x200 has joined #storyboard12:30
openstackgerritMerged openstack-infra/storyboard: setup for running as a stand alone application.  https://review.openstack.org/13187012:43
openstackgerritMerged openstack-infra/storyboard: Split Token DB API into separate file  https://review.openstack.org/13440812:50
*** jcoufal_ has joined #storyboard12:51
openstackgerritMerged openstack-infra/storyboard: User token API  https://review.openstack.org/13440912:53
*** jcoufal has quit IRC12:54
*** k4n0 has quit IRC13:00
openstackgerritMerged openstack-infra/storyboard-webclient: Add timeout to the blur event of tag-complete  https://review.openstack.org/13533413:02
*** yolanda has joined #storyboard13:04
openstackgerritMerged openstack-infra/storyboard-webclient: Switched use of "Resource.read()" to "Resource.get()"  https://review.openstack.org/13614813:04
openstackgerritMerged openstack-infra/storyboard: Added project group title to loader.  https://review.openstack.org/13324813:17
*** rainya has quit IRC13:26
*** rainya has joined #storyboard13:27
*** mase_x200 has quit IRC13:36
*** petefoth_ has joined #storyboard14:34
*** petefoth has quit IRC14:35
*** petefoth_ is now known as petefoth14:35
*** mattfarina has joined #storyboard15:52
krotscheckStoryboard meeting in #openstack-meeting-316:00
yolandahi16:00
krotscheckhey hey16:02
krotscheck#openstack-meeting-3 :)16:02
jedimikeello16:09
*** timrc-afk is now known as timrc16:26
openstackgerrityolanda.robla proposed openstack-infra/storyboard: Add API call to return task statuses  https://review.openstack.org/13522116:34
*** mrmartin has quit IRC16:35
*** mrmartin has joined #storyboard16:35
jedimikekrotscheck, hi :) so I've been quite ill recently, but I'm back and ready to aim for storyboard-core status again :D17:01
yolandaagh, i type too slow. Mostly wanted to say that i'm not 100% on the caching solution, but is fine for me as a provisional thing17:01
krotscheckOk!17:01
krotscheckSorry about skipping over that. It’s a seirous topic we actually need to continue discussing and iterating on.17:02
jedimikeno probs17:02
* krotscheck feels sheepish17:02
* krotscheck adds both of those to agenda in case we don’t resovle it next week.17:02
*** MaxV has quit IRC17:02
jedimikefor storyboard, i'd be happy with offset/limit, markers just don't work for apps like storyboard17:03
yolandajedimike, krotscheck, i'd like to see some progressive loading in storyboard17:04
krotscheckjedimike: I agree.17:04
yolandascrolling down and new stories and tasks are shown17:04
jedimikeyolanda, me too17:04
krotscheckyolanda: That’s a very controversial UI topic ;)17:04
krotscheckSome people love it, some hate it.17:04
krotscheckAlso, how would that work in our multifactor search results?17:05
*** MaxV has joined #storyboard17:05
yolandai deffinitely love it17:05
krotscheckNot saying it’s a bad thing. Just want to make sure it’s thought through.17:05
yolandanothing really urgent and needed but a nice feature17:05
jedimikei love it when it's done properly, that is, clicking back from a story page to the list page returns you to where you were and doesn't make you scroll down from the beginning again17:05
yolandaoh yes, of course17:06
krotscheckWell, the first step for that is for search results to be persisted.17:06
krotscheckSorry17:06
krotscheckSearch _criteria_ to be persisted.17:06
krotscheckAnd for them to work in the history properly we should encode them in the URL17:06
yolandabtw, krotscheck, thx for raising the topic of cores, i'll talk with the other core members about it17:06
jedimikehaha my thread has infected your search results thinking :)17:06
krotscheckyolanda: Of course!17:07
jedimikeyes, encoded in the url sounds right17:07
yolandaencoded urls can be very ugly, maybe something like short urls?17:07
*** wdutch has quit IRC17:08
jedimikehmmm, i'm not keen on that17:09
jedimikeyes, all the info in the url is ugly17:09
jedimikebut easy to consume17:09
jedimikeand search urls *are* ugly anyway17:09
jedimikewhen you're searching with different criteria, sort orders, etc.17:09
yolandabut depending on all the parameters you need to encode the url can be very long and nasty17:10
jedimikeyes17:10
yolandakrotscheck, jedimike , btw, i'm seeing a strange behaviour sometimes in storyboard17:11
yolandawhen i open the page for first time17:11
yolandain the login placeholder there is a loading that never disappears17:11
jedimikeif we do some kind of shortening, we end up having to implement our own url shortnening service and do all the housekeeping associated with that :)17:11
yolandaif i reload it, then the real "Login" text appears17:12
yolandadoes it happen to you?17:12
krotscheckyolanda: Yep17:12
krotscheckyolanda: I have two suspicions there.17:12
jedimikeyolanda, yep17:12
krotscheckyolanda: One is that all of our timestamps from the server come back without a timezone, which according to the RFC means it should be interpreted as local timezone.17:13
krotscheckAnd since the issuance dates are in UTC, that means the dates are misinterpreted.17:13
krotscheckOn top of that, I think the refresh token acquisition logic is just plain borked for some reason.17:13
jedimikeyolanda, heh, you just made pretty much the same comment as me on the story type spec :)17:14
yolandajedimike, thinking in the usage we would do in storyboard internally, for example17:14
jedimikeexactly17:15
jedimikeit would mean we couldn't target a story at enterprise edition17:15
yolandayes, that's it17:15
yolandai didn't refer the specific case, but yes, targetting a different workflow than the openstack one will be difficult with that spec17:15
jedimikeand I'd really not want the implementation to be "special" tags :)17:16
yolandahaving the ability to define a real workflow for the story type, and allow it to be configurable, will be great17:18
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard-webclient: Enable HTTP Caching on resources.  https://review.openstack.org/13614917:18
jedimikeyolanda, yeah, we need some kind of workflow for stories that are under discussion or ready to be worked on too. I find it difficult to work out what's ready to be worked on and what's not.17:20
yolandajedimike, even having something like "story status" ?17:22
jedimikeyeah17:22
yolandawe have task status, but not stories17:22
yolandakrotscheck, in launchpad when someone files a bug, there is a Pending or To be confirmed, then also if more people raise it, it's set to Confirmed17:22
jedimikeyeah, so I started work on a task that was marked "To do" on a story that was marked "Active"17:22
yolandathen a member of the community can change the status... is quite useful17:23
jedimiketurns out, the task wasn't supposed to be done and the story was under discussion17:23
jedimikeso on a story, "proposed", "accepted", "rejected" would be good. Any changes to the tasks would put it back to "proposed"17:23
jedimikeor something like that, it's a rough idea17:23
yolandajedimike, krotscheck, yes, now anyone can file a story, even a dupe (i raised a task about it), but a developer doesn't know if that's  a todo, it's an opinion...17:24
jedimikeyeah, so a few times I've gone to see what needs to be done and not been able to tell17:24
jedimikeor spent my time working on the wrong thing17:24
yolandayes, what i normally do is I bug krotscheck about that :)17:25
yolandahe is the story status teller :)17:25
krotscheckYerah, but I shouldn’t be.17:25
yolandai thought sometimes that the priority and status would be better apply to the story than to the task17:32
jedimikeyolanda, yeah I agree, although we could both them on both, not having them on the story makes it difficult to find what needs doing next17:33
* krotscheck pings ttx and gothicmindfood as they’ve got opinions on these things.17:36
krotscheckalso wendar17:36
yolandaleaving for today, staying with my children, it's a local holiday heer17:40
yolandahere17:40
krotscheckkk17:42
krotscheckI’m off to take a shower and commute.17:42
paulsher1oodfwiw we've been kicking around having a kanban view onto storyboard, to help with visualisation of what needs doing next. there's some tension between the fixed states of storyboard, and the varied states that discussions/work might go through in general before it hits code/git17:49
paulsher1oodfor example our default kanban has 'wishlist', 'todo', 'doing', 'review', 'done'... but we also sometimes use a whole triage board before that with 'incoming' 'needs clarification' 'can wait' 'prioritize' as lanes17:51
paulsher1oodideally at least some states would be customizable to fit the workflow for a specific situation. but i don't know how that could play nicely with storyboard's git/test/merge workflow etc17:54
krotscheckpaulsher1ood: yolanda is actually working on making task statuses configurable. That’s a first step :)18:06
krotscheckjedimike: Good catch on the caching.18:06
krotscheckTurns out the default angularjs cache does not do that :/18:06
jedimikereally? :(18:07
jedimikei thought it could... maybe the example i was looking at was wrong18:07
jedimikeah18:08
jedimikekrotscheck, i suppose using http://jmdobry.github.io/angular-cache/ which can do it, would be a bit overkill for a temporary solution? although it depends how long this is going to be temporary i guess18:09
krotscheckjedimike: I didn’t check the timestamp on the blog post I read.18:09
krotscheckBut yeah, that’s also an option.18:09
jedimikekrotscheck, now I look at the code, it was using ^^ (doh!)18:10
jedimikeand these things tend to be much less temporary than we think, from my experience ;)18:12
*** MaxV has quit IRC18:27
krotscheckPoint18:50
krotscheckWait, it’s using angular cache?18:50
* krotscheck is confused.18:50
jedimikehttp://jmdobry.github.io/angular-cache/ is a replacement for angular's... cache18:50
jedimikewonderfully named isn't it18:50
jedimikeso angular-cache has features that angular's cache doesn't18:50
krotscheckjedimike: Oh right. And it’s a prerequisite for angualr-data, which we’re considering as well.18:52
jedimikecool18:52
* krotscheck checks to see how easy just adding that to the patch would be.18:52
krotscheckOh man, that vagrant patch of mine makes my life SO MUCH EASIER18:53
jedimike:) vagrant rocks18:54
*** jcoufal_ has quit IRC19:15
*** MaxV has joined #storyboard19:16
*** gothicmindfood has quit IRC19:19
*** gothicmindfood has joined #storyboard19:21
*** timrc is now known as timrc-afk19:26
*** mrmartin has quit IRC19:47
krotscheckjedimike: Turns out angular cache is basically just a drop in.19:56
jedimikeawesome :)19:57
krotscheckjedimike: It appears that it doesn’t check with the max age header though.19:57
krotscheckjedimike: But I’m kindof ok with that.19:57
jedimikethat's something we'd need to think about when we move away from the interim solution, so i guess we could contribute that back then?19:58
krotscheckjedimike: SInce the original problem is to prevent the application form doing massive re-requests on a single page, we can actually set the max age manually to something fairly small, like a minute.19:58
jedimikeyeah19:58
krotscheckAnd that seems to work pretty well.19:58
krotscheckMy original code still updates the cache with the value returned from POST/PUT/DELETE, which is nice.19:59
krotscheckBut this also gives us finder control on the cache itsle.f19:59
*** MaxV has quit IRC19:59
jedimikethat's good, yep :) I look forward to more long winded threads about caching when the time comes, that's another thing I've done for large companies who had strict requirements... :)19:59
krotscheckAnd, well, I kindof feel that if we’re going to start doing caching based on HTTP headers, that level of integration is going to be on-par with also doing periodic HEAD requests, so we can do all that work at once.20:00
* jedimike nods20:00
jedimikeI designed the caching structure for a CMS used by a UK television station some years back20:01
krotscheckWhoa. We can actually have Angular-cache re-request a resource on expire.20:04
krotscheckBy which I mean we can add an expiration handler, which can do anything, including refreshing the value in cache.20:05
* krotscheck wonders if that’s something we want. Seems like it might be a ram problem.20:05
jedimikemaybe for certain pages?20:06
jedimikehmmm20:07
krotscheckYeah, it’s also got a backend storage mechanism.20:07
*** MaxV has joined #storyboard20:07
krotscheckSo if we ever want to roll a mobile native app, we can have the cache act like a local persistence layer.20:08
krotscheckAnyway, taht’s beside the point right now.20:08
* krotscheck goes back to just adding a cache with a max age.20:09
jedimikehehe20:09
*** ilyashakhat has quit IRC20:21
*** ilyashakhat has joined #storyboard20:22
paulsher1oodkrotscheck: thanks for the headsup. i'll watch for that20:25
*** jedimike has quit IRC20:41
*** MaxV has quit IRC21:00
*** jtomasek has quit IRC22:00
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard-webclient: Enable HTTP Caching on resources.  https://review.openstack.org/13614922:10
*** jtomasek has joined #storyboard22:11
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard-webclient: Enable HTTP Caching on resources.  https://review.openstack.org/13614922:12
*** mattfarina has quit IRC22:12
*** jtomasek has quit IRC22:24
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Plugins may now register cron workers.  https://review.openstack.org/12960922:36
krotscheckNikitaKonovalov, SergeyLukjanov: Comments for both of you on https://review.openstack.org/#/c/129609/22:36
openstackgerritMichael Krotscheck proposed openstack-infra/storyboard: Plugins may now register cron workers.  https://review.openstack.org/12960922:40
*** MaxV has joined #storyboard23:24
*** MaxV has quit IRC23:39
*** MaxV has joined #storyboard23:50

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!