minutes for tomorrow

[vwade]

notes for Friday

• standups

Whiteboard session

-- team progress, obstacles, and team-based solutions

• identify things that are going well, flowing smoothly, and areas where we feel most confident
• identify any obstacles, issues, and items that are affecting team progress
• identify things that can improve team organization and effectualize progress
• as a team, determine what are our next steps moving forward

Session progress

• zoom call
• each team member shares their screen and describes their progress
• be sure to identify any issues or problems

Project Items

1. Discuss design and layout, CSS styling
2. Discuss API endpoints, GET, POST, and PUT requests -- grades should be permanent
3. Grading system
4. Propose a leveling algorithm. (example, +10% EXP needed per level)

Projects System

1. requires auth
2. when a user visits /projects a list of all available projects will be presented
3. when a user visits /projects/:id the Student will be able to either Enroll in or Submit a project
4. on the FRONT -> GET /projects/:id will retrieve the current project from the API and return an JSON object containing the following:

   {
   "name": "Project name",
   "grade": "0 or greater value of last attempt",
   "enrolled": "boolean of true or false",
   "project": {
       "exp": "Integer value of EXP award",
       "team": "Individual or Group",
       "description": "An introductory paragraph to the project, or Lorem Ipsum",
       "links": [
           "an array of resource URLs for the project",
           "this may include PDF and TXT files"
       ]
   }
   }

5. Project information will be included in the API response. Please use this to populate frontend values.

Enrollment System

1. requires auth
2. when a user is on the Project page (eg. /project/:id)
3. if a user is not enrolled in a Project, and Enroll button is visible on the project page
4. send a POST request to /project/:id
5. if an Assignment already exists that contains the Student ID and Project ID, do not create a new Assignment -- this option should not be available
6. in the API -> create a new Assignment that links the Student to the current Project
7. initialize the Assignment with a grade of 0, and connect it to the Student and Project
8. return a status code 201 Created upon successful creation

Grading System

1. requires authorization
2. when a user clicks Submit on the project page
3. send a PUT request to /submissions
4. the request body should contain the Student ID, Project ID, and Grade
5. in the API call -> retrieve the Assignment that contains the Student's ID and Project's ID
6. if the Assignment cannot be found, then the student is not enrolled in the given project (need: Enroll button, Error page) -- send status 404 Not Found
7. update the values in the Assignment with the values provided from the request body
8. the grade should be the maximum of the current Assignment grade and requested grade
9. return status code 200 OK

model Assignment {
    id               Int     @id @default(autoincrement())
    grade            Int
    student          Student @relation(fields: [studentId], references: [id])
    studentId        Int
    currentProject   Project @relation(fields: [currentProjectId], references: [id])
    currentProjectId Int
}

---

Thursday

• Out of office until 11 am
• Do normal standups and team coordination

---

Wednesday

• standups (what we worked on / what we have planned for today / what's next)
• make the CARDS
• everyone should have assigned themselves at least one task from the cards
• everyone should have started their own feature branch with at least one commit
• everyone should have a clear idea of what they are working on and what they need help with
• each person should only work on one thing at a time -- add to the "In Progress" card slot
• watch and learn, and ask questions

time management

• after our team meetings it is OK to take a break
• everyone should find time to continue working on their tasks and updating their feature branches on their downtime
• if you don't have anything to do, feel free to pull a card from the project and begin working on it
• be sure to move your cards from/to the appropriate status category (todo/in-progress/done)
• if you have new ideas for things or features to work on, as always, make the CARDS
• cards are the way we complete our tasks and the project on time!
• thank you!

MVP requirements

• backend, prisma setup and db migration
• backend, what are the routes we need to set up?
• frontend, creating components and navigation features -- testing
• test everything, debug prep & troubleshooting

questions

• what are we doing well?
• what needs attention?

---

Tuesday

reminder to talk about

• times to meet up / availability
• standups (what we worked on/what needs to be worked on / what's next)
• brainstorm / site wireframe
• db schema
• api & frontend brainstorm

pitch to Lester & Esteban

• learning experience tracker via projects (project learning tracker)
• a process to learn without the need of classes or instructors
• MVP - user profile & project page with EXP calculation
• add videos and learning materials
• add admin/teacher/instructor interface to add new projects
• add ai assistant that is personalized to each student's progress (data procurement & analysis)
• add additional modules to site (info/admin/videos)

new modalities

• peer-to-peer scheduling (time slots / appointments)
• p2p currency