Re: Removing problematic language in geo-replication

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

 



Thank you for the update. Looking forward to the completion of this
activity in early 2021!

On Wed, 30 Dec 2020 at 18:00, Ravishankar N <ravishankar@xxxxxxxxxx> wrote:
>
> Hello,
>
> Just a quick update:  all geo-rep related offensive words (as a matter
> of fact, even the non geo-rep ones) that can be removed from the code
> have been done so from the devel branch of the glusterfs repo. I thank
> everyone for their suggestions, debugging/testing help and code reviews.
>
> Since we have some soak time before the changes make it to the
> release-10 branch, I would encourage you to test the changes and report
> any issues that you might find. Please try out both new geo-rep set ups
> as well as upgrade scenarios (say from a supported release version to
> the latest devel branch).
>
> Also, for any new PRs that we are sending/ reviewing/merging, we need to
> keep in mind not to re-introduce any offensive words.
>
> Wishing you all a happy new year!
> Ravi
>
> On 22/07/20 5:06 pm, Aravinda VK wrote:
> > +1
> >
> >> On 22-Jul-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.
> >
> >> 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@xxxxxxxxxxx
> >> https://lists.gluster.org/mailman/listinfo/gluster-devel
> >>
> > Aravinda Vishwanathapura
> > https://kadalu.io
> >
> >
> >
>
> -------
>
> Community Meeting Calendar:
> Schedule -
> Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
> Bridge: https://meet.google.com/cpu-eiue-hvk
>
> Gluster-devel mailing list
> Gluster-devel@xxxxxxxxxxx
> https://lists.gluster.org/mailman/listinfo/gluster-devel
>


-- 
sankarshan mukhopadhyay
<https://about.me/sankarshan.mukhopadhyay>
-------

Community Meeting Calendar:
Schedule -
Every 2nd and 4th Tuesday at 14:30 IST / 09:00 UTC
Bridge: https://meet.google.com/cpu-eiue-hvk

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