diff --git a/.eslintrc.json b/.eslintrc.json index c708a1f..3df5505 100644 --- a/.eslintrc.json +++ b/.eslintrc.json @@ -1,33 +1,20 @@ -{ - "env": { - "browser": true, - "es2021": true, - "node": true - }, - "extends": "eslint:recommended", - "overrides": [ - ], - "parserOptions": { - "ecmaVersion": "latest", - "sourceType": "module" - }, - "rules": { - "indent": [ - "error", - "tab" - ], - "linebreak-style": [ - "error", - "unix" - ], - "quotes": [ - "error", - "double" - ], - "semi": [ - "error", - "always" - ], - "no-global-assign": 0 - } -} +{ + "env": { + "browser": true, + "es2021": true, + "node": true + }, + "extends": "eslint:recommended", + "overrides": [], + "parserOptions": { + "ecmaVersion": "latest", + "sourceType": "module" + }, + "rules": { + "indent": ["error", "tab"], + "linebreak-style": ["error", "unix"], + "quotes": ["error", "double"], + "semi": ["error", "always"], + "no-global-assign": 0 + } +} diff --git a/.github/workflows/css-linting.yml b/.github/workflows/css-linting.yml index 48b333a..4400716 100644 --- a/.github/workflows/css-linting.yml +++ b/.github/workflows/css-linting.yml @@ -1,23 +1,23 @@ -name: CSS Linting - -on: - pull_request: - branches: - - main - - # Allows you to run this workflow manually from the Actions tab - workflow_dispatch: - -jobs: - # Single deploy job since we're just deploying - test: - runs-on: ubuntu-latest - steps: - - name: Install apt updates - run: sudo apt -y update; sudo apt -y upgrade; - - name: Checkout - uses: actions/checkout@v3 - - name: Install dependencies - run: sudo npm install - - name: Run tests - run: sudo npm run lint-css \ No newline at end of file +name: CSS Linting + +on: + pull_request: + branches: + - main + + # Allows you to run this workflow manually from the Actions tab + workflow_dispatch: + +jobs: + # Single deploy job since we're just deploying + test: + runs-on: ubuntu-latest + steps: + - name: Install apt updates + run: sudo apt -y update; sudo apt -y upgrade; + - name: Checkout + uses: actions/checkout@v3 + - name: Install dependencies + run: sudo npm install + - name: Run tests + run: sudo npm run lint-css diff --git a/.github/workflows/deploy-githubpages.yml b/.github/workflows/deploy-githubpages.yml index 17c672b..3a6471c 100644 --- a/.github/workflows/deploy-githubpages.yml +++ b/.github/workflows/deploy-githubpages.yml @@ -1,53 +1,53 @@ -# Simple workflow for deploying static content to GitHub Pages -name: Deploy GitHub Pages - -on: - # Runs on pushes targeting the default branch - push: - branches: - - main - - # Allows you to run this workflow manually from the Actions tab - workflow_dispatch: - -# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages -permissions: - contents: read - pages: write - id-token: write - -# Allow one concurrent deployment -concurrency: - group: "pages" - cancel-in-progress: true - -jobs: - # Single deploy job since we're just deploying - deploy: - environment: - name: github-pages - url: ${{ steps.deployment.outputs.page_url }} - runs-on: ubuntu-latest - steps: - - name: Install apt updates - run: sudo apt -y update; sudo apt -y upgrade; - - name: Install prerequisites - uses: actions/setup-node@v3 - with: - node-version: 18 - - name: Checkout - uses: actions/checkout@v3 - - name: Install dependencies - run: sudo npm install - - name: Run tests - run: sudo npm run js-doc - - name: Setup Pages - uses: actions/configure-pages@v2 - - name: Upload artifact - uses: actions/upload-pages-artifact@v1 - with: - # Upload only the src repository - path: './source/' - - name: Deploy to GitHub Pages - id: deployment - uses: actions/deploy-pages@v1 +# Simple workflow for deploying static content to GitHub Pages +name: Deploy GitHub Pages + +on: + # Runs on pushes targeting the default branch + push: + branches: + - main + + # Allows you to run this workflow manually from the Actions tab + workflow_dispatch: + +# Sets permissions of the GITHUB_TOKEN to allow deployment to GitHub Pages +permissions: + contents: read + pages: write + id-token: write + +# Allow one concurrent deployment +concurrency: + group: "pages" + cancel-in-progress: true + +jobs: + # Single deploy job since we're just deploying + deploy: + environment: + name: github-pages + url: ${{ steps.deployment.outputs.page_url }} + runs-on: ubuntu-latest + steps: + - name: Install apt updates + run: sudo apt -y update; sudo apt -y upgrade; + - name: Install prerequisites + uses: actions/setup-node@v3 + with: + node-version: 18 + - name: Checkout + uses: actions/checkout@v3 + - name: Install dependencies + run: sudo npm install + - name: Run tests + run: sudo npm run js-doc + - name: Setup Pages + uses: actions/configure-pages@v2 + - name: Upload artifact + uses: actions/upload-pages-artifact@v1 + with: + # Upload only the src repository + path: "./source/" + - name: Deploy to GitHub Pages + id: deployment + uses: actions/deploy-pages@v1 diff --git a/.github/workflows/html-linting.yml b/.github/workflows/html-linting.yml index c24292b..d1cf355 100644 --- a/.github/workflows/html-linting.yml +++ b/.github/workflows/html-linting.yml @@ -1,23 +1,23 @@ -name: HTML Linting - -on: - pull_request: - branches: - - main - - # Allows you to run this workflow manually from the Actions tab - workflow_dispatch: - -jobs: - # Single deploy job since we're just deploying - test: - runs-on: ubuntu-latest - steps: - - name: Install apt updates - run: sudo apt -y update; sudo apt -y upgrade; - - name: Checkout - uses: actions/checkout@v3 - - name: Install dependencies - run: sudo npm install - - name: Run tests - run: sudo npm run lint-html +name: HTML Linting + +on: + pull_request: + branches: + - main + + # Allows you to run this workflow manually from the Actions tab + workflow_dispatch: + +jobs: + # Single deploy job since we're just deploying + test: + runs-on: ubuntu-latest + steps: + - name: Install apt updates + run: sudo apt -y update; sudo apt -y upgrade; + - name: Checkout + uses: actions/checkout@v3 + - name: Install dependencies + run: sudo npm install + - name: Run tests + run: sudo npm run lint-html diff --git a/.github/workflows/js-linting.yml b/.github/workflows/js-linting.yml index b642926..bda9cf5 100644 --- a/.github/workflows/js-linting.yml +++ b/.github/workflows/js-linting.yml @@ -1,25 +1,25 @@ -name: JS Linting - -on: - pull_request: - branches: - - main - - # Allows you to run this workflow manually from the Actions tab - workflow_dispatch: - -jobs: - # Single deploy job since we're just deploying - test: - runs-on: ubuntu-latest - steps: - - name: Install apt updates - run: sudo apt -y update; sudo apt -y upgrade; - - name: Install prerequisites - run: sudo apt install -y nodejs npm; - - name: Checkout - uses: actions/checkout@v3 - - name: Install dependencies - run: sudo npm install - - name: Run tests - run: sudo npm run lint-js \ No newline at end of file +name: JS Linting + +on: + pull_request: + branches: + - main + + # Allows you to run this workflow manually from the Actions tab + workflow_dispatch: + +jobs: + # Single deploy job since we're just deploying + test: + runs-on: ubuntu-latest + steps: + - name: Install apt updates + run: sudo apt -y update; sudo apt -y upgrade; + - name: Install prerequisites + run: sudo apt install -y nodejs npm; + - name: Checkout + uses: actions/checkout@v3 + - name: Install dependencies + run: sudo npm install + - name: Run tests + run: sudo npm run lint-js diff --git a/.github/workflows/js-unittest.yml b/.github/workflows/js-unittest.yml index 918ce70..daaab10 100644 --- a/.github/workflows/js-unittest.yml +++ b/.github/workflows/js-unittest.yml @@ -1,29 +1,29 @@ name: JS Unit Test on: - pull_request: - branches: - - main + pull_request: + branches: + - main - # Allows you to run this workflow manually from the Actions tab - workflow_dispatch: + # Allows you to run this workflow manually from the Actions tab + workflow_dispatch: jobs: - # Single deploy job since we're just deploying - test: - runs-on: ubuntu-latest - steps: - - name: Install apt updates - run: sudo apt -y update; sudo apt -y upgrade; - - name: Install prerequisites - uses: actions/setup-node@v3 - with: - node-version: 18 - - name: Checkout - uses: actions/checkout@v3 - - name: Install dependencies - run: sudo npm install - - name: Start local http server - run: sudo npm run http-server & - - name: Run tests - run: sudo npm test \ No newline at end of file + # Single deploy job since we're just deploying + test: + runs-on: ubuntu-latest + steps: + - name: Install apt updates + run: sudo apt -y update; sudo apt -y upgrade; + - name: Install prerequisites + uses: actions/setup-node@v3 + with: + node-version: 18 + - name: Checkout + uses: actions/checkout@v3 + - name: Install dependencies + run: sudo npm install + - name: Start local http server + run: sudo npm run http-server & + - name: Run tests + run: sudo npm test diff --git a/.github/workflows/prettier-linting.yml b/.github/workflows/prettier-linting.yml new file mode 100644 index 0000000..550780c --- /dev/null +++ b/.github/workflows/prettier-linting.yml @@ -0,0 +1,27 @@ +name: Prettier + +on: + pull_request: + branches: + - main + + # Allows you to run this workflow manually from the Actions tab + workflow_dispatch: + +jobs: + # Single deploy job since we're just deploying + test: + runs-on: ubuntu-latest + steps: + - name: Install apt updates + run: sudo apt -y update; sudo apt -y upgrade; + - name: Install prerequisites + uses: actions/setup-node@v3 + with: + node-version: 18 + - name: Checkout + uses: actions/checkout@v3 + - name: Install dependencies + run: sudo npm install + - name: Run tests + run: sudo npm run lint-prettier diff --git a/.github/workflows/prettier.yml b/.github/workflows/prettier.yml deleted file mode 100644 index 8003d23..0000000 --- a/.github/workflows/prettier.yml +++ /dev/null @@ -1,29 +0,0 @@ -name: Prettier - -on: - pull_request: - branches: - - main - - # Allows you to run this workflow manually from the Actions tab - workflow_dispatch: - -jobs: - # Single deploy job since we're just deploying - test: - runs-on: ubuntu-latest - steps: - - name: Install apt updates - run: sudo apt -y update; sudo apt -y upgrade; - - name: Install prerequisites - uses: actions/setup-node@v3 - with: - node-version: 18 - - name: Checkout - uses: actions/checkout@v3 - - name: Install dependencies - run: sudo npm install - - name: Start local http server - run: sudo npm run http-server & - - name: Run tests - run: sudo npm lint-prettier \ No newline at end of file diff --git a/.htmlhintrc b/.htmlhintrc index c833339..10b35f2 100644 --- a/.htmlhintrc +++ b/.htmlhintrc @@ -1,4 +1,4 @@ -{ - "attr-value-not-empty": false, - "space-tab-mixed-disabled": "tab" -} +{ + "attr-value-not-empty": false, + "space-tab-mixed-disabled": "tab" +} diff --git a/.prettierrc.json b/.prettierrc.json new file mode 100644 index 0000000..3a2e4ee --- /dev/null +++ b/.prettierrc.json @@ -0,0 +1,5 @@ +{ + "printWidth": 160, + "tabWidth": 4, + "useTabs": true +} diff --git a/.stylelintrc.json b/.stylelintrc.json index c3e95e2..ec100eb 100644 --- a/.stylelintrc.json +++ b/.stylelintrc.json @@ -1,7 +1,7 @@ { "extends": "stylelint-config-standard", "ignore": ["inside-parens", "param", "value"], - "rules":{ + "rules": { "indentation": "tab" } -} \ No newline at end of file +} diff --git a/110722-sprint1.md b/110722-sprint1.md index 264f428..ca5883a 100644 --- a/110722-sprint1.md +++ b/110722-sprint1.md @@ -1,9 +1,13 @@ # Meeting Minutes (11/07/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: First Sprint + Meeting notes for the first sprint ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Gavyn Ezell @@ -15,27 +19,29 @@ Meeting notes for the first sprint 9. Arthur Lu ## Absentees + 1. Isaac Otero ## Meeting Details -- When: 11/07/2022 at 6:00PM -- Where: CSE Building Second Floor + +- When: 11/07/2022 at 6:00PM +- Where: CSE Building Second Floor ## Agenda: -- ### Old/Unresolved Business - - N/A -- ### New Business - - The first sprint: - - Create more Gitflows and automation. Verify current workflows and actions - - Determine interface details for the app (user experience) - - Start on the backend -- ### Next Meeting's Business + +- ### Old/Unresolved Business + - N/A +- ### New Business + - The first sprint: + - Create more Gitflows and automation. Verify current workflows and actions + - Determine interface details for the app (user experience) + - Start on the backend +- ### Next Meeting's Business ## Decisions Made -- Linting details decided (TABS NOT SPACES) + +- Linting details decided (TABS NOT SPACES) ## End Time -- 11/07/2022 at 8:00PM - - +- 11/07/2022 at 8:00PM diff --git a/README.md b/README.md index 4a2b1cf..45169df 100644 --- a/README.md +++ b/README.md @@ -2,4 +2,4 @@ [Team Page Link](https://github.com/cse110-fa22-group29/cse110-fa22-group29/blob/main/admin/team.md) -[Food Journal](https://cse110-fa22-group29.github.io/cse110-fa22-group29/) \ No newline at end of file +[Food Journal](https://cse110-fa22-group29.github.io/cse110-fa22-group29/) diff --git a/admin/cipipeline/phase1.md b/admin/cipipeline/phase1.md index ccb48f0..81345ce 100644 --- a/admin/cipipeline/phase1.md +++ b/admin/cipipeline/phase1.md @@ -1,39 +1,39 @@ -# CI/CD Phase 1 - -## Overall Pipeline Architecture - -Rather than create one large pipeline with many steps which increases complexity, we decided to create many small independent pipelines which work in parallel to conduct code quality checking. Using this strategy, if any one pipeline has issues, we can still continue development without delay, and the quality of code is likely to remain high. - -## Overview of Pipeline Features - -We've identified 5 major features which we definitely want to implement in the CI/CD pipeline. - -- Deployment -- Unit Testing -- Linting -- End To End Validation -- Manual Validation - -We created this diagram to demonstrate our strategy of multiple simple pipelines. - -![Pipeline Diagram](phase1.drawio.png) - -## Finished Features and Implementation - -So far the features listed below have been completed to some degree: - -- Deployment - - Implemented: action triggered on any push to main, uses the github pages action to publish the app - - ToDo: Add minifications ste between trigger and github pages action -- Unit Testing - - Implemented: action triggers on any PR, uses mocha to perform unit testing on core components - - ToDo: trigger workflow only on certain PRs which relate to JS code -- Linting (JS) - - Implemented: ction triggers on any PR, uses eslint to perform style enforcement on all JS components - - ToDo: trigger workflow only on certain PRs which relate to JS code -- Linting (HTML) - - Implemented: action triggers on any PR, uses HTMLhint to perform style enforcement on all HTML components -- Linting (CSS) - - Implemented: action triggers on any PR, uses Stylelint to perform style enforcement on all CSS components - -## Planned Features and Timeline +# CI/CD Phase 1 + +## Overall Pipeline Architecture + +Rather than create one large pipeline with many steps which increases complexity, we decided to create many small independent pipelines which work in parallel to conduct code quality checking. Using this strategy, if any one pipeline has issues, we can still continue development without delay, and the quality of code is likely to remain high. + +## Overview of Pipeline Features + +We've identified 5 major features which we definitely want to implement in the CI/CD pipeline. + +- Deployment +- Unit Testing +- Linting +- End To End Validation +- Manual Validation + +We created this diagram to demonstrate our strategy of multiple simple pipelines. + +![Pipeline Diagram](phase1.drawio.png) + +## Finished Features and Implementation + +So far the features listed below have been completed to some degree: + +- Deployment + - Implemented: action triggered on any push to main, uses the github pages action to publish the app + - ToDo: Add minifications ste between trigger and github pages action +- Unit Testing + - Implemented: action triggers on any PR, uses mocha to perform unit testing on core components + - ToDo: trigger workflow only on certain PRs which relate to JS code +- Linting (JS) + - Implemented: ction triggers on any PR, uses eslint to perform style enforcement on all JS components + - ToDo: trigger workflow only on certain PRs which relate to JS code +- Linting (HTML) + - Implemented: action triggers on any PR, uses HTMLhint to perform style enforcement on all HTML components +- Linting (CSS) + - Implemented: action triggers on any PR, uses Stylelint to perform style enforcement on all CSS components + +## Planned Features and Timeline diff --git a/admin/cipipeline/phase2.md b/admin/cipipeline/phase2.md index 5075e7c..56f21dc 100644 --- a/admin/cipipeline/phase2.md +++ b/admin/cipipeline/phase2.md @@ -1,47 +1,48 @@ -# CI/CD Phase 2 - -## Overall Pipeline Architecture - -Rather than create one large pipeline with many steps which increases complexity, we decided to create many small independent pipelines which work in parallel to conduct code quality checking. Using this strategy, if any one pipeline has issues, we can still continue development without delay, and the quality of code is likely to remain high. - -## Overview of Pipeline Features - -We've identified 5 major features which we definitely want to implement in the CI/CD pipeline. - -- Deployment -- Unit Testing -- Linting -- End To End Validation -- Manual Validation - -We also identified some features which are nice to have: -- Automatic documentation publishing -- Minification -- HTML Validation and accessibility scoring - -We created this diagram to demonstrate our strategy of multiple simple pipelines. - -![Pipeline Diagram](phase2.drawio.png) - -## Finished Features and Implementation - -So far the features listed below have been completed to some degree: - -- Deployment - - Implemented: action triggered on any push to main, uses the github pages action to publish the app - - Implemented: uses JSDoc to generate documentation on the same site at [docs](https://cse110-fa22-group29.github.io/cse110-fa22-group29/docs/) - - ToDo: Add minification step between trigger and github pages action -- Unit Testing - - Implemented: action triggers on PR to main, uses mocha to perform unit testing on core components -- End to end testing - - Implemented: action triggers on PR to main, uses mocha and puppeteer to perform end to end testing -- Linting (JS) - - Implemented: action triggers on PR to main, uses eslint to perform style enforcement on all JS components -- Linting (HTML) - - Implemented: action triggers on PR to main, uses HTMLhint to perform style enforcement on all HTML components -- Linting (CSS) - - Implemented: action triggers on PR to main, uses Stylelint to perform style enforcement on all CSS components -- Linting (general) - - Implemented: action triggers on PR to main, uses Prettier to perform style checking on all file types - -## Planned Features and Timeline +# CI/CD Phase 2 + +## Overall Pipeline Architecture + +Rather than create one large pipeline with many steps which increases complexity, we decided to create many small independent pipelines which work in parallel to conduct code quality checking. Using this strategy, if any one pipeline has issues, we can still continue development without delay, and the quality of code is likely to remain high. + +## Overview of Pipeline Features + +We've identified 5 major features which we definitely want to implement in the CI/CD pipeline. + +- Deployment +- Unit Testing +- Linting +- End To End Validation +- Manual Validation + +We also identified some features which are nice to have: + +- Automatic documentation publishing +- Minification +- HTML Validation and accessibility scoring + +We created this diagram to demonstrate our strategy of multiple simple pipelines. + +![Pipeline Diagram](phase2.drawio.png) + +## Finished Features and Implementation + +So far the features listed below have been completed to some degree: + +- Deployment + - Implemented: action triggered on any push to main, uses the github pages action to publish the app + - Implemented: uses JSDoc to generate documentation on the same site at [docs](https://cse110-fa22-group29.github.io/cse110-fa22-group29/docs/) + - ToDo: Add minification step between trigger and github pages action +- Unit Testing + - Implemented: action triggers on PR to main, uses mocha to perform unit testing on core components +- End to end testing + - Implemented: action triggers on PR to main, uses mocha and puppeteer to perform end to end testing +- Linting (JS) + - Implemented: action triggers on PR to main, uses eslint to perform style enforcement on all JS components +- Linting (HTML) + - Implemented: action triggers on PR to main, uses HTMLhint to perform style enforcement on all HTML components +- Linting (CSS) + - Implemented: action triggers on PR to main, uses Stylelint to perform style enforcement on all CSS components +- Linting (general) + - Implemented: action triggers on PR to main, uses Prettier to perform style checking on all file types + +## Planned Features and Timeline diff --git a/admin/meetings/101122-kickoff.md b/admin/meetings/101122-kickoff.md index c77c288..72ae174 100644 --- a/admin/meetings/101122-kickoff.md +++ b/admin/meetings/101122-kickoff.md @@ -1,47 +1,54 @@ -# Meeting Minutes (10/12/2022) -## Team 29: Hackers1995 -## Meeting Topic: Kickoff Meeting -This meeting is being held to kickoff the start of many meetings to come during the quarter. -## Attendance -1. Rhea Bhutada -2. George Dubinin -3. Gavyn Ezell -4. Henry Feng -5. Kara Hoagland -6. Marc Reta -7. Sanjit Joseph -8. Isaac Otero -9. Daniel Hernandez - -## Absentees -1. Arthur Lu - -## Meeting Details -- When: 10/12/2022 at 3:30PM -- Where: Zoom - -## Agenda: -- ### Old/Unresolved Business - - N/A -- ### New Business - - go over github organization - - review assignments - - go through rules - - start branding/team name -- ### Next Meeting's Business - - figure out roles - - decide weekly meeting times - - figure out team bonding events - - brainstorm CRUD applications - - complete any remaining assignments - -## Decisions Made -- went over github organizations and reviewed the assignments -- went through the rules and agreed on the contract -- figured out the brand name - -## End Time -- 10/12/2022 at 4:30PM - - - +# Meeting Minutes (10/12/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Kickoff Meeting + +This meeting is being held to kickoff the start of many meetings to come during the quarter. + +## Attendance + +1. Rhea Bhutada +2. George Dubinin +3. Gavyn Ezell +4. Henry Feng +5. Kara Hoagland +6. Marc Reta +7. Sanjit Joseph +8. Isaac Otero +9. Daniel Hernandez + +## Absentees + +1. Arthur Lu + +## Meeting Details + +- When: 10/12/2022 at 3:30PM +- Where: Zoom + +## Agenda: + +- ### Old/Unresolved Business + - N/A +- ### New Business + - go over github organization + - review assignments + - go through rules + - start branding/team name +- ### Next Meeting's Business + - figure out roles + - decide weekly meeting times + - figure out team bonding events + - brainstorm CRUD applications + - complete any remaining assignments + +## Decisions Made + +- went over github organizations and reviewed the assignments +- went through the rules and agreed on the contract +- figured out the brand name + +## End Time + +- 10/12/2022 at 4:30PM diff --git a/admin/meetings/101222-checkin1.md b/admin/meetings/101222-checkin1.md index d31c903..d45c369 100644 --- a/admin/meetings/101222-checkin1.md +++ b/admin/meetings/101222-checkin1.md @@ -1,32 +1,41 @@ -# Meeting Minutes (10/12/2022) -## Team 29: Hackers1995 -## Meeting Topic: Weekly Check-In Meeting -This meeting is the first weekly meeting with TA -## Attendance -1. Gagan Gopalaiah -2. Rhea Bhutada -3. Kara Hoagland -4. Marc Reta -5. Arthur - -## Meeting Details -- When: 10/12/2022 at 8:00PM -- Where: Zoom - -## Agenda: -- ### Reviewed Project Details - - building CRUD app - - utilizing HTML, CSS, JavaScript - - general domain is better than specific domain -- ### Get Started early - - brainstorm CRUD apps - - review assignments - - figure out unit test code - - familiarize yourself with GitHub Actions - -## Important Information -- Gagan OH (6:30PM-7:30PM on Wednesday) in CSE Basement -- Reserved the room if any of us want to meet there. TA not going to present unless required. - -## End Time -- 10/12/2022 at 8:30PM \ No newline at end of file +# Meeting Minutes (10/12/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Weekly Check-In Meeting + +This meeting is the first weekly meeting with TA + +## Attendance + +1. Gagan Gopalaiah +2. Rhea Bhutada +3. Kara Hoagland +4. Marc Reta +5. Arthur + +## Meeting Details + +- When: 10/12/2022 at 8:00PM +- Where: Zoom + +## Agenda: + +- ### Reviewed Project Details + - building CRUD app + - utilizing HTML, CSS, JavaScript + - general domain is better than specific domain +- ### Get Started early + - brainstorm CRUD apps + - review assignments + - figure out unit test code + - familiarize yourself with GitHub Actions + +## Important Information + +- Gagan OH (6:30PM-7:30PM on Wednesday) in CSE Basement +- Reserved the room if any of us want to meet there. TA not going to present unless required. + +## End Time + +- 10/12/2022 at 8:30PM diff --git a/admin/meetings/101922-checkin2.md b/admin/meetings/101922-checkin2.md index 5286bc1..cfbecc6 100644 --- a/admin/meetings/101922-checkin2.md +++ b/admin/meetings/101922-checkin2.md @@ -1,50 +1,62 @@ -# Meeting Minutes (10/19/2022) -## Team 29: Hackers1995 -## Meeting Topic: Weekly Check-In Meeting -This meeting is the second weekly meeting with TA. - -## Attendance -1. Gagan Gopalaiah -2. Rhea Bhutada -3. George Dubinin -4. Kara Hoagland -5. Marc Reta -6. Arthur Lu -7. Gavyn Ezell -8. Isaac Otero - -## Meeting Details -- When: 10/19/2022 at 8:00PM -- Where: Zoom - -## Agenda: -- ### Recap of last week - - went over assignments - - discussed feelings on the midterm - -- ### New Potential Meeting Time - - without TA unless necessary - - before lecture on Monday in CSE Basement - -- ### Upcoming Assignments - - two coming up - - brainstorm activity (due 10/23) - - continue brainstorming throughout the week - - due sunday - - pitch (11/1) - - initial draft by 10/25 - 10/26 - -- ### Tips on Designing - - user center design - - define the problem first, then the tools/techniques - - finalize on the product and its features, then decide on how to build it - -- ### Standup - - not expected everyday - - once every two days is ideal - - doesn't have to be too descriptive - -- ### Review of Recent Brainstorming Session - -## End Time -- 10/19/2022 at 3:50PM \ No newline at end of file +# Meeting Minutes (10/19/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Weekly Check-In Meeting + +This meeting is the second weekly meeting with TA. + +## Attendance + +1. Gagan Gopalaiah +2. Rhea Bhutada +3. George Dubinin +4. Kara Hoagland +5. Marc Reta +6. Arthur Lu +7. Gavyn Ezell +8. Isaac Otero + +## Meeting Details + +- When: 10/19/2022 at 8:00PM +- Where: Zoom + +## Agenda: + +- ### Recap of last week + + - went over assignments + - discussed feelings on the midterm + +- ### New Potential Meeting Time + + - without TA unless necessary + - before lecture on Monday in CSE Basement + +- ### Upcoming Assignments + + - two coming up + - brainstorm activity (due 10/23) + - continue brainstorming throughout the week + - due sunday + - pitch (11/1) + - initial draft by 10/25 - 10/26 + +- ### Tips on Designing + + - user center design + - define the problem first, then the tools/techniques + - finalize on the product and its features, then decide on how to build it + +- ### Standup + + - not expected everyday + - once every two days is ideal + - doesn't have to be too descriptive + +- ### Review of Recent Brainstorming Session + +## End Time + +- 10/19/2022 at 3:50PM diff --git a/admin/meetings/102122-brainstorm.md b/admin/meetings/102122-brainstorm.md index 9f8f7c0..6b53bcd 100644 --- a/admin/meetings/102122-brainstorm.md +++ b/admin/meetings/102122-brainstorm.md @@ -1,44 +1,54 @@ -# Meeting Minutes (10/21/2022) -## Team 29: Hackers1995 -## Meeting Topic: Application Brainstorming -This meeting is held to help the group decide on what application. We will also discuss preliminary designs. -## Attendance -1. George Dubinin -2. Gavyn Ezell -3. Henry Feng -4. Arthur Lu -5. Marc Reta -6. Kara Hoagland -7. Sanjit Joseph -8. Rhea Bhutada -9. Isaac Otero -10. Daniel Hernandez - -## Absentees -N/A - -## Meeting Details -- When: - - 10/21/2022 at 10:00AM - - 10/21/2022 at 1:30PM -- Where: Zoom - -## Agenda: -- ### Old/Unresolved Business - - N/A -- ### New Business - - List ideas that have been shared so far - - List new ideas/ideas that haven't been recorded on the doc yet - - Discuss, vote, and decide on one idea -- ### Next Meeting's Business - - Discuss design features for the chosen app - -## Decisions Made -- Added UCSD Food Reviewer App idea to the brainstorming doc -- The 10AM group cast 3 votes for the Social Media Auxilary and 1 vote for the UCSD Food Reviewer App (one participant voted twice) -- The 1:30PM group cast 7 votes for the UCSD Food Reviewer App and 5 votes for the Copy/Paste App -- We will move forward with the UCSD Food Reviewer App - -## End Time -- 10/21/2022 at 11:00AM -- 10/21/2022 at 2:30PM \ No newline at end of file +# Meeting Minutes (10/21/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Application Brainstorming + +This meeting is held to help the group decide on what application. We will also discuss preliminary designs. + +## Attendance + +1. George Dubinin +2. Gavyn Ezell +3. Henry Feng +4. Arthur Lu +5. Marc Reta +6. Kara Hoagland +7. Sanjit Joseph +8. Rhea Bhutada +9. Isaac Otero +10. Daniel Hernandez + +## Absentees + +N/A + +## Meeting Details + +- When: + - 10/21/2022 at 10:00AM + - 10/21/2022 at 1:30PM +- Where: Zoom + +## Agenda: + +- ### Old/Unresolved Business + - N/A +- ### New Business + - List ideas that have been shared so far + - List new ideas/ideas that haven't been recorded on the doc yet + - Discuss, vote, and decide on one idea +- ### Next Meeting's Business + - Discuss design features for the chosen app + +## Decisions Made + +- Added UCSD Food Reviewer App idea to the brainstorming doc +- The 10AM group cast 3 votes for the Social Media Auxilary and 1 vote for the UCSD Food Reviewer App (one participant voted twice) +- The 1:30PM group cast 7 votes for the UCSD Food Reviewer App and 5 votes for the Copy/Paste App +- We will move forward with the UCSD Food Reviewer App + +## End Time + +- 10/21/2022 at 11:00AM +- 10/21/2022 at 2:30PM diff --git a/admin/meetings/102322-decision.md b/admin/meetings/102322-decision.md index bc64f86..8b44465 100644 --- a/admin/meetings/102322-decision.md +++ b/admin/meetings/102322-decision.md @@ -1,40 +1,50 @@ -# Meeting Minutes (10/23/2022) -## Team 29: Hackers1995 -## Meeting Topic: Application Final Decision -This meeting is held to help the group decide on which kind of app to build. -## Attendance -1. George Dubinin -2. Henry Feng -3. Arthur Lu -4. Marc Reta -5. Kara Hoagland -6. Rhea Bhutada -7. Isaac Otero - -## Absentees -1. Sanjit Joseph -2. Gavyn Ezell -3. Daniel Hernandez - -## Meeting Details -- When: - - 10/23/2022 at 1:00PM -- Where: Zoom (Rhea's Meeting Room) - -## Agenda: -- ### Old/Unresolved Business - - N/A -- ### New Business - - Decide on a final app idea -- ### Next Meeting's Business - - Discuss design features for the chosen app - -## Decisions Made -- Maybe for the food reviewer app. Presenting possible writeup to Gagan -- Maybe for the resume builder. Presenting possible writeup to Gagan https://docs.google.com/document/d/1zdvVxd47Ivdz-D0rZGNJqc3D9GiQj0n_xMJKapOV39A/edit?usp=sharing -- Maybe for Social Media Local Archive. Presenting possible writeup to Gagan https://docs.google.com/document/d/1upNr6lneB2uzCoQ12_aa1CMg1W8p2NBFb6xmP7i4-z4/edit?usp=sharing -- No to the copy/paste app (not local first) - -## End Time -- When: - - 10/23/2022 at 2:00PM +# Meeting Minutes (10/23/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Application Final Decision + +This meeting is held to help the group decide on which kind of app to build. + +## Attendance + +1. George Dubinin +2. Henry Feng +3. Arthur Lu +4. Marc Reta +5. Kara Hoagland +6. Rhea Bhutada +7. Isaac Otero + +## Absentees + +1. Sanjit Joseph +2. Gavyn Ezell +3. Daniel Hernandez + +## Meeting Details + +- When: + - 10/23/2022 at 1:00PM +- Where: Zoom (Rhea's Meeting Room) + +## Agenda: + +- ### Old/Unresolved Business + - N/A +- ### New Business + - Decide on a final app idea +- ### Next Meeting's Business + - Discuss design features for the chosen app + +## Decisions Made + +- Maybe for the food reviewer app. Presenting possible writeup to Gagan +- Maybe for the resume builder. Presenting possible writeup to Gagan https://docs.google.com/document/d/1zdvVxd47Ivdz-D0rZGNJqc3D9GiQj0n_xMJKapOV39A/edit?usp=sharing +- Maybe for Social Media Local Archive. Presenting possible writeup to Gagan https://docs.google.com/document/d/1upNr6lneB2uzCoQ12_aa1CMg1W8p2NBFb6xmP7i4-z4/edit?usp=sharing +- No to the copy/paste app (not local first) + +## End Time + +- When: + - 10/23/2022 at 2:00PM diff --git a/admin/meetings/102622-checkin3.md b/admin/meetings/102622-checkin3.md index ae63c62..1f9e2c3 100644 --- a/admin/meetings/102622-checkin3.md +++ b/admin/meetings/102622-checkin3.md @@ -1,44 +1,54 @@ -# Meeting Minutes (10/26/2022) -## Team 29: Hackers1995 -## Meeting Topic: Weekly Check-In Meeting -This is our third weekly meeting with Gagan. - -## Attendance -TA. Gagan Gopalaiah -1. Rhea Bhutada -2. George Dubinin -3. Sanjit Joseph -4. Arthur Lu -5. Gavyn Ezell - -## Meeting Details -- When: 10/26/2022 at 3:00 PM -- Where: Zoom (Gagan's Zoom room: https://ucsd.zoom.us/j/5177090642) - -## Agenda: -- ### Present our ideas to Gagan - - All ideas seem to be doable - - Consider a few tweaks to "CRUDify" apps - - Gagan is partial to food review app idea, but any of them can work - - -- ### Tips for projects - - SOCIAL MEDIA ORGANIZER: avoid API integration if possible/only make it a small part, not a main feature - - RESUME BUILDER: try to "CRUDify" it more if we're going for this - -- ### Standups - - Once per 2 days, 3 in worst case - - Perhaps make a separate slack channel for these to avoid clutter - -## Moving forward: -- ### BY FRIDAY: - - Try and meet tomorrow (10/27) to make a final decision - - Let Gagan know what we've decided on - - Complete project pitch assignment - need to present to Gagan tomorrow 10/27, due on canvas 11/1 - -- ### OVER WEEKEND: - - (If possible) Start on CI/CD pipeline (basic js app/unit tests, use Github actions to set up) - - -## End Time -- 10/26/2022 at 4:00 PM +# Meeting Minutes (10/26/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Weekly Check-In Meeting + +This is our third weekly meeting with Gagan. + +## Attendance + +TA. Gagan Gopalaiah + +1. Rhea Bhutada +2. George Dubinin +3. Sanjit Joseph +4. Arthur Lu +5. Gavyn Ezell + +## Meeting Details + +- When: 10/26/2022 at 3:00 PM +- Where: Zoom (Gagan's Zoom room: https://ucsd.zoom.us/j/5177090642) + +## Agenda: + +- ### Present our ideas to Gagan + + - All ideas seem to be doable + - Consider a few tweaks to "CRUDify" apps + - Gagan is partial to food review app idea, but any of them can work + +- ### Tips for projects + + - SOCIAL MEDIA ORGANIZER: avoid API integration if possible/only make it a small part, not a main feature + - RESUME BUILDER: try to "CRUDify" it more if we're going for this + +- ### Standups + - Once per 2 days, 3 in worst case + - Perhaps make a separate slack channel for these to avoid clutter + +## Moving forward: + +- ### BY FRIDAY: + + - Try and meet tomorrow (10/27) to make a final decision + - Let Gagan know what we've decided on + - Complete project pitch assignment - need to present to Gagan tomorrow 10/27, due on canvas 11/1 + +- ### OVER WEEKEND: + - (If possible) Start on CI/CD pipeline (basic js app/unit tests, use Github actions to set up) + +## End Time + +- 10/26/2022 at 4:00 PM diff --git a/admin/meetings/102722-final_decision.md b/admin/meetings/102722-final_decision.md index cf9ec04..713c6d9 100644 --- a/admin/meetings/102722-final_decision.md +++ b/admin/meetings/102722-final_decision.md @@ -1,60 +1,69 @@ -# Meeting Minutes (10/27/2022) -## Team 29: Hackers1995 -## Meeting Topic: Final Project Decision -We're figuring out what project we're going to do, and figure out what we need for the starting pitch. - -## Attendance -1. Rhea Bhutada -2. Sanjit Joseph -3. Arthur Lu -4. Henry Feng -5. Marc Reta -6. Kara Hoagland -7. Daniel Hernandez -8. Gavyn Ezell -9. Isaac Otero - -## Meeting Details -- When: 10/27/2022 at 5:00 PM -- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) - -## Agenda: -- ### Decide which project we're doing - - Gagan seemed to like the food review app idea best in their current states - - We all seem to agree that the food review app is acceptable - - Made a couple clarifications, no major changes or objections to the app - -- ### Start project pitch - - Created google slides: **https://docs.google.com/presentation/d/1_XWihJGVChFtYS38RnYJtQUuFKsgvewOCOkdeMHFRg4/edit?usp=sharing** - - Prof recommends skimming the book: **https://basecamp.com/shapeup** (esp. ch.5 on risks and rabbit holes) - - Finishing Risks + Rabbit holes here in the meeting - - Kara posted a design prototype in Slack: https://cse110fall2022.slack.com/archives/C04598WA7P1/p1666918573779859 - -- ### App Description - - Renaming it to a "Food Diary" app, not limited to UCSD - - Allows users to store info about recent foods, restaurant name, location, price, your rating etc. - - Probably provides food suggestions based on where you've eaten (and liked) before - - We're not going to try anything with external data atm. - - -## Moving forward: -- ### BY TOMORROW: - - FINISH PITCH SLIDES - - MUST CHANGE DIAGRAM TO ALL RESTAURANTS (Isaac will change this) - - Daniel will update the pitch slides by adding images/graphics. - - Daniel + Sanjit are doing visual representation. - - Gayvn is doing potential competitors - - Henry, Sanjit, Kara are doing user personas - - Rhea is doing statement + purpose - - Arthur + Marc are doing "why it's a CRUD app" - - - See if we can have a short meeting tomorrow before meeting Gagan just to review our pitch. - - Put all components in specs folder before pitch - - Meet at 2:30? Meeting with Gagan is probably at 3:30 - -- ### LATER: - - Have some people split off and work on the basic UI design. Technically Sanjit had the 'art role' according to the TA but not sure what that entails. More ppl would def be helpful. TBD who else is helping - - -## End Time -- 10/27/2022 at 6:15 PM +# Meeting Minutes (10/27/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Final Project Decision + +We're figuring out what project we're going to do, and figure out what we need for the starting pitch. + +## Attendance + +1. Rhea Bhutada +2. Sanjit Joseph +3. Arthur Lu +4. Henry Feng +5. Marc Reta +6. Kara Hoagland +7. Daniel Hernandez +8. Gavyn Ezell +9. Isaac Otero + +## Meeting Details + +- When: 10/27/2022 at 5:00 PM +- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) + +## Agenda: + +- ### Decide which project we're doing + + - Gagan seemed to like the food review app idea best in their current states + - We all seem to agree that the food review app is acceptable + - Made a couple clarifications, no major changes or objections to the app + +- ### Start project pitch + + - Created google slides: **https://docs.google.com/presentation/d/1_XWihJGVChFtYS38RnYJtQUuFKsgvewOCOkdeMHFRg4/edit?usp=sharing** + - Prof recommends skimming the book: **https://basecamp.com/shapeup** (esp. ch.5 on risks and rabbit holes) + - Finishing Risks + Rabbit holes here in the meeting + - Kara posted a design prototype in Slack: https://cse110fall2022.slack.com/archives/C04598WA7P1/p1666918573779859 + +- ### App Description + - Renaming it to a "Food Diary" app, not limited to UCSD + - Allows users to store info about recent foods, restaurant name, location, price, your rating etc. + - Probably provides food suggestions based on where you've eaten (and liked) before + - We're not going to try anything with external data atm. + +## Moving forward: + +- ### BY TOMORROW: + + - FINISH PITCH SLIDES + - MUST CHANGE DIAGRAM TO ALL RESTAURANTS (Isaac will change this) + - Daniel will update the pitch slides by adding images/graphics. + - Daniel + Sanjit are doing visual representation. + - Gayvn is doing potential competitors + - Henry, Sanjit, Kara are doing user personas + - Rhea is doing statement + purpose + - Arthur + Marc are doing "why it's a CRUD app" + + - See if we can have a short meeting tomorrow before meeting Gagan just to review our pitch. + - Put all components in specs folder before pitch + - Meet at 2:30? Meeting with Gagan is probably at 3:30 + +- ### LATER: + - Have some people split off and work on the basic UI design. Technically Sanjit had the 'art role' according to the TA but not sure what that entails. More ppl would def be helpful. TBD who else is helping + +## End Time + +- 10/27/2022 at 6:15 PM diff --git a/admin/meetings/102822-project_pitch.md b/admin/meetings/102822-project_pitch.md index d67e1ae..4ad6511 100644 --- a/admin/meetings/102822-project_pitch.md +++ b/admin/meetings/102822-project_pitch.md @@ -1,24 +1,31 @@ -# Meeting Minutes (10/28/2022) -## Team 29: Hackers1995 -## Meeting Topic: Project Pitch -We finished up the project pitch docs and presenting them to Gagan. - -Google slides: **https://docs.google.com/presentation/d/1_XWihJGVChFtYS38RnYJtQUuFKsgvewOCOkdeMHFRg4/edit?usp=sharing** - -## Meeting Details -- When: 10/28/2022 at 2:30 PM -- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) - -## Agenda: -- ### Finish Project Pitch documents - - Finished user stories/diagrams and uploaded to github - - Went over presentation before showing TA - - Presented project to Gagan - - **Overall reaction - he liked our app! More feedback to come, but we can feel free to start some basic work.** - -## Moving forward: -- I think we need to upload our project pitch to canvas by 11/1 -- Start on the really basic stuff as discussed in lecture (hello world for CI/CD setup, etc) - -## End Time -- 10/28/2022 at 4:00 PM +# Meeting Minutes (10/28/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Project Pitch + +We finished up the project pitch docs and presenting them to Gagan. + +Google slides: **https://docs.google.com/presentation/d/1_XWihJGVChFtYS38RnYJtQUuFKsgvewOCOkdeMHFRg4/edit?usp=sharing** + +## Meeting Details + +- When: 10/28/2022 at 2:30 PM +- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) + +## Agenda: + +- ### Finish Project Pitch documents + - Finished user stories/diagrams and uploaded to github + - Went over presentation before showing TA + - Presented project to Gagan + - **Overall reaction - he liked our app! More feedback to come, but we can feel free to start some basic work.** + +## Moving forward: + +- I think we need to upload our project pitch to canvas by 11/1 +- Start on the really basic stuff as discussed in lecture (hello world for CI/CD setup, etc) + +## End Time + +- 10/28/2022 at 4:00 PM diff --git a/admin/meetings/110122-meeting.md b/admin/meetings/110122-meeting.md index 92e5186..6e2b19b 100644 --- a/admin/meetings/110122-meeting.md +++ b/admin/meetings/110122-meeting.md @@ -1,41 +1,50 @@ -# Meeting Minutes (11/01/2022) -## Team 29: Hackers1995 -## Meeting Topic: Work going forward -We're trying to figure out what our goals are for the project and how to get started. - -## Meeting Details -- When: 11/01/2022 at 7:00 PM -- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) - -## Attendance - 1. Rhea - 2. Gavyn - 3. Isaac - 4. Kara - 5. Marc - 6. Henry - 7. Daniel - 8. Sanjit - -## Notes: - - Gagan suggests we have a feature backlog and pull stuff from that - - Using Github Issues for our feature backlog - - - Perhaps integrate TTS from Lab5 into something (pick a random restaurant while driving, etc) - - - Created figma sketch for app design, uploaded to github and google slides - -## Moving forward: -- ### BY TONIGHT: - - We'll submit our pitch files -- ### LATER: - - Sanjit will upload a basic hello world program in order to test deployment/github actions - - Arthur will start figuring out how to configure github actions - -- ### PREFERENCES: - - BACKEND: Henry, Gavyn, Kara - - FRONTEND: Isaac - - NO PREFERENCE: Daniel, Marc, Rhea, Sanjit - -## End Time -- 11/01/2022 at 9:00 PM +# Meeting Minutes (11/01/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Work going forward + +We're trying to figure out what our goals are for the project and how to get started. + +## Meeting Details + +- When: 11/01/2022 at 7:00 PM +- Where: Zoom (Rhea's Zoom room: https://ucsd.zoom.us/j/8054288343) + +## Attendance + +1. Rhea +2. Gavyn +3. Isaac +4. Kara +5. Marc +6. Henry +7. Daniel +8. Sanjit + +## Notes: + +- Gagan suggests we have a feature backlog and pull stuff from that +- Using Github Issues for our feature backlog + +- Perhaps integrate TTS from Lab5 into something (pick a random restaurant while driving, etc) + +- Created figma sketch for app design, uploaded to github and google slides + +## Moving forward: + +- ### BY TONIGHT: + - We'll submit our pitch files +- ### LATER: + + - Sanjit will upload a basic hello world program in order to test deployment/github actions + - Arthur will start figuring out how to configure github actions + +- ### PREFERENCES: + - BACKEND: Henry, Gavyn, Kara + - FRONTEND: Isaac + - NO PREFERENCE: Daniel, Marc, Rhea, Sanjit + +## End Time + +- 11/01/2022 at 9:00 PM diff --git a/admin/meetings/110222-checkin4.md b/admin/meetings/110222-checkin4.md index ab7b1c0..e3cfdf4 100644 --- a/admin/meetings/110222-checkin4.md +++ b/admin/meetings/110222-checkin4.md @@ -1,34 +1,39 @@ -# Meeting Minutes (11/02/2022) -## Team 29: Hackers1995 -## Meeting Topic: Weekly TA Catchup with Gagan -We are meeting with Gagan to discuss early phase design concepts and decisions we need to think about as we start the early coding phase. - -## Attendance -1. Rhea Bhutada -2. George Dubinin -3. Gagan Gopalaiah - -## Meeting Details -- When: 11/02/2022 at 3:30PM -- Where: Zoom - -## Agenda: - -## Discussion Points by Gagan - - Now that we finished designs stage there are 2 approaches - - The first is to just start coding without thinking about design (cowboy coding). It works but can get bumpy down the road - - The second is to look at the project from a birds eye view and break it down into milestones and tasks. First break it down into weeks and then decide on what to do each day of the week. This will make it easier to keep things organized. - - Jira and GitHub issues will be super helpful. Jira is a more expensive option so instead prof recommends creating issues. - - Start thinking about storage options. Think local first and decide on options like: - - locally stored json files - - browser local storage - - "real" database like IndexDB - - Think about different models to keep track of changes and versions. Consider the branching model (one central repository and everyone has a branch or one breanch per feature) and the forking model (the central repository is copied and developers work in these copies and push changes to their own copies before syncing to the central repo). Useful info here: https://www.flagship.io/git-branching-strategies/ - - Think about how pull requests will be approved and create a system for PR review and suggests. - - Break down the project and decide on which tasks to be completed. Then decide on how long sprints will last and how tasks will be assigned. - - We need to create the ADR and place it in the brainstorming section of the repo. This will contain details about specific project decisions that we made like database decisions (for example). - -## End Time -- 11/02/2022 at 4:00PM - - +# Meeting Minutes (11/02/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Weekly TA Catchup with Gagan + +We are meeting with Gagan to discuss early phase design concepts and decisions we need to think about as we start the early coding phase. + +## Attendance + +1. Rhea Bhutada +2. George Dubinin +3. Gagan Gopalaiah + +## Meeting Details + +- When: 11/02/2022 at 3:30PM +- Where: Zoom + +## Agenda: + +## Discussion Points by Gagan + +- Now that we finished designs stage there are 2 approaches + - The first is to just start coding without thinking about design (cowboy coding). It works but can get bumpy down the road + - The second is to look at the project from a birds eye view and break it down into milestones and tasks. First break it down into weeks and then decide on what to do each day of the week. This will make it easier to keep things organized. +- Jira and GitHub issues will be super helpful. Jira is a more expensive option so instead prof recommends creating issues. +- Start thinking about storage options. Think local first and decide on options like: + - locally stored json files + - browser local storage + - "real" database like IndexDB +- Think about different models to keep track of changes and versions. Consider the branching model (one central repository and everyone has a branch or one breanch per feature) and the forking model (the central repository is copied and developers work in these copies and push changes to their own copies before syncing to the central repo). Useful info here: https://www.flagship.io/git-branching-strategies/ +- Think about how pull requests will be approved and create a system for PR review and suggests. +- Break down the project and decide on which tasks to be completed. Then decide on how long sprints will last and how tasks will be assigned. +- We need to create the ADR and place it in the brainstorming section of the repo. This will contain details about specific project decisions that we made like database decisions (for example). + +## End Time + +- 11/02/2022 at 4:00PM diff --git a/admin/meetings/110322-technology_discussion.md b/admin/meetings/110322-technology_discussion.md index 8b17a33..f3d29a6 100644 --- a/admin/meetings/110322-technology_discussion.md +++ b/admin/meetings/110322-technology_discussion.md @@ -1,44 +1,48 @@ -# Meeting Minutes (11/03/2022) -## Team 29: Hackers1995 -## Meeting Topic: Technologies Discussion -We're deciding on what web technologies we will incorporate into our food blog application. - -## Attendance -1. Rhea Bhutada -2. Sanjit Joseph -3. Arthur Lu -4. Henry Feng -5. Marc Reta -6. Kara Hoagland -7. Daniel Hernandez -8. Gavyn Ezell -9. Isaac Otero - -## Meeting Details -- When: 11/03/2022 at 3:00PM -- Where: In-person (CSE Basement B250) and George's Zoom room - -## Agenda: -- ### Answer the questions that Gagan's asked the team leads yesterday - - What high level approach will we have to coding? - - Slow approach with diagrams and short sprints of around 3 days. Biweekly meetings where we catch up with what happened end of each sprint. - - What issue tracker will we use? - - Use GitHub issues for tracking. Assign and breakdown tasks at the begining of each sprint. - - What database will we use? - - Rely on localStorage short-term and implement a non-relational database like MongoDB later. - - What branching/forking strategy will we use - - We will be creating branches for different features and be submitting PRs direclty to the master branch. Forks will only be created for large overhaul type changes - - How will PRs be approved - - The team will be split up into groups for different aspects of the app (front end, ui, database for example) and PRs will be reviewed and approved by 1 other member of the respective group - - Introduce the ADR and discuss how we will create it - - - - - -## Assignments: -- ### By X point in time: -- - - -## End Time -- 11/03/2022 at 4:00 PM \ No newline at end of file +# Meeting Minutes (11/03/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Technologies Discussion + +We're deciding on what web technologies we will incorporate into our food blog application. + +## Attendance + +1. Rhea Bhutada +2. Sanjit Joseph +3. Arthur Lu +4. Henry Feng +5. Marc Reta +6. Kara Hoagland +7. Daniel Hernandez +8. Gavyn Ezell +9. Isaac Otero + +## Meeting Details + +- When: 11/03/2022 at 3:00PM +- Where: In-person (CSE Basement B250) and George's Zoom room + +## Agenda: + +- ### Answer the questions that Gagan's asked the team leads yesterday + - What high level approach will we have to coding? + - Slow approach with diagrams and short sprints of around 3 days. Biweekly meetings where we catch up with what happened end of each sprint. + - What issue tracker will we use? + - Use GitHub issues for tracking. Assign and breakdown tasks at the begining of each sprint. + - What database will we use? + - Rely on localStorage short-term and implement a non-relational database like MongoDB later. + - What branching/forking strategy will we use + - We will be creating branches for different features and be submitting PRs direclty to the master branch. Forks will only be created for large overhaul type changes + - How will PRs be approved + - The team will be split up into groups for different aspects of the app (front end, ui, database for example) and PRs will be reviewed and approved by 1 other member of the respective group + - ## Introduce the ADR and discuss how we will create it + +## Assignments: + +- ### By X point in time: +- + +## End Time + +- 11/03/2022 at 4:00 PM diff --git a/admin/meetings/110422-project_breakdown.md b/admin/meetings/110422-project_breakdown.md index cdde94f..6faa0a4 100644 --- a/admin/meetings/110422-project_breakdown.md +++ b/admin/meetings/110422-project_breakdown.md @@ -1,32 +1,41 @@ -# Meeting Minutes (11/04/2022) -## Team 29: Hackers1995 -## Meeting Topic: Technologies Discussion -We're planning out our first sprint and breaking up the project into tasks. Tasks will be assigned to groups and GitHub issues will be created -for each task and assigned to a group. - -## Attendance -1. Rhea Bhutada -2. Sanjit Joseph -3. Arthur Lu -4. Marc Reta -6. Kara Hoagland -7. Daniel Hernandez -8. Gavyn Ezell -9. Isaac Otero -10. Henry Feng - -## Meeting Details -- When: 11/04/2022 at 10:00AM -- Where: George's Zoom room - -## Agenda: -## Sprint 1 Categories and Assignments -Frontend: Isaac, Sanjit, and Daniel -Backend: Rhea, George, Gavyn, Kara, -- Save to database -- Load from database -- Clear database -Unit Testing: Arthur, Marc - -## End Time -- 11/03/2022 at 10:30 AM \ No newline at end of file +# Meeting Minutes (11/04/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Technologies Discussion + +We're planning out our first sprint and breaking up the project into tasks. Tasks will be assigned to groups and GitHub issues will be created +for each task and assigned to a group. + +## Attendance + +1. Rhea Bhutada +2. Sanjit Joseph +3. Arthur Lu +4. Marc Reta +5. Kara Hoagland +6. Daniel Hernandez +7. Gavyn Ezell +8. Isaac Otero +9. Henry Feng + +## Meeting Details + +- When: 11/04/2022 at 10:00AM +- Where: George's Zoom room + +## Agenda: + +## Sprint 1 Categories and Assignments + +Frontend: Isaac, Sanjit, and Daniel +Backend: Rhea, George, Gavyn, Kara, + +- Save to database +- Load from database +- Clear database + Unit Testing: Arthur, Marc + +## End Time + +- 11/03/2022 at 10:30 AM diff --git a/admin/meetings/110822-sprint1day2.md b/admin/meetings/110822-sprint1day2.md index d620fb3..850bb10 100644 --- a/admin/meetings/110822-sprint1day2.md +++ b/admin/meetings/110822-sprint1day2.md @@ -1,9 +1,13 @@ # Meeting Minutes (11/08/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: In-Person First Sprint Day 2 + Meeting notes for the first sprint ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Gavyn Ezell @@ -12,28 +16,30 @@ Meeting notes for the first sprint 6. Daniel Hernandez ## Meeting Details -- When: 11/08/2022 at 2:00PM -- Where: Mike's Red Tacos + +- When: 11/08/2022 at 2:00PM +- Where: Mike's Red Tacos ## Agenda: -- ### Old/Unresolved Business - - N/A -- ### New Business - - Isaac now knows what Wolftown is - - Pair programming setup with VSCode -- ### Next Meeting's Business + +- ### Old/Unresolved Business + - N/A +- ### New Business + - Isaac now knows what Wolftown is + - Pair programming setup with VSCode +- ### Next Meeting's Business ## App Progress -- The landing page is closer -- Review card css file entered -- Review Card javascript logic implemented (thanks Gavin) -- + +- The landing page is closer +- Review card css file entered +- Review Card javascript logic implemented (thanks Gavin) +- ## Decisions Made -- Linting details decided (TABS NOT SPACES) + +- Linting details decided (TABS NOT SPACES) ## End Time -- 11/07/2022 at 8:00PM - - +- 11/07/2022 at 8:00PM diff --git a/admin/meetings/110922-checkin5.md b/admin/meetings/110922-checkin5.md index 764192c..a297f0e 100644 --- a/admin/meetings/110922-checkin5.md +++ b/admin/meetings/110922-checkin5.md @@ -1,36 +1,43 @@ -# Meeting Minutes (11/09/2022) -## Team 29: Hackers1995 -## Meeting Topic: Weekly TA Catchup with Gagan -We are meeting with Gagan to discuss progress made on Sprint 1 and testing strategies that we need to keep in mind as we continue developing. - -## Attendance -1. Rhea Bhutada -2. George Dubinin -3. Gagan Gopalaiah -4. Sanjit Joseph - -## Meeting Details -- When: 11/09/2022 at 3:30PM -- Where: Zoom - -## Agenda: - -## Discussion Points by Gagan -- Provided updates on first sprint -- Testing Tips - - functionality testing - - test one feature - - test individual functions - - static testing - - checking if its meeting the conventions and standards for specific programming language - - linting - - specific to programming language - - overall - - if tested properly, we reduce problems end-to-end testing -- Documentation - - What the code does? - - What the file is for? - - JS Docs - -## End Time -- 11/09/2022 at 4:00PM +# Meeting Minutes (11/09/2022) + +## Team 29: Hackers1995 + +## Meeting Topic: Weekly TA Catchup with Gagan + +We are meeting with Gagan to discuss progress made on Sprint 1 and testing strategies that we need to keep in mind as we continue developing. + +## Attendance + +1. Rhea Bhutada +2. George Dubinin +3. Gagan Gopalaiah +4. Sanjit Joseph + +## Meeting Details + +- When: 11/09/2022 at 3:30PM +- Where: Zoom + +## Agenda: + +## Discussion Points by Gagan + +- Provided updates on first sprint +- Testing Tips + - functionality testing + - test one feature + - test individual functions + - static testing + - checking if its meeting the conventions and standards for specific programming language + - linting + - specific to programming language + - overall + - if tested properly, we reduce problems end-to-end testing +- Documentation + - What the code does? + - What the file is for? + - JS Docs + +## End Time + +- 11/09/2022 at 4:00PM diff --git a/admin/meetings/111322-retrospective.md b/admin/meetings/111322-retrospective.md index 977ed74..b32426d 100644 --- a/admin/meetings/111322-retrospective.md +++ b/admin/meetings/111322-retrospective.md @@ -1,8 +1,11 @@ # Sprint 1 Retrospective (11/14/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Sprint 1 Retrospective ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Sanjit Joseph @@ -15,54 +18,64 @@ 10. Isaac Otero ## Meeting Details -- When: 11/14/2022 at 4:30PM -- Where: On Campus + +- When: 11/14/2022 at 4:30PM +- Where: On Campus ## Agenda: + Discuss the review, share more detailed thoughts on sprint 1, and create some resolutions for sprint 2 ## Sprint 1 Review Below (for convenience) ## Sprint 1 REVIEW + In collecting feedback during our final sprint the leads decided to ask members individually about their experience during sprint 1 to then summarize these responses. Each member was asked 4 questions with their summarized responses below: ### What do you think worked well in the first sprint? + We resolved to hold each of our sprint 1 meetings in person with a remote option available to members that couldn't attend. We really liked hanging out at the restaurants before working on the sprint and these experiences encouraged psychological safety in the group. We made some noticeable progress which was very encouraging for the group. Specifically, we figured out quite a bit of the CI/CD pipeline details which will help us going forward and we got a solid grasp of what the visual aspects and feel of the website will be. ### What can we improve on for the next sprint? + We ran into trouble early on due to some lack of planning for specific tasks. The members agreed that we should have spent more time defining tasks for specific members and defining goals for our different teams (frontend, backend, and unit testing). There was some concern over members not being able to attend all meetings and we think this could have been fixed with regularly scheduled meetings. Some technical concerns were the Javascript unit testing pipeline development lagging behind code development and pipeline requirements being unclear. Perhaps we should write out a style document to guide the automated linting process. ### What was your contribution to the sprint? -* Rhea Bhutada: Worked on the backend features including how to get create new review card page to open in a new window -* Gavyn Etzel: Helped with javascript side of things for website -* Henry Feng: Local image store and meeting support -* Sanjit: Default photo design and frontend star rating css -* Daniel: Helped modify html, added upload file feature -* Arthur Lu: Added JS Linting, Unit testing pipeline actions and rote a few simple unit tests; added deployment pipeline action -* Marc Rheta: Added HTML Linting and CSS Linting -* Isaac Otero: Low and mid fidelity wireframes of how our page will look like, Started working on homepage.html -* George Dubinin: Meeting notes, Repo organization, cookies -* Kara Hoagland: CRUD backend functionality + +- Rhea Bhutada: Worked on the backend features including how to get create new review card page to open in a new window +- Gavyn Etzel: Helped with javascript side of things for website +- Henry Feng: Local image store and meeting support +- Sanjit: Default photo design and frontend star rating css +- Daniel: Helped modify html, added upload file feature +- Arthur Lu: Added JS Linting, Unit testing pipeline actions and rote a few simple unit tests; added deployment pipeline action +- Marc Rheta: Added HTML Linting and CSS Linting +- Isaac Otero: Low and mid fidelity wireframes of how our page will look like, Started working on homepage.html +- George Dubinin: Meeting notes, Repo organization, cookies +- Kara Hoagland: CRUD backend functionality ### Was there anything blocking your progress in the sprint? -Communication was challenging especially for members that would attend over Zoom and it was a challenge keeping track of each member's progress. We ran into some issues with the branching strategy with branches rapidly multiplying at points and the GitHub tags not working. The biggest technical issue we experienced involved Node and ES6 compatibility issues. + +Communication was challenging especially for members that would attend over Zoom and it was a challenge keeping track of each member's progress. We ran into some issues with the branching strategy with branches rapidly multiplying at points and the GitHub tags not working. The biggest technical issue we experienced involved Node and ES6 compatibility issues. Overall we feel that sprint 1 was a success with many lessons learned. Our enthusiasm for the project is only building and we are excited to get back into it with sprint 2 after a much needed short break. ## Resolutions -* Divide up tasks and assign tasks to members -* Define objectives for team groups (frontend, backend, and unit testing) -* Scheduled meetings with more notice and keep meetings at a more central location so that more members can attend -* Get the unit testing modules up to date -* To-do: create a style guide -* Heed the styles and documentation (to avoid linter issues) + +- Divide up tasks and assign tasks to members +- Define objectives for team groups (frontend, backend, and unit testing) +- Scheduled meetings with more notice and keep meetings at a more central location so that more members can attend +- Get the unit testing modules up to date +- To-do: create a style guide +- Heed the styles and documentation (to avoid linter issues) ## Early Issues -* restructure local storage to store individual (key, review) pairs rather than storing data under one key (current schema) -* implement a file upload system (think canvas file upload) -* add a cuisine attribute for tagging and filtering -* Create UI buttons and low fidelity css -* Unit test all the above + +- restructure local storage to store individual (key, review) pairs rather than storing data under one key (current schema) +- implement a file upload system (think canvas file upload) +- add a cuisine attribute for tagging and filtering +- Create UI buttons and low fidelity css +- Unit test all the above ## End Time -- 11/14/2022 at 5:00PM \ No newline at end of file + +- 11/14/2022 at 5:00PM diff --git a/admin/meetings/111322-sprint-1-review.md b/admin/meetings/111322-sprint-1-review.md index b1823b6..f706e50 100644 --- a/admin/meetings/111322-sprint-1-review.md +++ b/admin/meetings/111322-sprint-1-review.md @@ -1,9 +1,13 @@ # Sprint 1 Review Meeting Minutes (11/13/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Sprint 1 Review + We are meeting with Gagan to discuss progress made on Sprint 1 and testing strategies that we need to keep in mind as we continue developing. ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Sanjit Joseph @@ -16,37 +20,45 @@ We are meeting with Gagan to discuss progress made on Sprint 1 and testing strat 10. Isaac Otero ## Meeting Details -- When: 11/13/2022 at 1:00PM -- Where: Capital One Cafe and Zoom + +- When: 11/13/2022 at 1:00PM +- Where: Capital One Cafe and Zoom ## Agenda: + Review the week 7 sprint and get the writeup for the Agile review assignemnt ## Sprint 1 REVIEW + In collecting feedback during our final sprint the leads decided to ask members individually about their experience during sprint 1 to then summarize these responses. Each member was asked 4 questions with their summarized responses below: ### What do you think worked well in the first sprint? + We resolved to hold each of our sprint 1 meetings in person with a remote option available to members that couldn't attend. We really liked hanging out at the restaurants before working on the sprint and these experiences encouraged psychological safety in the group. We made some noticeable progress which was very encouraging for the group. Specifically, we figured out quite a bit of the CI/CD pipeline details which will help us going forward and we got a solid grasp of what the visual aspects and feel of the website will be. ### What can we improve on for the next sprint? + We ran into trouble early on due to some lack of planning for specific tasks. The members agreed that we should have spent more time defining tasks for specific members and defining goals for our different teams (frontend, backend, and unit testing). There was some concern over members not being able to attend all meetings and we think this could have been fixed with regularly scheduled meetings. Some technical concerns were the Javascript unit testing pipeline development lagging behind code development and pipeline requirements being unclear. Perhaps we should write out a style document to guide the automated linting process. ### What was your contribution to the sprint? -* Rhea Bhutada: Worked on the backend features including how to get create new review card page to open in a new window -* Gavyn Etzel: Helped with javascript side of things for website -* Henry Feng: Local image store and meeting support -* Sanjit: Default photo design and frontend star rating css -* Daniel: Helped modify html, added upload file feature -* Arthur Lu: Added JS Linting, Unit testing pipeline actions and rote a few simple unit tests; added deployment pipeline action -* Marc Rheta: Added HTML Linting and CSS Linting -* Isaac Otero: Low and mid fidelity wireframes of how our page will look like, Started working on homepage.html -* George Dubinin: Meeting notes, Repo organization, cookies -* Kara Hoagland: CRUD backend functionality + +- Rhea Bhutada: Worked on the backend features including how to get create new review card page to open in a new window +- Gavyn Etzel: Helped with javascript side of things for website +- Henry Feng: Local image store and meeting support +- Sanjit: Default photo design and frontend star rating css +- Daniel: Helped modify html, added upload file feature +- Arthur Lu: Added JS Linting, Unit testing pipeline actions and rote a few simple unit tests; added deployment pipeline action +- Marc Rheta: Added HTML Linting and CSS Linting +- Isaac Otero: Low and mid fidelity wireframes of how our page will look like, Started working on homepage.html +- George Dubinin: Meeting notes, Repo organization, cookies +- Kara Hoagland: CRUD backend functionality ### Was there anything blocking your progress in the sprint? -Communication was challenging especially for members that would attend over Zoom and it was a challenge keeping track of each member's progress. We ran into some issues with the branching strategy with branches rapidly multiplying at points and the GitHub tags not working. The biggest technical issue we experienced involved Node and ES6 compatibility issues. + +Communication was challenging especially for members that would attend over Zoom and it was a challenge keeping track of each member's progress. We ran into some issues with the branching strategy with branches rapidly multiplying at points and the GitHub tags not working. The biggest technical issue we experienced involved Node and ES6 compatibility issues. Overall we feel that sprint 1 was a success with many lessons learned. Our enthusiasm for the project is only building and we are excited to get back into it with sprint 2 after a much needed short break. ## End Time -- 11/13/2022 at 3:00PM \ No newline at end of file + +- 11/13/2022 at 3:00PM diff --git a/admin/meetings/111622-checkin6.md b/admin/meetings/111622-checkin6.md index bc62529..7e02fd6 100644 --- a/admin/meetings/111622-checkin6.md +++ b/admin/meetings/111622-checkin6.md @@ -1,33 +1,40 @@ # Meeting Minutes (11/16/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Weekly TA Catchup with Gagan + We are meeting with Gagan to discuss Checkpoint 1 and Sprint 2 resolutions. ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Gagan Gopalaiah 4. Kara Hoagland ## Meeting Details -- When: 11/16/2022 at 3:30PM -- Where: Zoom + +- When: 11/16/2022 at 3:30PM +- Where: Zoom ## Agenda: ## Discussion Points by Gagan -- Updated Gagan on Sprint 1 - - looked at Girhub actions - - looked at the published page so far - - discussed retrospective -- Upcoming Assignments - - we have to come up with a video on the status of our app - - ramp up the styling part, so u can brag about the design of the app - - this video is supposed to encourage healthy competition -- Other Concerns - - JSDocs - not primary concern right now - - GitHub Pages vs. Netlify - - Gagan sees Netlify as more professional and not to difficult to implement + +- Updated Gagan on Sprint 1 + - looked at Girhub actions + - looked at the published page so far + - discussed retrospective +- Upcoming Assignments + - we have to come up with a video on the status of our app + - ramp up the styling part, so u can brag about the design of the app + - this video is supposed to encourage healthy competition +- Other Concerns + - JSDocs - not primary concern right now + - GitHub Pages vs. Netlify + - Gagan sees Netlify as more professional and not to difficult to implement ## End Time -- 11/16/2022 at 3:45PM + +- 11/16/2022 at 3:45PM diff --git a/admin/meetings/111722-sprint2meeting1.md b/admin/meetings/111722-sprint2meeting1.md index 01b31d9..b46fee6 100644 --- a/admin/meetings/111722-sprint2meeting1.md +++ b/admin/meetings/111722-sprint2meeting1.md @@ -1,9 +1,13 @@ # Meeting Minutes (11/07/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: First Sprint + Meeting notes for the first sprint ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Gavyn Ezell @@ -16,32 +20,40 @@ Meeting notes for the first sprint 10. Isaac Otero ## Meeting Details -- When: 11/17/2022 at 11:30PM -- Where: Design & Innovation Building + +- When: 11/17/2022 at 11:30PM +- Where: Design & Innovation Building ## Agenda: -- ### Old/Unresolved Business - - N/A -- ### New Business - - Second sprint commences! - - Focus on design progress for the project showoff - - Cuisine vs Tag identifiers for reviews (both?) - - localStorage will hold: - - list of active IDs which is updated for very create operation. An ID uniquely identifies a review - - value, "nextId" denoting the index of the next available slot for an Id - - entries for every single review (javascript object) - - a list for every tag that denotes which Ids belong to reviews containing this tag - End2end tests will rely on specific html element names which include the following: - - "create-btn" (located on homepage and used to create a new review) - - "submit-btn" (located on form and used to post review) - - "update-btn" (located on a specific review page) - - "delete-btn" (located on a specific review page) - - "tag-add-btn" (located on the review create form) -- ### Next Meeting's Business +- ### Old/Unresolved Business + - N/A +- ### New Business + + - Second sprint commences! + - Focus on design progress for the project showoff + - Cuisine vs Tag identifiers for reviews (both?) + + - localStorage will hold: + - list of active IDs which is updated for very create operation. An ID uniquely identifies a review + - value, "nextId" denoting the index of the next available slot for an Id + - entries for every single review (javascript object) + - a list for every tag that denotes which Ids belong to reviews containing this tag + + End2end tests will rely on specific html element names which include the following: + + - "create-btn" (located on homepage and used to create a new review) + - "submit-btn" (located on form and used to post review) + - "update-btn" (located on a specific review page) + - "delete-btn" (located on a specific review page) + - "tag-add-btn" (located on the review create form) + +- ### Next Meeting's Business ## Decisions Made -- + +- ## End Time -- 11/17/2022 at 1:00PM \ No newline at end of file + +- 11/17/2022 at 1:00PM diff --git a/admin/meetings/112022-sprint2meeting3.md b/admin/meetings/112022-sprint2meeting3.md index 4995cd3..3ff781f 100644 --- a/admin/meetings/112022-sprint2meeting3.md +++ b/admin/meetings/112022-sprint2meeting3.md @@ -1,8 +1,11 @@ # Meeting Minutes (11/20/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Second Sprint Meeting 3 ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Gavyn Ezell @@ -15,25 +18,31 @@ 10. Isaac Otero ## Meeting Details -- When: 11/20/2022 at 1:00PM -- Where: CSE Building Second Floor + +- When: 11/20/2022 at 1:00PM +- Where: CSE Building Second Floor ## Agenda: -- ### Old/Unresolved Business - - N/A -- ### New Business - - Planning for the Agile Steam Status Video - - *Present the status of your software* - - Show off the preliminary design of index.html - - Walk through the process of creating a journal entry - - *Description of current challenges to development* - - *Preview of the next sprint and what to look forward to* - - Front end redo for home page including semantic restructuring and enhanced CSS - - Documentation session for JS, CSS, and HTML files - - Pipeline details have largely been ironed out -- ### Next Meeting's Business - - Creation of team status video +- ### Old/Unresolved Business + - N/A +- ### New Business + + - Planning for the Agile Steam Status Video + + - _Present the status of your software_ + - Show off the preliminary design of index.html + - Walk through the process of creating a journal entry + - _Description of current challenges to development_ + - _Preview of the next sprint and what to look forward to_ + + - Front end redo for home page including semantic restructuring and enhanced CSS + - Documentation session for JS, CSS, and HTML files + - Pipeline details have largely been ironed out + +- ### Next Meeting's Business + - Creation of team status video ## End Time -- 11/20/2022 at 3:00PM \ No newline at end of file + +- 11/20/2022 at 3:00PM diff --git a/admin/meetings/112322-checkin7.md b/admin/meetings/112322-checkin7.md index 8688282..72dfb87 100644 --- a/admin/meetings/112322-checkin7.md +++ b/admin/meetings/112322-checkin7.md @@ -1,33 +1,40 @@ # Meeting Minutes (11/23/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Weekly TA Catchup with Gagan + We are meeting with Gagan to discuss status video and general updates on project. ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Gagan Gopalaiah ## Meeting Details -- When: 11/23/2022 at 3:30PM -- Where: Zoom + +- When: 11/23/2022 at 3:30PM +- Where: Zoom ## Discussion Points by Gagan -- progress looks good!! -- deadline for project - - december 3rd/4th code freeze - - no new features - - only debugging - - after december 3rd/4th we need to focus on making a good final video -- final video - - played on finals day, voted on in class - - need to spend a good amount of time on it - - essential to make this good -- last week there are going to be one-to-one sessions held - - Gagan will be asking questions to the team - - everyone needs to be aware of all aspects of the project -- start end-to-end testing on project -- quickly discussed team roles + +- progress looks good!! +- deadline for project + - december 3rd/4th code freeze + - no new features + - only debugging + - after december 3rd/4th we need to focus on making a good final video +- final video + - played on finals day, voted on in class + - need to spend a good amount of time on it + - essential to make this good +- last week there are going to be one-to-one sessions held + - Gagan will be asking questions to the team + - everyone needs to be aware of all aspects of the project +- start end-to-end testing on project +- quickly discussed team roles ## End Time -- 11/23/2022 at 3:52PM + +- 11/23/2022 at 3:52PM diff --git a/admin/meetings/112722-sprint-2-review.md b/admin/meetings/112722-sprint-2-review.md index ff68262..c5728dd 100644 --- a/admin/meetings/112722-sprint-2-review.md +++ b/admin/meetings/112722-sprint-2-review.md @@ -1,9 +1,13 @@ # Sprint 2 Review Meeting Minutes (11/27/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Sprint 2 Review -We are reviewing the second sprint 2 progress made and highlights + +We are reviewing the second sprint 2 progress made and highlights ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Sanjit Joseph @@ -16,48 +20,58 @@ We are reviewing the second sprint 2 progress made and highlights 10. Isaac Otero ## Meeting Details -- When: 11/27/2022 at 4:30PM -- Where: Zoom + +- When: 11/27/2022 at 4:30PM +- Where: Zoom ## Agenda: + Review the second sprint and discuss assiget the writeup for the Agile review assignemnt ## Sprint 2 REVIEW + In collecting feedback for the sprint the leads decided to ask members individually about their experience during sprint 2 to then summarize these responses. Each member was asked 4 questions with their summarized responses below: ### ➼ What do you think worked well in the first sprint? -Communication within the group was improved and our joint study sessions where more productive. The design team got the support they needed to accomplish the majority of their work on the project. The push to emphasize the sub-teams responsible for different tasks turned out to be a great idea and everyone put in a good effort. + +Communication within the group was improved and our joint study sessions where more productive. The design team got the support they needed to accomplish the majority of their work on the project. The push to emphasize the sub-teams responsible for different tasks turned out to be a great idea and everyone put in a good effort. ### ➼ What can we improve on for the next sprint? + With the vast majority of feature implementation underway the rapid progress created a lot of bugs which otherwise could have been avoid with more careful planning. Some members felt that even though they made a great effort they weren't able to contribute as much as they wanted to. Some of the code documentation fell behind and some design discussions were circumvented because some members where busy. One consequence was that relatively few ADRs were created even though we made many important design decisions during sprint 2. ### ➼ What was your contribution to the sprint? -* Rhea Bhutada: I mainly helped implement the backend for the CRUD features of the app and documentation related to this. This mainly entailed changing the way that we were storing user data in local storage. Additionally, I helped design the form and homepage. -* Gavyn Etzel: Helped with JavaScript functionality (CRUD Features), and also did a lot of the documentation for the script files -Helped work through the storage revamp for our review cards -Also helped integrate our first design/style setup with functionality -* Henry Feng: Worked on implementing local image uploading and storing features for updating and creating profiles. -* Sanjit: I reimplemented the star ratings since they had some issues and weren’t merged with sprint 1. I fixed a bunch of linting issues that popped up from that as well. I did a fair bit of color palette brainstorming with the team. I also went over our app design for the sprint video and edited that together. Most importantly I put a chef hat on the raccoon -* Daniel: Helped in initial CreatePage and HomePage design which improved through feedback from the rest of the group. -Helped in styling suggestions. -* Arthur Lu: Worked on fixing some CI/CD pipeline issues -Implemented e2e testing for basic update and delete functionality -Helped with fixing the homepage and review page layout -Helped with fixing the article tag overflow issue -* Marc Rheta: Implemented the e2e testing for reading and create -Allowed tabs for CSS/HTML linters -* Isaac Otero: I was able to help out with the sprint video for the last sprint and thought of how our page will look like, Started working on homepage.html -* George Dubinin: Meeting notes, Repo organization, Front-end (a little), Project Status Review video. -* Kara Hoagland: I helped set up the new local storage design, reimplemented the CRUD features using the new local storage design, contributed to the styling, added a default img, backend on the details page + +- Rhea Bhutada: I mainly helped implement the backend for the CRUD features of the app and documentation related to this. This mainly entailed changing the way that we were storing user data in local storage. Additionally, I helped design the form and homepage. +- Gavyn Etzel: Helped with JavaScript functionality (CRUD Features), and also did a lot of the documentation for the script files + Helped work through the storage revamp for our review cards + Also helped integrate our first design/style setup with functionality +- Henry Feng: Worked on implementing local image uploading and storing features for updating and creating profiles. +- Sanjit: I reimplemented the star ratings since they had some issues and weren’t merged with sprint 1. I fixed a bunch of linting issues that popped up from that as well. I did a fair bit of color palette brainstorming with the team. I also went over our app design for the sprint video and edited that together. Most importantly I put a chef hat on the raccoon +- Daniel: Helped in initial CreatePage and HomePage design which improved through feedback from the rest of the group. + Helped in styling suggestions. +- Arthur Lu: Worked on fixing some CI/CD pipeline issues + Implemented e2e testing for basic update and delete functionality + Helped with fixing the homepage and review page layout + Helped with fixing the article tag overflow issue +- Marc Rheta: Implemented the e2e testing for reading and create + Allowed tabs for CSS/HTML linters +- Isaac Otero: I was able to help out with the sprint video for the last sprint and thought of how our page will look like, Started working on homepage.html +- George Dubinin: Meeting notes, Repo organization, Front-end (a little), Project Status Review video. +- Kara Hoagland: I helped set up the new local storage design, reimplemented the CRUD features using the new local storage design, contributed to the styling, added a default img, backend on the details page ### ➼ Was there anything blocking your progress in the sprint? + A few members got sick over the break and with midterms picking up for other classes some members had trouble dedicting time for the project but everyone still put in a great effort overall. ## Next Sprint Goals + - Resolve the 4 issues open on GitHub right now - - Make the project "local first" by creating a cache + - Make the project "local first" by creating a cache - Bug fixes and final product adjustments possibly pushed to sprint 4 - We aim to keep sprint 3 short (a few days max) - JS docs (we can potentially leave this out with an explanation of where our documentation is) + ## End Time -- 11/27/2022 at 5:00PM \ No newline at end of file + +- 11/27/2022 at 5:00PM diff --git a/admin/meetings/112822-retrospective.md b/admin/meetings/112822-retrospective.md index ec04e19..de50e0c 100644 --- a/admin/meetings/112822-retrospective.md +++ b/admin/meetings/112822-retrospective.md @@ -1,8 +1,11 @@ # Sprint 1 Retrospective (11/28/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Sprint 1 Retrospective ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Sanjit Joseph @@ -15,57 +18,67 @@ 10. Isaac Otero ## Meeting Details -- When: 11/28/2022 at 4:00PM -- Where: Zoom + +- When: 11/28/2022 at 4:00PM +- Where: Zoom ## Agenda: + Discuss the review, share more detailed thoughts on sprint 2, and create some resolutions for sprint 3 ## Sprint 3 Review Below (for convenience) + In collecting feedback for the sprint the leads decided to ask members individually about their experience during sprint 2 to then summarize these responses. Each member was asked 4 questions with their summarized responses below: ### ➼ What do you think worked well in the first sprint? -Communication within the group was improved and our joint study sessions where more productive. The design team got the support they needed to accomplish the majority of their work on the project. The push to emphasize the sub-teams responsible for different tasks turned out to be a great idea and everyone put in a good effort. + +Communication within the group was improved and our joint study sessions where more productive. The design team got the support they needed to accomplish the majority of their work on the project. The push to emphasize the sub-teams responsible for different tasks turned out to be a great idea and everyone put in a good effort. ### ➼ What can we improve on for the next sprint? + With the vast majority of feature implementation underway the rapid progress created a lot of bugs which otherwise could have been avoid with more careful planning. Some members felt that even though they made a great effort they weren't able to contribute as much as they wanted to. Some of the code documentation fell behind and some design discussions were circumvented because some members where busy. One consequence was that relatively few ADRs were created even though we made many important design decisions during sprint 2. ### ➼ What was your contribution to the sprint? -* Rhea Bhutada: I mainly helped implement the backend for the CRUD features of the app and documentation related to this. This mainly entailed changing the way that we were storing user data in local storage. Additionally, I helped design the form and homepage. -* Gavyn Etzel: Helped with JavaScript functionality (CRUD Features), and also did a lot of the documentation for the script files -Helped work through the storage revamp for our review cards -Also helped integrate our first design/style setup with functionality -* Henry Feng: Worked on implementing local image uploading and storing features for updating and creating profiles. -* Sanjit: I reimplemented the star ratings since they had some issues and weren’t merged with sprint 1. I fixed a bunch of linting issues that popped up from that as well. I did a fair bit of color palette brainstorming with the team. I also went over our app design for the sprint video and edited that together. Most importantly I put a chef hat on the raccoon -* Daniel: Helped in initial CreatePage and HomePage design which improved through feedback from the rest of the group. -Helped in styling suggestions. -* Arthur Lu: Worked on fixing some CI/CD pipeline issues -Implemented e2e testing for basic update and delete functionality -Helped with fixing the homepage and review page layout -Helped with fixing the article tag overflow issue -* Marc Rheta: Implemented the e2e testing for reading and create -Allowed tabs for CSS/HTML linters -* Isaac Otero: I was able to help out with the sprint video for the last sprint and thought of how our page will look like, Started working on homepage.html -* George Dubinin: Meeting notes, Repo organization, Front-end (a little), Project Status Review video. -* Kara Hoagland: I helped set up the new local storage design, reimplemented the CRUD features using the new local storage design, contributed to the styling, added a default img, backend on the details page + +- Rhea Bhutada: I mainly helped implement the backend for the CRUD features of the app and documentation related to this. This mainly entailed changing the way that we were storing user data in local storage. Additionally, I helped design the form and homepage. +- Gavyn Etzel: Helped with JavaScript functionality (CRUD Features), and also did a lot of the documentation for the script files + Helped work through the storage revamp for our review cards + Also helped integrate our first design/style setup with functionality +- Henry Feng: Worked on implementing local image uploading and storing features for updating and creating profiles. +- Sanjit: I reimplemented the star ratings since they had some issues and weren’t merged with sprint 1. I fixed a bunch of linting issues that popped up from that as well. I did a fair bit of color palette brainstorming with the team. I also went over our app design for the sprint video and edited that together. Most importantly I put a chef hat on the raccoon +- Daniel: Helped in initial CreatePage and HomePage design which improved through feedback from the rest of the group. + Helped in styling suggestions. +- Arthur Lu: Worked on fixing some CI/CD pipeline issues + Implemented e2e testing for basic update and delete functionality + Helped with fixing the homepage and review page layout + Helped with fixing the article tag overflow issue +- Marc Rheta: Implemented the e2e testing for reading and create + Allowed tabs for CSS/HTML linters +- Isaac Otero: I was able to help out with the sprint video for the last sprint and thought of how our page will look like, Started working on homepage.html +- George Dubinin: Meeting notes, Repo organization, Front-end (a little), Project Status Review video. +- Kara Hoagland: I helped set up the new local storage design, reimplemented the CRUD features using the new local storage design, contributed to the styling, added a default img, backend on the details page ### ➼ Was there anything blocking your progress in the sprint? + A few members got sick over the break and with midterms picking up for other classes some members had trouble dedicting time for the project but everyone still put in a great effort overall. ## Next Sprint Goals + - Resolve the 4 issues open on GitHub right now - - Make the project "local first" by creating a cache + - Make the project "local first" by creating a cache - Bug fixes and final product adjustments possibly pushed to sprint 4 - We aim to keep sprint 3 short (a few days max) - JS docs (we can potentially leave this out with an explanation of where our documentation is) ## Resolutions -* Sprint 3 first meeting happening 11-29 at 5:00PM -* Make sure that there's enough communication between front-end and back-end -* Focus on meeting with your subgroup and then touch base with the main group -* Keep documentation up to date with the rest of the project -* We need to finalize the home page design (this has been open for a while). -* Fix image sizing issues by focusing on supporting 300x300 pixel images with sizes of around 2-5 megabytes + +- Sprint 3 first meeting happening 11-29 at 5:00PM +- Make sure that there's enough communication between front-end and back-end +- Focus on meeting with your subgroup and then touch base with the main group +- Keep documentation up to date with the rest of the project +- We need to finalize the home page design (this has been open for a while). +- Fix image sizing issues by focusing on supporting 300x300 pixel images with sizes of around 2-5 megabytes ## End Time -- 11/14/2022 at 5:00PM + +- 11/14/2022 at 5:00PM diff --git a/admin/meetings/112922-Sprint3Opener.md b/admin/meetings/112922-Sprint3Opener.md index dde1ac3..e91d178 100644 --- a/admin/meetings/112922-Sprint3Opener.md +++ b/admin/meetings/112922-Sprint3Opener.md @@ -1,8 +1,11 @@ # Meeting Minutes (11/29/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Sprint 3 Debut Meeting ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Gavyn Ezell @@ -14,22 +17,25 @@ 9. Arthur Lu (remote) ## Meeting Details -- When: 11/29/2022 at 5:00PM -- Where: Design and Innovation Building + +- When: 11/29/2022 at 5:00PM +- Where: Design and Innovation Building ## Agenda: -- ### Old/Unresolved Business - - Resolve pretty print linting PR - - Resolve documentation not being merged to main PR -- ### New Business - - Create ADR for image storage - - Review sorting defaults (recent or top rated) - - Adding lists of reviewIDs corresponding to reviews which share specific star ratings - - Create function for retrieving top 20 reviews organized by decreasing star ratings - - Implement search for for flitering tags - - Frontend checked out new branch for alternate home page designs -- ### Next Meeting's Business - - Creation of team status video + +- ### Old/Unresolved Business + - Resolve pretty print linting PR + - Resolve documentation not being merged to main PR +- ### New Business + - Create ADR for image storage + - Review sorting defaults (recent or top rated) + - Adding lists of reviewIDs corresponding to reviews which share specific star ratings + - Create function for retrieving top 20 reviews organized by decreasing star ratings + - Implement search for for flitering tags + - Frontend checked out new branch for alternate home page designs +- ### Next Meeting's Business + - Creation of team status video ## End Time -- 11/20/2022 at 3:00PM \ No newline at end of file + +- 11/20/2022 at 3:00PM diff --git a/admin/meetings/113022-Sprint3Cont.md b/admin/meetings/113022-Sprint3Cont.md index 5689e85..b69572c 100644 --- a/admin/meetings/113022-Sprint3Cont.md +++ b/admin/meetings/113022-Sprint3Cont.md @@ -1,30 +1,36 @@ # Meeting Minutes (11/30/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Sprint 3 Continued ## Attendance + 1. Rhea Bhutada 2. George Dubinin -4. Henry Feng -5. Kara Hoagland -7. Sanjit Joseph -9. Arthur Lu +3. Henry Feng +4. Kara Hoagland +5. Sanjit Joseph +6. Arthur Lu ## Meeting Details -- When: 11/30/2022 at 2:00PM -- Where: Design and Innovation Building + +- When: 11/30/2022 at 2:00PM +- Where: Design and Innovation Building ## Agenda: -- ### Old/Unresolved Business - - Fix empty page for no-tag search - - Catch testing up with what we implemented yesterday -- ### New Business - - Cache the site for local first (high priority) - - Implement editing form "in place" (optional for this sprint) - - Change icon for "add review" entry - - Overcoming UI test challenges -- ### Next Meeting's Business - - Creation of team status video + +- ### Old/Unresolved Business + - Fix empty page for no-tag search + - Catch testing up with what we implemented yesterday +- ### New Business + - Cache the site for local first (high priority) + - Implement editing form "in place" (optional for this sprint) + - Change icon for "add review" entry + - Overcoming UI test challenges +- ### Next Meeting's Business + - Creation of team status video ## End Time -- 11/30/2022 at 2:00PM \ No newline at end of file + +- 11/30/2022 at 2:00PM diff --git a/admin/meetings/1212022-check10.md b/admin/meetings/1212022-check10.md index 80a9937..6017cd2 100644 --- a/admin/meetings/1212022-check10.md +++ b/admin/meetings/1212022-check10.md @@ -1,22 +1,29 @@ # Meeting Minutes (12/1/2022) + ## Team 29: Hackers1995 + ## Meeting Topic: Weekly TA Catchup with Gagan + We are meeting with Gagan to discuss status video and general updates on project. ## Attendance + 1. Rhea Bhutada 2. George Dubinin 3. Gagan Gopalaiah ## Meeting Details -- When: 12/1/2022 at 12:00PM -- Where: Zoom + +- When: 12/1/2022 at 12:00PM +- Where: Zoom ## Discussion Points by Gagan -- Don't code up anything after Sunday. Reserve the time for bug fixes -- Final Interview is a 4-5 minute interview about general course specific topics -- Live demo of the app for Gagan -- Gagan asks us to evaluate instructional assistants + +- Don't code up anything after Sunday. Reserve the time for bug fixes +- Final Interview is a 4-5 minute interview about general course specific topics +- Live demo of the app for Gagan +- Gagan asks us to evaluate instructional assistants ## End Time -- 12/1/2022 at 12:20PM \ No newline at end of file + +- 12/1/2022 at 12:20PM diff --git a/admin/misc/rules.md b/admin/misc/rules.md index 204bacd..30ecda7 100644 --- a/admin/misc/rules.md +++ b/admin/misc/rules.md @@ -1,57 +1,66 @@ -# Team Working Agreement -## Term: Fall 2022 -## Creation: 10/12/2022; Revised: N/A -## Group Identification - - Team 29 - - TA: Gagan Gopalaiah - - Instructor: Professor Thomas Powell - - Team Name: Hackers1995 - -## Team member info (name/email) - 1. Rhea Bhutada, rbhutada@ucsd.edu - 2. George Dubinin, gdubinin@ucsd.edu - 3. Gavyn Ezell, gezell@ucsd.edu - 4. Henry Feng, hefeng@ucsd.edu - 5. Kara Hoagland, khoaglan@ucsd.edu - 6. Marc Reta, mreta@ucsd.edu - 7. Sanjit Joseph, smjoseph@ucsd.edu - 8. Isaac Otero, irotero@ucsd.edu - 9. Arthur Lu, a8lu@ucsd.edu - 10. Daniel Hernandez, d7hernan@ucsd.edu - -## RULES: -#### 1) Primary Means of Communication and Expectations -- All members will communicate via Slack. -- All members will be expected to read messages from group chats and direct messages, and respond in no more than 4 hours and no later than 10PM. -- All pull requests require 3 people to review the code being pushed to main. - -#### 2) Scheduling Meetings (Schedule at least one meeting as part of constructing your team agreement.) -- Members are expected to meet at least once a week with the group either in-person or on Zoom. Future meeting details will be determined within a 24 hours window. -- Team members hosting the meeting will send out a reminder of the meeting with an agenda 2 hours before the meeting. - -#### 3) General Responsibilities for All Team Members - -- Respect the contributions of others. -- Work on assignments early to allow others to review and debug any issues. -- Communicate any issues or problems as early as possible. -- Be open to criticism. - -#### 4) Specific Team Member Responsibilities/Deadlines (Optional) - -- A daily standup is required every day from every team member. A daily standup includes what you've completed, what you want to work on, and what issues you encountered for the day. If you haven't done anything for that day, write down what you will be contributing. - -#### 5) Conflict Resolution - -- Conflicts between individuals will first try to be resolved amongst the people involved. -- Group conflicts will be voted on. -- Ongoing conflicts will be reported to the TA. -- Unprofessionalism of any kind will not be tolerated. Conflicts involving this will immediately be brought up with the TA - -#### 6) Expectations of Faculty and GTA’s - -- If a team member fails to live up to this agreement, the situation may be reported to the staff, but the team will still be responsible for submitting a completed assignment. Staff will be available to meet with teams to resolve issues. - -## Team Signatures - -#### Print Name: -#### Signature: +# Team Working Agreement + +## Term: Fall 2022 + +## Creation: 10/12/2022; Revised: N/A + +## Group Identification + + - Team 29 + - TA: Gagan Gopalaiah + - Instructor: Professor Thomas Powell + - Team Name: Hackers1995 + +## Team member info (name/email) + + 1. Rhea Bhutada, rbhutada@ucsd.edu + 2. George Dubinin, gdubinin@ucsd.edu + 3. Gavyn Ezell, gezell@ucsd.edu + 4. Henry Feng, hefeng@ucsd.edu + 5. Kara Hoagland, khoaglan@ucsd.edu + 6. Marc Reta, mreta@ucsd.edu + 7. Sanjit Joseph, smjoseph@ucsd.edu + 8. Isaac Otero, irotero@ucsd.edu + 9. Arthur Lu, a8lu@ucsd.edu + 10. Daniel Hernandez, d7hernan@ucsd.edu + +## RULES: + +#### 1) Primary Means of Communication and Expectations + +- All members will communicate via Slack. +- All members will be expected to read messages from group chats and direct messages, and respond in no more than 4 hours and no later than 10PM. +- All pull requests require 3 people to review the code being pushed to main. + +#### 2) Scheduling Meetings (Schedule at least one meeting as part of constructing your team agreement.) + +- Members are expected to meet at least once a week with the group either in-person or on Zoom. Future meeting details will be determined within a 24 hours window. +- Team members hosting the meeting will send out a reminder of the meeting with an agenda 2 hours before the meeting. + +#### 3) General Responsibilities for All Team Members + +- Respect the contributions of others. +- Work on assignments early to allow others to review and debug any issues. +- Communicate any issues or problems as early as possible. +- Be open to criticism. + +#### 4) Specific Team Member Responsibilities/Deadlines (Optional) + +- A daily standup is required every day from every team member. A daily standup includes what you've completed, what you want to work on, and what issues you encountered for the day. If you haven't done anything for that day, write down what you will be contributing. + +#### 5) Conflict Resolution + +- Conflicts between individuals will first try to be resolved amongst the people involved. +- Group conflicts will be voted on. +- Ongoing conflicts will be reported to the TA. +- Unprofessionalism of any kind will not be tolerated. Conflicts involving this will immediately be brought up with the TA + +#### 6) Expectations of Faculty and GTA’s + +- If a team member fails to live up to this agreement, the situation may be reported to the staff, but the team will still be responsible for submitting a completed assignment. Staff will be available to meet with teams to resolve issues. + +## Team Signatures + +#### Print Name: + +#### Signature: diff --git a/admin/team.md b/admin/team.md index de75ace..d528b29 100644 --- a/admin/team.md +++ b/admin/team.md @@ -1,73 +1,76 @@ -# **Hackers1995** - -## **Brand** -![poster](./branding/teamposter.jpg) - -## **Values** -- Openness -- Honesty -- Respect -- Integrity -- Diversity/Inclusion - -## **Roster** -### **TA: Gagan Gopalaiah** - - -### **Team Lead: Rhea Bhutada** -- #### About Me: - - My name is Rhea Bhutada and I am currently a CS major and CogSci minor at ERC. The intersection between neuroscience and computer science really fascinates me and I generally try to apply myself to projects that deal with the overlap of both of these fields. This year I'm working as an undergraduate researcher at the Swartz Center for Computational Neuroscience, which has been an extremely cool experience. Other than that I love to stay active. I used to play basketball in high school and was in an NCAA commercial with Shaq. But lately, I’ve been really into running. Overall, I'm excited to contribute to this project! Although I haven't had too much industry experience, I am interested to see how I can apply my previous course work to backend or frontend design. -- #### Link to Github: https://github.com/rheabhutada02 - - -### **Team Lead: George Dubinin** -- #### About Me: - - Hello World! I'm a fifth year (3rd year transfer) computer science major from the North Bay Area. Web development has been a big focus of mine since taking Prof Powell's 134B last winter and I'm stoked to be back in the "full stack" developer seat for 110. I am the second the team lead and in addition to my love for leading and working on team projects I am also fascinated by web development technologies including containerization, infrastructure as code (IaC), software as a service (SAAS), and web-based encryption (security). I am also an avid DJ and the traininer manmager for the DJ club on campus. This quarter is shaping up to be a memorable one! -- #### Link to Github: https://github.com/look-its-ashton - - -### **Gavyn Ezell** -- #### About Me: - - My name is Gavyn Ezell and I’m from Hawaii. Currently a 3rd year CS Major at Muir. I love video games, playing piano, and going to the gym. For SWE, backend interests me most (I am not good with design and visuals), and I’m hoping to learn a lot more backend from this project! -- #### Link to Github: https://github.com/gavyn-ezell - - -### **Daniel Hernandez** -- #### About Me: - - My name is Daniel Hernandez and I am a 3rd year Computer Science major and music minor. Some of my interests in the CS field are ML, AI, and Cybersecurity. Outside of school, I play drums for a local band. For SE, the backend aspect appeals to me the most since I am able to utilize more of what I learned from my past classes. However, I would want to try frontend since I do enjoy design to some extent. -- #### Link to Github: https://github.com/d7hernan - - -### **Henry Feng** -- #### About Me: - - My name is Henry, and I am a 3rd year CS major. I was born in China and grew up in New Zealand. I wrote my first line of code, in Python during my second year of high school. My favourite foods are ramen, steak and pasta. Some of my hobbies include playing guitar, hiking, cooking, video games, and music (from the Persona series). I am excited to start this project and hope to contribute to both frontend and backend. -- #### Link to Github: https://github.com/dusk-moon - - -### **Kara Hoagland** -- #### About Me: - - My name is Kara Hoagland and I am a 3rd year Computer Engineering major. CS-wise, I'm interested in topics such as computer vision and RFID, but it's hard to limit oneself because there's so many interesting topics out there. Outside of CS, I enjoy D&D, biking, and reading. I got some industry experience over summer and love getting to see how that experience and my previous classes all apply to this project. I'm interested in full stack but more so the backend of things. -- #### Link to Github: https://github.com/KH-Cl - - -### **Marc Reta** -- #### About Me: My name is Marc Reta and I am a 3rd year Computer Engineering major in Warren College. I love exploring San Diego and going on adventures. I have a huge interest in Public Transportation. I'm looking foward to working with everyone in my group and learn how to create an application. -- #### Link to Github: https://github.com/Graydogminer - - -### **Sanjit Joseph** -- #### About Me: - - Hi! My name is Sanjit Joseph and I'm a 3rd year CE major at Sixth. I'm from the Bay Area, so I've been surrounded by technology most of my life. I'm into building computers and I waste a lot of time (and money) messing with my PC and playing video games on it. I enjoy things outside of tech, though--as an Eagle Scout, I've done tons of backpacking throughout California and the US. I also hold a black belt in Shotokan Karate. As for this class, I'm pretty excited about all the different aspects of software engineering; frontend and backend both appeal to me, but I'm really just excited to work on a long class project in a team setting. -- #### Link to Github: https://github.com/sm-joseph - - -### **Isaac Otero** -- #### About Me: - - My name is Isaac Otero, I am a 5th year Cog Sci major. I am interested in front end development. I want to implement what I’ve learned from my design classes into my projects for front end development. -- #### Link to Github: https://github.com/Isaac-Otero - - -### **Arthur Lu** -- #### About Me: - - My name is Arthur Lu and I am a 3rd year CE major. I am primarily interested in low level systems design, hardware development and optimization, and HPC architecture. I work as an undergraduate research assistant for Prof. Turakhia developing hardware accelerators for long length genome alignment. When I’m not busy, I like to relax with some retro video games. -- #### Link to Github: https://github.com/ltcptgeneral +# **Hackers1995** + +## **Brand** + +![poster](./branding/teamposter.jpg) + +## **Values** + +- Openness +- Honesty +- Respect +- Integrity +- Diversity/Inclusion + +## **Roster** + +### **TA: Gagan Gopalaiah** + +### **Team Lead: Rhea Bhutada** + +- #### About Me: + - My name is Rhea Bhutada and I am currently a CS major and CogSci minor at ERC. The intersection between neuroscience and computer science really fascinates me and I generally try to apply myself to projects that deal with the overlap of both of these fields. This year I'm working as an undergraduate researcher at the Swartz Center for Computational Neuroscience, which has been an extremely cool experience. Other than that I love to stay active. I used to play basketball in high school and was in an NCAA commercial with Shaq. But lately, I’ve been really into running. Overall, I'm excited to contribute to this project! Although I haven't had too much industry experience, I am interested to see how I can apply my previous course work to backend or frontend design. +- #### Link to Github: https://github.com/rheabhutada02 + +### **Team Lead: George Dubinin** + +- #### About Me: + - Hello World! I'm a fifth year (3rd year transfer) computer science major from the North Bay Area. Web development has been a big focus of mine since taking Prof Powell's 134B last winter and I'm stoked to be back in the "full stack" developer seat for 110. I am the second the team lead and in addition to my love for leading and working on team projects I am also fascinated by web development technologies including containerization, infrastructure as code (IaC), software as a service (SAAS), and web-based encryption (security). I am also an avid DJ and the traininer manmager for the DJ club on campus. This quarter is shaping up to be a memorable one! +- #### Link to Github: https://github.com/look-its-ashton + +### **Gavyn Ezell** + +- #### About Me: + - My name is Gavyn Ezell and I’m from Hawaii. Currently a 3rd year CS Major at Muir. I love video games, playing piano, and going to the gym. For SWE, backend interests me most (I am not good with design and visuals), and I’m hoping to learn a lot more backend from this project! +- #### Link to Github: https://github.com/gavyn-ezell + +### **Daniel Hernandez** + +- #### About Me: + - My name is Daniel Hernandez and I am a 3rd year Computer Science major and music minor. Some of my interests in the CS field are ML, AI, and Cybersecurity. Outside of school, I play drums for a local band. For SE, the backend aspect appeals to me the most since I am able to utilize more of what I learned from my past classes. However, I would want to try frontend since I do enjoy design to some extent. +- #### Link to Github: https://github.com/d7hernan + +### **Henry Feng** + +- #### About Me: + - My name is Henry, and I am a 3rd year CS major. I was born in China and grew up in New Zealand. I wrote my first line of code, in Python during my second year of high school. My favourite foods are ramen, steak and pasta. Some of my hobbies include playing guitar, hiking, cooking, video games, and music (from the Persona series). I am excited to start this project and hope to contribute to both frontend and backend. +- #### Link to Github: https://github.com/dusk-moon + +### **Kara Hoagland** + +- #### About Me: + - My name is Kara Hoagland and I am a 3rd year Computer Engineering major. CS-wise, I'm interested in topics such as computer vision and RFID, but it's hard to limit oneself because there's so many interesting topics out there. Outside of CS, I enjoy D&D, biking, and reading. I got some industry experience over summer and love getting to see how that experience and my previous classes all apply to this project. I'm interested in full stack but more so the backend of things. +- #### Link to Github: https://github.com/KH-Cl + +### **Marc Reta** + +- #### About Me: My name is Marc Reta and I am a 3rd year Computer Engineering major in Warren College. I love exploring San Diego and going on adventures. I have a huge interest in Public Transportation. I'm looking foward to working with everyone in my group and learn how to create an application. +- #### Link to Github: https://github.com/Graydogminer + +### **Sanjit Joseph** + +- #### About Me: + - Hi! My name is Sanjit Joseph and I'm a 3rd year CE major at Sixth. I'm from the Bay Area, so I've been surrounded by technology most of my life. I'm into building computers and I waste a lot of time (and money) messing with my PC and playing video games on it. I enjoy things outside of tech, though--as an Eagle Scout, I've done tons of backpacking throughout California and the US. I also hold a black belt in Shotokan Karate. As for this class, I'm pretty excited about all the different aspects of software engineering; frontend and backend both appeal to me, but I'm really just excited to work on a long class project in a team setting. +- #### Link to Github: https://github.com/sm-joseph + +### **Isaac Otero** + +- #### About Me: + - My name is Isaac Otero, I am a 5th year Cog Sci major. I am interested in front end development. I want to implement what I’ve learned from my design classes into my projects for front end development. +- #### Link to Github: https://github.com/Isaac-Otero + +### **Arthur Lu** + +- #### About Me: + - My name is Arthur Lu and I am a 3rd year CE major. I am primarily interested in low level systems design, hardware development and optimization, and HPC architecture. I work as an undergraduate research assistant for Prof. Turakhia developing hardware accelerators for long length genome alignment. When I’m not busy, I like to relax with some retro video games. +- #### Link to Github: https://github.com/ltcptgeneral diff --git a/package.json b/package.json index abf2630..66b994d 100644 --- a/package.json +++ b/package.json @@ -1,29 +1,27 @@ { - "name": "food-journal", - "version": "1.0.0", - "type": "module", - "scripts": { - "test": "mocha --recursive --require mock-local-storage './{,!(node_modules)/**}/*.test.js'", - "lint-js": "eslint **/*.js", - "fix-js": "eslint --fix **/*.js", - "lint-html": "htmlhint **/*.html", - "lint-css": "stylelint **/*.css", - "fix-css": "stylelint --fix **/*.css", - "http-server": "http-server source", - "js-doc": "jsdoc -d source/docs/ -r source/", - "lint-prettier": "prettier --check .", + "name": "food-journal", + "version": "1.0.0", + "type": "module", + "scripts": { + "test": "mocha --recursive --require mock-local-storage './{,!(node_modules)/**}/*.test.js'", + "lint-js": "eslint **/*.js", + "fix-js": "eslint --fix **/*.js", + "lint-html": "htmlhint **/*.html", + "lint-css": "stylelint **/*.css", + "fix-css": "stylelint --fix **/*.css", + "http-server": "http-server source", + "lint-prettier": "prettier --check .", "fix-prettier": "prettier --write ." - }, - "devDependencies": { - "eslint": "^8.27.0", - "htmlhint": "1.1.4", - "http-server": "", - "jsdoc": "^4.0.0", - "mocha": "10", - "mock-local-storage": "^1.1.23", - "puppeteer": "^18.2.1", - "stylelint": "14.14.1", - "stylelint-config-standard": "^29.0.0", - "prettier": "2.8.0" - } + }, + "devDependencies": { + "eslint": "^8.27.0", + "htmlhint": "1.1.4", + "http-server": "", + "mocha": "10", + "mock-local-storage": "^1.1.23", + "prettier": "2.8.0", + "puppeteer": "^18.2.1", + "stylelint": "14.14.1", + "stylelint-config-standard": "^29.0.0" + } } diff --git a/source/CreatePage.html b/source/CreatePage.html index 4c450ca..519ccbf 100644 --- a/source/CreatePage.html +++ b/source/CreatePage.html @@ -1,6 +1,5 @@ -
@@ -8,12 +7,11 @@