Thanks! I really like that you can drill down on various things until you reach GitHub.
With a few iterations we should be able to launch this.
- Show dates (and perhaps filter on "last week/month/etc."?) - A few people appear under two names (at least Eric [V.] Smith) - Contrast on the boxes here makes them hard to read for my old eyes: https://thanks-python.herokuapp.com/tag/v3.6.5 - For really old commits the "author" is often really just the person who reviewed and "merged" the patch - Ms Islington is credited for a number of commits -- shouldn't those be attributed to the original author somehow?
On Mon, Jun 25, 2018 at 5:03 AM Pablo Galindo Salgado pablogsal@gmail.com wrote:
Hi everyone,
After talking with Victor Stinner on some ideas on how to encourage contributions to CPython and how to give more visibility to contributors (see Victor notes: http://pythondev.readthedocs.io/community.html), based on the https://thanks.rust-lang.org/ project (than in turn was based on http://contributors.rubyonrails.org/) I have created the following prototype in my daily commute time:
https://thanks-python.herokuapp.com/
The project runs on Heroku at this moment, it fetches the latest changes from the git repository and updates every 30 minutes to get the latest information. You can click on any release to get the contributor names:
Example: https://thanks-python.herokuapp.com/tag/v3.6.5
(the names are obtained from the commit messages) and you can in turn click any contributor name to get the list of commits:
https://thanks-python.herokuapp.com/contributor/Mariatta
You can also obtain a list of all contributors (all time contributors):
https://thanks-python.herokuapp.com/all_time
I want also to emphasize that this is just a very basic prototype made for evaluating the idea and the possible benefit that it has, but is functional :)
The repo is located here:
https://github.com/pablogsal/thanks-python
At this point is a very simple flask app with a celery worker running in the background and a redis interface for celery and for storing the git data (so is very easy to bootstrap as the first thing it does when started is to clone the repo and fetch the data again).
What are your opinions on the matter?
P.S. Don't be to critic on my horrible html and web design skills ;)
Regards from sunny London Pablo Galindo Salgado _______________________________________________ core-workflow mailing list -- core-workflow@python.org To unsubscribe send an email to core-workflow-leave@python.org https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct