Am 03.01.16 um 08:04 schrieb Random832:
Michael Vilain <vil...@nospamcop.net> writes:
We used stash/bitbucket at my last contract. It's the second site I've
come across that used Atlasian's toolset. Yes, I know it's not
statistically significant.
Anyway, the pull/merge request workflow is becoming pretty standard.
I think you're missing a distinction between "pull/merge request
workflow" and the specific artifact that github _calls_ a "pull
request", which includes references to specific github accounts, a
discussion thread on their proprietary discussion software (vs an email
list or the python issue tracker) maintained on their servers and not
servers that PSF controls, etc.
Arguably, the most valuable outcome of the pull request in the end is
the patch, which is of course contained in the git repository. GitHub
also sends email notifications if a pull request is edited. So if the
account holder for GitHub keeps an archive of all mail from
notificati...@github.com, then also the big part of this discussion is
preserved. I doubt that many people want to go back to see the arguments
for a certain merge; this thread will also soon be abandoned, people
will know that Python lives on GitHub and live with it, move on and do
something more valuable.
Christian
--
https://mail.python.org/mailman/listinfo/python-list
