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 - August 2018 #329

Closed
bcoca opened this issue Jul 31, 2018 · 23 comments
Closed

Public Ansible Project Meeting Agenda - August 2018 #329

bcoca opened this issue Jul 31, 2018 · 23 comments

Comments

@bcoca
Copy link
Member

bcoca commented Jul 31, 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

@bcoca bcoca changed the title Edit New issue Public Ansible Project Meeting Agenda - August 2018 Public Ansible Project Meeting Agenda - August 2018 Aug 2, 2018
@gundalow
Copy link
Contributor

gundalow commented Aug 2, 2018

Ansible Contributor Summit 6 (Part of AnsibleFest 2018 Austin, Texas)

As part of http://www.ansible.com/ansiblefest

  • AnsibleFest Austin will be on both Tuesday 2nd and Wednesday 3rd October 2018
  • The Contributor Summit will also be over two days, on Monday 1st and Thursday 4th October, from 9:30am to 4pm (time subject to change).

This is your event

Ansible succeeds because of its community, and this contributor summit is for you. If you have any topics to discuss, large or small, please be sure to post those topics on the etherpad. For topics that other had added please vote by adding +1

https://etherpad.openstack.org/p/ansible-summit-october-2018

Please see https://groups.google.com/forum/#!topic/ansible-devel/ivrpVbLya8g for further info

Attending in person

We realize that not everybody can attend in person, which is why we’ll again be arranging a video conference and a meeting time on IRC in #ansible-meeting to encourage remote participation. This has worked very well for the past Contributor Summits. We’ll be sending out an email with the information for remote participation about a week before the Contributor Summit.

If you want to attend in-person please sign up at: https://www.eventbrite.com/e/ansible-contributor-conference-austin-2018-tickets-48557063484

After signing up you'll receive an email from Eventbrite with a discount code for AnsibleFest Austin.

Attending remotely

Please add your name at the bottom of this etherpad: https://etherpad.openstack.org/p/ansible-summit-october-2018

Call to action

  1. Add ideas to https://etherpad.openstack.org/p/ansible-summit-october-2018
  2. Attending in person: https://www.eventbrite.com/e/ansible-contributor-conference-austin-2018-tickets-48557063484 then use discount code to sign up to AnsibleFest
  3. Attending in person OR virtually: Add your name to the end of https://etherpad.openstack.org/p/ansible-summit-october-2018
  4. Happy automating!

Questions?

Thanks for all of your contributions to Ansible, and we hope to see you in Austin! And if you have any questions at all, please let us know.

Speak to gundalow on Freenode, or anyone else in #ansible-devel

@agowa
Copy link

agowa commented Aug 6, 2018

I'd like to put my pull request ansible/ansible#43689 onto the list.

Some possible changes were discussed that might make it more secure. No one on the core team could find a security hoe so we agreed to pass this on to a red hat cryptography expert for review.

@bcoca
Copy link
Member Author

bcoca commented Aug 6, 2018

ansible/proposals#39

@sivel
Copy link
Member

sivel commented Aug 8, 2018

For discussion on August 14:

Do we continue with deprecating with_ now? If not why? What do we need to get that on track?

Are we unhappy with the UI of transitioning to loop (too much jinja2?)? Who is going to make a proposal to get loop to where we need it.

If we hold off on deprecating with_ should we still proceed to deprecate the lookups that are not necessary, due to better alternatives using loop+filter?

No deprecations here. We need to re-group to determine the path forward for looping.

@abadger
Copy link
Contributor

abadger commented Aug 9, 2018

file will gain the ability to set a specific timestamp on the files it modifies: ansible/ansible#43230 shall we change the touch state so that it is idempotent by defaulting to timestamp=same (meaning, do not change the timestamp) for its action.

This would bring it inline with all the other states in file and make it idempotent but would be a backwards compatible break.

@sivel
Copy link
Member

sivel commented Aug 13, 2018

Swap default for INVALID_TASK_ATTRIBUTE_FAILED added in ansible/ansible#42480 to be True. This would cause users to have an immediate failure on playbook that may have been "working".

Swapping the default, and indicating in the error it can be toggled back to a warning.

@bcoca
Copy link
Member Author

bcoca commented Aug 13, 2018

ansible/ansible#39602<= choose a name and run with it

current bikeshed: incumbent (gives preference to currently executing hosts)

@maxamillion
Copy link
Contributor

maxamillion commented Aug 14, 2018

Request for further/final comments/review on the Yum and DNF refactor before merge. Also need to request an exception be granted for making a GPLv3 module_util as in some cases we are unable to get permission to re-license the derivative work. ansible/ansible#43621

@gundalow
Copy link
Contributor

gundalow commented Aug 14, 2018

Contributors Summit https://etherpad.openstack.org/p/ansible-summit-october-2018

  • Add ideas/topics
  • If attending in person please sign up

maxamillion added a commit to maxamillion/ansible that referenced this issue Aug 14, 2018
It was decided during the Ansible Core Developer Community Meeting
on 2018-08-14 that GPLv3 is acceptable for module_utils in specific
scenarios.

ansible/community#329 (comment)

Signed-off-by: Adam Miller <admiller@redhat.com>
@pilou-
Copy link
Contributor

pilou- commented Aug 21, 2018

* new module openssl_pkcs12

@jwitko
Copy link

jwitko commented Aug 22, 2018

- new module docker_swarm_service](ansible/ansible#19229)

@bcoca
Copy link
Member Author

bcoca commented Aug 23, 2018

ansible/ansible#42163

@remyleone
Copy link

remyleone commented Aug 23, 2018

I would like to have reviews on: ansible/ansible#44377

@remyleone
Copy link

remyleone commented Aug 23, 2018

@bcoca
Copy link
Member Author

bcoca commented Aug 27, 2018

ansible/proposals#57

@dagwieers
Copy link
Contributor

dagwieers commented Aug 28, 2018

ansible/ansible#37645

@bcoca bcoca closed this as completed Aug 28, 2018
@bcoca bcoca reopened this Aug 28, 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