Hi,
Could we please stick to the point of renaming a Git branch? Today,
renaming a branch is easy. The rationale has been given. I don't think
any argument is going to make the Steering Concil changing their mind
("the consensus was that we should do that"). If you want to help,
please remain at the technical level to help making this migration as
smooth as possible for everybody.
On Wed, Mar 10, 2021 at 2:09 PM Evpok Padding <evpok.padd...@gmail.com> wrote:
> If the discussion here can stay civil for changes with far more repercussions
> for Python (e.g. controversial PEPs), surely it can stay civil for this too.
Thanks. For people able to remain constructive and civil, please join
the discussion on the devguide on "listing terms which should be
avoided":
https://github.com/python/devguide/issues/605
While it's not easy to give an exhaustive list of terms which should
be avoided, IMO it would prevent future discussion like this thread.
I'm tired of such discussion which is not constructive at all and goes
nowhere. People love to take it as an opportonity to troll and quickly
messages become more and more offensive.
IMO
https://chromium.googlesource.com/chromium/src/+/master/styleguide/inclusive_code.md
is a good example to follow: it's short and gives concrete advices for
better terms.
Victor
--
Night gathers, and now my watch begins. It shall not end until my death.
_______________________________________________
Python-Dev mailing list -- python-dev@python.org
To unsubscribe send an email to python-dev-le...@python.org
https://mail.python.org/mailman3/lists/python-dev.python.org/
Message archived at
https://mail.python.org/archives/list/python-dev@python.org/message/5QI7XFD6EBKZOZ4OSERCOZW5PBORQNWG/
Code of Conduct: http://python.org/psf/codeofconduct/
