I think he&#x27;s got a point, though. Like why do I need both `setup.cfg` and `setup.py` (this one bothers me the most if `setup.cfg` contains one or two keys)? Why can&#x27;t things like `.pylintrc`, `.coveragerc`, `.travis.yml`, `AUTHORS`, `CHANGELOG`, `CONTRIBUTING`, and `MANIFEST.in` go into a subfolder? I do like how e.g. flake8 just uses the `tox.ini` file for it&#x27;s settings. While I can understand why `.travis.yml` makes sense to be separate, `.coveragerc` is usually like 5 lines long.<p>`pbr` seems like a step in the right direction. But right now, it feels a lot like Linux&#x2F;BSD&#x2F;Unix, where every dot file used to go into `~&#x2F;`. Happily, we&#x27;ve started putting stuff into `~&#x2F;.config&#x2F;$APPNAME`, which reduces the clutter and makes backups&#x2F;restoring much easier (Which you can also do with git! Something I only found out recently) So a `.config` directory in a repo would be neat.