Week 25 Review Ticket - JCC

NEW TEAM STRUCTURES

Most of this was sorted out and covered in a meeting

New members!

  1. Edwin: a great frontender and a beautifully kind soul
  2. Ryan McCoding: CORN!!
  3. Haoxuan: he like Video Game!
  4. Isabelle: Origami turtle??
  5. Aaron: “Chill” - yuricoder07
  6. Kevin: I sat with him in Stats

Triangles!

Aiden is currently managing both triangles in P1 because we have an odd number

Team 1

Name Role
Aiden Subteam Leader/Frontend lead/sass god/some backend
Ishi Frontend
Ekam Backend

Team 2

Name Role
Aiden same guy as before!
Ryan Full stack developer!!
Edwin Frontend

Team 3

Name Role
Drew Subteam Leader/Fully stacked 😱
Raymond Full stack developer
Haoxuan Backend
AJ Full stack developer

Team 4

Name Role
Toby Subteam Leader/DevOps/Backend/Websocket/Branches/Maintainer
Isabelle Backend
Aaron Frontend
Kevin Swing

Team Resources/Methodology

Branches and Merging

We’re still definitely sticking with the branch-based approach to team organization. We’ve updated all new members on this and, if you look at individual contributions, you’ll see some new examples of this.

Scrum Board

We’re continuing our board-oriented scrumming organization device linked here.

Communication

Our team primarily used Slack last trimester, but after our large team we no longer fit in a slack DM which has a limit of 8 people. Instead we have transition to discord, something we are all familiar and comforable with.

Here is what the homepage of our discord server looks like. We have multiple channels (seen on the right) and multiple roles (seen through the different colors by people’s names). Roles correspond to both triangle group and period number. We also have channels for coding help, general channels, important announcements, and resources like our two github repositories and our scrum board.

Here is where our group submits any issues that we need for a review. For example, the current issue is the debugging issue which each member has submitted here, which one of our team leaders will then organize into a single issue.

Here are what the roles in the discord server look like. These roles allow us to better identify and organize who is in each group, as well as communicate only with specific groups through discord’s ping features.

Team Progress

Student Lessons

Our lessons will be covered by subteam 2 (Aiden, Ryan, Edwin) and we will be teaching instances of classes, object instantiation, and 2D arrays.

  • Bulk of lessons handled by Ryan and Edwin
  • Code review from Aiden then to other heads (Toby and Drew)

Planning ticket

Nighthawk Resources

  • Subteam 1 (Aiden, Ishi, Ekam) is focusing on making wireframes to implement new features from new members
  • Subteam 3 (Drew, Raymond, Haoxuan, AJ) is working on deployment
  • Subteam 4 (Toby, Isabelle, Aaron, Kevin) is working on data science related features

Overall Project Goals

In group discussions, we’ve determined three main goals for our site:

  • Finishing base Canvas features (class creation and management, assignment creation and submission, and styling)
  • Following through on data science/graphing features for stats
  • Adding new group members’ project contributions
    • Video call features between student and teacher in a class period
    • Job search features may be mixed with user class period subjects or may be a separate feature for students to use (similar to what Naviance offers)

Individual Contributions

Debugging Events

Name Period Link Comment
Aiden 1 Issue Used both teacher_portfolio and project
Ryan 1 Issue Used project
Ekam 1 Issue Used project
Ishi 1 Issue Used project
Edwin 1 Issue Used teacher_portfolio
Drew 3 Issue Used project
Toby 3 Issue Used project
Raymond 3 Issue Used project
Kevin 3 Issue Used previous tri project
Aaron 3 Issue Used teacher_portfolio
AJ 3 Issue Used project
Haoxuan 3 awaiting Issue Used PENDING
Isabelle 3 awaiting Issue Used PENDING

Github Analytics (at a glance)

Aiden
Edwin
Aaron
Drew
Ryan
Isabelle
Kevin
Ishi
Toby
Ekam
AJ
Raymond
Haoxuan

Project Work

  • Aiden worked on adding drag-and-drop functionality using jQuery UI’s .draggable() and .droppable() methods
  • Drew worked on and successfully fixed authenticate using debugging.
  • AJ worked on fixing an issue with assignment creation using debugging.
  • Kevin worked on transporting job search functionality to the backend within this new branch.
  • Isabelle worked on transporting video call functionality to the backend within this new branch