Add basic contributor's page based on git commit history #124
Conversation
|
@jamesmunns I've seen the #123 you created, this PR might be a first start to address this issue. The script greez |
|
Hm, there're some duplicates in the contributors list. Also some people might prefer to be mentioned by their nick instead of their specified real name. We might have to do some postprocessing here, otherwise looks good to me. |
|
@therealprof sure, thing. It was anyway intended to be some sort of a draft, to discuss up on. I could think of adding mappings for the nicknames. However if the handling shall be more complex, I would prefer to do it in python. |
|
Using Python should be fine. |
* Add inital contributor's page * Add script to generate conributors page Related Issues: * #123
|
Hey @Nicoretti, thank you for the contribution! I'll do a quick vote of @rust-embedded/resources to see if we want to recognize people in this way. If so, we can figure out some of the details around duplication, automation, etc. |
|
CC @japaric - this would be another place where "bors runs some kind of script on every merge to master" would be useful. |
Disasm
added
the
S-waiting-on-team
|
Given the issues around duplication, people potentially not wanting their email address linked to, and not being able to have bors run a script yet, I think my vote would be to not have the Python script in the repo, but to run it once to generate a list of names, and then manually maintain the list and suggest new contributors add themselves to it if they want to when they submit PRs. I'd probably have either a list of names or names linked to GitHub profiles, rather than email addresses. |
Related Issues: