CTJ: Development Meeting Agenda

[MattPereira]

Overview

A place to park ideas, concerns, or other discussion topics for development team

2024:

• 2024-31-01: CTJ: Development Meeting Agenda #450 (comment)
• 2024-28-06: CTJ: Development Meeting Agenda #450 (comment)
• 2024-16-08: CTJ: Development Meeting Agenda #450 (comment)
• 2024-06-09: CTJ: Development Meeting Agenda #450 (comment)
• 2024-19-09: CTJ: Development Meeting Agenda #450 (comment)

[kcoronel]

hi team @MattPereira @bzzz-coding are you using this issue as an agenda instead of #39? If so, please let me and @sabheasley know via a comment in this issue so we can close issue #39.

Also, for an agenda item for your next meeting (Tuesday October 5?) "Checking our MK Docs code and making sure it is not broken."

[MattPereira]

I didn't know about issue #39 because Ava never mentioned it and I failed to spot it in the Links/Questions/Review column of the all team project board

@kcoronel is there a specific issue you are experiencing with the MK Docs?

[kcoronel]

not a problem, do you want me to close #39? With MK Docs, I've updated this doc section (I need to update it again) but this current version doesn't show up on the front-end

[MattPereira]

@kcoronel #39 is closed and yeah looks like the mkdocs deployment is indeed failing. We will do our best to fix it

https://github.com/hackforla/CivicTechJobs/actions/runs/6002157713/job/16277931316#step:4:138

[kcoronel]

Hi Team, adding the following item for discussion for your Dev Meeting:

• Please review the MVP Flow Desktop that the UI/UX Design team has created. It would be great to capture team feedback or any questions within the issue > MVP Flow (Desktop) #570

[LoTerence]

09-26-2024
Agenda

• Brief Team intros
  Questions:
  Where are you from?
  What techs and tools do you like the most?
  What experience do you have?
  What made you join HFLA?

• Roja

• Kevin

• Ida

• Ryan

• Terence

• Bitian

• Was everyone able to get a development environment running on their local machine? - Yes.

• Talk about current issues and state of the project:

• Everyone is new and joined within the last month, so no one on the team really knows anything about the state of the project.

  • Documentation is severely outdated.
  • The main branch is not in sync with the develop branch, which is why the old installation instructions and other docs are out of date.

• There is no deployment at all at the moment.

  • This is why I brought Ryan in to help with that.
  • As far as I know, there was never a successful deployment.
  • We absolutely need this for MVP-1 – without it, we have no project to demo.
  • update: Turns out there was a staging deployment: https://stage.civictechjobs.org/

• Status of the frontend is unknown. Frontend needs a total audit.

  • Right now, the UX team is working on the user flow for the qualifiers feature. It should be ready by November at the latest.
  • As of now there are only static pages - like landing page, credits, privacypolicy

• Backend is basically brand new at the moment.

  • Jimmy reset the backend completely, decoupling the develop branch from the main branch. The challenge will be to merge them back together as a team
  • The old backend was completely broken, so it had to be restarted

Issues we should address by next week:

Frontend

• Frontend Audit · Issue #586 · hackforla/CivicTechJobs · GitHub

Frontend: Review Lu's MVP flow:

• Gather team feedback · Issue #581 · hackforla/CivicTechJobs · GitHub
• MVP Flow (Desktop) #570

Devops

• Fix GitHub Action Issue Trigger · Issue #579 · hackforla/CivicTechJobs · GitHub
• Epic (Devops): Deploy develop Branch to Staging Environment in AWS
• right now our staging deployment is being charged 200 a month - need to investigate
• Ryan to help investigate the current state of our deployment in incubator and whats going on there (thank you Ryan)

Terence

• Fix mkdocs deployment - help Karen and PM team investigate issues with mkdocs deployment
• next: Update dev onboarding documentation to make it easier to recruit new devs
• Make a developer roadmap to meet goals of MVP-1
• Sync with Karen on Saturday about PM stuff
• ask karen about AWS accounts
• sync with Ryan about terraform + incubator, what we need
• find out current state of deployments + AWS

10/01/2024 AWS stage deployment update:

• no one on the team has credentials for the AWS. Its not on 1password.
• Next action: ask on the devops channel

[kcoronel]

Terrence and Karen Chat on September 30, 2024

