19:00:22 #startmeeting Ansible Community Meeting 19:00:22 Meeting started Wed Jan 18 19:00:22 2023 UTC. 19:00:22 This meeting is logged and archived in a public location. 19:00:22 The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions. 19:00:22 Useful Commands: #action #agreed #halp #info #idea #link #topic. 19:00:22 The meeting name has been set to 'ansible_community_meeting' 19:00:22 #topic Agenda https://github.com/ansible/community/issues/679 19:00:26 acozine, andersson007_, anwesha, baptistemm, bcoca, briantist, cidrblock, cyberpear, cybette, dericcrago, dmsimard, felixfontein, geerlingguy, gotmax, gundalow, gwmngilfen, ikhan_, jillr, jtanner, lmodemal, mariolenz[m], markuman, maxamillion, misc, nitzmahone, oranod, resmo, russoz, samccann, thaumos, zbr: The Ansible community meeting is starting now! 19:00:31 The ping list is stored at https://kutt.it/meeting-people. Feel free to add or remove yourself. 19:00:34 #info Agenda: https://github.com/ansible/community/issues/679 / Topics: https://github.com/ansible-community/community-topics 19:00:37 #topic Updates 19:00:49 ][['''''''''''''' 19:00:56 .hello2 19:00:58 maxamillion: maxamillion 'Adam Miller' 19:01:03 sorry :) 19:01:06 #chair maxamillion 19:01:06 Current chairs: felixfontein maxamillion 19:01:22 oooo, fancy 19:01:28 lol 19:01:31 hello all 19:01:32 o/ 19:01:40 #chair oranod 19:01:40 Current chairs: felixfontein maxamillion oranod 19:01:47 o/ 19:02:00 #chair samccann 19:02:00 Current chairs: felixfontein maxamillion oranod samccann 19:02:10 o/ 19:02:31 o/ 19:02:34 #chair andersson007___ mariolenz[m] 19:02:34 Current chairs: andersson007___ felixfontein mariolenz[m] maxamillion oranod samccann 19:04:07 FYI, there are two votes in progress: https://github.com/ansible-community/community-topics/discussions/categories/votes-in-progress 19:04:36 #info https://github.com/ansible-community/community-topics/discussions/181 and https://github.com/ansible-community/community-topics/discussions/182 are active votes (removal of community.google and community.skydive from Ansible 9) 19:05:08 especially the former needs more votes! 19:05:32 * maxamillion looks 19:05:38 Apart from the votes, what do you think about https://github.com/ansible-community/community-topics/issues/180 ? 19:05:53 that's a topic for later 19:06:04 let's first talk about the roadmap for Ansible 8 19:06:12 #topic Roadmap for Ansible 8 19:06:20 #link https://github.com/ansible/ansible/pull/79598 19:06:25 OK 19:06:32 #link https://github.com/ansible-community/community-topics/issues/176 19:06:56 acozine prepared a proposal (https://github.com/ansible/ansible/pull/79598), we should finalize it and vote on it ASAP 19:07:38 the main feature of this time's roadmap is that Ansible 8.0.0 should be released two (or at most three) weeks after ansible-core 2.15.0, and 8.1.0 will be a day after 2.15.1 19:08:11 what do you all think about it? 19:08:15 o/ 19:08:49 SGTM 19:09:09 #chair resmo 19:09:09 Current chairs: andersson007___ felixfontein mariolenz[m] maxamillion oranod resmo samccann 19:09:22 if nobody has objections I will start a vote on it later today 19:09:51 o/ 19:10:04 felixfontein: +1 19:10:05 #chair acozine 19:10:05 Current chairs: acozine andersson007___ felixfontein mariolenz[m] maxamillion oranod resmo samccann 19:10:06 +1 for vote 19:10:19 felixfontein: it will be important to get the approval of whomever is doing those releases. 19:10:24 agree 19:10:42 samccann: true 19:11:12 I've pinged them in the PR 19:11:32 once they say it's OK I'll start the vote then :) 19:12:36 ok, if anyone still wants to comment on this, add a comment to the PR (or the discussion topic) 19:12:46 #topic Keep cyberark.pas in Ansible 8? 19:12:48 #link https://github.com/ansible-community/community-topics/issues/180 19:13:11 it looks like they really started updating their collection and fixing problems 19:13:40 I think we should vote on cancelling the removal process. nobody made comments against that in the discussion topic so far... 19:13:43 what do you think? 19:14:02 (I would vote to keep them in Ansible 8) 19:14:05 SGTM 19:14:26 sgtm too 19:15:05 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 19:15:16 sgtm as well 19:15:17 same here. sgtm. 19:15:20 great to see someone cares about previously abandoned stuff 19:15:20 mariolenz[m]: since you mentioned this earlier, is there something you want to add? 19:16:01 sgtm 19:16:22 #chair Warkdev[m] 19:16:22 Current chairs: Warkdev[m] acozine andersson007___ felixfontein mariolenz[m] maxamillion oranod resmo samccann 19:16:24 Nope. I've already commented in the issue that I tend to keep the collection. So I'm fine with voting on this. 19:16:40 I'm fine with keeping cyberark 19:17:03 cool! then I'll create a vote after the meeting 19:17:26 #topic Definition and workflow for Ansible release blockers 19:17:29 #link https://github.com/ansible-community/ansible-build-data/pull/194 19:17:39 andersson007___ created a PR with a concrete proposal 19:18:08 what do folks think? do we need a better / more precise definition, or is this good enough (as the first step)? 19:18:46 i deliberately kept it broad 19:18:49 enough 19:18:59 imo 19:19:51 I like it 19:20:05 do you folks think we should vote on this? or actually just merge this? I'm currently tending to just merge it if everyone seems happy with it 19:20:12 Gives us some flexibility. I'm fine with it. 19:20:24 I'm in favor of merging. 19:20:39 me to:) 19:20:39 merge! 19:21:01 great :) if nobody objects until the end of the meeting, I'll press the button 19:21:06 merge away 19:21:11 #action felixfontein start a vote on keeping cyberark.pas 19:21:25 #action felixfontein merge https://github.com/ansible-community/ansible-build-data/pull/194 if nobody objects until the end of the meeting 19:21:48 finally some actions for me that aren't too much work ;) 19:22:27 mariolenz[m]: thanks for feedback on wording and typos! 19:22:58 #topic Improve Ansible PyPI README 19:22:59 or on mistakes i would say:) 19:23:02 #link https://github.com/ansible-community/community-topics/issues/173 19:23:07 #link https://github.com/ansible-community/antsibull/pull/474 19:23:24 we started this in early December, and then forgot about it over winter holidays it seems :) 19:24:26 IIRC we were discussing whether to adjust the design principles 19:25:42 what do you think about voting on it to merge it as-is, and create a follow-up for the design decisions (as that's potentially more controversial and we do not have a concrete proposal yet)? 19:26:02 +1 for merging as is 19:26:11 +1 to merging as is 19:26:35 if nobody objects I'll create a vote for that as well, then you can +1 there as well ;) 19:26:39 +1 to merging as is, it's an improvement over what we have, and we can iterate from there 19:26:50 I fully agree on that 19:26:53 vote early, vote often 19:26:59 :) 19:27:00 sounds reasonable 19:27:33 #action felixfontein create vote for merging https://github.com/ansible-community/antsibull/pull/474 as-is (design principles can be discussed and adjusted in a follow-up if someone wants to create a proposal) 19:27:37 great, thanks! 19:28:30 is there something else folks want to talk about? 19:28:43 there's still https://github.com/ansible-community/community-topics/issues/167 but it might be a long one for the remaining half an hour 19:29:44 I've got a couple of updates on those two community topics I created for the docsite user experience and opening up the publishing process. if nobody else has anything for the agenda. 19:30:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 19:30:09 #topic Docsite related things 19:30:15 oranod: here you go :) 19:30:24 :-) 19:30:34 #link https://github.com/ansible-community/community-topics/issues/174 19:31:13 wait, what happened to 167? 19:31:54 maxamillion: let's go back to that. I probably should've given it more time. 19:31:57 maxamillion: nobody said they want to discuss it now 19:32:05 ah ok 19:32:18 let's talk a bit about docsite first, and then switch back 19:32:51 sounds good 19:32:56 maxamillion: you can also directly comment on 167 if you want :) 19:33:03 167 seems good to start a meeting with, not to end with:) 19:33:09 yeah, sorry ... I'm multitasking badly and didn't notice the lagtime on that one 19:33:12 lol 19:34:34 wow, 30 mins build time for the docsite 19:35:04 yeah it runs faster than I thought 19:35:31 the nice thing is that with it, everyone can take a look at the log output ... in particular see which collections/plugins are causing trouble 19:36:13 30 minutes is speedy for the docs build! 19:36:18 nice work 19:36:20 yeah eventually I'd like to start tackling some of those warnings and other issues and try to get clean build logs 19:36:34 30 minutes is speedy? 19:36:36 ouch 19:36:50 comparatively, yes maxamillion esp. since collections 19:36:54 sphinx with a huge amount of .rst files and cross-references is slow :) 19:37:07 oof 19:37:08 it took a pretty chonky vm to get it to run. m5.xlarge. and I tried a few different options, like using a smaller instance and setting the CPUS with the make command. 19:37:38 is it cpu bound or i/o bound? 19:37:59 there's definitely a high memory requirement 19:38:27 ah, that sounds right ... probably a lot of deeply nested dicts 19:38:44 yeah, and LOTS of references (also thanks to breadcrumbs) 19:38:44 yeah, memory was usually the constraint 19:39:03 breadcrumbs are really nice, but also make sphinx really eat up memory 19:39:03 the end result is worth it, from a user experience perspective 19:39:07 but it is a slow beast 19:39:08 I agree 19:39:30 so do folks here think this is going to be a good option? shall we proceed? 19:39:34 the linux kernel uses sphinx these days, I wonder long it takes to build their docs 19:39:55 errr sorry, none of that is relevant .... I'll take my curiosities offline :) 19:40:09 Don Naro: is it at a point where someone from community could give it a try for test site only? 19:40:10 Don Naro: sorry, I've lost track of what we are (or are not) proceeding with . . . ? 19:40:23 nm, found the issue 19:40:26 sorry, acozine I mean the gh action 19:40:33 ah ok. yeah 174 19:40:58 oranod: does the GH action also publish to docs.ansible.com? 19:41:02 samccann: that's a good call. maybe I can set it up for docs.testing.ansible and let folks try it out. 19:41:11 (or is that the goal, but not there yet?) 19:41:19 ah 19:41:25 in any case, I like this :) 19:41:29 yeah my nickel would be to have it for test only so people can kick the tires and not impact actual user docs 19:41:38 felixfontein: not just yet but that's the goal. the "publish" is basically an rsync of html to a web server. 19:41:54 +1 for let's try it for docs.testing and get some feedback 19:42:03 especially being able to look at the logs without bugging the docs team or someone else with access :) 19:42:30 ok, thanks. that sounds great and I'll set it up a "live" demo for folks to play with. 19:42:51 I'll move on to the next thing I wanted to ask if that's ok 19:42:53 cool, thanks a lot! 19:42:54 sure 19:43:00 #link https://github.com/ansible-community/community-topics/issues/175 19:43:24 for this one samccann and I have been working on some docsite personas and we would like to get feedback 19:44:16 we're using these personas to help create better entry points to Ansible documentation and map out user journeys 19:45:01 @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting 19:45:06 if folks could please have a look at the personas here: https://hackmd.io/pZb5w5JFRQW3RJ73n23tlw?both#/ 19:45:06 and then add comments to the hackmd or to the issue, that'd be deadly 19:45:38 #info Please take a look at docsite personas defined here: https://hackmd.io/pZb5w5JFRQW3RJ73n23tlw?both#/ 19:46:01 thanks felixfontein forgot the info tag! 19:46:50 aaaaw https://i.imgur.com/aseD8ux.png :) 19:46:54 #info Please also feel free to look at the demo docsite here and provide feedback. this might help demonstrate how we're putting those personas to use: https://people.redhat.com/dnaro/docsite-demo/ 19:47:31 just bear in mind that the demo docsite is still very much a wip. I really only started with it earlier today so there is a lot to be done yet. 19:48:09 yeah the demo site gives an idea of the proposed 'flow'... and it uses those personas to start each journey so to speak (new user, creator, developer, etc) 19:48:51 Don Naro: we should probably hold a VOTE on the docsite personas at some point, just so we know people are looking at it etc 19:49:52 samccann: what would the vote achieve? +1 indicates you feel the personas are ok and complete? 19:50:11 yes. It's just a way to document that yes, people actually read it etc 19:50:23 otherwise we go hog wild and someone complains they never heard of it etc 19:50:40 sgtm 19:50:44 +1 19:51:03 the vote would need to say what to do if you don't want to add +1 because you disagree with something ;) 19:52:26 A so a new community-topic to say 'discuss personas' and then in discussions, a VOTE to actually cast the vote? 19:54:20 a vote while the thing is still modified sounds a bit strange to me 19:54:47 ok so 1 week discuss, then at next thurs. meeting we have an issue to vote? 19:55:29 sounds good. make sure to announce it in bullhorn and all over irc/matrix :) 19:55:59 I plan to hit the bullhorn tomorrow and ask for feedback 19:56:05 :+1: 19:56:24 woot! happy to see progress on this. Thanks Don Naro 19:56:37 +1 19:57:21 ok, let's have a quick open floor :) 19:57:23 #topic open floor 19:57:31 does anyone have something quick for the last few minutes? 19:57:38 Nothing to discuss, just FYI: I'm not sure if you've seen this, but there are now some scripts that I hope can be helpful to generate the text for Bullhorn announcements. At least for some of our community processes: https://github.com/ansible-community/community-topics/tree/main/scripts 19:57:58 I really like scripts for that 19:58:04 we should add more :) 19:58:05 +1 19:58:19 automate all the things!! 20:01:02 ok, thanks everyone! 20:01:04 #endmeeting