Objective
Build a new feature or fix a bug in an existing project and learn how to use source control within a team.
Success criteria
-
You ensure that files that should be ignored for source control purposes on your computer are being ignored before doing anything else.
-
You follow these steps precisely when using source control.
IMPORTANT
Failure to follow these steps leads to problems merging your code into the larger code base, which means everyone’s time is chewed up with problems that could have been avoided.
Your ability to follow these steps is what you are being evaluated on – not the code that you write.
-
Within your assigned GitHub issue, you included visual evidence – screenshot(s) or short screen recording(s) – demonstrating that the issue has been resolved.
This means that the issue you worked on was completed – new functionality was added or a bug was fixed.
-
Use of large language models to assist when writing code is permitted, but:
- if used, must be cited in an AI use log (exemplar / template)
- should be used only when absolutely necessary, as there are significant environmental and cognitive-development costs tied to AI use.
Bottom line
Are you a good member of the team?
If you can answer yes to every question below – you are.
- When other members of the team have a question, I make a real effort to help them.
- I assume best intentions and treat others with kindness and respect.
- I have actually read the steps for using source control within a team and followed them.
- I have a high attention to detail.
- I tested my work and included evidence within the pull request to show that my code changes meet the requirements outlined in the assignment issue.
- I am proactive and ask questions when I am blocked, of myself or the project leader. Put another way – no one has to chase me to for my work to get done.
- Relative to the difficulty level (also known as “size” – XS, S, M, L, XL) of an assigned issue, I complete my work in a timely manner.
UPDATE
The “look-for” items above were added after the first two weeks of the second thread of this course, in advance of the final week of contributions to Musicals @ LCS.
Due date
Your issue should be resolved by the end date noted in your assigned GitHub issue.
As you make progress with this task, on Notion, be sure to share your progress, including screenshots, and asking questions of Mr. Gordon, as needed.
TIP
Finishing an issue earlier – before the assigned end date – so long as you meet all the other criteria noted above – is always better and will provide a modest boost in your grade for this task.
In other words, don’t delay – if you can finish a task sooner rather than later, please do it.
Curriculum connections
This evaluation connects to the following overall Ontario Curriculum expectations for Grade 12 Computer Science:
- A4. Code Maintenance - use proper code maintenance techniques when creating computer programs.
- B1. Project Management - demonstrate the ability to manage the software development process effectively, through all of its stages – planning, development, production, and closing.
- B2. Software Project Contribution - apply standard project management techniques in the context of a student-managed team project.