Skip to content

Commit

Permalink
final details: speakers, quercus submission notes, slack setup instru…
Browse files Browse the repository at this point in the history
…ctions
  • Loading branch information
michelleark committed Jan 8, 2025
1 parent 188f8fb commit 7b828c7
Showing 10 changed files with 25 additions and 11 deletions.
14 changes: 12 additions & 2 deletions assignments/a1.md
Original file line number Diff line number Diff line change
@@ -28,10 +28,17 @@ Some of these requirements may be duplicated from CSC454/2527, you can use those
1. Company name.
2. A first version of your logo.
3. Team Folder with profiles.
- Include any relevant links to profiles or documents such as your GitHub profile, LinkedIn, Resume, Bio, Twitter profiles, etc
- Include any relevant links to profiles or documents such as your GitHub profile, LinkedIn, Resume, Bio, Twitter profiles, etc
- Be fun, write a small paragraph to help your teammates get to know you more
4. Team Principles
5. Leader election
6. Slack team creation & stand-up workflow setup
- Create a public channel named #team\-\<your-company-name-here> in the DCSIL slack
- Set up a "Weekly check in" Slack Workflow in your team channel for standups
- Bookmark your team repo created in this assignment to your team slack channel
- Create a bookmark section for all other (future) repos your team owns
- See #team-michelle-test for an example!
- All team members must join the public team channel

# What is the purpose of this assignment?

@@ -79,6 +86,8 @@ In your submission, tell us who your "leader" is. Note: this person will potenti

