I'd vote for "code health". It sends a much more positive vibe than "maintainability", and covers more than "refactoring".
On Wed, Feb 14, 2018 at 9:29 AM, Nick Coghlan <[email protected]> wrote: > On 14 February 2018 at 16:11, Brett Cannon <[email protected]> wrote: > > I would consider a "code health" a more general type for things that are > not > > user-facing. > > I agree "refactoring" would be too narrow, but "code health" has some > of the same problems (since not all changes along these lines are > going to be about code as such - e.g. syncing up changes to the docs > build system). > > "maintainability", perhaps? > > Cheers, > Nick. > > -- > Nick Coghlan | [email protected] | Brisbane, Australia > _______________________________________________ > core-workflow mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct > _______________________________________________ > core-workflow mailing list -- [email protected] > To unsubscribe send an email to [email protected] > https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct > -- --Guido van Rossum (python.org/~guido)
_______________________________________________ core-workflow mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
_______________________________________________ core-workflow mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mm3/mailman3/lists/core-workflow.python.org/ This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
