Your active participation to the codewalk discussions is an important aspect of the course. Feel free to make remarks and ask questions that help the you and the rest of the class understand the presented code. Of course, always remember to be respectful of everyone in the class. In particular, avoid to monopolize the discussion so that everyone gets a chance to speak.

After every codewalk, we will evaluate your participation in the discussion and give a score as feedback. Here is how you should read your scores:

1. A score 4 is code for making a very thoughtful comment during the code walk.
2. A score 3 is code for participating in the code walk discussion in a respectful way by asking questions to understand something about the presented code or by making helpful suggestions and remarks about the code.
3. A score 2 is code for no participation during the discussion.
4. A score 1 is code for participating in the discussion in a disruptive manner such as monopolizing the discussion and not letting others speak, making aggressive remarks about the presented code to show off etc.

A few notes more notes about participating in the discussion and the participation scores:

1. Please do not go down the path of adding and taking the average of your participation scores. As you will see on Canvas they do not count towards your overall points. This is on purpose: we assign scores to give you some feedback about how you are doing and fix things if there are issues. We will decide on your final participation grade based on your overall performance during the quarter and especially how you react to comments to fix issues related to your participation.
2. We expect that a score 4 will be pretty rare; at best once or twice per quarter. This is indicative of the expected quality of comments that will result in a score 4.
3. Most of the time you should expect to get a score 3 or score 2. A healthy mixture of these two scores corresponds to good performance in the discussion through out the quarter. So feel free to not participate in some discussions as long as you make an effort to participate from time to time. Also feel free to participate and speak your mind as long as you are respectful of your peers and you don’t monopolize the discussion so that everyone gets a chance to participate. We will warn you in either case when we think you need to adjust your participation level.
4. If you receive a score 1 you should expect to receive a comment that explains the issue. We expect that you will react accordingly to fix the situation.
5. When you participate, please say what you intend to say in a direct manner. Ask questions if you want to learn something or if you need a clarification. Make comments if you want to make a remark or suggestion about the presented code. Please do not try to mask remarks as questions by adding a question mark at the end.

If you would prefer to comment on others' code in an offline, more thoughtful manner, you may do so and have it count towards your participation grade.

More precisely, we will replace a 1 with a 2 on one of your participation scores each time you follow these steps:

1. Create a pull request on one of the public, codewalk repositories (the ones with the word codewalks in the name).
2. The pull request must have additional test cases in it and, if the test cases find bugs, they may offer fixes to the bugs.
3. You must let the instructors know that you've made the pull request explicitly.

Please note: any pair whose code has a pull request on it from another student must respond to the change, giving feedback about whether the new tests are correct or not. The instructors will evaluate both the pull request and the feedback of the original code's authors.