18:00:40 <ompragash[m]> #startmeeting Ansible Community Meeting
18:00:40 <zodbot> Meeting started Wed Jul 13 18:00:40 2022 UTC.
18:00:40 <zodbot> This meeting is logged and archived in a public location.
18:00:40 <zodbot> The chair is ompragash[m]. Information about MeetBot at https://fedoraproject.org/wiki/Zodbot#Meeting_Functions.
18:00:40 <zodbot> Useful Commands: #action #agreed #halp #info #idea #link #topic.
18:00:40 <zodbot> The meeting name has been set to 'ansible_community_meeting'
18:00:57 <cyberpear> o/
18:01:08 <ompragash[m]> #topic Agenda https://github.com/ansible/community/issues/645
18:01:29 <ompragash[m]> #chair cyberpear
18:01:29 <zodbot> Current chairs: cyberpear ompragash[m]
18:01:34 <cybette_> o/
18:01:50 <ompragash[m]> #chair cybette
18:01:50 <zodbot> Current chairs: cyberpear cybette ompragash[m]
18:01:58 <mariolenz[m]> o/
18:02:32 <ompragash[m]> Felix is not around today so wish me luck;)
18:02:45 <ompragash[m]> #chair mariolenz
18:02:45 <zodbot> Current chairs: cyberpear cybette mariolenz ompragash[m]
18:02:57 <ompragash[m]> #info Vote on “Ansible 7 Roadmap Planning will end on 2022-07-20” https://github.com/ansible-community/community-topics/discussions/118
18:03:38 <cybette_> ompragash: good luck :) although you're doing fine, you don't need it!
18:03:59 <samccann> o/
18:04:01 <ompragash[m]> acozine andersson007_ baptistemm bcoca briantist cyberpear geerlingguy gundalow gwmngilfen ikhan_ jillr jtanner lmodemal misc nitzmahone resmo samccann tadeboro cidrblock thaumos zbr: ping!
18:04:08 <ompragash[m]> #chair samccann
18:04:08 <zodbot> Current chairs: cyberpear cybette mariolenz ompragash[m] samccann
18:04:18 <ompragash[m]> yay thanks cybette
18:04:38 <ompragash[m]> #topic Updates
18:07:04 <ompragash[m]> Any topics to discuss today?
18:07:38 <cybette_> #info We're starting the planning for the next Ansible Contributor Summit in October (along with AnsibleFest). Please pre-register here to get updates and for better planning of topics/content for the event - https://ansiblecs202210.eventbrite.com/?aff=matrix
18:08:56 <samccann> woot!
18:09:00 <cybette_> #info CFP for AnsibleFest is closing soon! Get your proposals in by this Friday July 15th: https://reg.experiences.redhat.com/flow/redhat/rhaf22/cfp/login
18:09:45 <cybette_> and thanks to everyone who has already pre-registered or submitted proposals!
18:11:12 <samccann> #info community-writers are available to help with collection docs PR reviews and simple docs issues - https://github.com/orgs/ansible-community/projects/3/views/1
18:11:32 <samccann> they don't know ansible but they do know writing :-)
18:12:12 <ompragash[m]> awesome!
18:13:04 <ompragash[m]> may be we should create one badge for these doc contributions
18:13:04 <cybette_> coolness :)
18:13:17 <cybette_> ompragash: great idea!
18:13:23 <samccann> oh yeah a badge would be great!
18:13:58 <samccann> a lot have been in the ansible/ansible repo but we are slowly extending our reach to willing collections :-)
18:14:23 <samccann> or any other ansible project really. Just still trying to get the word out
18:15:01 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:18:18 <ompragash[m]> samccann: talking about docs, do you think we can have a section that talks about `Notational Conventions` which refers [RFC 2119](http://tools.ietf.org/html/rfc2119) & [rationale for the C99 standard](http://www.open-std.org/jtc1/sc22/wg14/www/C99RationaleV5.10.pdf#page=18) like for example in collection/overview repo as we mention a lot of MUST SHOULD...
18:20:14 <mariolenz[m]> Well if there are no topics to really discuss, FYI: I'm getting somewhere with [removing collection specific documentation out of ansible core](https://github.com/ansible-community/community-topics/issues/91) 😃
18:20:18 <mariolenz[m]> Now that Ansible 6.1.0 is released, I could stub out the [community.vmware dev guide](https://github.com/ansible/ansible/pull/78255)
18:21:10 <samccann> ompragash: yeah we use that a lot in the collection/overview (which needs to be ported over to docs.ansible.com). We can add a section to say we use those terms as per RFC2119
18:21:31 <samccann> mariolenz: woot!  Thanks for tackling those! it's a great help
18:22:05 <cybette_> mariolenz ++
18:22:13 <ompragash[m]> mariolenz++
18:22:17 <samccann> I need to get similar momentum for all the scenario guides that should also move to their collections.
18:24:47 <samccann> #info docs WG will back out the docs override on boolean parameters that force yes/no on docs output. Related to https://github.com/ansible-community/community-topics/issues/116
18:24:47 <mariolenz[m]> Yes, but I think there are far more scenario guides than there are platform guides. This is a bit discouraging.
18:25:14 <samccann> mariolenz: yeah my goal is to start by opening issues where I think they need to move and see how many the collection owners move over time. But yep, it's a huge list!
18:27:17 <samccann> one other docs item that might be of interest. We are experimenting with redirects to force 2.3 docs traffic to /latest/ except for when the referrer is blank (aka abookmarked link) or when the referrer is docs.ansible.com (aka deliberately navigating to very old docs).
18:28:23 <samccann> The goal is to keep the docs available for those who really are using them, but get google to stop showing them as top search results when folks really need latest docs, not something 4+ years old.
18:30:00 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:30:32 <ompragash[m]> if a new user starts with ansible-2.3 now I wonder how they might feel about collections later when they get to know about it
18:32:18 <mariolenz[m]> As far as I understand, the problem is not users that start with 2.3 but when they search for documentation Google links to 3. Or did I get this wrong?
18:32:21 <samccann> i'll be honest, I'm less worried about the 2.3 new user vs the 2.9 users that haven't switched yet, but yeah, painful
18:32:28 <mariolenz[m]> 2.3, not 3
18:32:31 <samccann> mariolenz: you are correct
18:33:15 <samccann> Google is raising the visibiility of old docs and we want to prevent that without actually removing thedocs because there likely are some people on 2.3
18:33:27 <samccann> (this goes for all the other EOL releases as well)
18:33:27 <mariolenz[m]> Yeah, looks like there are a lot of users still on 2.9. From the issues I see in `communitty.vmware`, even more than people on 2.10.
18:33:49 <samccann> interesting to know mariolenz !
18:34:29 <samccann> 2.9 just EOL'd for community users. Still hasn't for RH customers
18:34:46 <samccann> so I think the transition wave is probably still coming
18:36:31 <ompragash[m]> customers are still on 2.9 and controller still supports it so once if the controller drops 2.9 support completely then we can see more users using newer versions of ansible
18:38:13 <ompragash[m]> #topic open floor
18:40:23 <ompragash[m]> if there's no other topic to discuss then I am afraid this is the shortest of any community meeting that happened so far ;-)
18:41:20 <samccann> haha they do get shorter now that we have a lot of async discussions on the community-topics
18:43:05 <ompragash[m]> true that
18:43:15 <mariolenz[m]> ompragash: You don't have to be afraid. Sometimes, it's a good sign if meetings are short. Could mean that things are running smoothly ;-)
18:43:29 <cybette_> plus it's summer, many people are on PTO or holiday perhaps? (especially now that travelling is possible)
18:43:57 * samccann shivers thinking about the docs meetings back when collections transition started.. and how we had to have TWO a week for a time, and still they both went over
18:45:00 <remindbot[m]> @cybette:ansible.im cyb-clock chimes every 15 minutes during the community meeting
18:45:02 <jtanner> big changes generally involve big meetings
18:45:55 <ompragash[m]> #endmeeting