[python-committers] Github reviews are cannibalizing BPO
Eric V. Smith
eric at trueblade.com
Tue May 2 14:37:29 EDT 2017
More information about the python-committers mailing list
Tue May 2 14:37:29 EDT 2017
- Previous message (by thread): [python-committers] Github reviews are cannibalizing BPO
- Next message (by thread): [python-committers] Github reviews are cannibalizing BPO
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/2/17 2:13 PM, Guido van Rossum wrote: > I'm not necessarily disagreeing, I'm just skeptical that we can stop > this tide. New contributors are familiar with GitHub and GitHub only, > and for them, BPO looks and feels like a legacy system. And honestly, > for smaller projects, I've found GitHub a very effective place to have > discussions (e.g. most mypy design work is done there). Though I agree > that GitHub currently doesn't scale to the size of CPython unless you > work hard on setting up filtering (which *is* possible, just done very > differently). I grant that it's an uphill battle. But even github has a separate issue tracker, we're just not using it. So even github black belts should be familiar with the concept of an issue tracker being used for a different purpose than code reviews are. Eric.
- Previous message (by thread): [python-committers] Github reviews are cannibalizing BPO
- Next message (by thread): [python-committers] Github reviews are cannibalizing BPO
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list