Closed bcoca closed 5 years ago
carried over: @dagwieers :
@bcoca:
Meeting ended Thu Jan 31 15:27:56 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2019-01-31/ansible_core_irc_meeting.2019-01-31-15.00.html Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2019-01-31/ansible_core_irc_meeting.2019-01-31-15.00.txt Log: https://meetbot.fedoraproject.org/ansible-meeting/2019-01-31/ansible_core_irc_meeting.2019-01-31-15.00.log.html
I would like to discuss these as they solve various use-cases:
[x] I would like to discuss a sensible approach to landing various pieces of the Mitogen work:
[x] concrete plan for landing pieces of the existing connection layer implementation,
[x] patches necessary to remove ActionModule monkey-patches
[x] state of the threading/forking patches
[x] route for landing a complete strategy implementation that changes the process model
https://github.com/ansible/ansible/issues/51757 Discussed, comments added to issue
Can we add this one to discussion?
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-05/ansible_core_irc_meeting.2019-02-05-19.00.html 20:52 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2019-02-05/ansible_core_irc_meeting.2019-02-05-19.00.txt 20:52 Log: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-05/ansible_core_irc_meeting.2019-02-05-19.00.log.html
ansible_*_interpreter
task_vars issueI like to discuss @agaffney's proposal for inclusion:
command-warnings
?@gundalow We discussed this once in a meeting (see https://github.com/ansible/ansible/pull/25089#issuecomment-322585638), not sure if we want to come back on this. Did anything change?
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-12/ansible_core_irc_meeting.2019-02-12-19.00.html 15:00 Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2019-02-12/ansible_core_irc_meeting.2019-02-12-19.00.txt 15:00 Log: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-12/ansible_core_irc_meeting.2019-02-12-19.00.log.html
Can we add https://github.com/ansible/ansible/pull/38121 to the agenda?
Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-14/ansible_core_public_meeting.2019-02-14-15.01.html Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2019-02-14/ansible_core_public_meeting.2019-02-14-15.01.txt Log: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-14/ansible_core_public_meeting.2019-02-14-15.01.log.html
Please could we add this one by @AlanCoding to the discussion?:
vars
to include_role, et.al.)ANSIBLE_
docker_container
, docker_network
, docker_volume
and docker_compose modules
Meeting ended Tue Feb 19 20:19:09 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot .
[15:19]
cedwards
.choices
always be lowercase? Currently, the match is case-sensitive on Python, and has historically been case-insensitive for Powershell. Do we really want absent
and AbSeNt
to mean different things on a module with specific enumerated choices?If we choose to make it case-insensitive throughout Ansible (type='str'
with choices
specified), we'd probably need a deprecation warning to fire on any module that specifies choices
with an uppercase value. We can fix all the ones we ship, but there may be modules in the wild that expect specific-cased values. There are a number of other ways we could address it as well, but they'd probably require a lot more changes to the existing modules (eg the introduction of a lowerstr
type).
cc @jborean93
Meeting ended Thu Feb 21 15:22:15 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-21/ansible_core_public_irc_meeting.2019-02-21-15.00.html Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2019-02-21/ansible_core_public_irc_meeting.2019-02-21-15.00.txt Log: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-21/ansible_core_public_irc_meeting.2019-02-21-15.00.log.html
quiet
option to assert
module (to prevent automatic default to dump full item
s etc.)For 26 February:
My IRC nick is raktajino.
For 26 February:
Meeting ended Tue Feb 26 19:58:12 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-26/ansible_core_irc_public_meeting.2019-02-26-19.02.html Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2019-02-26/ansible_core_irc_public_meeting.2019-02-26-19.02.txt Log: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-26/ansible_core_irc_public_meeting.2019-02-26-19.02.log.html
Meeting ended Thu Feb 28 16:18:41 2019 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-28/ansbile_core_irc_public_meeting.2019-02-28-15.03.html Minutes (text): https://meetbot.fedoraproject.org/ansible-meeting/2019-02-28/ansbile_core_irc_public_meeting.2019-02-28-15.03.txt Log: https://meetbot.fedoraproject.org/ansible-meeting/2019-02-28/ansbile_core_irc_public_meeting.2019-02-28-15.03.log.html
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 addressed it should get strike-through.
(Migrated from a previous agenda)