-
Notifications
You must be signed in to change notification settings - Fork 144
Public Core Meeting Meeting - April, May 2017 #159
Comments
Discuss extending the module "shipit" workflow to non-modules, such as:
Migrated from
Update 12 Jan 2017 Meeting
Update 9th Feb 2017 Meeting
Feb 21 Meeting
Mar 2 Meeting
Mar 14
2017-03-23
|
From luto: ansible/ansible#19297 Fix for wildcards inside of a path for fileglob lookup (ie: Note this is for stable-2.2 and stable-2.3 Migrated from #150 (comment)
|
Define and document proposals process i.e ansible/proposals#50 was created and 'agreed' to immediately, w/o giving time for community feedback, which is happening now after implementation. Migrated from #150 (comment) We might need to review/update this: 7 Feb Meeting Discussed at the meeting. Many problems with the meta-proposal for creating proposals were discussed. Minimum timeframes were proposed but no agreement could be come to. Proposal documenting the new proposal process was asked for. 14 Feb Meeting
2 Mar Meeting
2017-03-23 20174-04
|
2017-04-04
|
2017-03-21: 2017-03-23:
Ticket is open to updates/discussion and once those are done it will be brought back for final approval 2017-04-11:
|
From bcoca Now that we support docs for many more plugin types, should we require all new plugins of those types to have docs included? 2017-03-30
2017-04-18
|
ansible/ansible#9563 (Adding nested dictionary lookups) - Do we want to accept this PR?
|
~~From @bmildren ~~
2017-04-04 Merged |
Ansible 2.3.0 FINAL has been released. Thank you for all your help with this release |
Decided on keeping current schedule for now. |
I've recently seen a few modules that:
Should 201705-02
|
aka branko on IRC
Before I continue making changes to the proposed pull request, I would like to get feedback on what would be acceptable in order to merge it so I would not spend effort going into wrong direction. Problem is as follows:
|
|
2017-05-09 Meeting 12:55 <@zodbot> Minutes: https://meetbot.fedoraproject.org/ansible-meeting/2017-05-09/ansible_core_meeting.2017-05-09-19.00.html |
Ansible All of these releases address at least one CVE (listed below). Users of 2.2.x should upgrade to 2.2.3 as soon as possible. The CVE impacting 2.1.x and 2.3.0 is MODERATE in nature, however users should look to upgrade as soon as the final releases are done. |
|
|
~~Is answer: depends on context |
|
Ansible Contributor Summit 4 (Part of AnsibleFest 2017 London) We are happy to announce our fourth Ansible Contributors Summit! Contributors Summit is a day-long working session with the core team and key contributors to discuss important issues affecting the Ansible community. You can participate in person or online Proposed topics: https://public.etherpad-mozilla.org/p/ansible-summit-june-2017 See https://groups.google.com/forum/#!topic/ansible-devel/stUITiM6hMs for more info action: noted |
Merged |
note: tested with downgrade + upgrade |
#note previous vote is thought to have been to reject PR |
#action vote results were "yes" at last meeting |
I almost certainly won't be able to make the meetings (1am and 5am my time) but @bcoca is aware of my thoughts. My helpful proposal that should catch 99% of problems but not cause issues for lots of users (i.e. it should be an improvement, but not necessarily perfect) is:
action: need to revisit once sivel can attend and discuss complete removal of warning |
I've made more detailed comments in my review in the pull request for the apt module.
action: mentioned PR is merged |
#action willthames committer rights to be discussed internally |
What constitutes authorship for a module? What criteria should there be to be added to the authors list? What responsibilities (if any) does being added to the authors list bring? |
Meeting ended Tue May 30 20:49:18 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . |
I'd like to bring up PR #24580 ansible/ansible#24580 I believe the PR is complete, and even has some additional unit tests. But it hasn't been approved enough to get included. One of the module maintainers recommended bringing it up in this meeting. |
ansible/proposals#65 Allow documenting option deprecation |
I would like to request reviews for PR#23862. |
We need guidance on ordered dictionaries for Windows modules. I prefer a common solution. ansible/ansible#25265 (comment) |
Would like to discuss:
|
I would like to discuss PR#21857 and PR#21764 @erasmix will be attending |
I would like to discuss if there is anything else I could do to have the following pull requests merged: |
Please use #162 going forward. |
Rolled over to June's agenda, please use #162 |
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~~
The text was updated successfully, but these errors were encountered: