Warning
-This page has not yet been updated for Spring 2024.
-Project Registration¶
+Project Registration¶
For each project, a Git repository will be created for you and your project partner on GitHub, a web-based hosting service for Git repositories. However, before that repository can be created for you, you need to have a GitHub account. If you do not yet have one, you can get an account here: https://github.com/join. Once you create your account, you may want to get the Student Developer Pack, which will give you access to a lot of other features (please note that having the Student Developer Pack is not necessary for this class; it’s just a nice benefit you get as a student)
If you’re unfamiliar with Git, you should work through the Git Basics Tutorial before proceeding further.
-To actually get your private repository, you will need an invitation URL, which we will provide through Ed Discussion when each project is released. When you click on an invitation URL, you will have to complete the following steps:
+To actually get your private repository, you will need an invitation URL, which we will provide through Canvas when each project is released. When you click on an invitation URL, you will have to complete the following steps:
You will need to select your CNetID from a list. This will allow us to know what student is associated with each GitHub account. This step is only done for the very first invitation you accept.
Next, you will need to create a new team, or join an existing team if your project partner has already created a team. Please make sure to coordinate with your project partner so you do not end up creating two separate teams.
-Please note that, while GitHub will allow you to select an arbitrary team name, your team name must be the project number (
+p1
,p2
, orp3
, followed by your CNetIDs in alphabetical order and separated by a hyphen (e.g.,p1-jdoe-jrandom
).Please note that, while GitHub will allow you to select an arbitrary team name, your team name must be your CNetIDs in alphabetical order and separated by a hyphen (e.g.,
jdoe-jrandom
).Finally, you must click “Accept this assignment” or your repository will not actually be created.
Once the repository has been created, DO NOT run the commands shown on GitHub to diff --git a/projects/started.html b/projects/started.html index 555b6f1..7ca42ff 100644 --- a/projects/started.html +++ b/projects/started.html @@ -99,13 +99,12 @@
Projects - Getting Started¶
--Warning
-This page has not yet been updated for Spring 2024.
-Before working on the projects, we recommend you check out the UChicago CS Student Resource Guide. In particular, please note the following:
-
-
You must use a CS Software Environment in this class. We may not be able to provide support if you develop and run your code in a different environment. The Student Resource Guide describes several ways of accessing a CS Software Environment (including remote options).
+You should be able to compile and run the code for this class on Windows, MacOS, and Linux. +If you are using a Windows system, you must specifically use WSL (Windows Subsystem for Linux). +We will not be able to provide support if your use Windows PowerShell.
+That said, bear in mind that our code has only been tests on a CS Software Environment. If you would prefer to use such an environment, the Student Resource Guide describes several ways of accessing a CS Software Environment (including remote options).
You can also run your development environment of choice on your personal computer, and connect to a CS machine only to compile, run, and test your code. This is particularly easy to set up using Visual Studio Code. The Student Resource Guide includes instructions on how to set up Visual Studio Code, and how to set it up to SSH into a CS environment.
If you are new to Git, you should work through the Git Basics Tutorial to familiarize yourself with Git.
@@ -115,7 +114,7 @@
documentation on Connecting to GitHub with SSH
Project 3 involves using a network simulator that requires root access on a Linux machine. In the past, we have provided a virtual machine for Project 3 so you could run code with root privileges; this year, we are exploring a few alternate mechanisms that may not involve installing a full virtual machine but, in case we do still have to use the virtual machine, you may want to ensure (well ahead of Project 3) that you are able to install and use the CS virtual machine.
The C style guide in the Student Resource Guide is the normative style guide for this class.
-When asking questions on Ed Discussion, you must follow the guidelines in the Asking Questions page in the Student Resource Guide.
+When asking questions on Ed Discussion, you must follow the guidelines in the Asking Questions section of our Getting Help page.
The Debugging Guide, linked from the guide, contains useful suggestions and pointers on how to debug your C code.