You each should individually maintain and update a weekly log book. You are advised to continuously update your log book.
To this end, create a single and separate log book for each team member, in which you add the main activities that you worked on during the project. We ask you to use a simple text file for this that can be shared with all team members. The name of this file should be your full name (firstname_lastname.txt). You should add this file to your git repository in a folder named org at the start of the project, and regularly update and commit(!) it to the repo. This will also make sure your TA has access to your log book from the start of the project.
Structure and content
Structure your log book by creating a Week 1, Week 2, etc. heading. Maintain a simple list of bullets with brief but specific descriptions of each activity that you worked on that fit on 1-2 lines max (do not write paragraphs). You should think about all the different things that you need to work on such as coding, modifying, updating, testing, designing, analyzing, writing, etc. Each item (bullet) in your log book should have the form: <bullet><date>: <activity-description>, where the activity description should start with a verb (indicating what you did). Some good examples are:
9-1: Created the Dialogflow agent, downloaded the JSON key file, and updated the flowkey and flowagent parameters in the
.mas2gfile.12-1: Added the c10 greeting pattern.
12-1: Tested the recipeRecommendation intent and added new training phrases to make it more robust.
The log book will be used to evaluate your participation as a team member within the team. We can use this as a basis for making individual grade differences at the end of the project.