Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update article.md #3724

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Conversation

audiodude
Copy link

Remove non-inclusive language.

Remove non-inclusive language.
@javascript-translate-bot javascript-translate-bot added the review needed Review needed, please approve or request changes label Jul 23, 2024
@javascript-translate-bot javascript-translate-bot requested a review from a team July 23, 2024 01:58
@CLAassistant
Copy link

CLAassistant commented Jul 23, 2024

CLA assistant check
All committers have signed the CLA.

@joaquinelio
Copy link
Member

joaquinelio commented Jul 23, 2024

Why.
I don't think time-consuming "inclusive" fixes solve anything

It's just a good metaphor here, it has nothing offensive in this technical context.

Of course, it's just my opinion.
Im just the spanish version repo maintainer and I see too many small changes to manage.

@audiodude
Copy link
Author

First, I don't think it's time-consuming. I've already made the PR to fix it, I'm not asking your team to fix it.

Second, I'm sorry if there's "too many small changes" for your liking. Perhaps you should remove the "Edit on GitHub" link from your sidebar if you no longer wish for people to contribute.

Finally, I'm not going to open an entire DEI debate here. But I don't think it's a particularly "good metaphor" (The cross site request behaves just like a slur for a disabled person). I believe the language I suggested is perfectly descriptive and informative, and no nuance or meaning is lost.

@audiodude
Copy link
Author

On second thought, I assume you mean "time-consuming" because the new phrasing will have to be translated into Spanish? If that's the problem I can ask a technical friend of mine who knows Javascript and speaks Spanish to make the change in that language, though it's unclear to me if such a change will be necessary (if the same non-inclusive language is used in Spanish for instance).

@joaquinelio
Copy link
Member

Im sorry.
Really.
I didnt want ro be offensive, My English may be a little rough and i couldnt make it more polite

As i said, i have no part in this repo. I get no money either, I do collaboration like you just did. the responsible team have NOTHING to do with my opinion. I just wanted to voice it.

@audiodude
Copy link
Author

No worries! I'm not personally offended, I just think that using inclusive language helps grow our developer and Javascript communities in a healthy way. I hope that those reviewing this change will see it the same way.

@joaquinelio
Copy link
Member

joaquinelio commented Jul 23, 2024

Im Not trying to make an excuse.
This is just in case you are curious

The changes are merged in all languages.
Last merge, 70+ commits in 49 files
Some new material,
Some grammar fix,
And many of my hated "style changes"

Screenshot_2024-07-23-15-19-48-481

About the "inclusive"
I just don't get it, but right, we don't want to bring the debate here.
And yes, it's an issue in Spanish too, maybe some countries more than others.
As a translator, I dont change style. If main repo changes, I'll do it in Spanish too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
review needed Review needed, please approve or request changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants