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

2020-07-22 Thread Kotresh Hiremath Ravishankar
+1 On Wed, Jul 22, 2020 at 2:34 PM Ravishankar N 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

[Gluster-devel] Announcing Gluster release 7.7

2020-07-22 Thread Rinku Kothiya
Hi, The Gluster community is pleased to announce the release of Gluster7.7 (packages available at [1]). Release notes for the release can be found at [2]. Major changes, features and limitations addressed in this release: None Please Note: Some of the packages are unavailable and we are working

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

2020-07-22 Thread Aravinda VK
+1 > On 22-Jul-2020, at 2:34 PM, Ravishankar N 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

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

2020-07-22 Thread Yaniv Kaul
On Wed, Jul 22, 2020 at 12:37 PM Shwetha Acharya wrote: > > 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 and Secondary sounds good. > ACK, though others use leader and

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

2020-07-22 Thread Sanju Rakonde
On Wed, Jul 22, 2020 at 2:34 PM Ravishankar N 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

[Gluster-devel] News from the AWS move (freebsd, centos 7)

2020-07-22 Thread Michael Scherer
Hi, so finally, after several hours of debugging (some DNS problem), we ironed the last problem with automated AWS install of Jenkins builder, and our news freshly installed c7 finished a regular regression run today: https://build.gluster.org/job/centos7-regression/10520/consoleFull We are

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

2020-07-22 Thread Shwetha Acharya
> 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 and Secondary sounds good. > > 2. Is it okay to target the changes to a major release (release-9) and > *not* provide backward

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

2020-07-22 Thread Ashish Pandey
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

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

2020-07-22 Thread Sunny Kumar
+1 for this. On Wed, Jul 22, 2020 at 10:04 AM Ravishankar N 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 >

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

2020-07-22 Thread Ravishankar N
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