18:00:20 #startmeeting Ansible Community Meeting 18:00:20 Meeting started Wed Sep 28 18:00:20 2022 UTC. 18:00:20 This meeting is logged and archived in a public location. 18:00:20 The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:20 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:20 The meeting name has been set to 'ansible_community_meeting' 18:00:20 #topic Agenda https://github.com/ansible/community/issues/645 18:00:20 acozine andersson007_ baptistemm bcoca briantist cyberpear cybette dericcrago dmsimard felixfontein geerlingguy gundalow gwmngilfen ikhan_ jillr jtanner lmodemal misc nitzmahone resmo samccann tadeboro cidrblock thaumos zbr: ping! 18:00:24 #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics 18:00:27 #topic Updates 18:00:28 o/ 18:00:35 #chair cyberpear 18:00:35 Current chairs: cyberpear felixfontein 18:00:39 o/ 18:00:47 Hello everyone 18:00:48 o/ 18:00:48 o/ 18:01:19 #chair mariolenz[m] anwesha DonNaro[m] cybette_ 18:01:20 Current chairs: DonNaro[m] anwesha cyberpear cybette_ felixfontein mariolenz[m] 18:02:17 o/ 18:02:22 o/ 18:02:36 my client wants to update, BRB 18:02:38 #chair acozine samccann 18:02:38 Current chairs: DonNaro[m] acozine anwesha cyberpear cybette_ felixfontein mariolenz[m] samccann 18:02:46 acozine: perfect timing ;) 18:03:15 felixfontein: it always seems to do that, for some reason 18:03:25 * acozine is back 18:04:21 #info the agenda for Ansible Contributor Summit 2022.10 is now available! https://hackmd.io/@ansible-community/cs202210-agenda 18:04:29 please have a look, the timings are subject to change as I confirm the sessions with the speakers, but the topics should be more or less finalized 18:05:03 #info Today Ansible 7.0.0a1 should get released 18:05:48 cybette_: in what timezone are the times? UTC? 18:05:50 Hooray! 18:06:01 (since it's somewhere in the US, I guess it's not UTC) 18:06:31 Fest is in Chicago, so it's probably Central US time 18:07:29 #info for more details about what's happening at AnsibleFest 2022 (the 2 days after Contributor Summit), check out this post: https://www.ansible.com/blog/the-automation-experience-ansiblefest-2022 18:07:45 felixfontein: good point, I will include the time zone info (yes, it's Chicago central US time) 18:07:48 thanks! 18:10:33 I have a query about an open PR. When should I ask it? 18:11:45 anwesha: usually outside of the meetings is best, if this isn't something that makes sense to discuss during the meeting 18:12:11 it depends very much on what the PR is about and for what (which collection or program) it actually is 18:13:18 #info We're looking for a bit of feedback on changing formatting of default / choices values / samples in the Ansible docs (use

): https://github.com/ansible-community/antsibull-docs/issues/38
18:13:27  felixfontein, okay understood. I am talking about your PR #212 about licensing of the plugin code.
18:14:03  anwesha: I'm working on a large set of repos, so #212 doesn't help me to know which PR you mean :)
18:14:33  felixfontein, sorry https://github.com/ansible-collections/overview/pull/212 this is the one.
18:14:54  ah
18:15:01  @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:15:05  yeah, that's a topic for discussion here
18:15:13  what exactly do you want to know about that PR?
18:17:13  felixfontein, is it a good idea to have the particular section of GPL being mentioned in there? Section 5(c)?
18:19:23  anwesha: I don't know. maybe someone else has a better opinion on this?
18:19:38  how exactly would you mention it in the PR?
18:20:31  Howdy! And we reached that part of the year when I can actually be here :) But sketchily, will have to do the school run soon.
18:20:40  #chair russoz[m]
18:20:40  Current chairs: DonNaro[m] acozine anwesha cyberpear cybette_ felixfontein mariolenz[m] russoz[m] samccann
18:20:54  good morning russoz[m] :)
18:22:40  felixfontein, "For these reasons, the GPLv3+ must be used. This is provision under section 5(c) of GPLv3+" something like this?
18:22:55  Good (morn|even)ing
18:23:08  felixfontein, at the end of the first paragraph.
18:24:45  strictly taking my 'documentarian' hat here - unless it's critical to point out section 5(c) I'd be wary of getting that specific. Things like that change and then the docs are outdated.
18:25:03  tho if this is a license, maybe they don't change what's covered under 5(c) ever?
18:25:24  yeah I was just about to ask if such sections do change in licenses?
18:25:30  as long as we stick to GPLv3 it shouldn't change, but I'm also wary about adding that, I'm not sure whether this very specific information is actually helping someone
18:26:24  samccann: for v3 of GPL it shouldn't change. the only things I would expect to change are typos that will be fixed, or links changed from http:// to https://, or other tiny details that should not have any legal impact
18:27:16  makes sense
18:30:00  @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:31:10  felixfontein, understood, may be then we should skip it then. More so since the regular developers are the consumers of the document.
18:32:19  felixfontein, what are the next steps to get it merged in the current form? (just curious, since I am new here).
18:33:49  anwesha: thanks for taking a look at it nonethelss, it's great to see more participation in the community :)
18:34:30  anwesha: we'll have to take a vote for it, and when the vote passes it can get merged
18:35:17  cybette_, that was the lawyer in me :)
18:35:34  felixfontein, thank you for the explanation.
18:35:46  if I remember / find time I'll start that vote today
18:35:53  so we can hopefully conclude this in 1-2 weeks
18:35:54  anwesha: lol, I had a feeling about that ;)
18:36:11  felixfontein, okay
18:36:28  cybette_, :)
18:41:42  Since there hasn't been any activity during the last 5 minutes I'd like to ask a question: Any problems with https://github.com/ansible-community/community-topics/issues/105#issuecomment-1242367646 ? This looks OK to me. Looks like toumorokoshi is starting to (re-) maintain google.cloud. If you don't object, I'd give a positive answer to this. Kind of an encouragement, you know?
18:43:51  looks reasonable to me, and yes to positive reinforcement
18:44:15  OK
18:44:39  sounds excellent
18:44:40  sounds good to me as well
18:45:01  @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:45:12  I don't know much (anything really) about magic modules, but any time someone steps up and says they have a sustainability plan, I do a little happy dance
18:45:32  I'm not really sure whether disconnecting the collection from magic modules is a good idea, since modules for new APIs, API changes, etc. need to be done manually from this point on
18:45:45  no idea how much work any of these approaches is though...
18:46:02  acozine: +1
18:50:25  hey folks, sorry I had other meetings
18:50:45  hi briantist
18:51:02  hello hello
18:52:30  I don't know "magic modules", what is it?
18:52:31  On the other hand, I think I've read somewhere that it's deprecated so every effort to move a collection away from magic modules looks like a good idea to me.
18:53:38  mariolenz[m]: it's a module generator by google. it supported ansible next to some other systems, but apparently they dropped ansible support from it.
18:54:05  https://github.com/GoogleCloudPlatform/magic-modules
18:57:31  #chair briantist
18:57:31  Current chairs: DonNaro[m] acozine anwesha briantist cyberpear cybette_ felixfontein mariolenz[m] russoz[m] samccann
19:01:08  quiet, isn't it?
19:01:25  are we still officially meeting?
19:01:36  Times's over, isn't it?
19:01:41  yes
19:01:56  maybe part of Europe is having an internet outage?
19:02:43  or slow bridge?
19:02:48  sorry, got side-tracked with https://github.com/ansible/ansible/issues/78912 :)
19:03:05  (which broke the Ansible 7.0.0a1 release process)
19:03:11  samccann: that could be it
19:03:28  felixfontein: uh-oh, that's not good
19:03:30  anyway, I think we can close the meeting
19:03:42  acozine: it's fortunately at the very end when running some tests, so the build itself still works fine
19:04:15  #endmeeting