[Gluster-devel] Removing problematic language in geo-replication

Aravinda VK aravinda at kadalu.io
Wed Jul 22 11:36:06 UTC 2020


+1

> On 22-Jul-2020, at 2:34 PM, Ravishankar N <ravishankar at redhat.com> 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.

> 
> 2. Is it okay to target the changes to a major release (release-9) and *not* provide backward compatibility for the CLI?

Functionality is not affected and CLI commands are compatible since all are positional arguments. Need changes in

- Geo-rep status xml output
- Documentation
- CLI help
- Variables and other references in Code.

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

Aravinda Vishwanathapura
https://kadalu.io





More information about the Gluster-devel mailing list