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
Hi all,
I have read the workflow in the code of Bedevere
(https://github.com/python/bedevere/blob/master/bedevere/stage.py#L7),
and there is one thing I do not understand.
Here is the PR - https://github.com/python/cpython/pull/5132
Steps:
1. label: "awaiting review"
2. I did the review and ask for some changes, so in this case, I don't
approve the review.
3. the label has been changed to "awaiting core review" by Bedevere, but
Why? I requested some changes and the PR is not in "awaiting changes"
For me, normally, the label should be on "awaiting changes" and after
a new commit/message from the author, the label should be "awaiting review"
Thank you,
Stéphane
--
Stéphane Wirtel - https://wirtel.be - @matrixise
I'm interested to try out Gitmate, and I've requested the permission for it
to be installed in Python GitHub organization.
https://gitmate.io/
Several of its features I'd like to try out for now:
- automatically add size labels on pull requests. It can analyze the
content of the pull request, and apply the size labels (xs, s, m, etc)
- apply stale label for inactive pull requsts
gitmate has been used by coala. Here is an example of a PR where it
automatically add stale, size labels, and also checks of PEP 8 compliance:
https://github.com/coala/coala/pull/4818
I find the code analysis feature of gitmate (checking for PEP 8 etc) is too
noisy, so I don't think we should add it now.
If it works for the devguide or core workflow, perhaps later we can try
adding this to cpython too?
Mariatta
