18:00:44 <felixfontein> #startmeeting Ansible Community Meeting
18:00:44 <zodbot> Meeting started Wed Mar  2 18:00:44 2022 UTC.
18:00:44 <zodbot> This meeting is logged and archived in a public location.
18:00:44 <zodbot> The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:44 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:44 <zodbot> The meeting name has been set to 'ansible_community_meeting'
18:00:44 <felixfontein> #topic Agenda https://github.com/ansible/community/issues/645
18:00:44 <felixfontein> 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:48 <felixfontein> #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics
18:00:51 <felixfontein> #topic Updates
18:03:58 <felixfontein> hmm. is it the wrong day? am I too early?
18:04:13 <jillr> right day and time by my calendar
18:04:57 <felixfontein> #chair jillr
18:04:57 <zodbot> Current chairs: felixfontein jillr
18:04:59 <felixfontein> good :)
18:05:25 <felixfontein> I was afraid I'd have to talk to myself ;)
18:09:55 <acozine> 0/
18:10:15 <acozine> I'm also in a team retrospective, so I may be distracted at times
18:11:06 <acozine> (it's a dev team thing, so I'm half team-member and half observer)
18:13:19 <acozine> um . . . hello?
18:13:23 <felixfontein> #chair acozine
18:13:23 <zodbot> Current chairs: acozine felixfontein jillr
18:13:30 <felixfontein> sorry, I started reading something else :)
18:15:00 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:17:16 <acozine> heh
18:18:43 <felixfontein> looks like there won't be much talking today
18:18:54 <jillr> my call is still going, sorry  :(
18:18:57 <felixfontein> I guess I'll info the current discussions, then we can see what happens
18:19:02 <jillr> hopefully it means we're doing well at async!
18:19:09 <felixfontein> we definitely should and will do :)
18:19:14 <felixfontein> (and actually do)
18:21:31 <jillr> I'm free to focus exclusively on this meeting now!
18:22:18 <felixfontein> #info Tadej Borovšak (tadeboro) resigned from the Steering Committee, both as a chairperson and a regular member, due to professional reasons (job change). Tadej, thanks for all you did for us, we wish you the best for your next steps in life and career!
18:22:24 <felixfontein> #link https://github.com/ansible-community/community-topics/issues/72
18:23:11 <felixfontein> #info Active vote: inclusion of community.sap and nautobot.nautobot-ansible in Ansible: https://github.com/ansible-community/community-topics/issues/74
18:23:37 <felixfontein> hmm, we have to adjust the date there
18:23:46 <felixfontein> andersson007_[m]: 2022-02-07 was before the vote even started :)
18:23:49 <felixfontein> should we do in 14 days?
18:25:52 <felixfontein> #info Please look at https://github.com/ansible-community/community-topics/issues/56#issuecomment-1055834177 regarding Ansible 6, including the related discussions https://github.com/ansible-community/community-topics/issues/70 and https://github.com/ansible-community/community-topics/issues/65
18:26:26 <jillr> agreed on 14 days for the inclusion candidates
18:26:53 <felixfontein> #info Ansible 6's first alpha is due in 6 weeks (April 12th)
18:27:47 <felixfontein> I've just adjusted the date to Mar 16
18:28:21 <felixfontein> from my POV, the most pressing issues are the open questions for Ansible 6, but I'm not sure how much sense it makes to discuss them today when almost nobody is here :)
18:29:16 <felixfontein> also all present folks already commented on https://github.com/ansible-community/community-topics/issues/70 ;)
18:29:23 <jillr> Hopefully folks will catch scrollback and comment on the tickets  :)
18:29:59 <felixfontein> yep :)
18:30:00 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:30:24 <felixfontein> I'll probably refraining from more #info/#link so that the minutes will be short and these links will be more prominent ;)
18:34:01 <briantist> hey folks
18:34:41 <felixfontein> #chair briantist
18:34:41 <zodbot> Current chairs: acozine briantist felixfontein jillr
18:34:44 <felixfontein> hey briantist :)
18:37:25 <acozine> heh, it's a majority non-RH week!
18:38:02 <felixfontein> indeed :)
18:38:15 <jillr> I can sneak out early and make it all about community!  ;)
18:38:41 <briantist> RH folks are part of the community too 😁
18:39:12 <acozine> don't go jillr !
18:39:18 <gundalow> Hey folks
18:39:26 <felixfontein> #chair gundalow
18:39:26 <zodbot> Current chairs: acozine briantist felixfontein gundalow jillr
18:39:29 <jillr> hola gundalow o/
18:39:29 <felixfontein> yay, one more ;)
18:40:09 <briantist> hey gundalow
18:40:44 <felixfontein> I guess with Tadej stepping down we should elect another chairperson
18:41:01 <felixfontein> gundalow: does someone from your team 'wants' :) to organize the election?
18:42:20 <gundalow> Yup, I was wondering if andersson007_ @andersson007_:matrix.org: chair person updates should be merged first. Though I guess we should get it moving.
18:42:28 <felixfontein> oh, and when talking about chairpersons, we might also want to talk about https://github.com/ansible-community/community-topics/issues/71, or more precisely the veto right
18:42:34 <felixfontein> gotcha :)
18:42:50 <felixfontein> gundalow: can you shed some light on the veto right?
18:42:56 <felixfontein> resp. the idea behind it?
18:43:08 <felixfontein> (I'd guess you discussed the changes internally)
18:43:49 <gundalow> I'm not sure where the idea came from.
18:44:12 <gundalow> AFAIK there wasn't any internal discussion
18:44:27 <felixfontein> ok
18:44:53 <felixfontein> I think it's ok to have it, assuming there is some kind of balancing mechanism (like a way for a large majority of the committee to break the veto)
18:44:59 <gundalow> Reviews on https://github.com/ansible/community-docs/pull/49 would be welcome
18:45:00 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:45:34 <felixfontein> what do others think about the veto right?
18:45:39 <felixfontein> now that we have at least a few voices present :)
18:45:54 <briantist> I am not necessarily opposed to it but it did strike me by surprise
18:46:00 <briantist> so I was wanting to know the background
18:46:01 <acozine> this is in the community-docs PR ^^^?
18:46:18 <briantist> or at least what scenarios we envisioned where the veto right would be used or makes sense
18:46:23 <felixfontein> acozine: yes
18:46:52 <jillr> I'm also not completely opposed, but I'm not sure I understand when and how it would be used
18:47:36 <felixfontein> briantist: I think it can make sense if it turns out that during a vote something went pretty wrong, like it was a very close call on something very controversial where only the minimal amount of folks voted (for whatever reasons); in that case the chairperson could veto to make sure this vote is re-done with more attention from the committee
18:48:17 <briantist> a right to declare a "misvote" might make more sense than a veto in that case
18:48:22 <acozine> hm, I'd be more comfortable saying the chairperson has the right to delay or call for a rescheduled vote
18:48:29 <felixfontein> (like a two-week voting window over new year change)
18:48:31 <briantist> or at least calling out that a veto does  not imply the matter can't bebrought to anothe rvote
18:48:39 <felixfontein> briantist: acozine: yes, both are better for this scenario :)
18:48:50 <acozine> "veto" sounds more like "over-rule and refuse to address the matter again"
18:49:06 <acozine> if the chair has that power, then s/he is more BDFL than chair
18:49:13 <briantist> acozine: agreed; this is why I'm curious about scenarios, it allows us to think about the purpose of the power
18:49:51 <felixfontein> it's more like BDFT, since the term's limited ;) except if the veto is used when electing the next chairperson?
18:49:57 <acozine> or, well, not "for life" but . . .
18:49:59 <jillr> power to call a revote makes more sense to me
18:49:59 <acozine> yeah
18:50:19 <gundalow> I'm not sure what process other projects use.
18:50:52 <felixfontein> a revote where a certain extra quorum from the committee is required, or just another 'regular' vote?
18:51:25 <briantist> not sure, but it should probably also include a limit on how many times a re-vote could be called
18:51:46 <felixfontein> yes, true :)
18:52:53 <felixfontein> maybe something like revote where 1/2 (or even 2/3) of the full committee have to vote for it? and if that passes, that is final?
18:53:54 <acozine> maybe a little research would help - into what other communities do?
18:54:15 <jillr> acozine: +1
18:54:27 <acozine> I like your suggestion felixfontein , but there might be other options we haven't thought of
18:54:41 <felixfontein> yes, definitely. some research would be great :)
18:54:46 <felixfontein> (any volunteers? ;) )
18:55:22 <jillr> unfortuantely I am at (if not over) capacity lately and can't sign up for anything new
18:55:59 <felixfontein> me too...
18:56:10 <briantist> same 😔
18:56:37 <felixfontein> maybe we sould rename Steering Committee to Over Capacity Club? :)
18:56:58 <acozine> heh
18:56:58 <briantist> the first rule of SCOCC is that you don't have time to read the rules
18:57:02 <jillr> hehe
18:57:13 <acozine> I could do a little digging later this week
18:57:15 <acozine> maybe Friday
18:57:16 <jillr> and I have another call in 3 minutes, so I have a hard stop
18:57:28 <felixfontein> briantist: lol
18:57:29 * acozine adds it to her calendar right away
18:57:38 <jillr> acozine++
18:57:40 <jillr> thank you!
18:57:46 <felixfontein> acozine: thanks a lot :)
18:58:23 <felixfontein> I guess we can also stop early to give jillr at least one minute to relax before the next meeting :)
18:58:29 <felixfontein> #endmeeting