hybridgroup/gobot

avoid master/slave terminology

gen2thomas opened this issue · 1 comments

gen2thomas commented

SPI: redefine signal names, see: https://www.oshwa.org/a-resolution-to-redefine-spi-signal-names/

  • MOSI/MISO/SS --> SDO/SDI/CS
  • Master/Slave --> Controller/Peripheral
gen2thomas commented

Additionally:

  • same as above for usages in I2C, use "controller/target", following the NXP decision, i2c-bus.org
  • substitute wrong github-paths https://github.com/hybridgroup/gobot/<blob/tree>/master to the "release" path
  • master.go with manager.go, same for related types
  • search for remaining occurrences of "master" and replace e.g. by one of the following names:
    controller, default, director, host, initiator, leader, manager, primary, principal, root
  • search for remaining occurrences of "slave" and replace e.g. by one of the following names:
    agent, client, device, performer, peripheral, replica, responder, satellite, secondary, subordinate, worker