#Triaged core critical

Thanks to everyone for all the work on this thread. I’ve read through the discussion, and it seems like setting English as the default langcode for configurations could be a straightforward way to avoid language conflicts during module installs. Here’s a quick summary and a few ideas on how we might combine some of the suggestions:

1. Default Configurations to English (langcode: en):
   
   Setting langcode to English across all module configurations would help avoid conflicts and keep things consistent, especially on multilingual sites. This way, English serves as the base, with other languages applied as overrides as needed.
2. Combined Contrib Module and Migration Path for Legacy Sites:
   
   For older sites, a contrib module could help automate the migration to this new standard. It could convert non-English langcode values to English and move existing language settings into overrides. This module could also support language overrides and protect configurations during updates.
3. Temporary Workarounds (config_ignore):
   
   While config_ignore and similar modules are useful right now, moving to a standardized langcode approach would eventually make these workarounds unnecessary, simplifying language management.