PROJECT: GETTING STARTED, PART TWO (ntr1)

OBJECTIVE

To continue getting started in your journey in the course this semester. Upon completion of this project, you should have established access to the pertinent class resources we will be utilizing all semester.

TIME MANAGEMENT

Please note that while this project has a DEADLINE, it is not intended for you to crank out all in one sitting, especially at the last minute.

Some steps may require some interaction, or successful completion and processing of steps from other, previous projects in order to proceed.

Be sure to give yourself adequate time and do not run out the clock thinking everything will be smooth sailing. Technical issues could crop up at any time.

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.

READ THE MAGE BOOK

Please take some time to read the "UNIX FOR THE BEGINNING MAGE" PDF that is available for download here

Feel free to ask any questions regarding its content and concepts on the DISCORD.

CREATE PRIVATE REPOSITORY ON GITHUB

On GITHUB, under the account you provided to the instructor, create a new private repository by the name of the current SEMESTER.

Please see this page for information on creating a new repository on github.

NOTE: the suggested name for your repository should be the name of the current SEMESTER. For example, if the semester is fall2026, that would be an ideal name for your new repository.

If you are taking multiple classes by the same instructor, you will be using this same repository for those other classes.

You will want to create subdirectories at the base level of this repository, one for each class you are taking. You may name them after the course DESIGs to facilitate navigation.

DESIG COURSE
cprog CSCS1320 C/C++ Programming
unix CSCS1730 UNIX/Linux Fundamentals
data CSCS2320 Data Structures
discrete CSCS2330 Discrete Structures
comporg CSCS2650 Computer Organization
sysprog CSCS2730 System Programming
c4eng ENGR1050 C for Engineers

You can use the mkdir command to create new directories. And use the ls command to list them.

To reduce confusion, please place all content that may be evaluated in the default main branch of your repository.

ESTABLISH README AND PROVIDE INFO

In your newly created repository on GITHUB, create a README.md file and in it, state the purpose of the repository. Feel free to document additional information pertinent for better understanding or navigating the repository.

Also in your README.md, include an ABOUT ME type of section that provides at least the following information:

  • name or preferred nickname
  • program of study you are matriculated in at CCC (CS, Cyber, IT, etc.)
  • any other information you'd like to share (preferred email, etc.)

An example README.md might contain (replace SEMESTER with the actual semester, DESIG# with specific course DESIG):

# SEMESTER repository for coursework at SUNY CCC

This  is  a repository  for  the  SEMESTER semester,  hosting  individual
coursework for my various courses.

Content is  categorized by course  DESIG, further arranged  by individual
project and exploration name.

## ABOUT ME

Hello, I am NAME. I am a  student enrolled in the PROGRAM program at SUNY
Corning Community College.

Include any preferred nicknames or other pertinent information you'd like
to share.

## DESIG1

This is where content generated during my explorations of DESIG1 will be stored.

## DESIG2

This is where content generated during my explorations of DESIG2 will be stored.

Be sure to add, commit, and push this to your repository. And synchronize any of your clones of this repository by doing a pull.

CHECK AND EDIT REPO CONFIG

To ensure consistent tracking of commits for class evaluation purposes, on each system that you clone your SEMESTER repository on, check the repository config to make sure your name and e-mail are set to recognized, sane values (using LAB46 as an example):

$ git config -l
user.name=Firstname Lastname
user.email=user@corning-cc.edu
...

Make sure your name is properly set, and that your email is set.

PLEASE use your actual name (first/nickname and last name), so that it is clear it is you making commits to repositories.

If you choose to use an e-mail address that is not clearly indicative of who you are, please notify your instructor of your chosen e-mail address so your commits are properly evaluated and credited to you.

Please see this page for information on configuring your name in git.

And then, see this page for information on configuring your e-mail address in git.

Unless you have experience and established preferences, set these values in a global fashion (on each system you're using git on) for convenience and peace of mind.

INVITE INSTRUCTOR TO REPOSITORY

On GITHUB, invite the instructor to be a contributor to this private repo.

Please see this page for information on inviting collaborators to a repository on GITHUB.

If you'd like them to potentially offer assistance, you can give your instructor read/write access. But at a minimum, they must be able to CLONE and READ the repository.

The instructor's GITHUB account is: wedge1020

CONTRIBUTE CONTENT TO CLASS REPO

The class repository will be used for various collaborative class activities, potentially involving:

  • recording, organizing, presenting of class notes
  • performing some prescribed documentation activity
  • working on a collaborative class project

The aim is for your regular (weekly) interaction in this repository to (in part), count towards the JOURNAL component of your grade.

A suggested ntr1-level contribution would be contributing to the course notes: ensure it contains the relevant information for getting started, as experienced across both ntr0 and ntr1, along with any additional informational tidbits you've encountered/discovered.

We may want to have a FREQUENTLY ASKED QUESTIONS section as well, where class members can pose questions, to have others respond to them.

SUBMISSION

Once again, no manual submission is needed: evaluation is able to be performed if you have successfully completed the needed steps described above.

52:ntr1:final tally of results (52/52)
*:ntr1:created private SEMESTER repository on GITHUB [13/13]
*:ntr1:establish README and provide requested info [13/13]
*:ntr1:invited instructor to your private SEMESTER repo [13/13]
*:ntr1:contribute content to class repository [13/13]

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