Standing Agenda, Public Core Meeting Meeting - October 2016

[gundalow]

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.md for the schedule

Once an item has been addressed it should get strike-though ~~strike-though~~

[abadger]

This is carry over from before: ansible/ansible#17768 release process is undergoing changes. jimi-c updated and closed ticket explaining those.

[gundalow]

Discussion around how to track and report Python3 status so other people can help
@gundalow will setup a Google Spreadsheet and drive it from the Testing Working Group

[stevekuznetsov]

Discussion around the API that users can expect with stdout callback plugins:

• can they control std{out,err} completely?
• what can we do about things like https://github.com/ansible/ansible/blob/devel/lib/ansible/playbook/helpers.py#L196-L200

@jimi-c to work on a global CallbackManager for 2.3 and making ansible use that instead of display functions when appropriate.

Discussion around how to more correctly use the Ansible Display:

• should it be a global object?

• It cannot remain in __main__ for Python3 compatibility.

• why is the following code used? It doesn't make a global if one doesn't exist, it makes a local copy everywhere:

  try:
      from __main__ import display
  except ImportError:
      from ansible.utils.display import Display
      display = Display()
  ```</strike>

@bcoca has a branch in progress here: https://github.com/bcoca/ansible/tree/top_lvl_callback (long way to go before it's ready) @stevekuznetsov will take a look and give feedback to bcoca.

Discussion around how to best make CLI actions programatically reusable -- break out logic that parses user input from the command line entirely and ensure that a user consuming the Ansible CLI to issue actions can generate the correct set of options the need to e.g. run a playbook.

@bcoca changes to a global callback container that loads early will address the above two points by refactoring the current Display.

[samdoran]

I'd like to discuss changing the examples format in existing modules to use multi-line YAML instead of key value pair shorthand.

I have a branch where I've done most of the work for core modules but would like to discuss before submitting the PRs.

Discussed on 2016-11-03
So have we agreed

1. "k: v" is good
2. Examples in new modules MUST be "k: v"
3. samdoran can is a star, and can push that live. Multiple modules in a single PR
4. gundalow will update the new module checklist
5. Will look at adding in sanity tests for this - We (@mattclay & @gundalow) will be looking at linter tooling once all the repo merge is done

[stevekuznetsov]

I would like to further discuss publishing versioned documentation on the docs.ansible.com domain. It's seemingly published from devel and very misleading.

Default documentation will be the latest stable release, with devel version being available but labeled.

[gundalow]

I'd like to float the idea of Ansible detecting passing invalid modes to file: (etc)
Not sure if by the time we parse that if we can tell if it's a number and if the leading zero has been dropped.

[Shaps]

I'd like to discuss ansible/ansible#18325. It seems a good idea to me to add the SSH_CONTROL_PATH_DIRECTORY, and remove the hardcoded value

This has been merged to devel.

[gundalow]

ansible/ansible-modules-core#5388 MySQL Security issue
from WouterOosterveld as something that should go into 2.2

[abadger]

Ticket rotated. new ticket: #140