18:00:16 #startmeeting Ansible Community Meeting 18:00:16 Meeting started Wed Jun 15 18:00:16 2022 UTC. 18:00:16 This meeting is logged and archived in a public location. 18:00:16 The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:16 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:16 The meeting name has been set to 'ansible_community_meeting' 18:00:16 #topic Agenda https://github.com/ansible/community/issues/645 18:00:16 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:20 #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics 18:00:23 #topic Updates 18:00:32 o/ 18:00:35 o/ 18:00:37 I'm over booked but sort of around 18:00:47 o/ 18:00:51 hi all 18:01:30 #chair briantist jillr orandon[m] 18:01:30 Current chairs: briantist felixfontein jillr orandon[m] 18:02:30 hi 18:03:09 #chair jtanner 18:03:09 Current chairs: briantist felixfontein jillr jtanner orandon[m] 18:03:43 o/ 18:04:12 #chair mariolenz[m] 18:04:12 Current chairs: briantist felixfontein jillr jtanner mariolenz[m] orandon[m] 18:04:31 o/ 18:04:40 o/ 18:05:34 What should we do with [Unmaintained collection: google.cloud](https://github.com/ansible-community/community-topics/issues/105)? 18:06:31 mariolenz[m]: agree on the Bullhorn announcement, modify it to use in the collection's issue tracker, and then start posting these things I guess :) 18:06:36 #chair samccann andersson007_[m] 18:06:36 Current chairs: andersson007_[m] briantist felixfontein jillr jtanner mariolenz[m] orandon[m] samccann 18:06:40 #chair andersson007_ 18:06:40 Current chairs: andersson007_ andersson007_[m] briantist felixfontein jillr jtanner mariolenz[m] orandon[m] samccann 18:10:05 the statistics for declaring the collection is unmaintained are interesting ... what other collections share similar stats? 18:12:49 https://github.com/ansible-community/community-topics/issues/79 has a list of some other collections that could be in a similar situation 18:13:59 someone would have to check them and compare them to the removal rules we have, to figure out which ones we can remove with the current rules (and what other rules we'd need to remove some more that seem to be worthwhile removing) 18:15:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:18:08 "mariolenz: agree on the Bullhorn..." <- felixfontein: I've added a proposal for the [google.cloud issue](https://github.com/ansible-community/community-topics/issues/105#issuecomment-1156782682). If that's OK for you and nobody else objects, I'd open the issue in google.cloud and also announce it on Bullhorn. 18:18:25 I've just added a comment with a small improvement :) 18:20:43 o/ 18:20:48 sorry just got out of another meeting 18:21:39 #chair cybette 18:21:39 Current chairs: andersson007_ andersson007_[m] briantist cybette felixfontein jillr jtanner mariolenz[m] orandon[m] samccann 18:22:14 does anyone else have comments/remarks on the announcements mariolenz[m] prepared for community.google in https://github.com/ansible-community/community-topics/issues/105 (scroll to the bottom)? 18:22:59 felixfontein: I'll add you cc when I open the issue in google.cloud, so you can have a last look it. And you'll see the announcment to Bullhorn in the chat, anyway. Thanks! 18:23:12 nope, ship it 18:23:24 jillr: thanks for checking! 18:23:27 mariolenz[m]: cool, thanks! 18:24:17 the announcement LGTM 18:25:34 added a nit comment 18:26:05 otherwise LGTM (or if you already sent it.. LG enuf TM ;-) 18:27:59 cool! 18:28:11 #topic Extend valid licenses for module_utils and modules 18:28:14 #info https://github.com/ansible-community/community-topics/issues/109 18:28:36 in that topic, I was suggesting to also Allow Apache-2.0 as a valid licnese for modules and module_utils 18:28:54 right now, we only allow BSD-2-clause and GPLv3+ for module_utils, and GPLv3+ for everything else 18:29:56 andersson007_ noted that we recently included PSF licensed code to several collections (for LooseVersion); this is a violation of the current rules 18:30:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:30:07 #info current rules: https://github.com/ansible-collections/overview/blob/main/collection_requirements.rst#licensing 18:30:25 i'm personally OK with any licenses. If the main issue is Legal's approval, could you extend the topic with all licenses we want and then i could try to reach out to Legal myself? 18:30:30 I'm proposing to extend the set of allowed licenses for module_utils and modules to cover at least Apache-2.0 and PSF 18:30:45 I think it makes sense to add some more licenses to the list if we have to ask legal anyway 18:31:17 (the Python license is actually not on https://wiki.debian.org/DFSGLicenses) 18:31:44 better to include as many as possible to approve all at once:) 18:32:05 yeah, but probably also not too many, to avoid the approval to take too long ;) 18:32:11 yep 18:32:16 reasonably 18:33:22 if anyone has suggestions for licenses to add, please add them to the topic (and/or mention them here)! 18:33:31 +1 18:33:46 let's maybe set up a final date? 18:33:55 otherwise it can last forever 18:34:26 maybe let's wait until in ~one week 18:34:32 +1 18:35:12 also if you're maintaining / involved in a collection, check whether it already uses some other licenses ;) 18:35:38 makes sense 18:36:24 especially look out for vendored code :) 18:38:11 yep 18:38:59 What does [compatible with the GPL-3.0-or-late meansr](https://github.com/ansible-community/community-topics/issues/109#issuecomment-1156801024)? 18:39:54 modules are gplv3. module_utils are in-lined in the module at runtime. so the module_util must have a license that is compatible with gplv3 (ie, the execution state of the code) 18:40:34 modules don't have to be gplv3 (except by our requirements) 18:40:53 valid. but since that's our requirement, that's why compatibility matters 18:41:01 indeed. 18:41:21 also the Ansible package is GPLv3+, so everytihng included has to be compatible with GPLv3+ 18:44:02 everyone interested please put your thoughts in https://github.com/ansible-community/community-topics/issues/109, it'll help formulate a request to legal 18:44:38 it can be your versions of the request 18:45:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:45:39 hmmmm 18:46:13 re-reading the guidelines, I now see why andersson007_ understands them differently. I wonder whether I'm forgetting something, but I remembered them quite differently - and apparently didn't read them clearly 18:46:53 we should fix them asap 18:47:13 maybe they actually already allow all GPLv3+ compatible licenses 18:47:51 https://github.com/ansible-collections/overview/pull/164 18:47:56 and https://github.com/ansible-community/community-topics/issues/2 18:48:19 just a year ago, and I already purged it from my mind... damn :) 18:48:44 ok, so I think the discussion is moot, since we already decided this... sorry for the confusion... 18:48:53 so no need for the request to legal, cool:) 18:49:02 yep 18:49:04 no problem:) 18:49:06 looks like :) 18:49:38 the topic can be closed?;) 18:52:34 done, I've added a final comment, and updated my previous incorrect comments 18:53:02 #info We noticed that we actually already decided this, see https://github.com/ansible-community/community-topics/issues/2 and https://github.com/ansible-collections/overview/pull/164 18:53:09 thanks! 18:53:38 one still has to make sure to use the licenses correctly, i.e. include the licenses, and make sure that code imports respect licenses. 18:53:54 like you cannot import GPLv3+ code in BSD/Apache/... licensed code, only the other way around 18:54:16 yeah, important to know 18:55:11 #topic Open Floor 18:56:05 #info google.cloud announcement: https://github.com/ansible-collections/google.cloud/issues/485 18:56:08 thanks mariolenz[m]! 18:56:28 need to drop off... thanks everyone! 18:57:48 thanks and bye samccann! 19:01:21 ok, since nobody seems to have something for open floor, let's close it :) 19:01:24 #endmeeting