1. Can I replace master:slave with primary:secondary everywhere in the code and the CLI? Are there any suggestions for more appropriate terminology?
>> Other options could be - Leader : follower 2. Is it okay to target the changes to a major release (release-9) and *not* provide backward compatibility for the CLI? >> I hope so as it is not impacting functionality. ---- Ashish ----- Original Message ----- From: "Ravishankar N" <ravishan...@redhat.com> To: "Gluster Devel" <gluster-devel@gluster.org> Sent: Wednesday, July 22, 2020 2:34:01 PM Subject: [Gluster-devel] Removing problematic language in geo-replication Hi, The gluster code base has some words and terminology (blacklist, whitelist, master, slave etc.) that can be considered hurtful/offensive to people in a global open source setting. Some of words can be fixed trivially but the Geo-replication code seems to be something that needs extensive rework. More so because we have these words being used in the CLI itself. Two questions that I had were: 1. Can I replace master:slave with primary:secondary everywhere in the code and the CLI? Are there any suggestions for more appropriate terminology? 2. Is it okay to target the changes to a major release (release-9) and *not* provide backward compatibility for the CLI? Thanks, Ravi _______________________________________________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
_______________________________________________ Community Meeting Calendar: Schedule - Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC Bridge: https://bluejeans.com/441850968 Gluster-devel mailing list Gluster-devel@gluster.org https://lists.gluster.org/mailman/listinfo/gluster-devel
