On 02.05.2017 00:32, Christian Heimes wrote: > This brings me to my questions > > 1) Should we try to move discussion back to BPO or are we fine with > having major decisions just in Github PRs?
We've had that discussion before: discussions always should happen on BPO, not Github PRs. PRs are just for code review, nothing more. AFAIK, there's no good way to enforce this except core devs pointing people to BPO instead of commenting on PRs. > 2) How can we retain enough information on BPO to keep it useful as > research database for past decisions? See above. > 3) How can we keep module maintainers and experts in the loop? For > example I don't have the resources to read all Github PRs, but I still > like to keep an eye on the ssl and hashlib module. See above :-) I have muted all Github notifications since it became impossible to follow them. -- Marc-Andre Lemburg eGenix.com Professional Python Services directly from the Experts (#1, May 02 2017) >>> Python Projects, Coaching and Consulting ... http://www.egenix.com/ >>> Python Database Interfaces ... http://products.egenix.com/ >>> Plone/Zope Database Interfaces ... http://zope.egenix.com/ ________________________________________________________________________ ::: We implement business ideas - efficiently in both time and costs ::: eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48 D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg Registered at Amtsgericht Duesseldorf: HRB 46611 http://www.egenix.com/company/contact/ http://www.malemburg.com/ _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
