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

Public Ansible Project Meeting Agenda - Apr 2018 #301

Closed
bcoca opened this issue Apr 3, 2018 · 18 comments
Closed

Public Ansible Project Meeting Agenda - Apr 2018 #301

bcoca opened this issue Apr 3, 2018 · 18 comments

Comments

@bcoca
Copy link
Member

bcoca commented Apr 3, 2018

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-though strike-though

When creating new agenda ensure core and meeting_agenda labels are set

@remyleone
Copy link

remyleone commented Apr 5, 2018

I would like to discuss this PR: ansible/ansible#38285 There is still debug information on it to help reviewers understand how it works. Feedback is welcomed :)

@bcoca
Copy link
Member Author

bcoca commented Apr 5, 2018

ansible/ansible#36357

@retr0h
Copy link

retr0h commented Apr 11, 2018

ansible/ansible#38200 we keep bringing it up at meetings but need @retr0h to discuss, closing it for now until we can get you at a meeting.

@mat013
Copy link

mat013 commented Apr 15, 2018

Hi

I have added a feature request ansible/ansible#37426 and I was recommended to participate into one of the meetings held. I imagine that this one would fit best in the core team.
So I am going to join that one.

I am a little bit new to this process so I will try to do my best to attend at the meeting but just so I am doing the right thing:

I far as I understand I have to connect to the freenode in the channel #ansible-meeting at 19.00 UTC on the following tuesday and just participate.

@pilou-
Copy link
Contributor

pilou- commented Apr 17, 2018

ansible/ansible#38196: I would like some feedback/reviews

@varunchopra
Copy link

varunchopra commented Apr 22, 2018

I'd like to discuss addition of dedicated win_partition, win_disk and win_volume modules over the win_disk_management module that has a PR going. Also, deprecation of win_disk_facts over dedicated modules (again).

Both win_disk_management and win_disk_facts are really cluttered, and I think dedicated modules would help us do the same job better. Would be bringing this up on Tuesday I guess.

skipped since not at meeting.

bcoca: This seems better suited for the windows group/meetings #294

@Im0
Copy link

Im0 commented Apr 23, 2018

Would like any reviews/comments about this filter plugin addition in mathstuff.py: ansible/ansible#39114

@abadger
Copy link
Contributor

abadger commented Apr 23, 2018

Proposal to implement tainting of vaulted variables: ansible/proposals#109 I'm putting this on the agenda because I think we should vote not to implement this. There's simply no way to ever make this better than a leaky sieve. Advertising it as a security feature would be bad.
rejected until there is a sane way to implement this and have it be secure

@remyleone
Copy link

remyleone commented Apr 24, 2018

I would like to have reviews on ansible/ansible#38739 and ansible/ansible#38587

@albertomurillo
Copy link

albertomurillo commented Apr 25, 2018

I'd like to discuss ansible/ansible#31956
It has been sitting around for too long, fixes an annoying bug and is already reviewed.
IRC: albertom

@sac
Copy link

sac commented May 3, 2018

I'd like to discuss PRs:
ansible/ansible#37822
ansible/ansible#37771

@bcoca bcoca closed this as completed May 3, 2018
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

10 participants