Wednesday, 2014-04-09

*** AaronGr has quit IRC02:46
*** AaronGr has joined #storyboard02:47
*** AaronGr has quit IRC02:48
*** AaronGr has joined #storyboard02:48
*** david-lyle has joined #storyboard03:18
*** cody-somerville has joined #storyboard03:19
*** cody-somerville has quit IRC04:44
*** jcoufal has joined #storyboard07:08
*** che-arne has joined #storyboard07:49
*** hashar has joined #storyboard08:01
*** ilyashakhat has quit IRC08:46
*** ilyashakhat has joined #storyboard08:53
*** david-lyle has quit IRC09:20
openstackgerritNikita Konovalov proposed a change to openstack-infra/storyboard: Hard delete for auth stuff  https://review.openstack.org/8627109:50
*** cody-somerville has joined #storyboard12:45
openstackgerritA change was merged to openstack-infra/storyboard: Missing docstrings added  https://review.openstack.org/8571812:49
*** cody-somerville has quit IRC12:52
*** jcoufal has quit IRC13:59
*** jcoufal has joined #storyboard14:00
*** saju_m has joined #storyboard14:26
*** cody-somerville has joined #storyboard14:53
*** cody-somerville has quit IRC14:53
*** cody-somerville has joined #storyboard14:53
*** david-lyle has joined #storyboard14:55
*** saju_m has quit IRC14:58
*** mfer has joined #storyboard15:03
*** hashar has quit IRC16:09
*** krotscheck has quit IRC17:19
*** krotscheck has joined #storyboard17:22
openstackgerritMichael Krotscheck proposed a change to openstack-infra/storyboard: Changed task states  https://review.openstack.org/8586818:02
*** hashar has joined #storyboard18:02
openstackgerritMichael Krotscheck proposed a change to openstack-infra/storyboard-webclient: Updated UI for tasks status  https://review.openstack.org/8587018:03
*** hashar has quit IRC18:24
openstackgerritA change was merged to openstack-infra/storyboard-webclient: Autoresize-width directive  https://review.openstack.org/8394518:26
*** hashar has joined #storyboard18:58
*** krotscheck has quit IRC19:20
*** openstackgerrit has quit IRC19:34
*** openstackgerrit has joined #storyboard19:42
*** krotscheck has joined #storyboard19:43
krotscheckttx: Are you going to argue with every single proposal that I make?19:57
krotscheckBecause, quite frankly, it’s demotivating.19:57
krotscheckWhy commit code if the only thing I have to look forward is a lengthy verbal battle trying to justify what I’m trying to accomplish.19:58
openstackgerritA change was merged to openstack-infra/storyboard-webclient: Updated UI for tasks status  https://review.openstack.org/8587020:00
*** david_lyle_ has joined #storyboard20:01
*** dklyle has joined #storyboard20:03
*** david-lyle has quit IRC20:04
*** david_lyle_ has quit IRC20:06
*** jcoufal has quit IRC20:13
openstackgerritA change was merged to openstack-infra/storyboard: Changed task states  https://review.openstack.org/8586820:15
*** openstackstatus has quit IRC20:15
*** openstackstatus has joined #storyboard20:16
*** hashar has quit IRC20:21
*** jcoufal has joined #storyboard20:32
ttxkrotscheck: hmm, not sure I follow. The idea behind code review is to discuss the value and correctness of the code being submitted.20:49
ttxkrotscheck: in that precise case you say that 3 years of usage of Launchpad by our community is not a data point20:50
ttxWe had those statuses, and nobody set them. What makes you believe that they would suddenly set those statuses in Storyboard ?20:50
krotscheckIn a nutshell: You frequently conflate feature wants, implementation specifics, and experience with the system that we’re tyring to improve on. You’re not arguing code merit, you’re arguing features.20:51
ttxI'm arguing the design of the solution yes.20:51
krotscheckNow there’s a distinct difference between what you want: Which is 4 specific statuses, and what you actually need -> which is a way to keep track of the current statuses of tasks on a story.20:52
ttxkrotscheck: i'm just saying that extra statuses that are not automatically set are actually less useful than no status at all20:52
ttxbecause of its inaccuracy20:53
ttxyou're arguing that we need extra statuses, even if they won't be set correctly20:53
ttxthat's design, not implementation detail20:54
krotscheckSo if task status is ALWAYS going to be adjusted by a third party, why bother allowing humans to edit htem at all?20:54
krotscheckIn fact, why have storyboard ?20:54
krotscheckIf everything is just going to be automatically update, why not just build a dashboard?20:54
krotscheckIt’s little more than a reporting app at that point.20:54
ttxkrotscheck: because in some cases, we'll track somethign else than code20:55
krotscheckAnd, furthermore, how do you flag a ticket that has a WIP patch?20:55
ttxsome "projects" will end up not being tied to code20:55
krotscheckRight, and the task statuses on those projects are going to be woefully inaccurate, yes?20:56
ttxthey will.20:56
krotscheckSo you’re ok with lack of accuracy in one case, but not in another?20:56
ttxmy -1 was meant to understand where you were going20:56
ttxotherwise I would have set -220:57
krotscheckThe place I’m going is simple: I don’t know if people are going ot use it.20:57
ttxSome projects will be 100% accurate20:57
ttxwith an extra status, none of them will20:57
ttxAnyway, I guess we can try and see20:57
ttxBut if you don't want code reviews, just say it20:57
krotscheckI believe that 100% accuracy on any project is not attainable.20:58
ttxsometimes the code review will question the value of the change proposed20:58
ttxand if you take it personally every time20:58
ttxthat won't fly very well.20:58
krotscheckWell, let’s put it like this.20:59
krotscheckI hate arguing. I like building things.20:59
krotscheckIf i have to spend days arguing about pretty much everything I try to do, it’s demotivating.20:59
krotscheckThe vast majority of what I do is “Hey, let’s see if this works”. That’s the nature of human interfaces, sometimes it’ll work, sometimes it won’t. But you can’t judge the merit of any UI until it’s actually in use by people.21:01
ttxkrotscheck: I just happen to have experience of our community and the systems it uses. I thought there was value in sharing that experience and feeding it back into the solution we design21:01
krotscheckAnd if “inprogress” fails? Great! We can remove it, that’s easy.21:02
krotscheckLesson learned.21:02
*** jeblair has joined #storyboard21:03
*** dklyle is now known as david-lyle21:03
openstackgerritMichael Krotscheck proposed a change to openstack-infra/storyboard: [WIP] Collate story metadata for status  https://review.openstack.org/8645221:13
*** openstackstatus has quit IRC21:14
*** jcoufal has quit IRC21:16
*** openstackstatus has joined #storyboard21:22
*** mfer has quit IRC21:31
krotscheckUgh. I think 95% of my frustration with python is that I don’t know where to look for a the answers.21:41
*** david-lyle has quit IRC22:02
*** openstack has joined #storyboard22:34
krotscheckAnyone with SQLAlchemy clue available for help? I’m trying to model http://paste.openstack.org/show/75457/ as an entity, and I’ve gotten as far as http://paste.openstack.org/show/75455/ , but now it’s throwing this: http://paste.openstack.org/show/75456/23:36

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