You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I was just in a presentation about this package, and while it sounds really interesting, I was surprised by the name choice. 'Groupies' is a commonly-understood slang term in English which has somewhat sexual connotations and an arguably derogatory and sexist meaning. I doubt this was intentional, to me it's obviously a play on the word "groups," but I would suggest using a different name instead. Maybe something like "numpy_groupers" after the fish?
I understand that changing the repo name is inconvenient, but as-is, the name is arguably not work-appropriate.
The text was updated successfully, but these errors were encountered:
Well, I'm no native speaker. The last time I had discussed the name with @d1manson was, when we merged our different groupby / accumarray projects and we had to find a common name, as none of us really liked the previous namings. Political correctness was not one of the issues we considered by then for the new name. Also we didn't see groupie as something derogatory, so the pun was intended. I personally don't really mind changing it, but it's also the first time in years, that there is someone complaining about the name. And there is enough software out there now that imports and depends on that name, it's probably not worth to rename it.
Hi all,
So I was just in a presentation about this package, and while it sounds really interesting, I was surprised by the name choice. 'Groupies' is a commonly-understood slang term in English which has somewhat sexual connotations and an arguably derogatory and sexist meaning. I doubt this was intentional, to me it's obviously a play on the word "groups," but I would suggest using a different name instead. Maybe something like "numpy_groupers" after the fish?
I understand that changing the repo name is inconvenient, but as-is, the name is arguably not work-appropriate.
The text was updated successfully, but these errors were encountered: