Hi, I sadly saw that you deleted the tox configuration file. Instead of just running `tox -e py310` to run the tests, I now needed to figure out to run the tests. So I went to the README.md, found the following section... ``` ## Running tests To run all tests in the suite run: make tests ``` So I did as advised... ``` ❯ make tests black --check --diff setup.py craft_providers tests All done! ✨ 🍰 ✨ 81 files would be left unchanged. codespell setup.py craft_providers tests make: codespell: Command not found make: *** [Makefile:74: test-codespell] Error 127 ``` So, after that I checked the other make commands ... there must be one to set up the dev environment, right? No :-/ Next thing I read the Makefile... ok, there is really no command to set up a dev environment. Next I read `setup.py` and found the `test` and the `dev` extras, so I ... - created a virtual environment ``` virtualenv venv -p python3.10 ``` - installed the dev extras ``` pip install .[dev] ``` And finally was able to run the tests... ``` make tests .... ``` Though actually, this did not run the tests - at least not at the beginning, but the linters oO When I now want to build the docs, I cannot run `tox -e docs`, but I need to do the whole ceremony again :-/ As you clearly indicated that you do not like the tox workflow, it would be great though to make contributions a bit easier. You could either update the contribution documentation or create a make target which creates a dev environment. I am good now, but maybe you could smoothen the process for future contributors. Thanks for considering!