Users should be able to change their associated data
@ajdlinux ci sta già lavorando.
Dal 27/11/2019.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
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
- Lingua principale
- Python
- Stelle
- 317
- Fork
- 91
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di getpatchwork/patchwork
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
getpatchwork/patchwork#668 ·
-
bug web-ui
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
getpatchwork/patchwork#546 · 2 commenti ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 52/100
getpatchwork/patchwork#664 ·
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
getpatchwork/patchwork#663 ·
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
getpatchwork/patchwork#645 ·
Tutte le issue di getpatchwork/patchwork
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 90/100
learningequality/ricecooker#747 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
BSData/horus-heresy-3rd-edition#3171 ·
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
run-llama/llama_index#23199 ·
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
KhronosGroup/glTF-Blender-IO#2769 ·