---
# System prepended metadata

title: cfgmgmt camp 2023 discussions
tags: [contributor summit]

---

# cfgmgmt camp 2023 discussions
###### tags: `contributor summit`

[Agenda](https://cfgmgmtcamp.eu/ghent2023/schedule/)

# Monday
## Other Discussions
## State of the Ansible Community 2023

~60 people
* Mailing List: Some know about it, more than Greg expected
* FIX: Contirbutor Graph core -> ansible/ansible
* Tenents
    * Strong Mission: 5
    * Transparency: 1 
    * Tolerance: Most
    * Decentralization: Most
    * Fair Authority: zero
    * Free Entry: 1/3->1/4
* Should we have a new Website: All
* Yes to forum: Most



## Seamless and Automated Integration with Ansible

* Zero resource module users
* Zero network automation folks
* 

## Making Ansible playbooks to configure Single Sign On for popular open source applications

* Likely to be used by 20+T
* speaker has great energy

## Writing Ansible automation content made easy with Ansible developer tools

* Basic questions around how to use execution environment usage
* Improving EE adoption (more docs around EE might help)

## Recording Ansible building Ansible with Ansible and testing it with Ansible


# Tuesday
## Other Discussions

## Terraforming with Ansible
* Love that we are calling out what's not in scope
* About 5 folks using AAP
* Need to include the links with the video & write-up 
* Q: Any plans to integrate with Terra Grunt 

## Under the hood: how ARA Records Ansible playbooks and makes them easier to understand and troubleshoot
* Most had attended his talk yesterday 
* Add list of callbacks mentioned in slides to Ansible awesome 

## Building an Ansible AAP cluster - Design and implementation
* ~4 folks had seen/used AAP

## Build and operate internal developer platforms with Ansible
## Event-Driven Ansible: Advancing your automation
## Making your project documentation flow

# Wednesday - Contributor Summit

Greg's State of the Community
* General support for new community website
* Forum discussion suggests SSO is important
* email and github integration is a must

Walter's Wisdom presentation
* presented as opt-out
* someone asked about the licenses used and the risks (aka copilot problems) (under legal review)
* how does it compare with co-pilot (answer - trained soley on ansible content, not generalized)
* Two questions about the availability of an API - not at this time.
* roadmap - community version available end of March, with launch at Summit in May (tentative)
* Two services - community and enterprise (Certified collections)
* content explanation and something else is only in enterprise
* Question about the model - dataset will be available but not the model.
* question about having to be opt-in in order to use the service. Answer is no, you don't have to contribute content to use the community version
* question about plugin generation - not on the roadmap

Don's Persona-led documentation journey
* dmsimard - draws distiction between maintainer and contributor developer. It's a different workflow to maintain a collection vs patch a bug somewhere. Maybe it is the community maintainer?
* user-journey mindmap - got positive feedback that the journeys are a great tool. 
* jinja2-docsite - links change, be careful on how we'll keep the links fresh from these html pages to the docsite. All links will be in one yaml file and use /latest/ as much as possible.
* don't over-engineer a static site generator. (general feedback is this jinja2-docsite is fine instead of some fancy static site generator)
* Someone suggested mkdocs (less complicated than sphinx). It's also being used today in galaxy and devTools. 
* Think about the longterm requirements (images, language customizations? etc) - maybe it needs rst for fuller functionality.

Joe & Walter's EDA
* dmsimard - using rulebooks outside of aap/awx (yesterday's demo)
* what kind of even-sources do people want to see and will community create them. (these are in the form of collectoins)




# Retrospective
It's always good to think about what we can improve on
Think about FOSDEM, cfgmgmt camp, Contributors Summit
* Booth
    * QR/Links to
        * Signup to Bullhorn
        * Join Matrix
    * Something interactive?
    * Diagram of everything in the ecosystem
    * Badger2040 eink badges :stuck_out_tongue:
    * Signs around stairs, etc 
* Print out agenda 
    * (might be challenging when the schedule isn't finalized until a couple days before the event, last minute changes.)
* Should we promote/sumerise the talks & livestreams in #User (rather than #Social)?
* ansible.com/community add bullhorn link
* Random stuff
    * Can we do our own Meetup Map?
    * what is this ansible.scm collection mentioned in the playbook on the screen? I can't find it on https://galaxy.ansible.com/ansible
    * https://quay.io/repository/ansible/ansible-builder?tab=tags&tag=latest 
    * is there an update when the community EE base images https://quay.io/repository/ansible/ansible-runner?tab=tags&tag=latest will be updated?
    * Should we have dedicated notetakers on our sessions so we capture feedback directly (aka don't forget)?
    * About half the room hadn't heard of Project Wisdom
    * Zero folks know about ansible/awx-resource-operator
        * Carol's idea of having a demo/Instruqt for it 
    * Greg to chase https://meta.discourse.org/t/urls-being-dropped-from-thunderbird-generated-replies/163751/30
* speaker guidelines
    * dark mode sucks, small fonts, etc.
    * Doubly so for people doing recorded demos
    * speakers should always put "where to join in" info - rooms, issues, etc
    * need clear "Call to Action" on the last slide, which they leave onscreen when doing Q&A (not the Thanks/Red Hat Link page)

FIXME: Tab complete wbentley
FIXME: Starting in NNN minutes

:bell: `Event-Driven Ansible: Advancing your automation` by Ricardo Carrillo Cruz & @wbentley15

>Red Hat recommends a “start small, think big” approach to automation. Event-Driven Ansible can help you get to the next level of sophistication when it comes to automating your digital landscape. Learn about this new pattern for Ansible, and see how it can help you solve problems more quickly and eliminate basic but important tasks so you can focus on your key priorities and deliverables.

## Livestreams:
* [Ansible Room, Feb 6](https://www.youtube.com/watch?v=cv-djb_gc18)
* [Ansible Room, Feb 7](https://www.youtube.com/watch?v=xz2QBv0Work)
* [BCon room, Feb 7 (including Walter's and Don's talks)](https://www.youtube.com/watch?v=XeAegYEojGI)
* [Contrib Summit Part 1, Feb 8](https://www.youtube.com/watch?v=y9mpfKP-wO8)
* [Contrib Summit Part 2, Feb 8](https://www.youtube.com/watch?v=8zF-50cWg7U)

## Recordings:
* [Greg Sutcliffe -- State of the Ansible Community](https://www.youtube.com/watch?v=B-AODeqjvss)
* [Greg (gwmngilfen) Sutcliffe -- Community Plans](https://www.youtube.com/watch?v=ezaX-cHlN-g)
* [David Moreau Simard -- How ARA Records playbooks and makes them easier to troubleshoot](https://www.youtube.com/watch?v=IXSqwIbUaIw)
* [Ton Kerstens -- Building an Ansible AAP cluster](https://www.youtube.com/watch?v=eqcmFIeWWLs)
* [Ricardo Carrillo Cruz -- Build and operate internal developer platforms with Ansible](https://www.youtube.com/watch?v=sA9ZXTgPcVk)
* [Walter Bentley + Ricardo C. Cruz -- Event-Driven Ansible: Advancing your automation](https://www.youtube.com/watch?v=Y2y0EXcoy2k)






