[15:51] <blackboxsw> hi rharper I noticed most of cloud-init/config/cc_*py contain semi-structured content describing the config feature and that some of the help docs are out of date. Have we previously discussed trying to generate the example or schema docs from these docstrings to keep docs from gettting dated?
[15:52] <blackboxsw> s/dated/out of sync/
[16:44] <powersj> rharper, smoser: does this list look right: https://paste.ubuntu.com/24517862/
[16:45] <smoser> is centos6 sysvinit ?
[16:45] <smoser> not upstart ?
[16:45] <powersj> it has /etc/init.d.. so I assumed sysvinit
[16:46] <powersj> that is looking at a lxc
[16:47] <powersj> [root@c6 init.d]# stat /proc/1/exe
[16:47] <powersj>   File: `/proc/1/exe' -> `/sbin/init'
[18:56] <powersj> rharper: can you bit flip https://code.launchpad.net/~powersj/cloud-init/+git/cloud-init/+merge/323351 if you are good with it?
[19:20] <rharper> powersj: will review asap
[19:22] <rharper> blackboxsw: we've not; I think the first step was getting in-file docs to turn into rtd info;  it's certainly reasonable to move that around from the header to something else;  not entirely convinced that we can capture everything as method docstrings versus how it's done today;
[19:23] <blackboxsw> rharper it just feels like there is a lot of duplication in the module docstrings that is almost, but not quite the RTD doc examples
[19:23] <blackboxsw> nothing I'll spend time on at the moment, but figured it warranted a bit of discussion at some point.
[19:25] <rharper> blackboxsw: ack, the rtd examples are not at their best
[19:28] <powersj> rharper: thx!