Linter check

.gitignore

@@ -439,3 +439,6 @@ x509.genkey
 
 # Clang's compilation database file
 /compile_commands.json
+code/codetime_server/docker-compose.yml
+code/codetime_server/Dockerfile
+code/codetime_server/run.sh

.travis.yml

@@ -1,21 +1,28 @@
-language: python
-python:
-  - "3.6"      # current default Python on Travis CI
-  - "3.7"
+matrix:
+  include:
+    - os: linux
+      language: python
+
 services:
   - xvfb
+  - mysql
+
+env:
+  - MYSQL_CODE_TIME_DB_NAME=codetime_db MYSQL_CODE_TIME_USER=travis MYSQL_CODE_TIME_PASSWORD='' MYSQL_CODE_TIME_HOST='127.0.0.1' MYSQL_CODE_TIME_CONNECTION_PORT=3306 CODE_TIME_SECRET_KEY=Sample
+
 before_install:
   - curl -OL https://raw.githubusercontent.com/SublimeText/UnitTesting/master/sbin/travis.sh
-# command to install dependencies
+
 install:
-  - pip install -r requirements.txt
-  - python setup.py install
   - pip install flake8==3.5
-  - sh sbin/travis.sh bootstrap
-  - sh sbin/travis.sh install_color_scheme_unit
-  - if ["$PCINSTALL" == true]; then sh sbin/travis.sh install_package_control; fi
-# command to run tests
+  - sh travis.sh bootstrap
+  - pip install -r code/codetime_server/requirements.txt
+
+before_script:
+  - mysql -e 'create database codetime_db;'
 script:
-  - flake8 --statistics
-  - sh sbin/travis.sh run_tests --coverage
-  - python -m pytes
+  - flake8 --max-line-length=200
+  - sh travis.sh run_tests
+  - cd code/codetime_server/
+  - coverage run --source='.' manage.py test codetime
+  - coverage report

PROJ2-selfAssessment.md

@@ -0,0 +1,61 @@
+# Group 18 Self Assessment
+
+## Total score
+
+- write down "4" into every right-hand-side cell
+- Look for evidence that any "4" should be something else
+- sum the right-hand-column, divide by number of rows
+
+<br clear=all>
+
+| What                     | Notes                                                                                                                                                                                    | score 0..4<br>(0=no, 2=ok, 4=wow!) |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------- |
+| Misc                     | Group members attended tutorial sessions                                                                                                                                                 |                                    |
+| Distrbuted dev model:    | decisions made by unanmyous vote                                                                                                                                                         |                                    |
+|                          | group meetings had a round robin speaking order                                                                                                                                          |                                    |
+|                          | group meetings had a moderator that managed the round robin                                                                                                                              |                                    |
+|                          | group meeting moderator rotated among  the group                                                                                                                                         |                                    |
+|                          | code conforms to some packaging standard                                                                                                                                                 |                                    |
+|                          | code has can be downloaded from some standard package manager                                                                                                                            |                                    |
+|                          | workload is spread over the whole team (one team member is often Xtimes more productive than the others... but nevertheless, here is a track record that everyone is contributing a lot) |                                    |
+|                          | Number of commits                                                                                                                                                                        |                                    |
+|                          | Number of commits: by different people                                                                                                                                                   |                                    |
+|                          | Issues reports: there are many                                                                                                                                                           |                                    |
+|                          | issues are being  closed                                                                                                                                                                 |                                    |
+|                          | License: exists                                                                                                                                                                          |                                    |
+|                          | DOI badge: exists                                                                                                                                                                        |                                    |
+|                          | Docs: doco generated , format not ugly                                                                                                                                                   |                                    |
+|                          | Docs: what: point descriptions of each class/function (in isolation)                                                                                                                     |                                    |
+|                          | Docs: how: for common use cases X,Y,Z mini-tutorials showing worked examples on how to do X,Y,Z                                                                                          |                                    |
+|                          | Docs: why: docs tell a story, motivate the whole thing, deliver a punchline that makes you want to rush out and use the thing                                                            |                                    |
+|                          | Docs: 3 minute video, posted to YouTube. That convinces people why they want to work on your code.                                                                                       |                                    |
+|                          | (hard) code conforms to some known patterns                                                                                                                                              |                                    |
+| Tools Matter             | Use of version control tools                                                                                                                                                             |                                    |
+|                          | Extensive use of version control tools                                                                                                                                                   |                                    |
+|                          | Repo has an up-to-date requirements.txt file                                                                                                                                             |                                    |
+|                          | Repo does not have "ignore" files.                                                                                                                                                       |                                    |
+|                          | Use of  style checkers                                                                                                                                                                   |                                    |
+|                          | Extensive Use of  style checkers                                                                                                                                                         |                                    |
+|                          | Use of code  formatters.                                                                                                                                                                 |                                    |
+|                          | Extensive Use of code  formatters.                                                                                                                                                       |                                    |
+|                          | Use of syntax checkers.                                                                                                                                                                  |                                    |
+|                          | Extensive use of syntax checkers.                                                                                                                                                        |                                    |
+|                          | Use of code coverage                                                                                                                                                                     |                                    |
+|                          | Extensive use of code coverage                                                                                                                                                           |                                    |
+|                          | other automated analysis tools                                                                                                                                                           |                                    |
+|                          | Extensive use of  other automated analysis tools                                                                                                                                         |                                    |
+|                          | test cases exist                                                                                                                                                                         |                                    |
+|                          | test cases are routinely executed                                                                                                                                                        |                                    |
+| consensus-oriented model | the files CONTRIBUTING.md and CODEOFCONDUCT.md has have multiple edits by multiple people                                                                                                |                                    |
+|                          | the files CONTRIBUTING.md lists coding standards and lots of tips on how to extend the system without screwing things up                                                                 |                                    |
+|                          | multiple people contribute to discussions                                                                                                                                                |                                    |
+|                          | issues are discussed before they are closed                                                                                                                                              |                                    |
+|                          | Chat channel: exists                                                                                                                                                                     |                                    |
+|                          | Chat channel: is active                                                                                                                                                                  |                                    |
+|                          | test cases:.a large proportion of the issues related to handling failing cases.                                                                                                          |                                    |
+| zero internal boundaries | evidence that the whole team is using the same tools: everyone can get to all tools and files                                                                                            |                                    |
+|                          | evidence that the whole team is using the same tools (e.g. config files in the repo, updated by lots of different people)                                                                |                                    |
+|                          | evidence that the whole team is using the same tools (e.g. tutor can ask anyone to share screen, they demonstrate the system running on their computer)                                  |                                    |
+|                          | evidence that the members of the team are working across multiple places in the code base                                                                                                |                                    |
+| low-regressions rule     | (hard to judge) features released are not subsequently removed                                                                                                                           |                                    |
+| short release cycles     | (hard to see in short projects) project members are committing often enough so that everyone can get your work                                                                           |                                    |