Weekly Summary
Testing! Week 1 has been all about development preparation - getting everything set up and ready to be tested. After all, the more tests we run, the least likely something is to break. And why provide you guys with a broken tool? We've also been brainstorming ideas on exactly what contributr is going to be. We've come up with what contributr's end result looks like and broke it down into stages for how it will all be released to the community.
Considering this is a learning group and the majority of us are learning as we go, this week has also consisted of reading a lot of documentation as well as other basic articles on how to properly write a git commit message.
Getting set up includes starting the Django project contributr, setting up testing with pip-tools, pytest-django, and Travis-CI. To catch up also read about python virtual environments (and how to set the SECRET_KEY in them) in this tutorial.
Week 2 started with more refinement of the setup. The requirements and settings are now different for running the server local or in production. Codecov stopped working, so we switched to Coveralls. Requires now checks the requirement files to see if any of them are outdated.
A lot of effort went into the automatic deployment of the master-branch of the repository.