[07:30] <dholbach> good morning
[08:02] <dholbach> hola dpm
[08:02] <dpm> morning dholbach
[08:02] <dpm> morning all
[08:15] <elfy> morning dholbach dpm
[08:15] <dholbach> hey elfy
[08:21] <dpm> hi elfy
[09:10] <czajkowski> aloha
[14:32] <dpm> balloons, mhall119, shall we do a quick standup for the autopilot docs work as discussed last week?
[14:35] <mhall119> dpm: on IRC?
[14:36] <dpm> mhall119, yeah, let's keep it lightweight
[14:36] <mhall119> ok
[14:37] <mhall119> so for my part I have a sphinx docs importer that mostly works, but the structure of the sphinx docs is going to require model and code changes to the django project, as well as custom CSS to make it look nicer
[14:38] <mhall119> however, the current API website is mid-refactor, which means I either have to make these new changes to the current production code, and have to re-merge the two branches later, or I update the importer to use the new code, add the new changes on top of hte refactor, and get that all deployed at one time
[14:39] <balloons> as for me, I've been working to get the json exports landed in uitk and autopilot. autopilot is landed however, uitk branch is not yet landed. I'd like to work on the narrative linking and updating but I'm dependent on the other tasks being completed first.
[14:40] <mhall119> oh, and I did check the narrative changes that balloons sent over and they don't appear to have changed anything that my importer is looking at, so we're good there
[14:41] <balloons> With that in mind, if mhall119 has a task I can complete I'm happy to pick it up.
[14:41] <mhall119> balloons: will we have packages in the archives for these docs in json format?
[14:41] <balloons> mhall119, yes, the autopilot package and the ubuntu-ui-toolkit-autopilot package
[14:41] <dpm> ok, cool. mhall119, have you thought about which way you want to go regarding the deployment/refactor)
[14:41] <mhall119> balloons: and the have now, or will have, json docs?
[14:41] <mhall119> .w 78
[14:41] <balloons> mhall119, yes, they will have json docs
[14:42] <mhall119> balloons: cool
[14:42] <balloons> mhall119, is that a task we missed then I think.. we can explicitly say you need to import from those packages
[14:43] <mhall119> dpm: if I'm going to spend the time updating the website code and css and re-deploying, I would really rather spend a little bit more time and roll it all into the devportal project now, rather than re-doing >50% of the same work later on down the road
[14:43] <mhall119> balloons: that doesn't really need to be a task at this point
[14:44] <dpm> mhall119, ok
[14:44] <dpm> mhall119, is there a task balloons can pick up?
[14:44] <balloons> mhall119, ack, k
[14:45] <mhall119> dpm: just the packaging parts I think
[14:45] <balloons> yea the larger blocker is getting the initial import work done
[14:45] <dpm> ok thanks, good work mhall119, balloons
[14:46] <balloons> mhall119, one other open question is about source linking. When you click the docs in the API it will link to the source code directly, ala http://people.canonical.com/~nskaggs/autopilot/_modules/autopilot/testcase.html#AutopilotTestCase
[14:46] <mhall119> balloons: yeah....that wasn't going to be included
[14:46] <balloons> mhall119, I was afraid of that. Why can it not be included>
[14:47] <mhall119> because it's more work and developers using autopilot don't really need it
[14:47] <balloons> this is something veebers definitely had as a requirement, so we'll need to talk about it
[14:48] <mhall119> balloons: ok,I can look into adding it, but there's no data structure in the API website currently to hold sourcecode
[14:48] <dpm> balloons, mhall119, if this is going to require a lot of work, I would leave it out for now.
[14:48] <dpm> I agree with Mike's assessment
[14:49] <dpm> balloons, was this requirement missing from the user stories?
[14:49] <balloons> mhall119, ok, yes I'll talk to veebers today and we can come up with a plan. However he wants it. I agree with both of you the first phase doesn't need to include it
[14:49] <dpm> I thought veebers had had a look at the sprint and the user stories
[14:49] <balloons> dpm, it's it's chris's email as something he wanted. However, we never formally launched the sprint, so it's hard to say
[14:50] <balloons> dpm, he did, it was in my notes. I talked to mhall119 about the others but just noticed the source linking, which is different than some of the other concerns about linking to the narrative and internal api linking
[14:50] <balloons> lots of linking concerns :-)
[14:51] <dpm> ok, balloons, would you mind talking to veebers and adding this to the backlog? However, this might require some discussion as to why linking to the autopilot would be useful for app developers
[14:51] <dpm> who only want to use AP
[14:52] <dpm> granted, it'd be nice to have, but not sure if the additional work required is worth it
[14:52] <dpm> sorry, I meant "linking to the autopilot source code"
[14:52] <balloons> dpm, sure
[14:53] <dpm> great, thanks
[14:53] <mhall119> balloons: are the current docs on /api/devel/ good enough for the time being?
[14:55] <balloons> mhall119, what do you mean? the static html docs? I had is update them at some point but it was painful on both ends. I don't plan to touch them
[14:55] <balloons> at the moment they do need updated again
[14:55] <mhall119> ok
[17:15] <dholbach> all rightie - have a great rest of your day - see you all tomorrow!
[21:53] <bkerensa> nigelb: le ping