Community: Public Ansible Project Meeting Agenda - May 2020

Created on 5 May 2020  路  27Comments  路  Source: ansible/community

Please leave a comment regarding any agenda item you wish to discuss. If you don't show up for the meeting, your item will be skipped. If your IRC nick is different from your Github username, leave that as well.

See https://github.com/ansible/community/blob/master/meetings/README.md for the schedule

Once an item has been discussed it should get checked off.

If you just want reviewers for your contribution try the #ansible-devel irc channel on freenode.

core meeting_agenda

Most helpful comment

All 27 comments

From april and @tremble https://github.com/ansible/community/issues/532#issuecomment-620172358

[ ] [ansible/ansible#69087](https://github.com/ansible/ansible/pull/69087) accept unvault lookup in base? (possibly a vault one also?)
[ ] [bcoca/collection#3](https://github.com/bcoca/collection/issues/3) new home for cannonical collection layout? (not example nor commented, though we should have those too)

I was introduced to https://github.com/ansible-community/protogen by @ssbarnea is it possible we can use this with that canonical collection layout to help promote proper testing?

diff things, that is 'collection repo', while the repo above just reflects 'pure collection structure reference'

Got it.

  • [x] ansible/ansible#69291 ansible-test: allow version_added tests for collections

  • [x] ansible/proposals#178 with first part of implementation ansible/ansible#69631 (was: a discussion on how version numbers should be handled that are potentially cross-collection; see also https://github.com/ansible/community/wiki/Version-numbers-for-documentation-deprecation-removal-in-the-collection-world)) (see below)

  • [x] ansible/proposals#178 with implementation ansible/ansible#69680
  • [x] ansible/ansible#69313 (name of changelog generator will change, this is mainly the question whether ansible/ansible is willing to use the new one instead of sticking to the one in ansible/ansible it's now called antsibull-changelog, part of antsibull, and now also installable from pypi)
  • [x] ansible/ansible#69727 implement remaining missing "deprecation by date" things, make proper deprecation of modules in collections possible (both by date and by version) without adding wrong data or ignoring ansible-test sanity errors.
  • [x] ansible/proposals#178 with implementation ansible/ansible#69680
  • [x] ansible/ansible#69795 ansible-doc: properly handle suboptions
  • [x] ansible/ansible#69796 parse return docs at same place where module docstring is parsed (and tag versions in it). Q: make invalid return YAML also an error, or soft-fail?
  • [x] ansible/ansible#69796 enforce that return value docs are YAML in ansible-doc (like DOCUMENTATION)
  • [x] ansible/ansible#69926 Inter-collection deprecation revisited (replace tagged versions/dates with extra fields). Comes with ansible/ansible#69935 to make Ansible 2.9 not crash when modules/plugins use new AnsibleModule.deprecate/Display.deprecated calls etc.
  • [x] ansible/ansible#69796 resp. the question whether plugin names should be FQCN in the plugin docs
  • [x] ansible/ansible#69742 resp. the question how tombstoning entries in ansible_builtin_runtime.yml / runtime.yml should look like
Was this page helpful?
0 / 5 - 0 ratings

Related issues

dagwieers picture dagwieers  路  10Comments

nitzmahone picture nitzmahone  路  13Comments

dagwieers picture dagwieers  路  26Comments

jillr picture jillr  路  8Comments

gundalow picture gundalow  路  5Comments