Nick Coghlan added the comment: Offline feedback from GvR:
* the currently accepted term for folks with commit access is "core developer", and this page isn't the place to attempt to change that, so I've switched to that conventional terminology throughout the page * the scope limitation to core developers now appears in the section heading in addition to the preamble text I agree there are legitimate concerns with "commits for the sake of commits" as a metric, but it's just one link used to contrast what a page like this can provide with what automated VCS analysis can do, and reviewing and incorporating other people's patches at a general bug fixing level is actually the area where we most struggle at the moment, especially for orphan modules. I'm going to post this updated version, and then try to encourage more folks to start filling in entries now that there's a better explanation of the page's purpose. ---------- Added file: http://bugs.python.org/file41108/core-developer-motivations.diff _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue25194> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
