Voting starts in March for the Drupal Association Board election.
This is a follow-up in response to comment 100based on
When setting up translation, and translation is enabled on an entity, for example on a content type, it doesn't actually do anything. Each field (or property) needs to be edited and the translation enabled there also.
A) bulk enabling of the fields and properties that are enablable when translation is enabled on the entity.
B) default new fields to translation enabled when they are added to an entity that has translation enabled.
Work on this is being postponed until after feature freeze.
Mock up the ui change and add a screen shot.
Code up the bulk functionality.
User interface changes
Add a bulk enable to same location translation is enabled on entities.
The ui can stay the same(to control enabling or disabling individual fields and properties.
Are there API changes/additions that would affect module, install profile, and theme developers?
Background from et-ui part 2 issue summary
Auto-enable translatability on every field.