lab08 : Group Peer Eval, One week to Code Freeze

Ops Review

In lab06 you prepared written instructions (and perhaps a video for your team’s project) that described how to start with only your team’s source code repo, and finish with an production ready instance of the application up and running on supported platform(s).

In this lab:

• The 4-5 people on your team will work together to try out the written instructions (and potentially videos) of the other team you got assigned from your discussion section, and provide feedback to them.
• Each team will also test the current state of the deployed product. NOTE: the performance of your product today has absolutely no grade consequences. It is merely a chance for constructive feedback that you can take into account in your week towards code freeze!
• In return, you’ll be receiving feedback from one of the other teams in your discussion section on your own deployment instructions and product.

The following table lists the review pairings for all teams:

Step 1: Prepare FEEDBACK Repo and grant access to your reviewers

As a team, you will be preparing a new private Github Repo in which the team that evaluates your work will collect their feedback for you. This repo should have the name of your main team repo, followed by DEPLOY_FEEDBACK.

For instance:

• 1pm-t3-course-recommender-DEPLOY-FEEDBACK
• 1pm-we-connect-DEPLOY-FEEDBACK
• etc.

This new repo is private. You will need to:

• grant write access to your team’s -DEPLOY-FEEDBACK repo to all members from the other team in your section that is reviewing your repo
• obtain write access to the other team’s repos for each person on your team that is participating in a review

Here is a table with the slack display names of all team members.

To grant access you’ll need the github id’s of the folks from the other team (which you can obtain using the /whois @ScreenName command on the course Slack.)

Please communicate with the other team through Slack. Contact persons for each team will be listed in this table and you can Slack DM with them to coordinate.

To grant access, you visit the Settings Page of the repo, then Manage Access (url is /settings/access).

Step 2: Create Stub for your Feedback

To make these instructions concrete:

• assuming you are Chris from team 1pm-t1-ride-share
• you have been assigned to provide deploy feedback for team 1pm-t3-restaurant-reviews.

1. Go to the -DEPLOY-FEEDBACK repo for the team you are supposed to provide feedback for (e.g. 1pm-t3-restaurant-reviews-DEPLOY-FEEDBACK)
2. Create a file with the name of your own team and name (e.g. 1pm-t1-ride-share-chris.md) in the root of the repo. You can just do this directly in the web ui on the master branch.

3. In this file, put the following template (substituting in your name and team name):

   # Feedback from team 1pm-t1-ride-share.md
   
   Review by Chris
      
   (Review in progress--leave this line here until review is final)
      
   TODO: Insert review here
      
   

Step 3: Actually try deploying the app

Each of you should then try deploying the app from the other team assigned to you.

If there are naming possibilities for deployments (e.g. Heroku apps), call your app: `cs148-s21-t1-chris-tries-t3, where:

• t1-chris is your team’s number and your name (which comes before -tries-)
• t3 is the team number of the code your are trying out (which comes after -tries-)

You may need to create Auth0 or Google credentials, MongoDB credentials, other API credentials, etc. Ideally, the creation of those will be sufficiently described in your deployment instructions, but for the purpose of successfully completing this peer review, feel free to share throwaway credentials with the reviewing team!

As you do, follow the instructions provided in the deployment instructions and/or video.

As you run into issues and/or problems, document these, and also work with the other team through Slack to try to resolve them.

As you edit, leave this line as the top of your review until the final step of the lab:

   (Review in progress--leave this line here until review is final)

Step 4: Finish your review

When you are done, provide a brief writeup in which you provide:

• A link to the running application (or your attempt at bringing up a running application). This can be a heroku deployment or a Google Drive link to an executable or zip file.
• Suggestions for the team on improving their deploy instructions

Then, turn to some comments about the app itself. Please address the following questions, plus anything else you think would be helpful for the team that is working on the app:

• What do you like about the app?
• What, if anything, did you find confusing about the app?
• What bugs did you find (if any?)
• What suggestions do you have for improvements or new features?
• Would you use this app? Why or why not?

Step 5: Notify the other team that your review is finished via Slack.

When your review is finished remove the line:

(Review in progress--leave this line here until review is final)

And replace it with:

Review Complete

Then notify the team whose deploy instructions and app you were reviewing, via Slack, that your review is complete.

One Week to Code Freeze

For the rest of this lab week, your team will work towards the code freeze deadline, Fri., 06/04/21, 11:59. No lab points are assigned to this portion of the work, but clearly, the work that you will put in will pay off in the final evaluations of your product and documentation!