Friday, 2016-08-12

*** alexismonville has quit IRC00:28
*** davidlenwell has quit IRC00:53
*** davidlenwell has joined #storyboard01:05
*** alexismonville has joined #storyboard01:16
*** alexismonville has quit IRC01:52
*** betherly has quit IRC02:55
*** francoblanco has quit IRC02:55
*** betherly has joined #storyboard02:59
*** francoblanco has joined #storyboard02:59
*** matthewbodkin has joined #storyboard07:52
*** mrmartin has joined #storyboard07:54
openstackgerritMatthew Bodkin proposed openstack-infra/storyboard-webclient: Tweak to the StoryBoard 'about' page Show where to file UX bugs with link Show where to file bugs in the API with link Make obvious what 'task tracking' includes Make clear that the user needs to login to be able to edit Grammar fix  https://review.openstack.org/35457008:08
*** mrmartin has quit IRC08:18
*** carl_baldwin_ has joined #storyboard08:31
*** carl_baldwin has quit IRC08:35
*** carl_baldwin_ is now known as carl_baldwin08:35
*** jamesmcarthur_ has joined #storyboard08:35
*** jamesmcarthur has quit IRC08:38
*** jamesmcarthur_ is now known as jamesmcarthur08:38
Zaraoh yeah, admin user pagination10:22
Zarawas the bug10:22
ZaraI was going to look at...10:23
matthewbodkinCan anybody give me any idea as to how I should rephrase/change/add to this sentence in the 'Why?' section of the about page...11:05
matthewbodkin'The OpenStack project has run into a number of limitations with existing tools; in particular, the workflow needed by a highly-distributed system that spans multiple projects is not well served.  This system uses the best concepts from existing tools and goes beyond to support the needs of the OpenStack project.'11:05
matthewbodkinAs Zara said, it's basically just a bunch of marketing rubbish at the moment :|11:06
Zara(see https://review.openstack.org/#/c/354570/1/src/app/pages/template/about.html.tpl@64 for context)11:08
matthewbodkinI know its a minefield but any help in the slightest would be much appreciated and it would help to get a more rounded view of what people think it should say11:08
ZaraI've procrastinated from rephrasing that since it's not that straightforward, so I'm fine for deferring 'til later, otherwise I'll look after I've tried this admin users bugfix.11:09
Zarathough, anyone else, feel free to dive in. (and thanks for asking over here! :D)11:10
matthewbodkinIts fine there's no rush, at least it's a simple fix of English grammar and not some coding mumbo jumbo11:10
Zarabe warned that one day, 'bikeshed' will read primarily as a verb, and then you'll long to code. :P11:16
persiaI suppose we have reached the point where we can no longer delay rewriting that.11:22
Zarathe main problems with it are vagueness/very little content, complex sentence structure. so probably the best general approach is to list things we do better (cross-project support, could link to diagram; RESTy API...) and if it turns out we've already covered everything, maybe we don't need that and it's self-explanatory11:27
Zaras/,/ and/11:27
persiaErr, no.11:28
*** alexismonville has joined #storyboard11:30
persiaThe main issues with it are that it frames the creation in terms of negative impressions of another project (now, thankfully, unnamed), and asserts it is openstack-specific, when for most of the development period, it was either not used by OpenStack (the first year), or not developed by OpenStack (most of the second year), although it is happily both used by and developed by OpenStack now.11:30
* persia has been procrastinating rewriting that text for a very long time, and will stop doing so.11:31
Zarathose are issues with it too; I don't think they're the biggest ones for most users, but we can disagree on that if you want.11:31
persiaHeh, I think most users ignore that section entirely, and that there are lots of different viewpoints here :)11:32
matthewbodkinAlso another thing, 'You can easily track backports of bugs to a specific branch'. This isn't true yet as the feature is only partially implemented. Would everybody suggest that I just delete this sentence as it is misleading?11:32
Zarapersia: agreed. I think people who do see it read it once, when first browsing to it, then never again, so I don't want anything on there that makes storyboard look more complicated than it is and makes them think 'no thanks, I'll stick to $closed_source_task_tracker'.11:34
persiamatthewbodkin: That feature is completely implemented in the API, just not exposed in the UI.  I'm happy with removing that clause if you think it makes it clearer, but I'd also be happy if it worked.11:35
persiaZara: Yep.  I shall strive for simplicity.11:35
matthewbodkinI agree with that, we want it to be simple, informative and possibly inviting11:35
Zaraalso, I'm not sure it's completely implemented in the API; I haven't tried creating a story against a branch other than master except through the ui accidentally, where I got an error that looked more like an api error (though could just be bitrot)11:36
Zaracreating branches other than master and linking them to projects works11:37
persiaAs I look at this page again, I wonder if there should be a "Worklists & Boards" section, pointing at the (upcoming) worklists & boards page.11:37
matthewbodkinI'll let you two argue over that one haha just as long as I know whether everybody is agreed on removing, changing or keeping it11:38
persiaBut that can wait until the navigation is present, the complex prioritisation works, and other things.11:38
matthewbodkinOkay I'll leave that out for now and just stick with what we've got11:39
Zarapersia: yeah. Ideally I want the whole page to display sans scroll (just arbitrarily as a way of identifying ETOOLONG), so we'll have to see what we can cut. but I think I could cut many sentences in half if pushed.11:40
* persia is really happy 7d38a86af2f8e388d7d4e33fd2c9305757922c45 landed to make this less unpleasant11:41
Zaratried searching that, not indexed in the googles11:43
persiaLooking at it in context, rather than having the first-draft text glowing behind my eyes as I try to sleep, I wonder if the README link could be moved to Contributing (as README links to the developer manual), and the "But Why" section just replaced with some other feature outline.11:43
persiaZara: It changed a diatribe against LP into the current text.11:43
Zaraah, right11:43
Zara+ I think sotk said that on the patch review11:43
Zaraso you may want to head over there :D11:44
persiawhich patch?11:44
ZaraI linked it for context earlier, hang on11:44
persia354570?11:44
Zarahttps://review.openstack.org/#/c/354570/11:44
Zarahah11:44
Zaragerrit took a while11:44
Zarayes11:44
persiaI used IRC logs :p11:45
Zarahahahaha I already had the tab, just wanted to link to the review rather than the specific line and I decided it'd be quicker to browse and copy then to shorten the url manually11:46
Zarait was a catastrophic failure and it shall be recorded forever11:46
* persia hugs eavesdrop11:46
Zarabut yeah, list of things we do better is my preferred approach (obviously not namecalling projects, though)11:47
ZaraIT IS WINDY TODAY11:47
Zaraand I still haven't done this pagination fix11:47
persiaBut, no, I don't see the thing I'm saying.11:47
* Zara turns into a submarine11:48
persiaI see complaints about introducing more OpenStack-specific language, and about providing links to filing bugs against OpenStack in the section on stories.11:48
persiamatthewbodkin: My recommendation is to not change the "But Why?" and "Contributing" sections.  I'll put something together today (or this weekend, if that fails), so that I end up getting the flames with`git annotate`11:51
Zaraoh, might be slightly different, he referred to moving something to 'contributing'11:51
persiaZara: Indeed: that was from the "Stories" section.11:51
persiaAnd I think it falls under the "adding too much text that belongs in README", mostly.11:52
*** matthewbodkin has quit IRC11:54
persiaErr, I didn't mean to scare him away :(11:55
ZaraI think his freenode connection is patchy, probably just means he's gone to have lunch11:56
bethwhiteHeh, it looks like he's gone for lunch, persia11:56
bethwhiteSnap Zara11:56
Zara:)11:56
persiaSo, I think this is best done in two batches.11:57
persia1) Replace "But Why?" with "Motivation"11:58
persia2) Move "Motivation" to README, and repalce with something about Worklists11:58
persiaActually, no, that's just ugly and confuses history.12:04
persiaI'll just stack the update above Change 279753, so that there is a sensible URL to use in the link.12:05
openstackgerritZara proposed openstack-infra/storyboard-webclient: Search for boards and worklists  https://review.openstack.org/34156212:10
*** matthewbodkin has joined #storyboard12:30
openstackgerritMerged openstack-infra/storyboard-webclient: Search for boards and worklists  https://review.openstack.org/34156212:37
Zara\o/12:38
persiaOne step closer.12:43
Zarathat sounds so ominous12:43
persiaDoes it help if I follow with "Storyboard will inevitably achieve a useful feature set"?12:44
Zarathe 'inevitably' there still has an unnerving ring to it12:45
persiaHrm.  Tricky.12:45
persiaSomehow I think any sentence beginning "Emerging from the depths of millions of seconds of history ..." won't help.12:48
* persia gives up12:48
Zarayeah, I think you have some sort of lovecraftian filter enabled that's intercepting your output and replacing it with stuff that implies the involvement of a tentacled, malevolent mass12:50
persia"In response to the existential pain imposed by that project that may not be named, the educated from four continents banded together to forge a new tool." sort of thing?12:52
Zaranow it's gone vaguely Lord of the Rings12:53
SotK+112:53
SotKits the forging a tool bit12:53
SotKthree tools for elven kings under the sky, seven for the dwarf lords in their halls of stone, etc. etc.12:54
persiaThe issue is that I don't want to say "banded together to combat the eldritch horror", because I'm not convinced that is fair, given that there were some groundbreaking and useful features added in the tool-that-must-not-be-named.12:55
matthewbodkinWhen someone comments on your patch, there is an option to 'fix' the problem which then allows you to edit your work. Can anybody tell me if this actually works when you save it as it looks good on my end but I'm not sure about everybody else's i.e. can other people see that you've fixed it and review it again, and does it then work in the merge? Or would it be best to just make a new commit? Opinions please13:09
SotKI imagine there'll be a "Publish Edit" button on the change page (where the reply button is iirc) which should update it for everyone else too13:10
* SotK tends to find editing locally and then submitting a new version of the change works best for anything other than a small fix though13:11
matthewbodkinI've just seen it now...13:12
matthewbodkinHow did I not notice that before?!? And thanks for the advice :)13:12
SotKgerrit's web ui is notoriously confusing at times :)13:13
openstackgerritMatthew Bodkin proposed openstack-infra/storyboard: Fix to slight errors in docs  https://review.openstack.org/35389113:35
Zara:)13:35
Zaraso, this is annoying. I can't check admin pagination works on my test instance as it only has 3 users, and pagination never works for js draft builds, so I can't use that either13:36
Zaraas far as I know it's just a question of adding:13:36
Zara+                        on-next-page="nextPage()"13:36
Zara+                        on-previous-page="previousPage()"13:36
Zarafor the result-set-pager on the admin user page13:36
SotKif it uses search-results somewhere that will be sufficient13:39
Zarayeah, I guess worst case it doesn't work and we're in the same position. idk why it wouldn't13:41
Zarai just don't trust it, haha13:41
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Create timeline events for boards and worklists  https://review.openstack.org/35014613:41
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Make it possible to get worklist/board timeline events via the API  https://review.openstack.org/35472913:41
openstackgerritAdam Coldrick proposed openstack-infra/storyboard: Send notifications to subscribers for worklists  https://review.openstack.org/35473013:41
Zaraeep13:42
openstackgerritZara proposed openstack-infra/storyboard-webclient: Fix Pagination for Admin Users Page  https://review.openstack.org/35473613:44
* SotK gets extremely nitpicky14:11
Zaraoh no14:12
persiaSotK: "Boards and Worklists" != "Boards & Worklists" :p14:15
persia(meta-nit)14:15
SotK:)14:16
Zaraahahaha, sotk, I meant to change that!14:16
Zarasince yeah the difference in order bothered me too14:16
Zaratotally forgot14:16
SotKit was highly troubling for my eyes14:16
Zaralol, it was for mine, I've just seen it too many times.14:16
Zarathanks14:16
Zaraalso, hahahaha, I remember my plan was to swap the lists round because I thought 'worklists and boards' sounded nicer14:18
persiaI also think it sounds nicer, but I'll switch the text in my editor to say "Boards and Worklists" if that is the direction we are taking.14:19
SotKI think 'worklists and boards' sounds nicer, I just want the order to be the same14:23
Zara(right, 'boards and worklists' sounds like a question; 'worklists and boards' is an answer, and pretty much nobody will care either way.=D)14:23
Zarahahaha14:23
Zarathis is my favourite bikeshed14:23
ZaraI'll switch the columns round in the interests of aesthetics14:23
persia"Worklists and Boards" it is then.14:25
* persia counts this as cerulean14:25
ZaraI'm actually really happy that everyone was bothered by it, makes me feel less weird. xD14:26
Zaraor a weirdo among weirdos, that also wfm14:26
openstackgerritZara proposed openstack-infra/storyboard-webclient: 'All Boards and Worklists' Page  https://review.openstack.org/27975314:46
persiaSome of the nitpicks are still there...14:47
Zarathe columns swapped position so they should be covered by that. I thought I got all the indents14:48
persia"All"14:48
Zaraoh yeah, just remembered those14:49
openstackgerritZara proposed openstack-infra/storyboard-webclient: 'All Boards and Worklists' Page  https://review.openstack.org/27975314:50
Zara(I don't care either way about 'All' but I don't want to leave SotK in distress)14:51
Zaraand I bet it'll bother him every time he sees it14:52
pedroalvarezcan't wait to see that merged :)14:53
persiaDo we care about the " and " vs. " & " thing I mentioned earlier?  I don't much, but I agree it doesn't match.14:53
ZaraI don't care; it's an ampersand in the sidebar because otherwise it spread over more lines14:54
Zara(ie: it goes:14:54
Zaraworklists14:54
Zaraand14:54
Zaraboards14:54
Zara(instead of:14:54
Zaraworklists14:54
Zara& boards14:54
Zaraso that makes the whole sidebar longer for no great reason14:55
persiaOh, hmm.  That's a good argument.14:55
Zara:) and then I'd rather not use ampersands anywhere we don't have to since I feel like it's a character that's ripe to being displayed weird or being hard to search for etc.14:55
Zara(speaking of which, I should check krotscheck's comment in that removed review :))14:59
persiaZara: You've an administrative block on the "move search icon" item.15:00
persiaWhich makes me a little unsure about the mention of it in the commit message for "All Boards and Worklists".  That commit message might also want to be "Worklists and Boards" :p15:00
SotKthe "All" needs to go because sometimes it isn't all of them (if there is  a filter) :)15:00
persiaIn the UI, yes (and it did).15:01
persiaIn the commit message, I'm less fussed.15:01
persia(but maybe you aren't?)15:01
ZaraSotK: true, I was thinking of the time before search15:02
* SotK isn't fussed about the commit message15:02
SotKI was just explaining why it was causing me distress15:02
Zarapersia: well, I'd still like a patch to remove that icon to be merged soon after, so it's still true, I just doubt it'll happen because of what would have to come first (nice header browse linking to search) :)15:02
Zarait lets people know the plan, which might be handy to have in the commit log15:03
persiaZara: I don't dispute the truth of the statement, just the value to the historian.15:03
Zaraheh, well, I don't know either way, but I intend to leave it in there, since it's context I'd want, looking at logs; I don't know if anyone would look. :)15:04
persiaI don't usually look at logs until many years later, and usually as a result of following a `git blame` trail.15:06
persiaI have no idea how I would go from that hopeful statement to the relevant commit using the tools I know (mostly git and tig) to find out what it means without context.15:06
persia(for that matter, it took me 5 minutes to find the relevant commit in gerrit today, even with all the context and currency)15:07
*** matthewbodkin has quit IRC15:47
* persia stumbles over wording16:52
Zarahello again16:53
persia"StoryBoard was created to serve the needs of a highly-distributed system that spans multiple projects." doesn't feel right, but anything else ends up reusing almost no words.16:54
Zaramaybe 'StoryBoard was created to enable cross-project work on a massive scale'? idk, I think the key with that will be to list the ways in which it serves the needs of that system, but I procrastinated from rewriting it because it wasn't obvious how to do it. :/16:56
ZaraI'm not sure that the distribution in itself makes any difference to storyboard (as far as I know that's just the thing that necessitates the creation of lots of projects), could be wrong16:57
Zara+ there are a few ways of reading 'distributed' and I'm not sure which one that intended16:58
persiaRIght then, I'll go with not preserving much of the wording.17:00
persiaFor me, "distributed" is mostly about the physical location of the developers.17:00
persiaThere's no equivalent of "go stick it on the wall" or similar.17:01
Zaraahh, hadn't thought of that; guess that's things like times in utc and integration with email (as there's no assumption of immediate communication)17:03
ZaraI'm heading off now, 'night! I have a wall of events timeline things to look at next week... \o/17:09
Zarawill probably pop back around 20:00 utc to peek at gerrit things17:09
openstackgerritAndreas Jaeger proposed openstack-infra/storyboard: Move other-requirements.txt to bindep.txt  https://review.openstack.org/35486517:31
openstackgerritAndreas Jaeger proposed openstack-infra/storyboard-webclient: Move other-requirements.txt to bindep.txt  https://review.openstack.org/35486617:31
openstackgerritMerged openstack-infra/storyboard-webclient: 'All Boards and Worklists' Page  https://review.openstack.org/27975318:49
*** alexismonville has quit IRC19:54
*** alexismonville has joined #storyboard19:54
*** alexismonville has quit IRC20:10
*** alexismonville has joined #storyboard20:27
-openstackstatus- NOTICE: The Gerrit service on review.openstack.org is restarting for a scheduled upgrade, but should return to service momentarily: http://lists.openstack.org/pipermail/openstack-dev/2016-August/101394.html20:51
-openstackstatus- NOTICE: The Mediawiki service at wiki.openstack.org will be offline from 21:00 UTC until approximately 23:00 UTC for a planned upgrade http://lists.openstack.org/pipermail/openstack-dev/2016-August/101395.html21:00
*** ChanServ changes topic to "The Mediawiki service at wiki.openstack.org will be offline from 21:00 UTC until approximately 23:00 UTC for a planned upgrade http://lists.openstack.org/pipermail/openstack-dev/2016-August/101395.html"21:00
-openstackstatus- NOTICE: ok https://wiki.openstack.org/ is now running Mediawiki 1.27.0; please let us know in #openstack-infra if anything seems wrong23:02
*** ChanServ changes topic to "ok https://wiki.openstack.org/ is now running Mediawiki 1.27.0; please let us know in #openstack-infra if anything seems wrong"23:02
-openstackstatus- NOTICE: https://wiki.openstack.org/ is now running Mediawiki 1.27.0; please let us know in #openstack-infra if anything seems wrong23:08
*** ChanServ changes topic to "StoryBoard - A task tracker for OpenStack development needs :: http://storyboard.openstack.org/ :: https://wiki.openstack.org/wiki/StoryBoard"23:08
*** alexismonville has quit IRC23:52

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