Office Hours & Communication

Office Hours & Communication#

Announcements#

Announcements will be made via GitHub Release. You can view them online in the releases page or you can get notifications by watching the repository, choosing “Releases” under custom see GitHub docs for instructions with screenshots. You can choose GitHub only or e-mail notificaiton from the notification settings page

Warning

For the first week they will be made by BrightSpace too, but after that, all course activities will be only on GitHub.

Help Hours#

Day Time Location Host
Monday 4:45-6:30 052 Tyler Trevor
Tuesday 3:00-4:00pm 134 Tyler Dr. Brown
Tuesday 11-12:30 052 Tyler Trevor
Tuesday 2:00 - 4:00 Zoom Marcin
Wednesday 2:00 - 4:00 049 Tyler Gyanko
Thursday 11-12:30 052 Tyler Trevor
Friday 2:00 - 4:00 049 Tyler Gyanko
Friday see GH org site Zoom Dr. Brown

Online office hours locations are linked on the GitHub Organization Page

Important

You can only see them if you are a “member” to join, make sure that you have completed Lab 0.

Tips#

For assignment help#

  • send in advance, leave time for a response I check e-mail/github a small number of times per day, during work hours, almost exclusively. You might see me post to this site, post to BrightSpace, or comment on your assignments outside of my normal working hours, but I will not reliably see emails that arrive during those hours. This means that it is important to start assignments early.

Using isses#

  • use issues for content directly related to assignments. If you push your code to the repository and then open an issue, I can see your code and your question at the same time and download it to run it if I need to debug it

  • use issues for questions about this syllabus or class notes. At the top right there’s a GitHub logo that allows you to open a issue (for a question) or suggest an edit (eg if you think there’s a tpo or you find an additional helpful resource related to something)

You can submit a pull request for the typo above, but be sure to check the pull request tab of the repo before submitting to see if it has already been submitted.

For E-mail#

  • use e-mail for general inquiries or notifications

  • Include [CSC392] in the subject line of your email along with the topic of your message. This is important, because your messages are important, but I also get a lot of e-mail. Consider these a cheat code to my inbox: I have setup a filter that will flag your e-mail if you include that in subject to ensure that I see it.

Should you e-mail your work?

No, request a pull request review or make an issue if you are stuck