lab04 : Legacy Code Next Steps
| num | ready? | description | assigned | due |
|---|---|---|---|---|
| lab04 | true | Legacy Code Next Steps | Wed 07/06 09:30AM | Fri 07/15 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 lab04.
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, and 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:
INSERT LIST OF AVAILABLE PROJECTS HERE
Open Source Project Next Steps
- Ensure that you have done a pull request for your lab03 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 M16_lab02.md file that has the elements indicated in lab02.
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.)
If you are still working on the same repo as in your initial code review, you might have already done some work on various issues. If so, talk with your mentor about those, and ask your mentor to review your work on those issues. If you have completed these successfully, and your mentor reviews your code, these can be submitted to the TA/Instructor for grading, and these can count towards your project points for this lab.
If not, then you start now. If there are not enough issues in your project, or if you have added issues, please ask your mentor to estimate the points for those issues. You may want to make a comment on the issue with your own suggestion, then negotiate.
Use the rubric that 100 points is about 2 hours of work, more or less. Note that this is MORE OR LESS. That doesn’t mean that if you put in 10 hours of work you automatically get 500 points. You have to actually accomplish something, not just “put in time”. Time estimation in software is notoriously difficult. If you put in 10 hours of work, you should have something to show for it, even if it wasn’t what you originally set out to do. The code should be demonstratably better in some way, and you should communicate with your mentor, TA and instructor EARLY AND OFTEN about what kinds of things you are running into.
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.
You should resolve as many issues as you can by due date for this lab (see the calendar). Your goal should be to get as much done as possible by then. Then, check in with your mentor and see what work is left, and how much more you may need to accomplish to earn the 1000 points you need to complete this part of the course.