BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//cfp.cfgmgmtcamp.org//U7CGMZ
BEGIN:VTIMEZONE
TZID:Europe/Brussels
BEGIN:STANDARD
DTSTART:20001029T030000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10
TZNAME:CET
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20000326T020000
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3
TZNAME:CEST
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:pretalx-2020-U7CGMZ@cfp.cfgmgmtcamp.org
DTSTART;TZID=Europe/Brussels:20200203T140000
DTEND;TZID=Europe/Brussels:20200203T145000
DESCRIPTION:The [Foreman](https://theforeman.org) community maintains a [co
 llection of over 40 Ansible modules](https://github.com/theforeman/foreman
 -ansible-modules) for interaction with the Foreman API and the various plu
 gin APIs. This all started with two modules in `ansible/ansible` in 2016 a
 nd escalated from there.\n\nToday we want to share the lessons learned fro
 m these three years of module development and maintenance.\nIncluding:\n\n
 * efficient abstraction -- all modules talk to the same base API\, receive
  the same credentials and execute similar actions\, let's abstract that aw
 ay!\n* good tests -- nobody wants to break stuff\, but you have to `assert
 ` that.\n* migrating to new API libraries -- should be fairly easy with an
  abstraction layer\, right?\n* onboarding new contributors -- (un)surprisi
 ngly the hardest part after you've built something for your own needs.\n\n
 We also want to talk about what's next: How we can further improve and eas
 e the interaction? Which challenges we see in the future?
DTSTAMP:20260913T141154Z
LOCATION:B.1.017
SUMMARY:Maintaining over 40 Ansible modules: 4 years later - Evgeni Golov
URL:https://cfp.cfgmgmtcamp.org/2020/talk/U7CGMZ/
END:VEVENT
END:VCALENDAR