You must [create a release](https://help.github.com/en/articles/creating-releases) on your repo. This will give us a snapshot in time and allow us to grade it. See release body criteria and example below. Assignments without a coherent release body that follow the instructions in this assignment will be rejected and marked 1 day late. See release body criteria and example below. Assignments without a coherent release body that follow the instructions in this assignment will be rejected and marked 1 day late.

One member of your team (could be the team leader, or any other leader) must submit a link to the release in Quercus for 'Assignment 1 - Team Introduction, Team Setup'. Only one team member needs do this.

Assignments are always due at 11:59:59pm Eastern Time.

### Release Body
@@ -108,8 +117,9 @@ Release bodies must include:
| Section | Description | Worth |
| --- | --- | --- |
| Company Logo & Name | Good logo/name that represents a modern idea | 5.0 |
| Slack Setup | Include the name of your `#team-` public Slack channel witin `team/README.md`. Additionally, set up an integration with | 5.0 |
| Team Profiles | Team profiles include photos and profile links of all teammates, clearly lists expertises, and a short biography. This includes all CSC454 members. | 10.0 |
| Leader Selection | Tells us who they chose and why, what is their role for your team? | 15.0 |
| Leader Selection | Tells us who they chose and why, what is their role for your team? | 10.0 |
| Team Principles | The team principles doc is a 1-page doc that covers: expectations of the team members, expectations for communication, roles and responsibilities, work delegation, etc.<br>The document will cover the entire team including CSC454/2527 students. An example can be found [here](./a1_example.md) | 55.0 |
| Participation & Teamwork (Individual Grade) | Effectively worked as a team member and shared equitable work load during this assignment.<br>Communication was regular and effective & acted in accordance with team principles. | 15.0 |
| | **Total:** | 100 |
2 changes: 2 additions & 0 deletions assignments/a2.md
Original file line number Diff line number Diff line change
@@ -64,6 +64,8 @@ Keep in mind that we are not suggesting to selectively hire people based on thei
You must [create a release](https://help.github.com/en/articles/creating-releases) on your repo.
This will give us a snapshot in time and allow us to grade it. See release body criteria and example below. Assignments without a coherent release body that follow the instructions in this assignment will be rejected and marked 1 day late.

One member of your team (could be the team leader, or any other leader) must submit a link to the release in Quercus for 'Assignment 2 - Team Exploration - Bias and Diversity Reflection'. Only one team member needs do this.

Assignments are always due at 11:59:59pm Eastern Time.

### Release Body
2 changes: 2 additions & 0 deletions assignments/a3.md
Original file line number Diff line number Diff line change
@@ -74,6 +74,8 @@ We expect all CSC491/2600 students to actively participate and have thoughtful d
You must [create a release](https://help.github.com/en/articles/creating-releases) on your repo.
This will give us a snapshot in time and allow us to grade it. See release body criteria and example below. Assignments without a coherent release body that follow the instructions in this assignment will be rejected and marked 1 day late.

One member of your team (could be the team leader, or any other leader) must submit a link to the release in Quercus for 'Assignment 3 - Tech Choices, Architecture Diagram, Roadmap'. Only one team member needs do this.

Assignments are always due at 11:59:59pm Eastern Time.

### Release Body
2 changes: 2 additions & 0 deletions assignments/a4.md
Original file line number Diff line number Diff line change
@@ -48,6 +48,8 @@ This will give us a snapshot in time and allow us to grade it. See release body

The release does not need to include pull requests or commits from every member. The body does not even need any content, just ensure it is there and appropriately labelled.

One member of your team (could be the team leader, or any other leader) must submit a link to the release in Quercus for 'Assignment 4 - UX Research'. Only one team member needs do this.

Assignments are always due at 11:59:59pm Eastern Time.

### Release Body
2 changes: 2 additions & 0 deletions assignments/a5.md
Original file line number Diff line number Diff line change
@@ -133,6 +133,8 @@ We expect all CSC491/2600 students to actively participate and have thoughtful d
You must [create a release](https://help.github.com/en/articles/creating-releases) on your repo.
This will give us a snapshot in time and allow us to grade it. See release body criteria and example below. Assignments without a coherent release body that follow the instructions in this assignment will be rejected and marked 1 day late.

One member of your team (could be the team leader, or any other leader) must submit a link to the release in Quercus for 'Assignment 5 - Dev Env, Test Infrastructure, & Production Setup'. Only one team member needs do this.

Assignments are always due at 11:59:59pm Eastern Time.

### Release Body
2 changes: 1 addition & 1 deletion assignments/a6.md
Original file line number Diff line number Diff line change
@@ -33,7 +33,7 @@ Demos _should not_ be a high quality production. You can record your screen for

### Additional Notes

- Demos will happen at the **beginning of class**. Demo order will be chosen at random by randomly selecting from the team list using SQL's `ORDER BY RAND()` function. You must be present for all demos and you must be on time, no excuses or exceptions (other than those noted below) without talking to the instructor _before the class starts_.
- Demos will happen at the **beginning of class**. Demo order will be chosen at random by randomly. You must be present for all demos and you must be on time, no excuses or exceptions (other than those noted below) without talking to the instructor _before the class starts_.
- **Missing the demo**: A student who misses a demo for any reason without first talking to the instructor will lose 25% of the total mark (e.g. 1 of the 4 demos).
- **Late for the demo**: Demos are chosen in a random order. If you are not present for your team's time slot, your team will be pushed down the list. For each slot your team is pushed down the list, you will lose 10% of your mark for that demo (1/4 of all demo marks). If you miss 3 demos (about 15-20 minutes), you will be marked absent for that demo and forfeit the full 25% for that demo.
- **Exceptions**: The above applies to all reasons with the exception of family emergencies or health emergencies. Things like work, TTC, other classes having term tests, etc. are not valid reasons to be late or miss a demo as these situations can be avoided or are known in advance. If you are going to be late due to work, term tests in other classes, etc - you must speak to the instructor _before the class starts_. If you are sick, please notify the instructor before class starts.
2 changes: 2 additions & 0 deletions assignments/a7.md
Original file line number Diff line number Diff line change
@@ -47,6 +47,8 @@ This will give us a snapshot in time and allow us to grade it. See release body

The release does not need to include pull requests or commits from every member. The body does not even need any content, just ensure it is there and appropriately labelled.

One member of your team (could be the team leader, or any other leader) must submit a link to the release in Quercus for 'Capstone Project: Software Submission'. Only one team member needs do this.

Assignments are always due at 11:59:59pm Eastern Time.

### Release Body
2 changes: 1 addition & 1 deletion other_pages/schedule.md
Original file line number Diff line number Diff line change
@@ -14,7 +14,7 @@ This is a class schedule indicating what we aim to do each week and the recommen
| 4 | Wednesday, January 29 2025 | - | Data Platforms & Analytics Landscape | TBD* |
| - | Monday, February 3 2025 | ❗A3 Due | - | - |
| 5 | Wednesday, February 5 2025 | ❗A6 Demo (1/4) | Student Demos | [Elias Tragas](https://www.linkedin.com/in/elias-tragas-a5642163): Staff TLM @ Stack AV - Data & AI Infrastructure for Autonomous Vehicles |
| 6 | Wednesday, February 12 2025 | - | Use Case Reviews | [Arkady Arkhangorodsky](https://ca.linkedin.com/in/arkadyark): Member of Technical Staff @ Cohere - AI Core Infrastructure|
| 6 | Wednesday, February 12 2025 | - | Use Case Reviews | [Arkady Arkhangorodsky](https://ca.linkedin.com/in/arkadyark): Member of Technical Staff @ Cohere - AI Core Infrastructure <br><br>[Olivia Markham](https://www.linkedin.com/in/omarkham/): Member of Technical Staff @ Cohere - Model Training|
| - | Sunday, February 16 2025 | ❗A4 Due | - | - |
| 7 | Wednesday, February 19 2025 | - | Reading Week | - |
| 8 | Wednesday, February 26 2025 | - | Instructor Away, Work in Class | [Allan Zhao](https://ca.linkedin.com/in/yuchi-allan-zhao): TA Tutorial - Topic TBD |
2 changes: 1 addition & 1 deletion policies/communications.md
Original file line number Diff line number Diff line change
@@ -8,7 +8,7 @@ You will see a theme throughout this course centred around communication. This i

#### Some Explicit Expectations

- Your team will have a standup configured on Slack and team members will be expected to respond to it at least once per week.
- Your team will have a standup configured via a Slack workflows and team members will be expected to respond to it at least once per week.
- You will use GitHub Issues to communicate with your team and show your work throughout the term
- Missing demos and other aspects of the class can and will be penalized _if you do not communicate in advance_. I cannot stress this enough - this class is very accommodating of your time and schedule, granted you respect the time of others (including the teaching staff).
- The class is not that large, I know who is attending lectures. I expect you to be able to communicate your needs - are you going to be late due to work? Are you going to be late because you have a class on the other side of campus? Talk to me, and we it won't be an issue.
6 changes: 0 additions & 6 deletions policies/recording.md
Original file line number Diff line number Diff line change
@@ -1,12 +1,6 @@
Video + Audio Recording
---

This course, including your participation, will be recorded on video and will be available to students in the course for viewing remotely and after each session.

Course videos and materials belong to your instructor, the University, and/or other source depending on the specific facts of each situation, and are protected by copyright. In this course, you are permitted to download session videos and materials for your own academic use, but you should not copy, share, or use them for any other purpose without the explicit permission of the instructor.

For questions about recording and use of videos in which you appear please contact your instructor.

### Student Recording

Students may create audio-recordings of the lectures for their personal use. Recordings are intended to permit lecture content review so as to enhance understanding of the topics presented. Audio-recordings are not substitutes for attending class.

0 comments on commit 7b828c7

Please sign in to comment.