I can do this task.
One question for my comprehension, are the private/public keys really related to the username/password? That would surprise me. There are certainly mathematically related, but I doubt the password/username thing. Do you have a link or a reference for that?
("Clé publique : Equivalent du numéro de compte (membre ou portefeuille). C’est celui que vous communiquez pour être certifié ou recevoir un paiement. Elle est calculée à partir du couple identifiant / mot de passe, et est liée mathématiquement à la clé publique")
In the workflow, you should propose a merge request with your branch. See the README.md for more details ;)
One question for my comprehension
I'm not interested in details. But I understood that when you choose a couple ID/password, they go through an algorithm (like SHA for example) and that generates your private and your public keys. I think that you could find some informations on duniter.org or in the whitepaper project.
Thanks for your response. I created a fork but still cannot create a merge request on this repo. I need at least the developer role to do this. Thanks!
There's nothing about the generation of the keys in the whitepaper, but thanks for the link, I didn't know this.