Skip to content
This repository has been archived by the owner on Jun 10, 2024. It is now read-only.

Public Ansible Project Meeting Agenda - Feb 2019 #436

Closed
bcoca opened this issue Jan 31, 2019 · 31 comments
Closed

Public Ansible Project Meeting Agenda - Feb 2019 #436

bcoca opened this issue Jan 31, 2019 · 31 comments

Comments

@bcoca
Copy link
Member

bcoca commented Jan 31, 2019

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)

@bcoca
Copy link
Member Author

bcoca commented Jan 31, 2019

carried over:
@dagwieers :

@bcoca:

@dagwieers

This comment has been minimized.

@dw

This comment has been minimized.

@jamescassell

This comment has been minimized.

@tgadiev

This comment has been minimized.

@vutkin

This comment has been minimized.

@dagwieers dagwieers pinned this issue Feb 7, 2019
@dw

This comment has been minimized.

@dagwieers

This comment has been minimized.

@gundalow

This comment has been minimized.

@gundalow

This comment has been minimized.

@dagwieers

This comment has been minimized.

@madonius

This comment has been minimized.

maxamillion added a commit to maxamillion/ansible that referenced this issue Feb 14, 2019
As per Community Core Meeting 2019-02-14 consensus, remove this
section of the bug report issue template.

ansible/community#436

Signed-off-by: Adam Miller <[email protected]>
@marcjay

This comment has been minimized.

@jamescassell
Copy link

jamescassell commented Feb 18, 2019

@felixfontein
Copy link
Contributor

felixfontein commented Feb 18, 2019

@AlanCoding
Copy link
Member

AlanCoding commented Feb 19, 2019

@bcoca
Copy link
Member Author

bcoca commented Feb 19, 2019

shinmog pushed a commit to PaloAltoNetworks/ansible that referenced this issue Feb 19, 2019
)

As per Community Core Meeting 2019-02-14 consensus, remove this
section of the bug report issue template.

ansible/community#436

Signed-off-by: Adam Miller <[email protected]>
@cedws
Copy link

cedws commented Feb 20, 2019

@nitzmahone
Copy link
Member

nitzmahone commented Feb 20, 2019

  • (for Feb 26) Should module args with 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

@felixfontein
Copy link
Contributor

felixfontein commented Feb 24, 2019

@akatch
Copy link

akatch commented Feb 24, 2019

For 26 February:

My IRC nick is raktajino.

@Akasurde
Copy link
Member

Akasurde commented Feb 25, 2019

For 26 February:

@devyanikota
Copy link

devyanikota commented Feb 28, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests