# lab05 : Legacy Code Next Steps

lab05 true Legacy Code Next Steps Sun 10/30 05:30PM Wed 11/09 05:00PM

THIS LAB COUNTS TOWARD THE PROJECT POINTS PORTION OF YOUR GRADE, NOT THE LAB PORTION.

That is, it counts towards the first 500 points of the 1000 point needed before the end of the course.

Those points are recorded in Gauchospace under proj1 and proj2, each of which is out of 250 points.

You should complete at least 500 points by the time of the due date listed for lab05.

# If you are switching pairs or projects

(If you are not switching pairs or projects, skip to the next section: “Open Source Project Next Steps”)

If you indicated that you wish to dissolve your pair, and/or keep your pair but move to a new project, you will need to indicate your preferences about which project you want to switch to.

The available projects are listed here. Additional projects may become available as/when other students indicate a preference to switch pairs or projects:

https://ucsb-cs56-f16.github.io/info/projects_alt/

# Open Source Project Next Steps

• Ensure that you have done a pull request for your repo
• This is the one that you did the “code review” steps on.
• This is the pull request that should, at a minimum, include a F16-lab03.md file that has the elements indicated in the instructions for lab03

At that point, what you do next depends on whether you are continuing on the same project, or starting a new one.

• If you are continuing on the same project, please see the instructions in the “Completing your Open Source Project” section below.

• If you are switching projects, there are some additional steps you’ll need to take first, detailed one this page: Instructions for Switching Projects. After completing those steps, you’ll continue with the steps under “Completing your Open Source Project” below.

# Completing Your Open Source Project

To complete your open source project, you need to accumulate 1000 points. You may count up a small number of extra points towards extra credit in the course (see Syllabus for details.)

When you complete issues, you make a pull request back to the github.com/UCSB-CS56-Projects verison of your repo, and you make a comment in the pull request: fixes issue #5 (for example). The mention of the issue by number, using the # symbol, should turn into into an automatic link to the issue.