• Team Lead Overview and Responsibility
• Overseeing the dev team, attending lead meetings, delegating work

Karen to do:

• Team Lead meeting - add Terrence - we will discuss decisions we have made for the project and how to document this on the wiki + prioritization of work
• Clear requirements
• Invite Terence to meeting with Bonnie
• Sunday morning send Terence MVP doc we will share with Bonnie
• Share with Bonnie ahead of PM/Org Meeting

[LoTerence]

10/03/2024

• Roja
• Kevin
• Ida
• Ryan
• Bitian
• Terence

Current Issues and state of project

• project lead expectations
• prioritize growth of developers
• rough plan
• devops
• review Lu MVP flow together

Rough plan:

1. stabilize the project
2. deploy staging asap
   1. The challenge is to have these two goals completed by the time the final designs come out
3. develop and deploy MVP-1

Dev roadmap

Terence

• investigate AWS in gh action and aws folder in code base

MVP Flow questions

• About MVP flow - we should set up a meeting with Lu and Bonnie so we can all get on the same page about what the user flow and requirements are. Need clarity on user flow - questions about project vs opportunities, etc.
• Ask questions - need clarity on requirements because it seems to have changed a lot on each iteration
• Go straight to Bonnie and get the most updated requirements straight from the source from ground zero. All the documents are from 3 to 4 years ago.
• Q: Civictechjobs needs to be integrated into the current onboarding process/flow
• Two jobs: be a volunteer job posting board, and also handle some part of the onboarding
• need an understanding of the vision and what we are trying to accomplish
• people who are posting opportunities need a flow too

Ryan

• look into AWS stage deployment - 100 copies

Bitian, Roja, Kevin

• begin working on migrating sass components to tailwind

[RSkuma]

(10/3/2024) Questions Regarding CivicTechJobs Design/Vision that came up during team meeting:

1. What is the main use for CTJ, a public facing recruitment site or an internal job board? Or Both? Or something else?

2a. What will CTJ's role in the onboarding process be? Will it be an additional step added to the current onboarding process?
2b. Or will it be a replacement or augment to the current onboarding process? If so, will it be working with existing systems like tables and people depot or will it be replacing them?

