I am happy to see this discussion. Red Hat CCS has been focused on eradicating the problematic language (master/slave, blacklist/whitelist) from our content. As of now, our focus is on non-engineering-dependent instances. Once engineering starts eradicating the problematic language from the engineering artifacts we will be more than happy to update our content accordingly. Please count us in!
Want to discuss more on this, please ping/email/buzz and we will be up for it.
----- Moush
_____________________________________________________________
Regards
Moushumi Kalita
Manager, Content Services - Cloud Storage & Data Services
On Wed, Jan 12, 2022 at 7:16 AM Josh Durgin <jdurgin@xxxxxxxxxx> wrote:
Thanks for bringing this up John. I think renaming the master branch
would be a good area to focus on immediately after Quincy is out, when
changing these pieces will be less disruptive.
We discussed this in the ceph leadership team meeting while Sage was
out in 2020 - folks agreed it was a good idea, and there are several
places to update. From the notes:
places to update:
- qa suites
- teuthology
- build scripts
- release scripts
- docs
- pull requests (script can retarget them)
git symlink-ref does not work with github, need to rename the branch
(e.g. git branch -m ...)
Josh
On Mon, Jan 10, 2022 at 8:35 AM Sage Weil <sage@xxxxxxxxxxxx> wrote:
>
> A year or two ago we replaced all instances of master/slave terminology in the code itself, but I don't think we've talked about renaming the main branch name. I suspect this might be a painful process given all of the bailing wire and duct tape involved in ceph-build.git and jenkins, but it might also be mostly handled with search/replace.
>
> s
>
> On Mon, Jan 10, 2022 at 9:52 AM John Bent <johnbent@xxxxxxxxx> wrote:
>>
>> All,
>>
>> Has a conversation been started yet about renaming the default development branch from master to main? And similarly cleaning other occurrences of ‘master’ in Ceph code and documentation?
>>
>> Thanks
>>
>> John
>> _______________________________________________
>> Dev mailing list -- dev@xxxxxxx
>> To unsubscribe send an email to dev-leave@xxxxxxx
>
> _______________________________________________
> Dev mailing list -- dev@xxxxxxx
> To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
