Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.
Individuals Video, Issue(s), Commits(s)
Video in CPT caption style , includes Web demo of key contribution to project, 1 minute
Issue(s) that show plans/progress to team objectives
Highlights of key commit(s) in Issues, summarizes code contributions
Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks
Per check.
0.55 not attempted/no check
0.7 attempted, incoomplete, but some runtime
0.8 mastery and runtime
0.9 above and beyond.
Freeform comment.
Provide positivies and growth summary.
Justify or comment on final score.
Be sure to provide extra details on anything below 0.7 average or above 0.8.
[x] Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom.
Individuals Video, Issue(s), Commits(s)
[ ] Video in CPT caption style , includes Web demo of key contribution to project, 1 minute
[x] Issue(s) that show plans/progress to team objectives
[x] Highlights of key commit(s) in Issues, summarizes code contributions
[x] Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks
Key contributor Score: 0.97
Good work division
Topic given was Bianry Colors + well thought of user interaction
Talked about team collaboration
Great attitude during presentation
Showed idea making process
Talked about future additions
Video in CPT caption style Score: 0.55
Not added in the Exit Ticket by the time I reviewed it.
Issues Score: 0.68
No Individual Issues in Git Hub Issues. Individual Review Ticket was incomplete but code contributions were explained inperson.
Key Commits: 0.78
Commits are present when checking Team Review but not individually linked. Present when checking contrbution history. Maybe next time could incoporate within the Exit Ticket.
Git Hub Analytics Score: 0.87
Low number of commits but commits have a lot of code in each commit. Evenly distibuted commits (end of each weekish)
FreeForm Comment:
Note that Exit Ticket and Video Link was not complete at grading time but Arnav explained to me some of the key features.
Video Link and Exit Ticket was added later.
I like the work on the Binary Color Vizaulier
lots of vizaulization based on user input
clear Binary link (RBG, darkness scale based on binary)
Individual Review "Arnav" grading "Anusha"
Individual should show that they were key contributor and example to team. This includes their participation in ideas, plans, creating individual issues, providing code commits to project, crossover grading participation, being on task and positive example in the classroom. Individuals Video, Issue(s), Commits(s)
Video in CPT caption style , includes Web demo of key contribution to project, 1 minute Issue(s) that show plans/progress to team objectives Highlights of key commit(s) in Issues, summarizes code contributions Review GitHub analytics for key commits in each weeks during the project, shows consistent participation for 3 weeks Per check. 0.55 not attempted/no check 0.7 attempted, incoomplete, but some runtime 0.8 mastery and runtime 0.9 above and beyond.
Freeform comment. Provide positivies and growth summary. Justify or comment on final score. Be sure to provide extra details on anything below 0.7 average or above 0.8.
https://tdwolff.github.io/NAVTFrontend/basics/colorcode
Link to video: https://youtu.be/WHJqMRG6I0g?si=oBH9KQ0tTXXfn9Ew