On Wed, 15 Jul 2020 16:34:51 +0200, Pierre-Louis Bossart wrote: > > > > >> On 7/14/20 12:26 PM, Takashi Iwai wrote: > >>> Follow the recent inclusive terminology guidelines and replace the > >>> word "slave" in vmaster API. I chose the word "replica" at this time > >>> since it seems fitting for the purpose. > >> > >> Thanks Takashi for starting this. > >> > >> For the HDaudio Volume widgets, the spec says they may have different > >> step size but use the same number of steps, so they are not copy-exact > >> versions in the usual 'replica' sense but rather follow or track the > >> master configuration. > >> > >> The internal guidance I see at Intel is to use 'replica' mainly in a > >> database/configuration management context. > >> > >> If the idea is that the 'replicas' use the same configuration as the > >> 'master', that'd be fine indeed but we may want to add a clarifying > >> comment that the end-result may be different for each 'replica'? > > > > I don't mind to pick up another word. > > What could be another better alternative? > > I don't have a suggestion that is really better. the usual suggestions > of 'secondary' or 'subordinate' are not really great in this context, > something like 'tracker' or 'follower' might work but are maybe more > vague for controls. "Follower" would fit for the purpose, I think. (Or better to say "retweeter"? :) > I am really fine with 'replica', just wanted to clarify that it's not > doing the same thing in multiple places but using the same > configuration in multiple places. Yeah point taken. thanks, Takashi
