18:00:49 <samccann> #startmeeting Community Working Group
18:00:49 <zodbot> Meeting started Wed Aug  3 18:00:49 2022 UTC.
18:00:49 <zodbot> This meeting is logged and archived in a public location.
18:00:49 <zodbot> The chair is samccann. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:49 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:49 <zodbot> The meeting name has been set to 'community_working_group'
18:00:58 <samccann> @room Meeting time! Who is here to talk about the community?
18:01:14 <acozine> o/
18:01:18 <cyberpear> o/
18:01:46 <mariolenz[m]> o/
18:02:45 <samccann> baptistemm: bcoca briantist geerlingguy ikhan jillr jtanner misc resmo zbr0 ping!
18:02:46 <samccann> #chair cyberpear mariolenz acozine
18:02:46 <zodbot> Current chairs: acozine cyberpear mariolenz samccann
18:02:54 <samccann> welcome welcome!
18:02:54 <briantist> o/
18:03:07 <samccann> #topic Agenda https://github.com/ansible/community/issues/645
18:03:12 <samccann> #chair briantist
18:03:12 <zodbot> Current chairs: acozine briantist cyberpear mariolenz samccann
18:03:21 <samccann> #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics
18:03:30 <samccann> #topic Updates
18:03:43 <samccann> We have some votes ending today, in theory, so here they are as reminders:
18:03:59 <samccann> #info VOTE ENDS TODAY - on adding rules on collection dependencies: https://github.com/ansible-community/community-topics/discussions/119
18:04:33 <acozine> should we tally up the existing votes?
18:04:42 <samccann> This one clarifies what happens when a dependent collection or a collection it depends on doesn't update in a timely manor.  Spoiler alert! someone gets the boot eventually!
18:05:23 <samccann> acozine: go for it!  I guess it's usually a count of all votes and then a count of the Steering Committee votes?
18:06:44 <acozine> for the vote in #119, 9 votes, all in favor
18:07:31 <acozine> of those, let me see, I think 6 or 7 are steering committee memmber . . . I need to check the current roster, as I have not looked at it in a while
18:07:50 <samccann> #info #119 - 9 votes, all in favor. 6 or 7 from steering committee
18:07:56 <samccann> coolness!
18:08:17 <samccann> next one -
18:08:18 <samccann> #info VOTE ENDS TODAY - removing google.cloud from Ansible 8 - https://github.com/ansible-community/community-topics/discussions/121
18:09:18 <samccann> 7 in favor, but we may be short on Steering Committee quorum. I need to find a link to that list of names...
18:09:58 <acozine> yeah, I can only find hte original list, which I know is out of date
18:10:43 <mariolenz[m]> Since we're agreed on removing `google.cloud` from Ansible 8, I've created a [Deprecate google.cloud](https://github.com/ansible-community/ansible-build-data/pull/150) PR. I hope this was the right thing to do. If it isn't, just close it or tell me and I'll close it.
18:10:55 <samccann> afaik this list is accurate - https://docs.ansible.com/ansible/latest/community/steering/community_steering_committee.html
18:10:56 <acozine> but on the first topic, I think jamescassell/cyberpear, cidrblock, myself, mariolenz, briantist, and felixfontein are all SC members, so that's 6 steering votes in favor
18:12:10 <mariolenz[m]> Oh, just for your information: We might have to deprecate [servicenow.servicenow](https://github.com/ansible-community/ansible-build-data/issues/144), too.
18:12:19 <samccann> #infor for #121 - 8 Steering Committe members in favor, 1 abstain
18:12:44 <samccann> #info https://github.com/ansible-community/ansible-build-data/issues/144 might need to be deprecated as well
18:13:45 <samccann> mariolenz: are you up for creating a community-topic for that deprecation/removal?
18:14:01 <cyberpear> what would be the deadline for bringing google.cloud back if we can get it properly maintained? (I'm still trying to get some resources dedicated to it, but no success yet)
18:14:14 <acozine> is there a replacement collection for servicenow?
18:15:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:15:02 <acozine> cyberpear: we're allowing new collections to be added in any release, so with maintainers on board, it wouldn't be a long wait to get google.cloud back in the package
18:15:02 <mariolenz[m]> samccann: yep
18:15:18 <cyberpear> 👍
18:15:57 <samccann> yeah don't quote me on it, but I thought there was even a chance it wouldn't be rremoved if there were maintainers on board before Ansible 8?
18:16:35 <cyberpear> yeah, that makes sense; I should've thought about it for a minute before asking :P
18:17:45 <samccann> :-) well it helps to clarify it for all of us. But like I said, that's a vague memory and we should ask when someone 'in the know' can validate it for sure
18:18:26 <samccann> okay last vote that ends today
18:18:27 <samccann> #info VOTE ENDS-TODAY  on normalize booleans in documentation, ansible-lint, ansible-doc, ... https://github.com/ansible-community/community-topics/discussions/120
18:19:32 <samccann> This one ^^^ I think was a tight call on steering committee votes and felixfontein pinged a couple of members who hadn't voted yet.  At least one (gundalow) is on PTO til the end of the month. I pinged thaumos as well, but haven't heard back so he may be on PTO as well.
18:19:47 <samccann> Do we extend the vote time another week?
18:20:41 <samccann> oh nvm
18:20:45 <samccann> I didn't see the most recent comments.
18:21:04 <samccann> and true/false wins the day!
18:21:29 <samccann> #info AnsibleFest registration is open! The event will be at Sheraton Grand Chicago Riverwalk on October 18-19, 2022. Check out the details and register at https://www.ansible.com/ansiblefest
18:21:35 <samccann> #info Ansible Contributor Summit will be the day before AnsibleFest (Oct 17, 2022) at the same location. Due to the focus of the event, space is limited and you'll pre-register to be on the "invite" list (so when you register for Fest you can add on Contributor Summit as an option) https://ansiblecs202210.eventbrite.com/?aff=matrix
18:21:41 <samccann> #info For those attending Contributor Summit virtually you can also register on Eventbrite and select the "Online" option
18:21:53 <samccann> just repeating that for a while  in case anyone hasn't heard :-) ^^
18:22:53 <acozine> hurrah for the decision on the boolean docs!
18:23:20 <acozine> even though it wasn't my first choice, I'm super happy we reached consensus and have a path forward
18:23:38 <samccann> consensus FTW!
18:23:59 <samccann> #info community topic on how to better track deliverables and ensure they are completed on time for future Ansible package releases  - https://github.com/ansible-community/community-topics/issues/122
18:24:35 <samccann> this one doesn't havea vote ending date, but people seem to like the milestones idea and we do have a repo we can tie it to in https://github.com/ansible-community/ansible-build-data repo.
18:25:19 <samccann> What do folks think about adding a VOTE ENDS of next Wednesday? I don't know if we have a rule for how long a topic needs to be open, but this one feels like it's just kind of up to us doing the work on ..how we want to coordinate ...the work ;-)
18:27:34 <acozine> yeah, another weeks seems reasonable
18:28:19 <samccann> I'm actually unsure what needs to be a vote vs a discussion that ends up with a conclusion (like this one). Anyone know?
18:28:25 <acozine> though it would be easier to vote if it were phrased as a yes/no question, so folks can vote +1 or -1
18:28:41 <samccann> #info we'll leave this one open another week in case there are more ideas out there
18:28:44 <acozine> heh
18:29:15 <acozine> yeah, I don't know as we need to vote on that, we could just try something and then see how it goes (for tracking release work)
18:29:18 <samccann> yeah see that's what I'm not sure of. does EVERYTHING need a vote? are some just offline discussions where someone declares the 'mood of the thread' at the end and we go off and od it?
18:29:54 <samccann> yeah that's my gut feeling as well. It only impacts those of us working on a release, and those interested in 'what's planned' in a release.
18:30:00 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:30:25 <samccann> ah ... cybettes here... if only in spirit/bot form!
18:30:36 <samccann> #info new community topic - Improve licensing rules for 'all other code' in the collection inclusion requirementshttps://github.com/ansible-community/community-topics/issues/123
18:30:49 <samccann> This one has a draft pr as well ttps://github.com/ansible-collections/overview/pull/212
18:31:30 <samccann> https://github.com/ansible-collections/overview/pull/212  ...a url that works!
18:33:55 <samccann> Anyone else have any updates today?
18:34:50 <mariolenz[m]> Wait a sec..
18:36:56 * samccann stares meditatively at passing clouds
18:37:03 * acozine waits
18:39:24 <acozine> did we lose you mariolenz ?
18:39:30 <samccann> ok meanwhile... back at the ranch... tiny tim has a docs topic
18:39:45 <samccann> #info how do we bring back CI testing for all rst based docs? - https://github.com/ansible-community/community-topics/issues/111
18:39:50 <mariolenz[m]> <samccann> "mariolenz: are you up for..." <- https://github.com/ansible-community/community-topics/issues/124
18:40:02 <samccann> oh cool thanks mariolenz !!
18:40:10 <mariolenz[m]> If that's OK, I don't have anything more.
18:40:56 <samccann> yeah that LGTM
18:41:18 <samccann> it points to where it's deprecated and people can debate on how to handle it (since it does have a replacement collection I guess)
18:43:04 <samccann> Anything else to bring up in the meeting today?
18:44:20 <acozine> not from me
18:44:40 <mariolenz[m]> nope, not from me
18:44:46 <samccann> ok sounds like a wrap
18:44:49 <samccann> #endmeeting