Change config-split-export command's alias so it's not an inappropriate, sexualized phrase

Created on 13 November 2018, over 6 years ago
Updated 11 August 2023, over 1 year ago

The Drush command to export configuration, "config-split-export", has an alias that is unnecessarily sexualized, "csex". This is inappropriate. Lets change this to be something less sexualized.

✨ Feature request
Status

Fixed

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States DamienMcKenna NH, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • πŸ‡ΈπŸ‡ͺSweden twod Sweden

    This issue was a major fuckup, breaking deploy scripts and existing workflows without warning because some people are somehow offended by an acronym?
    What's so damn inappropriate that sex can not be apart of even an acronym? You ARE CREATING issues with "inappropriate words" specifically by doing things like this.

    The fact that csex (AND csim!!!!???) was removed in some versions, there was no deprecation period, no replacement alias (at least not in 2.0.0-rc4), and the change was made for this specific reason is astonishingly stupid and an embarrassment for the maintainers!
    Had I seen this before we changed over to the 2.x branch I would rather have dropped the module completely than supporting such weak and unreliable maintainership.

    I would have been ashamed to propose a change like this and am now instead ashamed of being a part of a community which bent to such petty requests - achieving nothing but wasting countless developer's time over nothing but someone deciding sex offends them.
    What if I say "drush" offsends me because "ush" in Swedish has a negative association? Or that we should not even use "association" because it contains "ass"? See how moronic this gets if you even let it start?

  • πŸ‡¬πŸ‡§United Kingdom welly

    Is this real? Sexualised phrase? Please tell me this is some kind of April Fool's joke.

    Congratulations on breaking my build pipeline without any forewarning.

  • πŸ‡¬πŸ‡§United Kingdom welly

    "I stand by the point that the phrase is unnecessarily sexualized; the rationale for naming the commands that way doesn't make sense other than it kinda matches Drush's shortening of "config-export", and there's no reason to not rename them."

    Where do you stand on the county names Essex, Sussex? How about the navigation instrument - sextant?

    With all due respect, if you find an acronym "sexualised" then that's on you not the rest of us.

    But that's besides the point - your pearl clutching has caused build pipelines to break. There was no forewarning of this when the module was updated, nothing on the module homepage and nothing in the README.md file.

    That is the problem here not your personal embarrassment at an acronym with four letters in it.

Production build 0.71.5 2024