lab09 : Wrapping up your legacy code project (leaving a legacy)

num	ready?	description	assigned	due
lab09	true	Wrapping up your legacy code project (leaving a legacy)	Wed 11/29 02:00PM	Wed 12/06 05:50PM

This lab counts 300 points towards your lab grade.

This lab MUST BE DONE IN PERSON WITH YOUR MENTOR. Your best opportunity to do that is the Week 10 lab section time.

If you can’t be in lab that afternoon, and/or want to do it sooner, then if your mentor is wiling to meet you in person to do it, you may arrange a time to complete it earlier than that, but only

• AFTER YOU HAVE COMPLETED ALL YOUR WORK for lab05/lab07 (the legacy code project)
• AFTER YOU HAVE SUBMITTED YOUR FINAL PULL REQUEST FOR THE QUARTER for your legacy code project.

Issues for the next generation of CS56 students

To complete this lab, and be DONE with the legacy code project, you need to do EACH of these things:

1. (50 pts) Do some final edits in the README.md file of your legacy code project. Put in a section called “F17 final remarks” and in it, write a short “note” to the next set of students that will work on this legacy code project.

   Tell them exactly what you think would be helpful for them to know as they start the project: what the code does, what features could be added, what bugs exist, what opportunities for refactoring you see. Also add any advice you have on working with the code you have left them, for with legacy code in general.

2. (250 pts) Add a new F17_lab09.md file that contains links to 500 points of issues for the next generation of CS56 students to work on.

   You earn 1 point for every 2 points of issues that are referred to in this file.

   These may be issues that you came up with, or they may be issues left over from ones you mentor added, or a combination. Regardless of how the issues got there, there should be at least 500 points worth of them.

   Note, however that for issues to count towards the 500 points, they must have a “F17 OK” comment from your mentor, another mentor, a TA or an instructor. Leftover "M16 OK" or "W16 OK" comments do not count. And you MUST be in lab IN PERSON to get this "OK". (See below).

   If you don’t get this OK by 2017-12-06 17:50:00 -0800 then the points don’t count.

Additional Notes

• NOTE THAT YOU MUST discuss the new issues FACE TO FACE with your mentor IN LAB.

  You cannot rely on your pair partner to do this. If only one pair partner shows up, on that THAT pair partner will get the credit for this lab.

  If you will not be in lab on that date, you need to arrange to do this with your mentor in advance, if they are kind enough to arrange to meet with you outside of class. That would also mean you have to be done with your legacy code project early. And if your mentor is not available, you are out of luck—they have no obligation to accomodate your schedule.)

  Make sure that your mentor has signed off with an “F17 OK” comment on each issue that you are planning to count towards this 500.

Grading

• (50 pts): README.md note to next set of students.
• (250 pts): 500 points of issues remaining for the next generation of students on the main fork of your legacy code project.
  • Each issue must have an “F17 OK” comment from a mentor (comments from previous quarters do not count.)
  • Any issue not ok’d by mentor by the due date/time of this lab DOES NOT COUNT.
  • The issues do not count unless they are linked to in a F17_lab09.md file with the list of issues for the next CS56 class of students.
  • There should be a pull request for these changes to the README.md and F17_lab09.md file. (This could be a pre-existing current outstanding pull request for your lab07 work, or separate final “lab09” pull request.