CMI2 meeting - 2019-11-17 [#3178719]

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/3094199`
➤*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.

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

mtodor	here, maintainer of Thunder distro and update_helper module
borisson_	:wave:
bircher	Hi, bit late to the party

1️⃣ Do you have suggested topics you are looking to discuss? Post in this thread and we’ll open threads for them as appropriate.

mtodor	not thread on it's own => I just want to mention, that there is new release of update_helper (1.1) It fixes some bugs and improves developers experience when it comes to creation of CUDs.
alexpott	@mtodor congrats on the release! :slightly_smiling_face:
alexpott	@mtodor the update helper got an earlier shout in the channel from @kingdutch see #3097142: Make Update Helper work as source for the Config Distro module

I guess I could have come up with a topic for discussion today :disappointed: but with @bircher out and the rtbc queue at 3 pages and $work today I’m lacking inspiration. Sorry everyone.

:two: So in lieu that I’m going to post some issues I’d love to see progress on :slightly_smiling_face:
:two: :one: https://www.drupal.org/project/drupal/issues/2914174 - this is a key documentation task. I also think we could consider adding a argument to the hook so it’s more in developers faces when writing implementations.
:two: :two: https://www.drupal.org/project/drupal/issues/2628144
:two: :three: https://www.drupal.org/project/drupal/issues/2762235

2️⃣ 4️⃣ #2571235: [regression] Roles should depend on objects that are building the granted permissions

kingdutch	I wasn’t here but I actually like the fact that we can assign permissions that don’t necessarily exist (yet, or due to optional modules) :thinking_face:Would this change that?
kingdutch	Something that I have more problems with (and may make a contrib module for, unless one exists already) is that permissions have to be assigned in hook_install.Why is there no module.desired_permissions.yml file that can assign permissions to roles that exist in the system when the module is enabled or when a new role that matches is created.