[19:50] <balloons> veebers, a couple questions for you when you have a moment
[19:50] <balloons> 1) when will autopilot land with the json build?
[19:51] <balloons> 2) Are you ok with not having links to the source itself inside the api docs for the first iteration?
[19:52] <veebers> balloons: OTP at the mo, will be with you in a bit
[20:06] <veebers> balloons: 1.  I'll try get a card for next sprint(so next week)
[20:07] <veebers> balloons: 2. No, as that would make the documentation unusable, and with no guarantee when it will be rixed
[20:07] <veebers> fixed*
[20:09] <balloons> veebers, heh, ok we should chat more about 2; but first an update on what's been happening. You may have noticed we pushed things out a week as mhall needed more time to implement. The source docs are not something they are willing to implement right now and would require much more work.
[20:13] <balloons> veebers, we don't have to remove the static documents as soon as the initial import is complete; so we could keep those and refer to those until the import is done satisfactorily. That way at least the status quo is maintained
[20:14] <balloons> does that help things?
[20:14] <balloons> i would push to keep them until you are happy with the alternative
[21:35] <veebers> balloons: sorry was distracted. The problem I have with that is then there are 2 versions of the docs available (one being broken). Also, what's the guarantee that it will get finished and we don't sit in a half finished state for ever?
[21:36] <veebers> As long as there is a complete version of the docs around I can imagine there being less encouragement to get them done