proposal01 : Proposing a new legacy code project (optional)

num ready? description assigned due
proposal01 true Proposing a new legacy code project (optional) Tue 02/06 12:15PM Thu 02/08 11:59PM

Proposing a new legacy code project

Nearly all of the legacy code projects in the https://github.com/ucsb-cs56-projects organization started as “greenfield code” projects written by CS56 students.

In order to keep the pool of legacy code projects fresh, we need to allow a limited number of new greenfield projects each year.

We want to be sure that new projects meet a very high standard. Note that this standard is considerably higher than the standard that was used for the original pool of legacy code projects—that’s deliberate. We want the pool of projects to constantly be improving in quality.

Here are the current standards that a proposal for new legacy code project must meet:

If you are interested in writing such a proposal, please talk with your mentor or TA before starting.

Note that we will ONLY BE ACCEPTING ONE PROPOSAL per mentor team. So we may get more good proposals than we are in a position to accept.

Outline of your proposal

To create a proposal, create a public repo under the ucsb-cs56-f18 organization with the name proposal01_githubid1_githubid2 where githubid1 and githubid2 are the names of you and your pair partner.

In the README.md file for the repo, address the following. It should be possible to read and understand the entire writeup in 10 minutes time, so provide enough detail that we can follow what you are proposing, but not so much that we can’t read and digest it in 10 minutes.

  1. One sentence description of the proposed project
  2. A paragraph that elaborates on the one sentence description.
  3. Any other notes that you think are relevant.

Then, add issues to the repo for enough user stories to constitute 1000 points worth of work. Use the points assigned to the repo that you reviewed for lab03 as a guide.