PROJECT: GETTING STARTED, PART ONE (ntr0)

OBJECTIVE

To get started in your journey in the course this semester

TASK

By the deadline, please do the following:

Finally, there is information regarding the SUBMISSION and evaluation of the project at the tail end of this document.

SIGN ONTO CLASS DISCORD

We will be making use of DISCORD for class communications this semester.

If you already have an existing or preferred account, feel free to use that with this class. You will be identifying yourself, as a follow-on step, so there's no need for a class-specific account.

Please see this page for information on creating your personal DISCORD account, if you do not already have an account.

The invite to the DISCORD class server can be found near the top of the class homepage.

IDENTIFY YOURSELF AND CLASSES ON DISCORD

Once on the class DISCORD server, please identify yourself, along with the classes you are taking so proper roles can be assigned.

This will actually fully satisfy your week1 PARTICIPATION requirement for the class.

PROVIDE GITHUB ACCOUNT

We will be making use of GITHUB this semester in the course. To transact that, you will need to provide the instructor with your preferred GITHUB username you will be using in the class this semester.

You can provide this information via email (haas@corning-cc.edu), or even via DM on DISCORD.

Once your instructor has your GITHUB account, then the magic can happen.

If you already have an existing github account, you are free to use that.

Please see this page for information on creating your personal GITHUB account, if you do not already have an account.

PROVIDE SSH PUBLIC KEY

For various class-related activities this semester, we will be accessing the LAB46 SHELL SYSTEM, a Linux-based command-line environment that will host various course resources.

Access to the system is via SSH KEY only, so you will need to provide the instructor with the SSH PUBLIC KEY(s) you'd like to use to access the system.

Additionally, SSH KEY access is a preferred way of interacting with your GITHUB resources, so the key you use for LAB46 can also be used on GITHUB.

You can provide this information via email (haas@corning-cc.edu), or even via DM on DISCORD.

If you already have an existing SSH PUBLIC KEY, you are free to use that.

If you already have your SSH PUBLIC KEY installed on LAB46, you may already be all set in this regard: try logging in. For everyone else, logging into LAB46 will occur in the follow-up project ntr1.

Please see this page for information on generating an SSH key.

NOTE: If you already have an existing KEY access to LAB46, and wish to add additional KEYS (for additional development systems you find yourself using), just append your new SSH PUBLIC KEY to the end of your ~/.ssh/authorized_keys file on LAB46.

SUBMISSION

26:ntr0:final tally of results (26/26)
*:ntr0:signed into and are active on the class DISCORD [6/6]
*:ntr0:identified self and state classes on DISCORD [7/7]
*:ntr0:provided instructor preferred GITHUB USERNAME [6/6]
*:ntr0:provided instructor preferred SSH PUBLIC KEY [7/7]

Additionally:

  • Solutions not abiding by spirit of project will be subject to a 25% overall deduction
  • Solutions not utilizing descriptive why and how comments will be subject to a 25% overall deduction
  • Solutions not utilizing indentation to promote scope and clarity will be subject to a 25% overall deduction
  • Solutions not organized and easy to read (assume a terminal at least 90 characters wide, 40 characters tall) are subject to a 25% overall deduction