Skip to content
This repository has been archived by the owner on Nov 23, 2021. It is now read-only.

Group Meeting Minutes

Jump to bottom
junhaow1 edited this page Aug 24, 2020 · 21 revisions

Minutes

This page will contain the minutes for all the meetings

Group Meeting 1 - 2020/08/09

Meeting commenced at 1:04pm. All members present.

Meeting closed at 1:38pm. Discussed points listed below.

Team Roles

Team roles are allocated as follows. Responsibilities and decisions for key aspects of these roles will ultimately fall to the people listed. These are broadly defined roles for now.

Backend

  • Joshua Carpeggiani

Frontend

  • Angus Farquhar
  • Haohan Liu

Design/UX/UI & Business

  • Haohan Liu
  • Kevin Wang

Scrum Master

  • Phillip Tinsley

PR Logs

All changes and PRs made will be logged to a file. Already completed by Joshua.

Tests

Responsibility for code coverage and test writing will fall to the developer to cover their additions.

Go

As Go is a new language for many, effort should be made to learn some so everyone understands what is happening in the backend.

Team Name

Epic Portfolio - epicportfol.io

Domain Name Purchase

The domain name epicportfol.io has been purchased from domains.google.com for $95A. All team members willing to contribute 20%.

Custom Email Address

All team members have a unique email address set up at ***@epicportfol.io

Group Meeting 2 - 2020/08/16

Meeting commenced at 2:00pm. All members present.

Meeting closed at 3:02pm Discussed points listed below.

Local Setup

Everyone should try to set up the repo to run locally through docker. Windows require version 2004.

Concerns Regarding Google Cloud Run/Functions

The point that GCR/F cannot support web sockets and other functions was discussed. It was decided that we should not require these features.

User Authentication

User authentication will be implemented 'from-scratch' through JWT in proto. If this is not completed or fails to meet requirements, we will fall back to Firebase authentication.

Database

Data will be handled through PostgreSQL.

Login will store full name and preferred name to accomodate non-standard names.

Hashing and salting of user logins will happen on backend, according to guidelines on security.stackexchange.

Client Meeting 1 - 2020/08/22

Meeting commenced at 3:00pm. All members present.

Meeting closed at 3:35pm Discussed points listed below.

Project Goal

Build an e-portfolio website

Design

The site should take design cues from existing platforms such as LinkedIn.

The site should aim for responsive design.

Users

There will be primarily two types of users. Spectators and profile owners.

Spectators will only be able to view profiles, whereas profile owners can manage their ePortfolio page.

Profile owner uses the desktop to upload files

Technology

The client has no specific requirements for the technology stack.

Potential users

Uni students

recruiter

MVP 1 - Week 6

  • User accounts
  • User register, login/logout
  • User profiles, videos, hyperlink
  • Handling of image presentation

MVP 2 - Week 9

  • User status(online or offline)

User story

Page owner

  • As a page owner, I want to register so that having my own account on this website.
  • As a page owner, I want to login/logout so that I could enter my own page.
  • As a page owner, I want to embed text so that the page could describe myself.
  • As a page owner, I want to embed images/videos so that they support my profile.
  • As a page owner, I want to use templates so that I could make my uploaded files look better formatted.
  • As a page owner, I want to delete/edit files on my page so that my latest uni/work experience will be on the page.
Clone this wiki locally