CMI 2 meeting - 2020-02-19 [#3114639]

Meeting will happen in #config on drupal.slack.com.

---

Hello and welcome to this CMI 2.0 meeting!

This meeting:
➤ Is for core and contributed project developers as well as people who have an interest in advancing the configuration management capabilities of Drupal.
➤ Usually happens every other Wednesday at 16:00 UTC.
➤ Is done over chat.
➤ Happens in threads, which you can follow to be notified of new replies even if you don’t comment in the thread. You may also join the meeting later and participate asynchronously!
➤ Has a public agenda anyone can add to: `https://www.drupal.org/project/drupal/issues/3114639`
➤*Transcript will be exported and posted* to the agenda issue. For anonymous comments, start with a :bust_in_silhouette: emoji. To take a comment or thread off the record, start with a :no_entry_sign: emoji.

---

Ping @bircher @alexpott @diosbelmezquia @mtodor @ricardoamaro @borisson @jcandan @marcvangend @Kingdutch @phenaproxima @balsama @wouter @mikemadison (Edit https://www.drupal.org/node/3114639 if you do or don't want to be pinged)

---

0️⃣ Who is here today? Comment in the thread below to introduce yourself.

bircher	Hi, I am Fabian Bircher, CMI 2 co-coordinator maintainer of config split and a few others
phenaproxima (he/him)	Adam, from Acquia, in Boston, and mostly a-lurkin’
alexpott	Hullo Alex Pott core maintainer and CMI laggard
mtodor	Mladen (maintainer of update_helper module and Thunder distribution)
kingdutch	Alexander, developer for Open Social. Won’t be actively attending, but will see pings if you need me : )
borisson_	:wave: Joris - about to drive home from work, will catch up when I'm home.

2️⃣ Installing from config and install hooks of profiles

bircher	Did we reach a conclusion last time?
bircher	https://www.drupal.org/node/2357215https://www.drupal.org/node/2982052ht...
alexpott	I was going to comment on the issues after the last meeting but I’ve failed to.
bircher	I think the conclusion was to add a new hook only for the currently installing profile that gets called at the end of the installation. ie afterinstall_install_profile

3️⃣ Config environment: review next steps

bircher	#3033427: [plan] Add support for environment-specific configuration
bircher	Still the same as last time I guess..
borisson_	Yeah, I didn't get around to doing anything, so I don't think there is anything to review for now.

4️⃣ Contrib projects updating to the new transformation API

phenaproxima (he/him)	Is there documentation yet for this API? I’d be interested in learning more!
bircher	good question, it is a new event that gets dispatched when importing and exporting config
bircher	config_ignore has a patch
alexpott	@phenaproxima (he/him) ie. #3099674: Create 3.x version using the new Drupal 8.8 API
phenaproxima (he/him)	Ah, okay! This is useful.
bircher	@phenaproxima (he/him) or https://www.drupal.org/node/3050529
bircher	that one was probably the first one to use the new API..
clau	@bircher #3099674: Create 3.x version using the new Drupal 8.8 API has now tests and is green. I would appreciate if you can take a look
bircher	@clau thanks for the heads up. I will look into it!

5️⃣ Other contrib updates to share

alexpott	D9 config component is deprecation-free - #3112639: Remove all @deprecated code from config component
kingdutch	Open Social has started playing with the update_helper module and really like it.We may decide that we don’t need the flexibility Config Distro provides on top of it.Real conclusion for us is still a bit open, but that may impact the issue we created in the Config Distro issue queue.
bircher	@kingdutch are you going to use the update hook system then?
kingdutch	That would probably be what ends up happening.Some of the considerations we had today:- Update hooks allow definition of order, which can be more easily orchestrated with possible other required changes (e.g. non-config things).- Thought is required on what we ship for configuration changes either way. We suspect that a lot of configuration changes that we would ship is non-optional (otherwise they are probably not needed). So not applying them may break assumptions of some of our functionalities.That second one may be a bit specific to the opinionated nature of Open Social though.
kingdutch	The 8.0 release also took us quite a bit longer than expected so there’s less time on our end to invest into expanding tools if we don’t find a large advantage over something that’s already out there.
bircher	makes sense
andypost	I'm in progress of review state of domain module, looks no much affected[#3090180] (edited)