decided to place the argspec in `meta/main.yml`
under the `argument_specs` entry. that was to satisfy a request
from felixfontein for future docs reasons.(samccann,
16:14:32)
we have no doc specific requirements spec'd for
it at this time, but i would expect that to be filled out after the
initial PoC phase.(samccann,
16:14:42)
2.11 you can expect: 1) validates role args at
task execution time from spec in meta/main.yml, 2) ansible-doc
support to output role entrypoints and descriptions.(samccann,
16:19:03)
the role arg spec format will be a subset of
module arg spec. they will, in fact, share the same code.(samccann,
16:19:26)
ACTION: tadeboro to
investigate ways to move forward with role docs as we wait for role
argspec validation(acozine,
16:28:59)
removing the "update on role argspec" from the
agenda for the next few months, will add it back as a regular item
after 2.11 release(acozine,
16:29:33)
template for collection `/docs/` folder(acozine, 16:30:46)
directory: we're going to propose allocating a
specific subdirectory in the collection for building docsite content
from. Nothing unrelated to the docsite should be placed
there.(abadger1999,
16:38:44)
need 'some way' to make labels unique across
all the collections(samccann,
16:39:17)
an example of a potential label would be `..
_anscoll_community_crypto_LABEL::` (_anscoll_community_crypto_ is
the part that uniquifies the label.(samccann,
16:45:35)
need a way to exclude collections whose docs
are bad (for instance, contain conflicting labels) or include the
collections that are known good.(abadger1999,
16:49:29)
ACTION: acozine to
summarize today's conversation in a proposal or issue(acozine,
17:01:10)