Users should be able to change their associated data
@ajdlinux is already working on this.
Since Nov 27, 2019.
Assessment
This issue has not been assessed yet.
Description
Users should be able to change their associated data, like name and email, and not be stuck with one name forever. I'm quoting some bits here with a few comments on my own:
To try and put it simply, the author of a commit is tied in to the identity of the commit itself. If you change the author, it’s treated as an entirely new commit. Anyone who has grabbed a copy of your original commit and made subsequent changes on top of it finds themselves orphaned from the history of the project. To use a crude analogy, it’s like you rip the trunk of a tree out, while the branches are magically left hanging in the air, connected to nothing and isolated.
Of course, it’s not that the designers of Git tried to make it difficult for committers to change their names. It’s likely that most of them just didn’t think about what would happen if a developer needed to change their name retroactively, because most of the people who have worked on Git are cis men. They aren’t expected to change their names if and when they get married or divorced, and having cis privilege, they don’t need to change their name to something more consistent with their gender. Nevertheless, the inability to change one’s name retroactively without disrupting others’ work can mean that trans people — particularly trans women, who are likely to face harsh social stigma in any space where their trans history is known — will have to cease to contribute to their projects when they transition.
*additions by ng0:
Additionally this means that if your project has an open policy on names and you decide to change your name you will be stuck in the patchworks interface with the old name. In my case as I do not want to use my legal name due to personal reasons,it created this situation:
before signing up at patchwork, the authors name was "ng0".
Then I signed up, the process was unclear to me so I chose "non" "such" thinking i could change it later on.. after signing up I am now stuck with "non such".
I had no chance to test this myself, but you should also be aware of names which differ from the first+lastname form.
References: #49 and https://libreboot.org/git/#guidelines
- Dominant language
- Python
- Stars
- 317
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from getpatchwork/patchwork
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
getpatchwork/patchwork#668 ·
-
bug web-ui
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
getpatchwork/patchwork#546 · 2 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
getpatchwork/patchwork#664 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
getpatchwork/patchwork#663 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
getpatchwork/patchwork#645 ·
All issues in getpatchwork/patchwork
Similar issues
-
Add: hunch Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
AbdelStark/awesome-typesafe#104 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
DiamondLightSource/dodal#2211 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
openml/openml-python#1749 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
sipyourdrink-ltd/bernstein#6191 ·