3a. What should CTJ do for hfla members(volunteers who can login), what can they see and do?
3b. What should CTJ do for non-members(visitors who can't login), what can they see and do?

4. How do project leads post positions on CTJ? There is no workflow or mockup on Figma for that yet

5. What are the core functions of CTJ that should be a part of MVP-1? What functions are secondary and can be added later?

[ExperimentsInHonesty]

@JimmyJuarez10 I am adding this to your agenda issue so that you can discuss at your next dev meeting.

I got this message from @RSkuma

I was at the CivicTechJobs meeting to help with their deployment, but I wasn't able to get a complete picture of where they are at and was hoping you could help
CivicTechJobs currently has some assets on the Incubator AWS account, but at the meeting they said they are planning to migrate to Incubator in the near future. If that's true, where are the AWS resources currently on Incubator from? Are they already on Incubator? Is it an older version? Or a partial deployment?
2. Will CivicTechJobs be deployed on Incubator permanently? Or is it temporary with the intent to grant them their own AWS account later?
3. Does CivicTechJobs already have their own AWS account? Somebody on the CivicTechJobs team said they did, and that their account is being charged $200 a month. I'm thinking they were logged into Incubator when they saw that number but I would like to confirm

Can you clarify what y'all know and what you need help? And where we should communicate with you.

• I see this issue Epic (Devops): Deploy develop Branch to Staging Environment in AWS #585, but you also have these issues label:"feature: Architecture" aws

[LoTerence]

10/10/2024

• Roja
• Kevin
• Ida
• Ryan
• Bitian
• Terence

Agenda

• MVP flow
• Answer Ryan questions
• github branches

Terence

• ask design team about if there are final designs for the search results page
• ask design team if dev handoff sections are truly ready or if they still need changes - they are old, need verification from current team
• Ask design team if the design system is up to date, which component system to use
• write more specific requirements for the sass -> tailwind component story
• Look into why Ryan cannot assign issues to CTJ project board
  • 10/16 Update - I asked Karen to add Ryan to the CTJ write team on github.
• follow up with Ryan about maybe joining the Pm/org meeting

Ryan

• why project board automatically has a filter when you click on it - "documentation"
• Looking into AWS ctj resources

Bitian

• cant find the column number, project board is owned by HFLA

Kevin

• continue working on migrating sass button component to tailwind

[LoTerence]

10/17/2024

• Roja - not present
• Kevin - not present
• Ida - not present
• Ryan
• Bitian
• Terence

Agenda

• PM/Org meeting - gathered technical requirements, general overview of MVP-1 roadmap
• Design team questions (search results page, dev handoff up to date, design system final components)
• Frontend - any updates about sass+tailwind story - none
• Update on Cognito and Hosting of staging site

Figma question answers:

1. The final designs for the search result page aren't ready yet. We'll hand them off after completing usability testing, as there may be updates afterward.
2. Yes, the current dev handoff is final and up to date.
3. I've cleaned up the design system, and the current version in the red box is the most updated. However, there are still a few pending elements that may be added later.

AWS staging deployment:

• Not in incubator
• ask Jimmy
• maybe ask Ava

Bitian - github action story

• should be ready to close

People depot

• right now - people depot is under development
• current state - have a mock user pool
• We should do the same for development
• Requirement: There should be a unified cognito pool for HFLA projects
• cognito is for authentication
• It should be easy to integrate with cognito from our app

[LoTerence]

10/24/2024

• Roja
• Ida - not present
• Ryan - not present
• Bitian - not present
• Terence

Agenda

• Backend - Created DB schema model
• Frontend - any updates about sass+tailwind story

Bitian - github action story

• should be ready to close

[LoTerence]

11/07/2024

• Bitian
• Roja - not present
• Ida - not present
• Ryan
• Terence

Bitian

• fixed gh action
• will make an issue to start devveloping the API based on the models

Ryan

• the deployment is located in AWS incubator - Ryan found it
• Todo: Understand the process of how ctj's main branch is deployed to AWS right now

AWS

• Goal is to have one deployment for the develop branch, and one for the main branch
• Leave the current stage.ctj.org deployment untouched
• Once the develop branch deployment is fully tested, then we replace the old deployment method.

Terence

• Code: integrate whitenoise and nginx

Ida - Frontend

• Completed eslint story 🙌
• She will work on resolving all eslint errors next - issue 609

Agenda

• December break
• UX team / Lu should have qualifiers and skill matrix page designs ready in 1-2 months. So the frontend team will have new feature work to do around January/February. Lets aim to (1) finish migrating sass to tailwind by then; and (2) completely migrate webpack to vite.

Backend

• Created a new DB schema diagram
• Currently working on merging develop into main
• Aim to deploy a staging environment to AWS by next week.
• Aim to finish developing API server by the end of the month

[LoTerence]

11/14/2024

• Bitian
• Roja - not present
• Ida - not present
• Ryan
• Terence

Bitian

• wrote half the models so far, PR will be ready for review soon
• initial code for models, urls, serializers
• Suggestion: schedule live coding, pairing sessions

Ryan

• Gotten app hosted on AWS
• Cant reach them via the internet yet, because of load balancer (LB) issues
• LB requires targeted healthcheck

Terence

• fixed stage docker container to prepare for deployment

[LoTerence]

11/21/2024

• Roja - not here
• Ida - not here
• Bitian
• Ryan
• Terence

Karen needs to know:

• Our dev meeting schedule in December. What do you guys wanna do?
• What is a good first day to meet in January?

Agenda

• Next week dev meeting is on thanksgiving. Lets move it to another day?
• Our roadmap progress: https://docs.google.com/document/d/1KTElKAprzv46-FqIBBcT5w8fi1oh6b03nCQfvm13XGE

Dev team schedule:

• Next meeting: Wednesday 11/27 at 4pm PT
• dev meeting schedule in December: meet first two weeks, same time on Thursday 12/05 and 12/12
• January first day: 01/09/2025

Lets try to aim to finish as much of below by first two weeks of December

1. deployment pipelines
2. API server
3. catch up on technical documentation

Bitian

• Going to keep making progress on Django Data Models PR

Ryan

• Incubator deployment blocked by devops team - they are prioritizing VRMS deployment
• May not be available until mid January

Terence - this week:

• keep working on merging develop into main
• catch up on writing documentation