19:01:12 <felixfontein> #startmeeting Ansible Community Meeting
19:01:12 <zodbot> Meeting started Wed Dec  7 19:01:12 2022 UTC.
19:01:12 <zodbot> This meeting is logged and archived in a public location.
19:01:12 <zodbot> The chair is felixfontein. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
19:01:12 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
19:01:12 <zodbot> The meeting name has been set to 'ansible_community_meeting'
19:01:12 <felixfontein> #topic Agenda https://github.com/ansible/community/issues/645
19:01:16 <felixfontein> 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:01:21 <felixfontein> The ping list is stored at https://kutt.it/meeting-people. Feel free to add or remove yourself.
19:01:24 <felixfontein> #info Agenda: https://github.com/ansible/community/issues/645 / Topics: https://github.com/ansible-community/community-topics
19:01:27 <felixfontein> #topic Updates
19:01:47 <cybette_> o/
19:01:51 <felixfontein> #chair cybette_
19:01:51 <zodbot> Current chairs: cybette_ felixfontein
19:02:01 <oranod> o/
19:02:10 <felixfontein> #chair oranod
19:02:10 <zodbot> Current chairs: cybette_ felixfontein oranod
19:02:24 <cybette_> #info Ansible 6.7.0 has been Released! https://groups.google.com/g/ansible-devel/c/3SAbTPNFBM4
19:02:31 <cybette_> #info New release: ansible-core 2.14.1 https://groups.google.com/g/ansible-devel/c/AGqD9SR1D5I
19:02:49 <cybette_> #info Ansible 7.1.0 has been released! https://groups.google.com/g/ansible-devel/c/5yzi2ye9cPM
19:02:59 <cybette_> #info Cfgmgmtcamp registration is open! https://registration.cfgmgmtcamp.org/ghent/2023/ If you're planning to attend Ansible Contributor Summit, please also select Workshop/Fringe day!
19:03:49 <cybette_> #info New release: ansible-core 2.13.7 https://groups.google.com/g/ansible-devel/c/hGR4LnAkeCw
19:03:54 <maxamillion> .hello2
19:03:55 <zodbot> maxamillion: maxamillion 'Adam Miller' <maxamillion@gmail.com>
19:04:01 <maxamillion> o/
19:04:27 <felixfontein> #chair maxamillion
19:04:27 <zodbot> Current chairs: cybette_ felixfontein maxamillion oranod
19:05:53 <anwesha[m]> Hey everyone
19:06:23 <felixfontein> #chair anwesha[m]
19:06:23 <zodbot> Current chairs: anwesha[m] cybette_ felixfontein maxamillion oranod
19:06:56 <felixfontein> so, what do you folks want to talk about today?
19:07:03 <oranod> #info The Ansible docsite repo is now public. This repo contains the static HTML and assets for the layout and navigation on docs.ansible.com so the community can now fork it and make changes. You can find it at: https://github.com/ansible/docsite
19:07:24 <acozine> o/
19:07:31 <acozine> Great news Don Naro
19:07:59 * felixfontein just cloned it
19:08:11 <acozine> so many redirects
19:08:16 <oranod> Cheers acozine Another step towards opening up the entire publishing toolchain.
19:08:20 <oranod> yeah, so many redirects
19:08:36 <oranod> got to love them
19:09:03 <oranod> felixfontein: if there's room on the agenda I could bring up another item related to the docsite for discussion.
19:09:09 <felixfontein> #info Steering Committee members, please look at the vote https://github.com/ansible-community/community-topics/discussions/169 on the release schedule of Ansible around the winter holidays
19:09:32 <felixfontein> oranod: so far nobody had something for the agenda, so sure, we can talk about that :)
19:10:35 <oranod> #info We're planning a Proof of Concept for the Ansible docsite. details in https://hackmd.io/MguEzoFwT2GAg6IJ7J6xKw
19:11:16 <russoz[m]> o/
19:11:20 <felixfontein> #chair russoz[m]
19:11:20 <zodbot> Current chairs: anwesha[m] cybette_ felixfontein maxamillion oranod russoz[m]
19:12:07 <felixfontein> oranod: that definitely sounds interesting!
19:12:21 <KeyboardInterrup> As this is the first time, I am around for a Community Meeting, what are the chairs about? :)
19:12:27 <felixfontein> oranod: is that the topic you want to bring up?
19:12:32 <felixfontein> #chair KeyboardInterrup
19:12:32 <zodbot> Current chairs: KeyboardInterrup anwesha[m] cybette_ felixfontein maxamillion oranod russoz[m]
19:12:34 <oranod> This is something I've been talking about with ssbarnea and a couple other folks. I'm actually a little behind in mentioning it to webknjaz as well. but the idea is to evaluate some options that will help us create a next version of the docsite.
19:12:49 <maxamillion> KeyboardInterrupt: the chairs have the ability to give the meeting notes bot commands
19:13:11 <oranod> felixfontein: yeah, that's the topic. but I'm specifically interested in finding out what the broader community needs are and to make sure those are reflected in the POC requriements.
19:13:47 <felixfontein> #topic POC for a new Ansible docsite
19:13:53 <felixfontein> #link https://hackmd.io/MguEzoFwT2GAg6IJ7J6xKw
19:14:05 <oranod> ah, nuts. yeah. forgot the topic hashtag.
19:14:08 <oranod> thank you
19:14:29 <maxamillion> KeyboardInterrupt: also, welcome!
19:14:43 <oranod> yeah. welcome KeyboardInterrupt
19:14:54 <cybette_> welcome KeyboardInterrupt !
19:15:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
19:15:52 <anwesha[m]> Welcome KeyboardInterrupt
19:16:06 <KeyboardInterrup> thanks :)
19:16:19 <oranod> What might be the best way to ensure the docsite POC meets the community needs? Should I create a community discussion topic and let folks add thoughts there?
19:16:35 <acozine> So this is a step toward having all projects represented as `docs.ansible.com/<project_name>/`?
19:16:36 <felixfontein> oranod: I guess this is more about projects like ansible-lint, ansible-builder, ..., and not so much about ansible content (collections, roles)?
19:17:16 <gotmax> oranod: Yeah, creating a community-topics ticket and announcing it on the bullhorn
19:17:34 <acozine> instead of having some projects documented on readthedocs or elsewhere
19:17:41 <russoz[m]> oranod: This looks promising! I for one am interested in writing docs for some module utils (in c.g. at this point), and I haven't found the place to put them yet. This looks like something that could be figured out in this context.
19:18:43 <oranod> felixfontein: and acozine correct, yes. finding mechanisms to allow projects to get their content on `docs.ansible.com`
19:19:21 <acozine> with the docsite repo now public, folks could add entry points for those projects there, too
19:19:51 <maxamillion> is the Ansible SDK listed in that hackmd this thing https://github.com/ansible/ansible-sdk/ or something else?
19:19:54 <felixfontein> russoz[m]: that's a tricky thing... I don't think these would be covered by that, but they should better use extra-docs in the collection... but then we have a strange mix of user content and dev content on the collection's docsite
19:21:11 <russoz[m]> Maybe we could come up with a standard way to do it, that's what I was thinking
19:21:49 <felixfontein> yes, that would be great
19:21:56 <oranod> russoz: I think we're aligned with that. I've been thinking about how to approach it. maybe we could discuss this a bit more when you're ready to start writing.
19:21:58 <russoz[m]> But I can see how that is still a bit tricky
19:22:55 <oranod> it is def a bit tricky. there is so much content out there.
19:23:06 <acozine> dang, the building inspector is here, sorry to duck out but I want to make sure they sign off on our renovations
19:23:19 <felixfontein> maybe have another docs/docsite/ directory in the collection that's mapped to dev/ instead of docsite/ in the collection's RST directory, and have a separate index for the collections having that? like a developer index?
19:23:24 <acozine> looking forward to the continuing conversation!
19:23:37 <felixfontein> acozine: as long as it's not the docs building inspector :)
19:23:41 <oranod> acozine: to your point about the docsite, I actually have a PR in the works for that already at: https://github.com/ansible/docsite/pull/125
19:23:51 <russoz[m]> And different types of content - some will have docs, some will not
19:24:22 <oranod> also maxamillion that is the SDK, yeah
19:25:28 <russoz[m]> felixfontein: Hmm, I like the idea
19:26:34 <russoz[m]> But one thing I am not very familiar with, yet, is the docs building processes here
19:27:15 <maxamillion> Don Naro: +1
19:28:38 <oranod> I'm probably not 100% on the full picture for the docs building process around collections. but for what goes into docs.ansible.com at the moment there are several Jenkins jobs that Sphinx build docs then rsync the generated HTML to a web server.
19:28:50 <felixfontein> russoz[m]: it's mainly done by antsibull-docs
19:29:10 <felixfontein> (the one for integrating the collection docs into docs.ansible.com/ansible/xxx/)
19:29:12 <oranod> and then there's antsibull-docs lol
19:29:46 <felixfontein> :D
19:30:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
19:30:01 <oranod> really I guess this is one of the things I need to familiarize myself with a lot more so that we take that fully into account
19:30:32 <oranod> anyway I can stop talking and will put some details into the community-topics then get to the bullhorn to gather more details about requirements.
19:31:22 <oranod> I am glad to hear that the POC idea is interesting to everyone here though. that kind of makes my night. so thanks!
19:31:40 <gotmax> russoz[m]: I'd assume docstrings are a good start for module_utils docs. It would be nice to have Sphinx docs for module_utils in both collections and core.
19:32:24 <felixfontein> gotmax: that will probably blow up the docs build if that's integrated in the current docsite build...
19:33:02 <felixfontein> (sphinx is a memory hog, and the ansible package generates a huge docsite)
19:34:41 <samccann> coming in way late o/
19:34:53 <felixfontein> #chair samccann
19:34:53 <zodbot> Current chairs: KeyboardInterrup anwesha[m] cybette_ felixfontein maxamillion oranod russoz[m] samccann
19:37:24 <russoz[m]> Thank you Don Naro :)
19:38:05 <felixfontein> ok, is there something else folks want to discuss?
19:38:36 <oranod> you're welcome russoz feel free to ping me directly if you want to talk about the module utils docs etc. I'd be curious to learn more about that any way.
19:38:58 <anwesha[m]> I have a question. To my knowledge we go to the core members to get the information if there is any release blocker or not. Do we have a central location to find the release blockers?
19:40:08 <felixfontein> not that I know off
19:40:11 <felixfontein> #topic open floor
19:40:39 <felixfontein> it would be nice to have that though...
19:40:47 <anwesha[m]> Can we have one? A single source of truth for the information relating to release blockers? Such as a Github issue, tag for issue (release blocker) or something else?
19:41:51 <felixfontein> for the community Ansible release, sure. for ansible-core, I guess we'd have to ask core
19:44:32 <felixfontein> for Ansible, we could use issues in ansible-build-data with a special label
19:44:42 <felixfontein> or do you want a unified place for both ansible-core and Ansible?
19:45:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
19:45:22 <anwesha[m]> felixfontein: okay, I was talking about community Ansible release.
19:46:05 <felixfontein> anwesha[m]: in that case I think ansible-build-data would be perfect
19:46:06 <samccann> well community release can be blocked by a blocked core release, right?
19:46:20 <felixfontein> samccann: yes, like Ansible 7.1.0 :)
19:47:18 <anwesha[m]> Who are the people who are going to file the blocker issues?
19:48:14 <felixfontein> that's a very good question...
19:48:34 <russoz[m]> Folks, sorry, I have to go now. Good evening/afternoon/morning 😁
19:48:37 <felixfontein> in the past we only had blockers for X.0.0b1, or potentially for X.0.0 itself
19:48:43 <felixfontein> bye russoz[m]! have a great day!
19:49:11 <gotmax[m]> I feel we should mention ansible-build-data in ansible PyPI description or somewhere. It's not very visible.
19:49:38 <felixfontein> as long as folks don't start creating support issues in there then :)
19:49:50 <gotmax[m]> Also, we'd need to have a clear split between what should be reported to ansible-build-data and what should be reported to collections
19:50:14 <gotmax[m]> and what should be asked in #users:ansible.com or #ansible or some other support forum :)
19:51:16 <samccann> what sorts of things get reported on ansible-build-data?
19:51:20 <samccann> just curious
19:52:08 <felixfontein> so far, almost nothing
19:52:20 <anwesha[m]> russoz: see you, have a wonderful day
19:52:46 <gotmax[m]> https://github.com/ansible-community/ansible-build-data/issues?q=is%3Aissue. Most of it is just administrative stuff
19:53:27 <felixfontein> https://github.com/ansible-community/ansible-build-data/issues/114 was a proper report
19:53:44 <gotmax[m]> BTW, I have a short update on the ansible source dist thing
19:53:50 <felixfontein> https://github.com/ansible-community/ansible-build-data/issues/28 maybe as well, but all others were more administrative
19:53:59 <anwesha[m]> Who decides whether the issue is a release blocker or not?
19:54:15 <gotmax[m]> felixfontein: yup. Side note: this is why collections need to run sanity tests :)
19:54:22 <felixfontein> anwesha[m]: for the x.0.0 release, I'd guess he Steering Committee
19:54:31 <felixfontein> though we didn't have a potential blocker for a longer time
19:54:38 <felixfontein> gotmax[m]: oh yes, definitely!
19:55:25 <felixfontein> anwesha[m]: but yes, that's not really properly specified anywhere I think
19:56:04 <samccann> thanks felixfontein for the example issues. helps me understand the conversation :-)
19:56:09 <anwesha[m]> Okay understood.
19:56:42 <samccann> should we propose something for how an Ansible package blocker should be reported and then voted on etc?
19:57:22 <felixfontein> anwesha[m]: in the past when we were voting in the community meeting, we moved the meeting so that we could vote a few days before the releases how to proceed. but now since we do almost everything asynchronous, that no longer works
19:57:44 <felixfontein> samccann: that's probably a good idea
19:57:47 <anwesha[m]> okay.
19:57:59 <felixfontein> though we should also include some indication what will count as a blocker, and in which cases
19:58:36 <anwesha[m]> I think we should come up with the definition/scope of a release blocker and whole life cycle of it.
19:58:48 <samccann> so it starts as a discussion - what would be a blocker, and how should we deal with it, decide go/nogo on potential filed blockers etc?
19:59:05 <felixfontein> :+1: to both
19:59:08 <samccann> ..yeah what anwesha said :-)
20:00:34 <felixfontein> does anyone want to start a discussion topic in community-topics on this?
20:01:38 <anwesha[m]> Yes, I can
20:01:53 <felixfontein> cool, thanks a lot anwesha[m]!
20:02:07 <felixfontein> ok, if nobody has anything else, I'll close this meeting for today
20:02:46 <felixfontein> #endmeeting