-
Notifications
You must be signed in to change notification settings - Fork 3
Meeting Minutes
LachezaraLaz edited this page Mar 31, 2023
·
2 revisions
- sprint 1 tasks were assigned to all team members
- brainstorming about possible languages/technologies to be used in the project
- compiled questions to ask the project coordinator
- tech to be used in the project will be confirmed in Meeting 2
Based on the Grading excel files for sprint 1:
-
[Lachezara] Update the readme.md to show:
- the info of your team members (real name and GitHub user name, role/Strengths of the member in the project)
- what languages & techniques do you plan to use (if haven't decided, then write sth like TBD)
- [Megan] Update the readme.md to show the description / objective / core features of the project
- [EVERYONE] Document your meeting at the wiki page (recommended) of your repo or under the issues. (at least one meeting)
- [Lache, Sahana, Inas, Suha] Create/document high-level user stories for 4 core features
- [Lache, Sahana, Inas, Suha] Finish the tasks before the DDL and create some issues (a few sub user story of core features/story cards) under the milestone of the next sprint (you can still commit after the DDL if the changes you do are beyond the requirement of this sprint)
-
[EVERYONE] Meaningful commits description
- Most of the commit messages are meaningful and correctly describe the commit
-
[EVERYONE] commits referenced with issue numbers
- Have at least one commit referenced with an issue
- [EVERYONE] Do pull requests & review them.
- [EVERYONE] Assign some pull request / issue to members to work on them & everyone should participate in the contributions (i.e., we are able to see the contribution somewhere in your repo)
- ideas:
- Python - might be easier to use/learn in a short period of time
- C# - might be harder to learn in the semester
- Basic web dev stuff (HTML, CSS?)
- employers
- students
- other candidates
- admin
- discord being used as the means for communication and sending important documents to the team.
- questions to ask the project coordinator have been noted outside of the meeting minutes -> Inas will reach out
- tentative deadline to get assigned sprint 1 tasks done: Jan 30 - Jan 31
- finalized everyone's role in the project
- discussed the uses of git in the project
- going through the last tasks required for sprint 1
- Megan: Full-Stack Developer, Technical Lead
- Inas: Business Analyst, Full-Stack Developer
- Sahana: UI/UX Designer, Frontend Designer
- Suha: QA Lead, Backend Developer
- Lachezara: Project Manager, Full-Stack Developer
- create pull request for the
ReadME.md-> Megan - assign user stories to team members
- discuss the organization/format of the project
- create more meaningful commits when doing readme.me commits
- login function (frontend/backend)
- email notification (backend component)
- creating a commit while doing pull request
- assigning issue numbers to commits/pull requests
- scope of a commit for the project
- project guidelines: does everyone one have to do a commit
- creating a commit while doing pull request
The features that the group will work on is:
- Feature 2: Adding and manage postings to the System by the Employers
- Feature 4: Creating and Managing Student Profile
Here are the HTML pages that need to be created for the features prioritized in sprint 2.
- Feature 2:
- dashboard page that all postings that employer made
- new/edit posting page
- Feature 4:
- login page with a link signup
- signup page
- profile page with edit button that leads you to edit profile
- edit profile page
- Backend: Python, mySQL
- Frontend: HTML, CSS, JavaScript, React?
- discussed general attributes to appear on the page
- decided on a database
- showing of frontend design of feature 2
Name suggestion:
- LinkedOut Further discussions later - to be decided for the end of the week
We will be using the built-in databased on Python, SQLite. Structurally similar to SQL and we would need to create at least 5 tables:
- all login info
- job postings
- candidate user profiles
Feature 2: Job Posting Management dashboard page
- each posting would be a row of a table -> job name -> company of employment -> job description -> qualifications -> work location (hybrid, online or in person) -> salary -> person of contact -> creation date page for accepting/editing job posting info
- form will have the following fields: -> job name -> company of employment -> job description -> qualifications -> work location (hybrid, online or in person) -> salary -> person of contact -> creation date Feature 4 - Profile creation profile section
- profile pic
- contact info (email)
- portfolio link
- bio
- job history
- skills
- edit button signup section:
- full name
- password
- user type (candidate or employee)
- search bar
- add tags to job postings
- filter by tags
Inas will be messaging the project coordinator to get approval of the additional features
Tuesday at 7pm
- Story points
- User story -> task breakdowns
- Issues for sprint 3
- Acceptance test to be started
- HTML pages should be stored in a folder called "template"
- CSS file should be stored in "static"
- Story points dhave been assigned to user stories
- Login (user authentication)
- Signup (add data to database table)
- Create profile (uses userProfiles, WorkExperiences)
- Employer Dashboard (uses LoginInfo, JobPostings)
- 2 Admin Pages
- 1 Employer Candidate Page (see candidates and select one for interview)
- 1 Notification Page (+ Database table for notifs + add notif icon to header
- 1 Brose Postings Page
- 2 Admin Pages (1 for User Profiles and 1 for Postings) [2 Admin Funcs; User Profiles + Postings; CRUD] <-- Inas
- 1 Employer Candidates Page (see candidates and select, new col in database for selected candidate) [2 Backend Funcs; See Candidate + Select Candidate] <-- Suha (tentative)
- 1 Notification Page (+ Database table for notifs + add notif icon to header) [1 Backend Func; Show Notifications] <-- Lache
- 1 Browse Postings Page (2 version: Employer w/ CRUD; User w/ View Details) [2 Backend Func; 1 for Employer w/ CRUD + 1 for User w/ View Details] <- Suha
- 1 Job Posting Info (for Candidate) [1 Backend Func; Display Info + Apply (Post)] <-- Lache
- megan -> Admin Pages, Edit Job Posting page (employer)
- sahana -> View job posting (candidate), description page (candidate), Application page (candidate), notification page
- Core #4 resume doesnt load from profile.
- 1 New Notifications Table (1 notifKey, 1 userID, 1 message, 1 dateSent (if date obj exists in Python))
- 1 New Job Applicants Table
- 1 New column in Job Postings for 'selectedCandidate'
-test automation/ acceptance test -(sahana) -tags: remote, hybrid, in person, full time, part time, internship
Frontend: -submit feedback page for student and employer -view feedback page for admin -feedback button in footer -fixing footer on every page -for admin, view feedback in navbar -add and edit job posting pages should have tags -added column for tag for employer job dashboard -added info for tag in candidate view job posting (lache) -added info for tag in view job description (lache)
-Bug- profile page navbar icons dont work -Bug- fixing search inputs on view jobs page
Backend: -Searching by name (js) (meg) -add function from apply to job applicant table (Lache) -test website in every way and give errors and create bugs (lache) -create table database for feedback -add column in job posting table for tags -implement backend for feedback (suha) -implementing tags for job posting (lache)