18:00:04 #startmeeting Ansible Community Meeting 18:00:04 Meeting started Wed Aug 24 18:00:04 2022 UTC. 18:00:04 This meeting is logged and archived in a public location. 18:00:04 The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 18:00:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 18:00:04 The meeting name has been set to 'ansible_community_meeting' 18:00:04 #topic Agenda https://github.com/ansible/community/issues/645 18:00:05 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:08 o/ 18:00:08 #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics 18:00:11 #topic Updates 18:00:20 #chair andersson007_ 18:00:20 Current chairs: andersson007_ felixfontein 18:00:36 o/ 18:00:36 0/ 18:00:51 #chair cybette_ samccann 18:00:51 Current chairs: andersson007_ cybette_ felixfontein samccann 18:01:12 o/ 18:01:15 o/ 18:01:33 #chair briantist DonNaro[m] 18:01:33 Current chairs: DonNaro[m] andersson007_ briantist cybette_ felixfontein samccann 18:02:16 o/ 18:02:19 #chair mariolenz[m] 18:02:19 Current chairs: DonNaro[m] andersson007_ briantist cybette_ felixfontein mariolenz[m] samccann 18:02:25 #info Ansible 6.3.0 has been released! 18:04:39 is anyone else feeling tired after a long day? :) 18:04:52 ok, not all of you had a long day yet... ;) 18:05:33 you can still before tired after a short day 18:05:50 I'm with you felixfontein looOOooong day today. I mysteriously woke up at 5 am. 18:05:55 I'm tired after a long week. oh wait it's only wednesday... 18:06:08 DonNaro[m]: haha, here it was no mystery, but one of our cats... 18:06:27 misc: cybette_: indeed! 18:06:44 Not only long, too hot, too. 18:07:06 how hot is it for you? 18:07:16 here it got up to 28 degrees (celsius), but not more fortunately 18:07:51 it's a balmy 17C here 18:07:55 31 18:08:17 Should we do something about [dellemc.os6/9/10](https://github.com/ansible-community/community-topics/issues/128#issuecomment-1225846837)? Theay look unmaintained to me. 18:08:34 currently 31°C here too 18:08:36 DonNaro[m]: oooh, nice! 18:09:11 31 is definitely too hot for working 18:09:11 (at least for me) 18:09:11 maybe we should consider moving to ireland ;) 18:09:19 seems like a cool place 18:09:34 the tradeoff is rain, lots of rain 18:09:48 * briantist has to change the weather app to °C to compare to everyone else ;) 18:10:21 Ireland is nice. I've been to Cork several times and it was always great. 18:10:53 Galway is the best though (ofc I'm biased) 18:11:04 mariolenz[m]: thanks for actually bringing us back to topic...! should we start the unmaintained process for them? 18:11:31 I've only been to Dublin once so far 18:12:24 Thats the question. If we agree that they look unmaintained, I would start the process. OK? 18:12:34 DonNaro[m]: I like this joke, like it only rains three times per year in Ireland... once from January to April, once from Mid-April to August, and once from September to December 18:13:04 felixfontein: rofl. that's spot on though. 18:13:24 commit histories: https://github.com/ansible-collections/dellemc.os10/commits/master https://github.com/ansible-collections/dellemc.os9/commits/master https://github.com/ansible-collections/dellemc.os6/commits/master 18:14:22 dellemc.os10 apparently had a commit since the 1.2.0 release... except that that release was never published 18:14:57 but maybe starting the removal process (by announcing this in The Bullhorn and in the collection repos) would be a wake-up call to the maintainers 18:15:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:15:09 either they wake up, or well, that's probably it 18:15:21 might also be useful to get some input from the ansible network folks on this 18:15:48 they might know more about these collections (maybe even rumors from users?) 18:16:54 afaik dell maintains them on their own 18:17:38 anyway, if we had corresponding topics/issues, it'd look more serious 18:17:51 Additionally, the last commits to dellemc.os10 were from andersson007_ whos just tried to fix some things but isn't really a maintainer of the collection, as far as I can see. 18:18:10 yep 18:18:58 moreover, independent folks submit PRs but they haven't been reviewed by dell's maintainers 18:19:58 looks abandoned 18:20:08 issues are also ignored 18:20:20 OK, so I'll start the process to declare those collections unmaintained? Agreed? 18:21:26 +1 18:21:30 +1 18:21:34 +1 18:22:13 +1 18:23:10 cool, I think we agree then to start the process 18:23:25 Good, then I'll do. Anything else to discuss? 18:23:40 so we'll announce that we will vote about determining whether the collections are unmaintained in ~one month, and then see whether something happens 18:23:49 (in case anyone forgot how this works) 18:24:40 #info We want to start the unmaintained removal process for dellemc.os(10|9|6) to determine whether they are unmaintained, and if they are, remove them from Ansible in the future 18:25:38 dmsimard started working on sanity testing all collections some months back 18:25:52 and also posted about errors in the collection repos 18:26:01 (I noticed when looking at the dellemc.os* repos ;) ) 18:26:17 maybe we should follow-up on the collections which ignored that so far 18:26:45 and/or discuss what to do if a collection continues to ignore this 18:27:04 I guess there are two possiblities: the collection actually is unmaintained; or the maintainers actively ignore it 18:27:14 ignore = unmaintained 18:27:26 in the latter case, we might want to think about throwing them out as well 18:27:50 andersson007_: could also be not enough time to fix 1000s of sanity errors, but still fixing other stuff (which actually breaks some users) 18:28:19 Why is "ignored" different from "unmaintained"? 18:28:24 I would still expect at least a response in that case (along the lines of 'sorry, we have too little time for that, and are busy with other maintainer things') 18:28:35 +1 18:28:51 you can ignore a specific issue, but still fix bugs, implement features, ... 18:29:00 the latter two things do not count as unmaintained 18:29:11 you can't ignore issues with collection requirements:) 18:29:24 well, you can, it's mainly that you should not :) 18:29:28 you can if your collection is out of the package:) 18:29:44 (so far we never enforced the requirements on already included collections, so so far the strategy 'ignore' worked well...) 18:30:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:30:01 Well, yes. A specific PR or issue. But it looks like they igonre all PRs and issues. 18:30:14 (it's like saying that the person jumping from a skyscraper is still reporting "everything's fine so far" also on the second floor) 18:30:16 yeah 18:30:54 mariolenz[m]: you mean dellemc? yes. I meant in general, some collections might ignore our sanity errors issue, but not others 18:31:10 (I was about to write 'ignore our sanity issue'...) 18:33:01 I don't have sanity issue because I don't have sanity 18:33:16 haha! 18:33:27 sanity is for .... sane people, I guess 18:33:34 :D 18:34:10 my collection is absolutely sane, it doesn't need to be checked 18:34:22 felixfontein: Sorry, I didn't see this. But yes, it's a problem if collections are maintained but ignore our sanity errors issues. 18:34:26 once is enough 18:34:34 at inclusion 18:34:47 :) 18:36:02 * felixfontein just opened one tab for every sanity issue referenced in https://github.com/ansible-community/community-topics/issues/96 18:37:28 * andersson007_ thinks that felixfontein has a lot of memory in his laptop 18:37:31 felixfontein: did that crash your browser? 18:37:51 not yet 18:38:07 I usually have a lot of tabs open anyway, my firefox is pretty battle tested ;) 18:38:56 robust and proven 18:39:03 can be relied on 18:39:27 :) 18:39:58 ok, so I guess we should re-run the sanity tests on all included collections as well, to see how much changed 18:40:25 andersson007_: I think dmsimard worked on this while being in your team, do you have access to the scripts / results / ... he created? 18:41:07 felixfontein: i should check, though i think i have the same as you all have 18:41:50 i saw only the issues 18:42:51 iirc there's a link to the script he used somewhere in the issues 18:43:12 ok, I guess we can investigate and ask him when we cannot figure it out ourselves :) 18:43:26 is there anything else someone wants to talk about? 18:45:00 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 18:49:38 if nothing else comes up, we should stop early :) 18:50:31 I'm trying to find the issue / discussion from dmsimard about the collections that have sanity problems. I f someone knows it please post it here as a kind of reference. Apart from this, I don't think I have anything else to discuss. 18:51:02 mariolenz[m]: do you mean https://github.com/ansible-community/community-topics/issues/96 ? 18:52:18 #endmeeting