| *** diablo_rojo has quit IRC | 00:05 | |
| *** diablo_rojo has joined #storyboard | 00:06 | |
| * SotK will try those suggestions tomorrow | 00:14 | |
| SotK | except the book | 00:14 |
|---|---|---|
| SotK | though I do sometimes want to make storyboard have a jokey ui where search results are a bookshelf and you click on the books | 00:15 |
| Zara | pleeeeeease | 00:18 |
| diablo_rojo | That would be excellent | 00:18 |
| Zara | like the way old harry potter website | 00:18 |
| Zara | I wonder if that exists on the internet any more... | 00:20 |
| * Zara fails to find it. :( | 00:26 | |
| davidlenwell | wayback machine!!! | 00:27 |
| Zara | I have a feeling it was about 150% flash content so idk if it'd be archived. I remember there was quidditch game on it and I think it was an official site, might've even been warner bros. used to play on it when I was about 12 hahaha | 00:30 |
| Zara | also let's put a quidditch game in storyboard | 00:31 |
| Zara | 'you want to file a bug? first you gotta catch the snitch!' *all projects are suddenly bug-free* | 00:32 |
| Zara | now our core team has expanded, I can be deeply irresponsible :D | 00:33 |
| diablo_rojo | Zara, nope! | 00:33 |
| diablo_rojo | I'll give back my credentials | 00:34 |
| Zara | aw man | 00:34 |
| davidlenwell | one of my flash websites from 2003 archived | 00:34 |
| Zara | oh neat! | 00:35 |
| Zara | link? :D | 00:35 |
| davidlenwell | give me a minute | 00:35 |
| Zara | (also hah, I just searched 'harry potter sites', but mistyped it as 'harry potter sits', to which google helpfully responded with 'great hall'. that is indeed where harry potter sits...) | 00:36 |
| diablo_rojo | Ha ha ha ha | 00:36 |
| diablo_rojo | sites like pottermore? | 00:37 |
| Zara | yeah, it was an old precursor to pottermore, used to go on it at school. | 00:39 |
| Zara | there was a list of fan sites that also had some official ones so was gonna plug those into the wayback machine... | 00:39 |
| diablo_rojo | Ahh yeah that makes sense | 00:40 |
| Zara | tried the warner bros one but it just redirects to the wayback homepage... | 00:41 |
| davidlenwell | ha ha.. found it! https://web.archive.org/web/20040518113517/http://www.thedave.net:80/ | 01:01 |
| davidlenwell | but I remember now.. this only got archived because I literally made the swf file the index file on my web server. | 01:01 |
| davidlenwell | Zara: ^ | 01:01 |
| davidlenwell | all the other archives of the site while I had it flash only show the html file | 01:02 |
| openstackgerrit | Kendall Nelson proposed openstack-infra/storyboard master: [WIP]Migration Error with Suspended User https://review.openstack.org/532706 | 01:04 |
| Zara | :D | 01:21 |
| Zara | everything about that website is perfect | 01:22 |
| davidlenwell | it is mildly embarrassing.. just glad it didn't have the version from 2000 archived. | 02:00 |
| *** mwhahaha has joined #storyboard | 03:43 | |
| mwhahaha | hey so i'm trying to follow https://docs.openstack.org/infra/storyboard/install/development.html and i'm getting http://paste.openstack.org/show/642523/ when i try and load up the webclient | 03:43 |
| mwhahaha | any ideas? | 03:43 |
| *** jamesmcarthur has joined #storyboard | 04:18 | |
| *** jamesmcarthur has quit IRC | 04:18 | |
| *** jamesmcarthur has joined #storyboard | 04:19 | |
| mwhahaha | for the record, it seems that https://review.openstack.org/#/c/528436/ has broken it | 04:25 |
| persia | Interesting. As Storyboard is continuously deployed, that should have broken https://storyboard.openstack.org/ | 05:24 |
| *** jamesmcarthur has quit IRC | 05:36 | |
| *** jamesmcarthur has joined #storyboard | 05:52 | |
| mwhahaha | It was probably already installed correctly so it only may appear on a fresh install | 05:57 |
| *** jamesmcarthur has quit IRC | 06:00 | |
| *** jamesmcarthur has joined #storyboard | 06:28 | |
| *** jamesmcarthur has quit IRC | 06:33 | |
| *** jamesmcarthur has joined #storyboard | 06:35 | |
| *** jamesmcarthur has quit IRC | 07:12 | |
| *** jamesmcarthur has joined #storyboard | 07:19 | |
| *** jamesmcarthur has quit IRC | 07:24 | |
| *** jamesmcarthur has joined #storyboard | 07:30 | |
| *** jamesmcarthur has quit IRC | 07:35 | |
| *** jtomasek has joined #storyboard | 07:39 | |
| *** jtomasek has quit IRC | 07:39 | |
| *** jamesmcarthur has joined #storyboard | 07:39 | |
| *** jtomasek has joined #storyboard | 07:40 | |
| *** jamesmcarthur has quit IRC | 07:44 | |
| *** jamesmcarthur has joined #storyboard | 07:46 | |
| *** jamesmcarthur has quit IRC | 07:55 | |
| *** jamesmcarthur has joined #storyboard | 08:04 | |
| *** jamesmcarthur has quit IRC | 08:09 | |
| *** jamesmcarthur has joined #storyboard | 08:15 | |
| *** jamesmcarthur has quit IRC | 08:21 | |
| *** jamesmcarthur has joined #storyboard | 08:22 | |
| *** jamesmcarthur has quit IRC | 08:26 | |
| *** jamesmcarthur has joined #storyboard | 08:31 | |
| *** jamesmcarthur has quit IRC | 08:36 | |
| *** jamesmcarthur has joined #storyboard | 08:37 | |
| *** jamesmcarthur has quit IRC | 08:42 | |
| *** jamesmcarthur has joined #storyboard | 08:48 | |
| *** jamesmcarthur has quit IRC | 08:53 | |
| *** jamesmcarthur has joined #storyboard | 09:01 | |
| *** jamesmcarthur has quit IRC | 09:05 | |
| *** jamesmcarthur has joined #storyboard | 09:17 | |
| *** jamesmcarthur has quit IRC | 09:19 | |
| SotK | interesting, I didn't hit any issues when testing that patch | 09:42 |
| SotK | also interesting, storyboard.o.o's deployment seems broken | 09:43 |
| SotK | the webclient on there is reporting it was built from commit 09332833aa5f994ab36bb1ddad01f2ba39f33746, which is from August | 09:45 |
| SotK | we've not actually merged a whole lot since then, but the things we have are indeed missing | 09:45 |
| SotK | the bug in that patch is probably that index.html includes angular-bootstrap/ui-bootstrap-tpls.js, but the package name got changed to angular-ui-bootstrap when moving it into package.json | 09:52 |
| * SotK has no idea how he managed to not have an issue | 09:52 | |
| SotK | I didn't do a fully from-scratch build which may explain it, but it'd still've had to install all the things | 09:53 |
| * SotK probably just did something dumb in the process | 09:54 | |
| Zara | hm, haven't had issues building locally though I was getting a warning about that component changing name. | 11:49 |
| Zara | http://paste.openstack.org/show/642552/ . can try from scratch. | 11:56 |
| *** davidlenwell has quit IRC | 12:01 | |
| Zara | mwhahaha: could you paste the command you're using? I just tried a build with a fresh clone of the webclient, but it succeeds for me. | 12:01 |
| *** davidlenwell has joined #storyboard | 12:01 | |
| Zara | oh sorry misread, it's not an error in the build but when navigating to the site after the build. I do see that with a fresh clone. will try to update some things... | 12:09 |
| Zara | tried changing that line, am seeing: http://paste.openstack.org/show/642609/ | 12:45 |
| SotK | changing which line? | 12:47 |
| Zara | oh I changed the line in index.html but actually I think it didn't help, it just tried a different step first that time. | 12:49 |
| Zara | so currently I don't think that line is the issue but I'll be able to dig into it more later today | 12:52 |
| Zara | and looks like we're currently due another 'update all the webclient packages' spree. in the meantime, best option is probably to build from the 09332833aa5f994ab36bb1ddad01f2ba39f33746 commit | 12:57 |
| Zara | mwhahaha: thanks for finding this issue! | 13:01 |
| persia | Zara: Does it work for you if you change package.json to name it "angular-bootstrap" rather than "angular-ui-bootstrap"? | 13:06 |
| * persia doesn't have a working webclient build environment currently, but would rather have expected the build-javascript-content job to have broken and is confused how this passed testing | 13:08 | |
| SotK | because the build works, it just explodes hideously at runtime | 13:09 |
| Zara | it already finds the package and builds it. we thought index.html was pointing at the wrong thing, but then I've just pointed at the right thing. so guessing something else is pointing at the wrong thing. | 13:09 |
| * SotK obviously failed miserably when testing it | 13:09 | |
| SotK | changing the line to "angular-bootstrap": "0.12.2" in package.json should fix it | 13:10 |
| persia | You aren't alone: I failed miserably when comparing the content of package.json and bower.json | 13:10 |
| persia | But yeah, fixing package.json seems the better solution than playing whack-a-mole with references to the old name. | 13:11 |
| * Zara wonders why s.o.o is using such an old webclient though | 13:11 | |
| Zara | that was a much more recent change | 13:11 |
| persia | That's a ifferent bug, and one that shouldn't be solved until mwhahaha's bug is squashed (or nobody gets storyboard) | 13:12 |
| SotK | I suspect the continuous deployment got broken at some point (I assume when switching to zuulv3), and we just didn't notice because we've yet to merge anything with a particularly obvious UI effect | 13:12 |
| Zara | the fix requires changes to both the package.json and index from the looks of it. | 13:17 |
| Zara | however one will then hit: Error: setting getter-only property "offsetWidth" | 13:18 |
| SotK | hm, what needs changing in index? | 13:18 |
| Zara | actually ignore me on that | 13:20 |
| persia | I would think pulling the archived 0.12.0 tarball should avoid changes in the code that would make it horrible. | 13:21 |
| persia | Mind you, it probably makes sense to try to update at some point, but perhaps not today :) | 13:21 |
| Zara | (those errors won't break anything in the UI though) | 13:22 |
| SotK | pulling the archived tarball is what currently happens, just changing the path didn't work because that tarball doesn't contain the release build afaict | 13:22 |
| Zara | SotK's fix does indeed work, no tarball should be necessary | 13:22 |
| persia | SotK: Right: I meant "because the code pulls the archived tarball on build, arbitrary upstream changes should not be able to break anything, so just changing the path in package.json should do it" | 13:30 |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient master: Fix reference to angular-bootstrap in package.json https://review.openstack.org/532819 | 13:40 |
| Zara | mwhahaha ^ should fix it | 13:42 |
| persia | Zara: Is 0.12.2 safe? I thought it was pinned to 0.12.0 for a reason (although I have no idea which reason). | 13:43 |
| Zara | the only npm version for this is 0.12.2 | 13:47 |
| Zara | it worked at a glance but would be worth checking more thoroughly | 13:47 |
| SotK | the git history doesn't suggest any reason for being pinned there | 13:48 |
| Zara | also hm, I'd like a test for that sort of issue since evidently our ci wouldn't've caught it, but not sure where to start with that | 14:10 |
| persia | For 0.12.0, one needs to pull the tarball (as was done by bower.json and package.json (with the name change). | 14:15 |
| persia | But I don't understand how angular-bootstrap works well enough to evaluate changing 0.12.0 to 0.12.2 | 14:16 |
| persia | I'm hoping the CI will give me a javascript object I can download that points at storyboard-dev.o.o, so I can play with it. | 14:17 |
| persia | But I'm not sure that's really a good test. | 14:17 |
| *** tosky has joined #storyboard | 16:06 | |
| tosky | hi, question about the migration of a project: is it possible to start using storyboard for the worklist/boards and migrate the bugs later, or does the migration of bugs wipe everything? | 16:18 |
| persia | tosky: The migration of bugs doesn't wipe anything. The problem is more that the project configuration is binary. | 16:19 |
| persia | Well. more correctly, the migration of bugs only wipes changes in migrated bugs, so it shouldn't be long-term continuous, or storyboard is read-only. | 16:20 |
| persia | I'm not sure how much worklist/boards will help without bugs migration, unless either a) all planned work is exclusive of all open bugs or b) you are willing to accept duplicate tasks | 16:21 |
| SotK | the migration script should skip over already-imported bugs, changes in migrated bugs shouldn't be lost iirc | 16:22 |
| SotK | I've never actually checked that though | 16:22 |
| tosky | the idea is to keep tracking properly the long term TODOs, which are tracked right now mostly on the PTG etherpad (ok, some of them are existing bugs) | 16:22 |
| tosky | but I see the point about tasks which are really bugs, we would have the problem of properly referencing the bugs | 16:23 |
| persia | SotK: I thought that updates in LP were updated in SB, overwriting changes made directly in SB, but my understanding comes from discussion at Paris summit, so not really recent. | 16:24 |
| persia | tosky: In storyboard, everything that could be done is considered a "task". Some things are scheduled to be done (possibly using worklists and boards). Other things wait for a volunteer (minor bugs that aren't getting attention). | 16:25 |
| SotK | persia: I may well be mistaken | 16:25 |
| persia | SotK: I am very likely out of date. Maybe we can find a volunteer to test :) | 16:25 |
| Zara | it does skip over already-imported bugs. I believe it will still import new comments and things on them if they exist, but ti'd be worth checking that one. | 16:26 |
| Zara | real issue with having things in both places is that people will start updating some things in lp and some in sb | 16:26 |
| Zara | and that'll get confusing | 16:27 |
| Zara | 'why didn't you reply to my comment?' 'I was looking at sb, you made it in lp' and vice versa | 16:27 |
| tosky | I get your point | 16:27 |
| tosky | but already-imported bugs: in this scenario there wouldn't be "already imported bugs", unless storyboards is able to associated a newly created task with an existing bug coming from the import | 16:28 |
| persia | tosky: Right, if you don't run the migration script, and you enable storyboard, you can have things in LP and in SB. The main risk is in terms of communication with users and contributors. | 16:29 |
| persia | Plus the potential for duplicate stories if you happen to fix any bugs. | 16:29 |
| tosky | the idea could be: track high level tasks only for now, to not forget them, and get used to it, and still use launchpad for the "actionable" bugs until the migration is done | 16:31 |
| tosky | but I'm the man-in-the-middle trying to get all the details; I will get back to the PTL and the rest of the team with this chat log and try to see if we can go with a direct full migration | 16:31 |
| tosky | one of the requirement is "isn’t heavily dependent on other projects", what does it mean exactly? | 16:32 |
| tosky | (btw, thanks for the help!) | 16:33 |
| Zara | it's similar to the point that just came up, if a project depends on lots of other projects that use lp | 16:33 |
| Zara | then people get confused switching between the two for tracking | 16:33 |
| Zara | (you're welcome! :) ) | 16:33 |
| persia | tosky: If you want to use storyboard features, then I'd suggest migrating. Reasons to defer migration include a) you have lots of open bugs with active submitters, b) you have lots of open cross-project bugs that you intend to work on in the next few months, c) you have lots of communications indicating how to use LP that you need to update first, d) you have lots of automatin using the LP API that you'd need to port first. | 16:33 |
| tosky | but depends how? In my case, Sahara uses a lot other projects (basically everything) | 16:34 |
| persia | tosky: Do you have lots of cross-project bugs in LP? | 16:34 |
| Zara | so a story in storyboard and the corresponding bug in lp will be missing a bunch of info as things will be split across the trackers. so it means 'if your project has a lot of cross-project bugs with things currently in lp' | 16:34 |
| tosky | ah cross-project bugs - no, I don't think so | 16:34 |
| Zara | it's a chicken and egg problem with migrating projects :) | 16:34 |
| persia | In that case, although your code might depend on code from other project, your task tracking probably doesn't depend on task tracking in other projects, so you can more safely migrate. | 16:35 |
| tosky | and about bugs, there are no many with pending patches that can't be redirected to the new identifier | 16:35 |
| Zara | :D (storyboard is designed for cross-project work, but the migration itself is tricky for projects with cross-project bugs. I quite like the irony.) | 16:35 |
| tosky | do I see it correctly that there is really no user documentation? I see the development documentation and the migration documentation | 16:36 |
| Zara | we have docs though they don't live anywhere official yet, diablo_rojo is working on fixing that. | 16:37 |
| Zara | https://storyboard-blog.io/ is pretty detailed | 16:37 |
| Zara | there are some docs around for things like gerrit syntax and things like that, but I think the blog is the best resource for explaining sb for people coming from lp currently | 16:37 |
| tosky | oh, interesting, thanks | 16:38 |
| persia | tosky: Insofar as possible, Storyboard strives not to need UI docs. As it turns out, that isn't working as well as hoped, so there might become some soon (if someone compiles the various bits that have been drafted). | 16:38 |
| Zara | yeah, we have bits and pieces floating around but we'd *like* the ui to be easy enough to use that we don't need dedicated docs for that | 16:39 |
| Zara | in the meantime, we have quite a lot of materials, they're just not centralized. (https://storyboard.openstack.org/#!/story/2000667 if you'd like one with diagrams) | 16:40 |
| tosky | still, some basic information on how to best organize your project and use the tools are pretty much needed for any program | 16:40 |
| persia | Indeed :) | 16:42 |
| Zara | we've found different projects have different preferred workflows and organisational structures | 16:42 |
| Zara | so how-to guides seem fine, but historically we've preferred not to dictate how people *should* do things | 16:45 |
| Zara | since we don't run the projects ourselves | 16:46 |
| persia | I think it is a good thing to allow freedom to do anything permitted by the tool (and have a permissivce tool), but conversely, something suggesting the projects->tasks->stories and stories->task->project relation helps folk to develop good workflows for their project. | 16:46 |
| Zara | yep, I agree with that :) | 16:47 |
| Zara | (and I don't think it's converse :P) | 16:47 |
| tosky | no, of course, not full guides but at least know if and how people can apply their workflow with the tools features (and limitations, even if done on purpose) | 16:47 |
| persia | Heh. I suppose suggesting that documenting the data model is dictating a thought pattern might be considered a stretch :) | 16:48 |
| tosky | eh :) | 16:48 |
| tosky | also, not all the teams may have a workflow, or may be interested to at least hear about others | 16:48 |
| tosky | and for a cross-project tool, it's also interesting to know which are the invariants always valid in order to properly collaborating | 16:49 |
| SotK | tosky: what is your current workflow (in Launchpad I assume) out of interest? | 16:52 |
| Zara | ah, are you thinking of teams having a place to document their own workflows so that others can find them? | 16:52 |
| tosky | Zara: also | 16:53 |
| tosky | SotK: ehm, we are probably on the "not totally organized" side; we have a set of goals defined during the PTG (and Summit before them), mostly we track features with specs | 16:54 |
| tosky | and discuss over the spec review | 16:54 |
| SotK | in the past I've used a story in storyboard to track a spec, with tasks for the individual things that need doing to implement it | 16:59 |
| SotK | that can sometimes lead to stories with lots of tasks though | 16:59 |
| Zara | maybe that's good in the sense that it accurately conveys just how much goes into a given spec. can be worse to use, though (then again, we now divide story tasks up by projects) | 17:06 |
| *** tellesnobrega has joined #storyboard | 17:06 | |
| Zara | (so maybe easier to navigate than it used to be) | 17:07 |
| *** jamesmcarthur has joined #storyboard | 17:43 | |
| -openstackstatus- NOTICE: Due to an unexpected issue with zuulv3.o.o, we were not able to preserve running jobs for a restart. As a result, you'll need to recheck your previous patchsets | 17:48 | |
| * diablo_rojo sees the neutron migration is STILL running... | 18:23 | |
| Zara | how long has it been going? | 18:24 |
| Zara | bigger projects looked like they'd take about 2 days | 18:24 |
| diablo_rojo | A full day and a half ago- I started Tuesday afternoon. | 18:25 |
| diablo_rojo | This is on track to be the same. | 18:25 |
| Zara | 12 hours to go maybe :D | 18:25 |
| diablo_rojo | Though I should take it as good news that it hasn't died yet. | 18:25 |
| *** jamesmcarthur has quit IRC | 18:46 | |
| diablo_rojo | Vitrage is onboard, but wants to wait till the end of the release which I said was cool :) | 19:28 |
| persia | Brave folk, to switch task trackers right at release time, just when the number of new users experiencing new issues is highest. | 19:41 |
| persia | If I was in charge of projects that were undergoing LP->SB transition, I'd try very hard to time the change precisely mid-cycle, ideally after most active users had switched to the new release (and had their immediate issues resolved), and sufficiently before the next release that a) devs could have some bobble time dealing with thensition before feature freeze, and b) appropriate user-facing documentation could be udpated to ensure users weren't | 19:43 |
| persia | confused about how to file bugs with the upcoming release. | 19:43 |
| *** jtomasek has quit IRC | 21:43 | |
| *** jtomasek has joined #storyboard | 23:15 | |
| *** jtomasek has quit IRC | 23:21 | |
| Zara | SotK, diablo_rojo: I think https://review.openstack.org/#/c/532819/ has requisite reviews for merge, just don't wanna merge my own patch. :) | 23:37 |
| * diablo_rojo reviews | 23:38 | |
| Zara | thanks! :) | 23:40 |
| Zara | I was hoping to update some more webclient components this evening, but am increasingly unlikely to get to it tonight | 23:53 |
| diablo_rojo | I am currently testing my WIP handling the heat/i18n user suspended error. Hopefully that pans out. | 23:59 |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!