Finalize your set up on GitHub and provide a top-level README for your Git repo.
Work with your project team. There’s no other set up this time.
Create a public repository for your project on GitHub, make all team members contributors, and add a link to this repository to your living document.
The top-level README should briefly describe the idea and goals of your project and explain the layout of the repository.
Next week’s milestone will have you finalize your system’s architecture and design, but start exploring, prototyping, and setting up resources. For example, if your project requires setting up a web or SQL server, get started on this task and add relevant instructions and information to your Git repository.
Review and follow the Git conflict resolution tutorial. When merge conflicts come up later in the quarter, you will be happy that you did.
Complete the four tasks and submit the link to your repository on Canvas by 01/24 EOD.
This is up to you, but in the past teams have found it easiest to write the report collaboratively, either through GitHub or by writing the markdown file in a Google doc before committing it to the repository.
We recommend that you get started on setting up your repository and commit this first report to the “reports” folder. However, if you are facing issues with your Git set up, you can put your report in a Google doc and share it directly with your project manager. Please make sure to later copy your 01/18 status report into the reports folder, in case you are sharing it directly.
This is a great introduction to writing Markdown!