Users should be able to change their associated data
@ajdlinux y travaille déjà.
Depuis le 27/11/2019.
Évaluation
Cette issue n'a pas encore été évaluée.
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
- Langage dominant
- Python
- Étoiles
- 317
- Forks
- 91
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Guide de contribution
Ouvrir le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de getpatchwork/patchwork
-
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
getpatchwork/patchwork#668 ·
-
bug web-ui
Difficulté 2/5 1-3 heures Accessibilité débutants 74/100
getpatchwork/patchwork#546 · 2 commentaires ·
-
Difficulté 3/5 1-2 jours Accessibilité débutants 52/100
getpatchwork/patchwork#664 ·
-
Difficulté 4/5 3-5 jours Accessibilité débutants 48/100
getpatchwork/patchwork#663 ·
-
Difficulté 3/5 1-2 jours Accessibilité débutants 45/100
getpatchwork/patchwork#645 ·
Toutes les issues de getpatchwork/patchwork
Issues similaires
-
essnmx good first issue
Difficulté 1/5 Moins d'une heure Accessibilité débutants 95/100
-
[Feature] 奇物选择添加优先级 Ouverte
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
Giskard-AI/giskard-oss#2840 · 1 commentaire ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Ouvertearea: repo bug perceived difficulty: 2
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
-
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
yeti-platform/yeti#1380 ·