Re: Removing problematic language in geo-replication

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Wed, Jul 22, 2020 at 2:34 PM Ravishankar N <ravishankar@xxxxxxxxxx> wrote:
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?
primary:secondary looks good to me.

2. Is it okay to target the changes to a major release (release-9) and
*not* provide backward compatibility for the CLI?
This should be fine, as it is glusterd which passes the request to the peers. This will not cause any issue in the heterogenous cluster as well.


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@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel



--
Thanks,
Sanju
_______________________________________________

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@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-devel


[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux