Skip to content

DOC update contributors #52138

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

Merged
merged 1 commit into from
Apr 12, 2023
Merged

Conversation

MarcoGorelli
Copy link
Member

In the Slack channel, a contributor has been requested to be renamed due to having changed their legal name

I think it's a reasonable request, we can just add a mapping within announce.py to map the old name to the new one (I've just encoded them to avoid hard-coding someone's name in a file)

@MarcoGorelli MarcoGorelli added this to the 2.0 milestone Mar 23, 2023
@jreback
Copy link
Contributor

jreback commented Mar 23, 2023

even though this is easy i don't think it should be done

history is history and we should be changing it

@MarcoGorelli
Copy link
Member Author

In general I agree, but for context, this is someone who changed their name after coming out - I think we should allow it

Github already displays the new name

No need to change the commits themselves, but just displaying a new name in the release notes sounds fine

Copy link
Member

@jorisvandenbossche jorisvandenbossche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @MarcoGorelli !
I think this is an easy and elegant solution

history is history and we should be changing it

We are not changing any git history or historical docs. We are just updating future docs to use a new name in our own generated list of contributors.

@rhshadrach
Copy link
Member

rhshadrach commented Mar 23, 2023

Once you change from one GitHub username to another, is your previous username available for the taking by others? If that's the case, then I'm -1 here.

Otherwise I'm +0 here. I don't think we have an obligation to update prior whatsnew (even if they are being built in the future), and this would be a bit of an annoyance if it were widely used (I don't expect it will be). At the same time, I can see the desire from a contributor's standpoint and the implementation is simple enough.

@jorisvandenbossche
Copy link
Member

Once you change from one GitHub username to another, is your previous username available for the taking by others? If that's the case, then I'm -1 here.

AFAIK this is not actually related to GitHub usernames. It is the name you use in your git commit, and that's just a local git config setting at the time of making the commit, that then is embodied in the commit author details.
I can perfectly set up my git config to use any other name that could clash with other people's name or github username.

@rhshadrach
Copy link
Member

Ah, that's right, thanks. While that makes me a bit wary here, I'm +0.

@MarcoGorelli
Copy link
Member Author

looks like this is somewhat controversial...removing from the 2.0 milestone for now, let's not rush it

@MarcoGorelli MarcoGorelli removed this from the 2.0 milestone Mar 27, 2023
@MarcoGorelli MarcoGorelli added this to the 2.0.1 milestone Apr 12, 2023
@MarcoGorelli
Copy link
Member Author

merging as per today's discussion

@MarcoGorelli MarcoGorelli merged commit 32ea575 into pandas-dev:main Apr 12, 2023
meeseeksmachine pushed a commit to meeseeksmachine/pandas that referenced this pull request Apr 12, 2023
mroeschke pushed a commit that referenced this pull request Apr 12, 2023
Backport PR #52138: DOC update contributors

Co-authored-by: Marco Edward Gorelli <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants