Voting starts in March for the Drupal Association Board election.
Since date formats in shipped config are going to end up on localize.drupal.org, they need to have a context to be able to identify them. Strings like "Y" or "m-d" will be confusing for translators, without a context.
@Gabor mentioned there was some discussion for adding context to schema in general, but I couldn't find an issue.
I'm not familiar with core's config translation, so I'd like to know how big (or small) of a change would it be to add context (for date_formats at least) in core? Is it even possible?