Tuesday, 2018-01-16

EmilienMin a story, why urls aren't automatically href'ing ? http://storyboard.macchi.pro:9000/#!/story/174314000:28
EmilienMI have to copy/paste the url in my browser00:29
EmilienMI guess it would be a feature ;-)00:29
diablo_rojoEmilienM, https://storyboard.openstack.org/#!/story/200087600:37
diablo_rojoThey work for me?00:37
diablo_rojoMight be something with the migration?00:37
diablo_rojoI just added that one by hand.00:37
diablo_rojoWe migrated kolla-k8s and the stories there with urls are all hrefed fine https://storyboard.openstack.org/#!/project/91600:39
diablo_rojoEmilienM, ^^00:39
EmilienMsounds good to me then00:41
EmilienMjust checking :P00:41
EmilienMI like the tags import00:41
*** tosky has quit IRC00:52
persiadiablo_rojo: As a drum-beating measure, bug numbers are approaching collision.  When we picked 2 million, we anticipated transition soon.  Bug creation speed in LP seems to have slowed some since then, but it continues to move.  While I am not authoritative, I strongly suspect that any project not migrated by the time the LP bug counter reaches 2000000 will not be able to migrate without complex manual adjustment.08:46
*** tosky has joined #storyboard10:27
SotKoh dear, that lack of href'ing feels like its an unnoticed change caused by switching markdown parsers11:24
SotKshould be easy enough to fix though I think11:28
* SotK should have time to send a patch later11:28
EmilienMvenv: commands succeeded (tripleo migration from launchpad to my local SB instance)14:42
EmilienMdiablo_rojo: just a heads-up ^ no error14:42
EmilienMdiablo_rojo: I'll share the instance with my team so they can take a look at how it would be14:42
*** jamesmcarthur has joined #storyboard15:52
persiaThere seem to be separate tags "storyboard-blocker" and "blocking-storyboard-migration": should these be consolidated?  Do they have different semantic meaning to anyone in this channel?16:14
ZaraI don't know where the storyboard-blocker originated. blocking-storyboard-migration was used by our ex-facilitator for organisational purposes, aiui. in general they seem to be relative to individual projects but the tags don't convey that.16:16
SotKthat matches my memory16:17
persiaI'm considering re-tagging storyboard-blocker to blocking-storyboard-migration (which was recently mentioned on openstack-dev@), unless there are objections.16:35
persiaIn practice, I don't think any of the bugs are actually blocking migration: just potential blockers for some folk.16:36
persia(as we've seen plenty of successful migrations despite them)16:36
SotKfeel free :)16:37
Zarayeah, application of the tag isn't evaluated (and I don't know who would be able to evaluate its application! :))16:38
SotKand yeah, I think that is the meaning of the tag, "thing which someone considers blocking for them from migrating"16:38
SotKmaybe s/them/their project/, but that is how I've seen it being used16:38
persiaIs there any way to delete a tag from the tag cache?  I'd like to abolish "storyboard-blocker" entirely.16:38
ZaraI suspect not, I think there'd still be a db record for it16:39
SotKI also suspect not16:39
SotKa temporary solution could be "ask a db admin nicely"16:40
Zara(As I remember a new 'tag' is created in the db (with id etc) each time someone writes a new tag, and then those are reused.)16:40
persiaAh, too bad.  I suppose this is one of those things that would need someone with db access, with odd side effects (like maybe messing up the history of the story for which I just changed tags)16:40
SotKprobably16:40
persiaThen probably better to just leave it.  Oh well.16:40
Zararenaming vs removing might work for that16:40
Zarabut it'd have to happen in teh db16:41
Zara*the db16:41
Zaraand yes the history would refer to the new name16:41
persiaFuture improvement would be to have a way to deprecate tags by admin users, so tag searches skipped deprecated ones by default.16:41
ZaraI think that'd be pretty easy to implement16:41
persiaof course, admins would find this unpleasant (as they would be potentially swamped by requests), so no hurry on implementation (or even documentation of a story suggesting the feature) :)16:41
Zaraokay. I think the *technical* side of that would be easy at least16:42
Zarathough probably lots of places it'd be easy to miss, but it only really matters on the 'add tag' screen16:43
persiaAlso the search screen and the browse/filter screens.16:46
persiaEspecially given the need to switch from search to browse and back to search to reinitialise after deleting things (the story for which I just changed tags, and for which I can verify behaviour).16:47
ZaraI think those are less of a problem (they contribute less to new stories being split between tags) though it would be better to change those too16:49
persiaI agree they are less of a problem.16:58
persiadhellmann: You may find https://storyboard-blog.io/things-that-storyboard-does-differently.html a useful guide for setting up an automatic board.  There are plans to integrate that into openstack-hosted docs at some point, but it is work looking for hands at this point.17:42
dhellmannpersia : thanks18:17
dhellmannI think the thing I was missing was realizing that a "lane" and a "worklist" are the same thing18:18
dhellmannit honestly didn't occur to me to click through on the lane to edit its settings18:18
dhellmannI'm also unable to figure out how to define a query for "tasks for story X with status Y"18:19
dhellmannif I say I want tasks I can type "todo" in and get an option for that but I can't figure out the syntax for specifying that only tasks on a given story are relevant for a board18:19
dhellmannI'm starting to wonder if I should be using boartty instead of the web ui, but if that's true then it makes me rather sad18:25
ZaraI think that feature was planned but not there yet, so you wouldn't necessarily need boartty right now but you would need some custom script to populate a board with that query (but could then use the web ui after that). it is something we wanted to add to the web ui, though.18:32
fungiregarding the tripleo test-drive thread on the -dev ml, anybody have any particular objection to or recommendation why we shouldn't drop the robots.txt on the storyboard.openstack.org deployment?18:38
fungiit looks like it's been baked into the webclient since krotscheck's initial commit on that repo, so may be vestigial but i could be missing some important reason to keep it even on production deployments18:38
fungii'm bringing it up with the infra team in our meeting in ~20 minutes to see if anyone has opinions from that end as well18:39
fungiparticularly, i expect teams would like their stories to show up in popular web search engines when relevant18:40
krotscheckOH NO SOMEONE MENTIONED ME18:40
fungikrotscheck is now known as kibo18:40
* krotscheck doesn't mind.18:40
fungi;)18:40
krotscheckAFAIK Google's the only search engine that knows how to read and parse running javascript.18:41
fungithat's a fair point18:41
krotscheckSo, robots is unlikely to help.18:41
krotscheckSB would have to switch to HTML5 routing, and implement something akin to Angular Universal to pre-render the various pages on-server.18:42
fungiwe may end up needing to consider a future feature for a plaintext embedder at story urls as a workaround, and yeah, sounds complicated18:42
fungithanks for the very salient points18:42
Zarathe only argument I can come up with for preventing crawlers (not a good one imo) is that someone might paste sensitive data from their terminal into a story. but in that situation they should change their passwords etc.18:42
Zarathat's on the assumption that search engines can see it though, otherwise probably no good reason to allow them18:43
krotscheckIf that's done, don't forget to manage cache headers.18:43
fungiyeah, i expect at least some teams are going to view lack of search engine indexing a major feature parity gap compared to lp (or other popular trackers)18:44
* krotscheck goes back to lurching18:44
krotscheck*lurking even18:44
fungikrotscheck: thanks, also a great point. enjoy your lurking!18:44
Zara+1!18:44
SotKyeah, I think that lacking the ability to find bug reports using google will cause a lot of pain for folk, its definitely something we need to think on18:47
* SotK will not be around for the infra meeting today so will catch up on any discussion he misses later18:47
fungino worries18:47
fungiand i suppose dropping the robots.txt on sb.o.o for now cant hurt for now, at least to see whether "teh goog" picks up any actual story content18:48
* Zara wonders if it'd pick up the things at the api endpoints18:49
SotKyeah, I have no issue with dropping it18:49
dhellmannpersia, Zara : where is the source for that blog?18:49
Zara(eg: https://storyboard.openstack.org/api/v1/stories/32)18:49
Zaradhellman: currently it's hosted here: https://github.com/Zarathecat/storyboard-blog , we'd like to move it to other infra but I've been busy and nobody else has volunteered yet :D18:50
dhellmannok. I'm working on at least the post persia pointed me to18:50
Zaranice! :)18:54
Zara(I should be clear, in terms of hosting content as docs, diablo_rojo has offered to start working on that so you could sync up with her if you're thinking along those lines. :) in terms of moving the blog itself to other infra, afaik nobody is looking at that at the moment)18:58
*** diablo_rojo has quit IRC19:05
*** diablo_rojo has joined #storyboard19:21
Zaramordred: oh yeah... I remember I meant to do a quick rebase on that ui-router patch, then couldn't remember how to send the changes to someone else's patch and I've been too busy to look it up :/19:32
Zarathere are some fun abandoned patches from me where I sent like 3 ui router patches in one night to the wrong place19:33
Zaramaybe will get to it tonight but I think that's the only thing blocking that :D19:33
*** openstackgerrit has joined #storyboard19:34
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: import blog post "Things that StoryBoard does differently"  https://review.openstack.org/53441219:34
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: separate worklist instructions from theory  https://review.openstack.org/53441319:34
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: fix document cross-link syntax  https://review.openstack.org/53441419:34
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: fix syntax for toctree  https://review.openstack.org/53441519:34
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: fix literal block markup for blocks within bullet lists  https://review.openstack.org/53441619:34
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: escape an example URL as literal text to avoid build warning  https://review.openstack.org/53441719:35
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: fix field list markup syntax  https://review.openstack.org/53441819:35
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: highlight notes about permissions on API endpoints  https://review.openstack.org/53441919:35
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: import blog post "Mapping Launchpad to StoryBoard"  https://review.openstack.org/53442019:35
openstackgerritDoug Hellmann proposed openstack-infra/storyboard master: import blog post "Why StoryBoard for OpenStack?"  https://review.openstack.org/53442119:35
dhellmannZara, diablo_rojo: ^^19:35
dhellmannthat builds without warnings but the actual content could probably use some tone cleanup19:36
Zarathanks, will take a look later tonight!19:36
mordredZara: git review -d 384554 ; git fetch origin ; git rebase -i origin/master ; # fix things ; git rebase --continue ; git review19:44
mordredZara: but I can also help out with that if you don't get to it before I do19:44
diablo_rojodhellmann, awesome! I'll look now.19:46
Zaramordred: ahaaaa I missed `git fetch origin` so it posted the new patch as a brand new patch. thanks.19:50
Zara(I assume that's the relevant bit since the rest is my usual workflow)19:50
mordredZara: well - the most important bit is the Change-Id: line19:51
mordredZara: your new patch has an extra Change-Id line in it - I'm guessing something from rebasing and squashing perhaps?19:52
*** ianw has joined #storyboard19:52
Zaraah possibly19:52
mordredZara: in any case - all totally fixable ...19:52
openstackgerritMonty Taylor proposed openstack-infra/storyboard-webclient master: WIP Migrate to using webpack  https://review.openstack.org/53442419:52
Zara:D thanks19:53
Zaradon't send patches late at night folks19:53
Zarayou will forget how to gerrit19:53
openstackgerritMonty Taylor proposed openstack-infra/storyboard-webclient master: Update UI-Router  https://review.openstack.org/38455419:53
mordredZara: there you go ^^19:53
Zarathanks :)19:55
mordredZara: I also pushed up the in-progress poking around webpack witha long commit message about where it's at currently - just in case someone else wants to play with that before I get to it19:57
Zaracool, thanks. I have a general 'update all the webclient things' I've been meaning to get to20:02
diablo_rojoWe have a lot of reviews to do it seems20:18
SotKthank you for all the patches dhellmann!20:25
SotKalso mordred :)]20:25
SotKs/]//20:25
dhellmannSotK : I'm happy to help.21:01
dhellmannThe next thing I want is the "query language" documented. I need to see if I can reverse engineer that from the code somehow21:01
persiaA thought on robots.txt: I suspect that the majority of interesting content is the story description and task notes: much of the commentary is likely to be false positives if crawled.  I wonder about the value of having a special spider page that just contains links to story URLs, with static rendering of the story description and task notes as fallback for non-JS-aware clients.  Dunno how this would affect JS-capable crawlers, but given a list of21:02
persiastories they may be able to parse each.21:02
*** diablo_rojo has quit IRC21:27
*** diablo_rojo has joined #storyboard21:27
mordredpersia: so - interestingly enough - one of the 'features' in the newer frameworks like angular2 is server-side rendering - exactly to address this particular use case: https://angular.io/guide/universal22:29
mordred"the server is slow and less scalable, move all the processing to the client!" "the client is underpowered slow, move all the processing to the server!" ... lather, rinse, repeat22:30
* persia seems to remember about 10 cycles of that over the past few decades22:32
* mordred too22:35
*** jamesmcarthur has quit IRC22:36
persiaOf course, the same argument applies to "virtualise your workload"/"software runs faster directly on hardware", or at least has since 1964: before that most virtual machines ran on dedicated hardware, with one virtual machine per real computer (back to 1942, before which there were no virtual machines, to the best of my knowledge).22:36
*** jamesmcarthur has joined #storyboard22:43
*** jamesmcarthur has quit IRC22:59
*** jamesmcarthur has joined #storyboard23:00
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient master: Enable link detection in the markdown parser  https://review.openstack.org/53446123:27
SotKtiny patch that I promised to fix the link detection issue EmilienM noticed23:29
EmilienMwow23:30
EmilienMSotK: thank you23:30
EmilienM"linkify: true"23:30
EmilienMthat's it? :-)23:30
SotKyeah, turned out very easy indeed23:37
Zaranice!23:52
Zarashould be at a computer shortly...23:52

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