b048046d85c74aa519e44a1fe6ea4bed5498a6b7
haas/spring2026/common/projects/ntr0.md
| ... | ... | @@ -8,16 +8,80 @@ To get started in your journey in the course this semester |
| 8 | 8 | |
| 9 | 9 | By the deadline, please do the following: |
| 10 | 10 | |
| 11 | - * sign onto the class Discord server with your preferred account |
|
| 12 | - * on Discord, identify yourself and indicate what class(es) you are in |
|
| 13 | - * provide the instructor (haas@corning-cc.edu) with your github username |
|
| 14 | - * provide the instructor (haas@corning-cc.edu) with your SSH public key |
|
| 11 | + * [SIGN ONTO CLASS DISCORD](#sign-onto-class-discord) |
|
| 12 | + * [IDENTIFY YOURSELF AND CLASSES ON DISCORD](#identify-yourself-and-classes-on-discord) |
|
| 13 | + * [PROVIDE GITHUB ACCOUNT](#provide-github-account) |
|
| 14 | + * [PROVIDE SSH PUBLIC KEY](#provide-ssh-public-key) |
|
| 15 | 15 | |
| 16 | -NOTE: if desired, your SSH public key may be the same one you use to |
|
| 17 | -access github. |
|
| 16 | +Finally, there is information regarding the [SUBMISSION](#submission) and |
|
| 17 | +evaluation of the project at the tail end of this document. |
|
| 18 | + |
|
| 19 | +### SIGN ONTO CLASS DISCORD |
|
| 20 | + |
|
| 21 | +We will be making use of DISCORD for class communications this semester. |
|
| 22 | + |
|
| 23 | +If you already have an existing or preferred account, feel free to use |
|
| 24 | +that with this class. You will be identifying yourself, as a follow-on |
|
| 25 | +step, so there's no need for a class-specific account. |
|
| 26 | + |
|
| 27 | +Please see [this page](https://support.discord.com/hc/en-us/articles/31676852332439-Discord-Sign-Up-and-Registration-Guide) for information on creating your personal DISCORD account, if you do not already have an account. |
|
| 28 | + |
|
| 29 | +The invite to the DISCORD class server can be found near the top of the |
|
| 30 | +class homepage. |
|
| 31 | + |
|
| 32 | +### IDENTIFY YOURSELF AND CLASSES ON DISCORD |
|
| 33 | + |
|
| 34 | +Once on the class DISCORD server, please identify yourself, along with |
|
| 35 | +the classes you are taking so proper roles can be assigned. |
|
| 36 | + |
|
| 37 | +This will actually fully satisfy your week1 PARTICIPATION requirement for |
|
| 38 | +the class. |
|
| 39 | + |
|
| 40 | +### PROVIDE GITHUB ACCOUNT |
|
| 41 | + |
|
| 42 | +We will be making use of GITHUB this semester in the course. To transact |
|
| 43 | +that, you will need to provide the instructor with your preferred GITHUB |
|
| 44 | +username you will be using in the class this semester. |
|
| 45 | + |
|
| 46 | +You can provide this information via email (`haas@corning-cc.edu`), or |
|
| 47 | +even via DM on DISCORD. |
|
| 48 | + |
|
| 49 | +Once your instructor has your GITHUB account, then the magic can happen. |
|
| 50 | + |
|
| 51 | +If you already have an existing github account, you are free to use that. |
|
| 52 | + |
|
| 53 | +Please see [this page](https://docs.github.com/en/get-started/onboarding/getting-started-with-your-github-account) for information on creating your personal GITHUB account, if you do not already have an account. |
|
| 54 | + |
|
| 55 | +### PROVIDE SSH PUBLIC KEY |
|
| 56 | + |
|
| 57 | +For various class-related activities this semester, we will be accessing |
|
| 58 | +the LAB46 SHELL SYSTEM, a Linux-based command-line environment that will |
|
| 59 | +host various course resources. |
|
| 60 | + |
|
| 61 | +Access to the system is via SSH KEY only, so you will need to provide the |
|
| 62 | +instructor with the SSH PUBLIC KEY(s) you'd like to use to access the |
|
| 63 | +system. |
|
| 64 | + |
|
| 65 | +Additionally, SSH KEY access is a preferred way of interacting with your |
|
| 66 | +GITHUB resources, so the key you use for LAB46 can also be used on |
|
| 67 | +GITHUB. |
|
| 68 | + |
|
| 69 | +You can provide this information via email (`haas@corning-cc.edu`), or |
|
| 70 | +even via DM on DISCORD. |
|
| 71 | + |
|
| 72 | +If you already have an existing SSH PUBLIC KEY, you are free to use that. |
|
| 73 | + |
|
| 74 | +If you already have your SSH PUBLIC KEY installed on LAB46, you may |
|
| 75 | +already be all set in this regard: try logging in. For everyone else, |
|
| 76 | +logging into LAB46 will occur in the follow-up project `ntr1`. |
|
| 18 | 77 | |
| 19 | 78 | Please see [this page](https://docs.github.com/en/authentication/connecting-to-github-with-ssh/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent) for information on generating an SSH key. |
| 20 | 79 | |
| 80 | +NOTE: If you already have an existing KEY access to LAB46, and wish to |
|
| 81 | +add additional KEYS (for additional development systems you find yourself |
|
| 82 | +using), just **append** your new SSH **PUBLIC** KEY to the end of your |
|
| 83 | +`~/.ssh/authorized_keys` file on LAB46. |
|
| 84 | + |
|
| 21 | 85 | ## SUBMISSION |
| 22 | 86 | |
| 23 | 87 | ``` |
haas/spring2026/common/projects/wcpX.md
| ... | ... | @@ -104,20 +104,20 @@ accumulate in a given week to get full credit: |
| 104 | 104 | | week | report | opens on | closes | total points needed | |
| 105 | 105 | | NUM | NAME | | on | | |
| 106 | 106 | | ---- | ------ | -------- | -------- | ------------------- | |
| 107 | -| 1 | wcp1 | 20260122 | 20260128 | 2 | |
|
| 108 | -| 2 | wcp2 | 20260129 | 20260204 | 2 | |
|
| 109 | -| 3 | wcp3 | 20260205 | 20260211 | 4 | |
|
| 110 | -| 4 | wcp4 | 20260212 | 20260218 | 4 | |
|
| 111 | -| 5 | wcp5 | 20260219 | 20260225 | 4 | |
|
| 112 | -| 6 | wcp6 | 20260226 | 20260304 | 4 | |
|
| 113 | -| 7 | wcp7 | 20260305 | 20260311 | 8 | |
|
| 114 | -| 8 | wcp8 | 20260312 | 20260325 | 8 | |
|
| 115 | -| 9 | wcp9 | 20260326 | 20260401 | 8 | |
|
| 116 | -| A | wcpA | 20260402 | 20260408 | 8 | |
|
| 117 | -| B | wcpB | 20260409 | 20260415 | 8 | |
|
| 118 | -| C | wcpC | 20260416 | 20260422 | 8 | |
|
| 119 | -| D | wcpD | 20260423 | 20260429 | 8 | |
|
| 120 | -| E | wcpE | 20260430 | 20260506 | 8 | |
|
| 107 | +| 1 | `wcp1` | 20260122 | 20260128 | 2 | |
|
| 108 | +| 2 | `wcp2` | 20260129 | 20260204 | 2 | |
|
| 109 | +| 3 | `wcp3` | 20260205 | 20260211 | 4 | |
|
| 110 | +| 4 | `wcp4` | 20260212 | 20260218 | 4 | |
|
| 111 | +| 5 | `wcp5` | 20260219 | 20260225 | 4 | |
|
| 112 | +| 6 | `wcp6` | 20260226 | 20260304 | 4 | |
|
| 113 | +| 7 | `wcp7` | 20260305 | 20260311 | 8 | |
|
| 114 | +| 8 | `wcp8` | 20260312 | 20260325 | 8 | |
|
| 115 | +| 9 | `wcp9` | 20260326 | 20260401 | 8 | |
|
| 116 | +| A | `wcpA` | 20260402 | 20260408 | 8 | |
|
| 117 | +| B | `wcpB` | 20260409 | 20260415 | 8 | |
|
| 118 | +| C | `wcpC` | 20260416 | 20260422 | 8 | |
|
| 119 | +| D | `wcpD` | 20260423 | 20260429 | 8 | |
|
| 120 | +| E | `wcpE` | 20260430 | 20260506 | 8 | |
|
| 121 | 121 | |
| 122 | 122 | There are no make-ups. If you miss performing an activity, you can either |
| 123 | 123 | make up the credit by other participation activities, or even make up for |
| ... | ... | @@ -139,7 +139,7 @@ using the `wcp` tool. |
| 139 | 139 | |
| 140 | 140 | It takes 2 arguments: |
| 141 | 141 | |
| 142 | - * the class DESIG you are checking the report on (eg: c4eng, cprog, unix) |
|
| 142 | + * the class `DESIG` you are checking the report on (eg: `c4eng`, `cprog`, `unix`) |
|
| 143 | 143 | * the wcpNUM report name (where NUM is `1` for wcp1/week1) |
| 144 | 144 | |
| 145 | 145 | And you can do so as follows (replace 'DESIG' with your lowercase class |