Mailman 3 April 2018 - core-workflow

IRC vs Slack vs Discord vs Gitter
by INADA Naoki 06 Apr '18

06 Apr '18

Hi, Nowadays, joining to IRC is a hurdle for new contributors. There are some alternative, modern web applications: * Slack -- Most used for tech communities. * Discord -- Similar to slack. It is focusing game, but support OSS too. [1] * Gitter -- Most integrated with Github. typing, mypy, pip use it already. [1] https://discordapp.com/open-source I know adding communication channel is not good always. (We couldn't keep https://discuss.python.org/) But I think IRC is really high hurdle for young people. How about trying one of them? (maybe, gitter?) Regards, -- INADA Naoki <songofacandy(a)gmail.com>

15 37

Add a "refactoring" type to the issue tracker?
by Nick Coghlan 06 Apr '18

06 Apr '18

For https://bugs.python.org/issue32836, I ended up picking "behaviour" as the issue type (since we're reporting that we're using a symbol that we don't actually use), but it did prompt the thought: should we add a "refactoring" type to the issue tracker? Right now, we tend to mark refactoring changes as "enhancement", but I'm thinking there would be value in making it clear that we don't expect end users to notice a particular change, it's just for the benefit of current and future maintainers. Cheers, Nick. -- Nick Coghlan | ncoghlan(a)gmail.com | Brisbane, Australia

5 6

python.zulipchat.com is now open!
by Brett Cannon 06 Apr '18

06 Apr '18

You can sign up at https://python.zulipchat.com/register/ . Do read the text on the sign-up page as it mentions key things like automatically hyperlinking for issues, the CoC, etc. The instance is currently very open at Zulip's/Greg's suggestion. That means people can add bots, create streams, etc. If this starts to get out of hand we can lock it down and make those things admin-only. Otherwise we are leaving it open for now to see what practices emerge from usage. To start, I have created several streams that orient around various mailing lists we already have. I also set up bots for commits, PR comments/reviews (although that's so new I have not seen it triggered yet :), and bot deployments for Bedevere and the Knights Who Say Ni (when Mariatta comes back from her break we can ask her to hook up miss-islington). I think this covers the major areas of our workflow to get us started with this experiment. Initially this should be oriented towards the development of Python and not using Python. If this experiment turns out really well we can talk about either expanding this instance or opening a separate instance for people to go discuss Python in general, using it, getting help, etc. I am also not announcing this on python-committers or python-dev yet until we have played with it for a week or so. If this ends up looking like a worth-while experiment and experience then we can make a broader announcement. And then after that if this continues to be beneficial we can then start discussing officially integrating Zulip into our communication ecosystem for core development.

1 0

confusing result from `make patchcheck`
by Ethan Furman 05 Apr '18

05 Apr '18

Running `make patchcheck` resulted in the following: Getting the list of files that have been added/changed ... fatal: ambiguous argument 'origin/3.7': unknown revision or path not in the working tree. How does one fix that? The commands leading up to this: git checkout -b bpo-33217-3.7 upstream/3.7 <edit Lib/enum.py and Lib/test/test_enum.py> make distclean cp Modules/Setup.dist Modules/Setup ./configure --with-pydebug && make -j2 ./python -m test.regrtest test_enum.py ./python -m test.regrtest make patcheck Any help appreciated! :) -- ~Ethan~

3 6