Voting starts in March for the Drupal Association Board election.
Config Translation introduces the concept of translation mappers so that arbitrary config objects can be translated with config translation forms. We even have a
ConfigMapperInterface::addConfigName() method so that contributed modules can control add their config objects to translation forms.
Sadly, though, contributed modules never actually get a chance to call that method at an appropriate time, so that de facto it's not possible to enhance config translation forms.
This came up inwhere Field UI module wants to alter the config translation mappers of various other modules. This is a Config Translation critical, but that probably still just makes it normal in the core queue.
Move the actual form building of the config translation form into #process, so that hook_form_alter() implementations have a chance to add config names.
User interface changes
Data model changes