CivicTechJobs
CivicTechJobs copied to clipboard
CTJ: Development Meeting Agenda
Overview
A place to park ideas, concerns, or other discussion topics for development team
2024:
- 2024-31-01: https://github.com/hackforla/CivicTechJobs/issues/450#issuecomment-1920705795
- 2024-28-06: https://github.com/hackforla/CivicTechJobs/issues/450#issuecomment-2197701370
- 2024-16-08: https://github.com/hackforla/CivicTechJobs/issues/450#issuecomment-2294340311
- 2024-06-09: https://github.com/hackforla/CivicTechJobs/issues/450#issuecomment-2333070134
- 2024-19-09: https://github.com/hackforla/CivicTechJobs/issues/450#issuecomment-2362577809
2023-12-09
- [ ] How to reconcile conflicts between sass and tailwind
- [ ] Matt has concerns about if people depot's amazon cognito setup is viable for CTJ login
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."
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?
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
@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
FYI added this issue to our CTJ general project board as well :) - let me know if you have any questions
2023-10-18
- AWS deployment failing
- https://github.com/hackforla/CivicTechJobs/actions/runs/6518963880/job/17704947779
- https://stage.civictechjobs.org/
- MKdocs deployment failing
- https://github.com/hackforla/CivicTechJobs/issues/456
01-31-2024
- Talked a about fix regarding MkDocs build
- https://github.com/hackforla/CivicTechJobs/issues/456
- Go over high level sketch of what the E2E flow should look like from Dev perspective
- Planning to switch backend from Django to Express.js since that is what the team is more familar, need to talk to project manager to see if thats okay.
- Gave benny directive to look into vite for building our frontend.
06-28-2024
Issues worked on this Week:
- Bitian: Submitted this pull request https://github.com/hackforla/CivicTechJobs/pull/547
- Benny: Submit this pull request https://github.com/hackforla/CivicTechJobs/pull/545
- Jimmy: Reviewed Benny and Bitian's pull request and is working on adding the djangorestframework.
Issues we will work on next Week:
- Bitian: Will work on getting the unit tests for the healthcheck api.
- Benny: Might be traveling / Will work on this when he gets back.
- Jimmy: Continue working on adding djangorestframework to ctj-backend.
08-16-2024
Issues worked on this Week:
- Live troubleshooting of issue [add issue here]
Issues we will work on next Week:
Product Team Questions: - Front end developers selections
- onboarding and first issues; Terrence Lo, Roja Pinnamraju, Alejandro Martinez (okay with not being lead), Anahis Valenzuela Terence_Lo_Resume.pdf Pinnamraju_Resume.pdf Alejandro Martinez Anahis-Valenzuela-Resume-Civic-Tech-Jobs.pdf
-
What kinds of projects will I be working on? You will be working on transferring our ux designs into the front end for our product while the backend devs work on getting the backend setup.
-
Will these projects be collaborative team efforts, or more individual contributions? A mix of both. We will expect weekly team meetings for you to collaborate through any blockers or challenges but you will be assigned to your own piece of work via issues.
-
I noticed the role involves working with React frameworks. Will volunteers also have opportunities to work with other technologies, such as Express and Node? I am totally fine working on more Frontend/React work just curious what technologies volunteers work with. For frontend we only expect to use React.
-
How many people are working on the team currently? What is the balance between developers and designers? Currently we have 2 backend devs and 2 designers. The designs are mostly 80% of the way there.
-
How many hours do you expect a developer to work on this project per week? I think at the beginning around 1-2 hours a week if we keep the team to 4 front end developers.
- Offboarding Benny
-
do we want to find another back-end developer?
-
Please review issues currently assigned to you and close issues appropriately. Nooria will be following up with you Jimmy to grab some time to clean up the board.
Notes: End point is up and running [Add screenshot]
Database - need to create a couple more tables
- Tables created: opportunities
- To create: CoP (nice to have)
- Login (necessary)
UX - what fields are we asking for in the design to match the user behavior ex: search field: CoP, skills level, what should be criteria here
Bitian - async works well - back week of 8/22 ask for availability T-Thurs anytime after 6pm - 7pm
Jimmy okay with deleting old issues to clean up the board
09-06-2024 Issues worked on this Week:
Anahis: Spoke with Terence for reorganizing the skills matrix. Terence: Reviewed Django Demo Walkthrough and submitted #564 for review. Jimmy: Meeting with Karen and leads Roja: N/A
09-19-2024 Issues worked on this past week:
- [X] Terence: Submitted a couple of PRs
- #572
- #571
- [X] Roja
- [X] Kevin
- [X] Jimmy
Issues we will work on next week: Terence: Look over the front end json and define what that needs look like Roja: Get going with development. Kevin: Get going with development try to run the locally , familiarize with the code base. Jimmy: Will work on terraform scripts for deploying to ecr.
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 > https://github.com/hackforla/CivicTechJobs/issues/570
09-26-2024 Agenda
-
[x] 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?
-
[x] Roja
-
[x] Kevin
-
[x] Ida
-
[x] Ryan
-
[x] Terence
-
[x] Bitian
-
[x] Was everyone able to get a development environment running on their local machine? - Yes.
-
[x] 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
developbranch from themainbranch. The challenge will be to merge them back together as a team - The old backend was completely broken, so it had to be restarted
- Jimmy reset the backend completely, decoupling the
Issues we should address by next week:
Frontend
Frontend: Review Lu's MVP flow:
- [x] Gather team feedback · Issue #581 · hackforla/CivicTechJobs · GitHub
- [x] MVP Flow (Desktop) #570
Devops
- [x] Fix GitHub Action Issue Trigger · Issue #579 · hackforla/CivicTechJobs · GitHub
- [x] Epic (Devops): Deploy develop Branch to Staging Environment in AWS
- [x] right now our staging deployment is being charged 200 a month - need to investigate
- [x] Ryan to help investigate the current state of our deployment in incubator and whats going on there (thank you Ryan)
Terence
- [x] Fix mkdocs deployment - help Karen and PM team investigate issues with mkdocs deployment
- [x] next: Update dev onboarding documentation to make it easier to recruit new devs
- [x] Make a developer roadmap to meet goals of MVP-1
- [x] Sync with Karen on Saturday about PM stuff
- [x] 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
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
10/03/2024
- [ ] Roja
- [ ] Kevin
- [ ] Ida
- [ ] Ryan
- [ ] Bitian
- [ ] Terence
Current Issues and state of project
- [x] project lead expectations
- [x] prioritize growth of developers
- [x] rough plan
- [x] devops
- [x] review Lu MVP flow together
Rough plan:
- stabilize the project
- deploy staging asap
- The challenge is to have these two goals completed by the time the final designs come out
- develop and deploy MVP-1
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
(10/3/2024) Questions Regarding CivicTechJobs Design/Vision that came up during team meeting:
- 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?
-
How do project leads post positions on CTJ? There is no workflow or mockup on Figma for that yet
-
What are the core functions of CTJ that should be a part of MVP-1? What functions are secondary and can be added later?
@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 https://github.com/hackforla/CivicTechJobs/issues/585, but you also have these issues label:"feature: Architecture" aws
10/10/2024
- [ ] Roja
- [x] Kevin
- [ ] Ida
- [x] Ryan
- [x] Bitian
- [x] Terence
Agenda
- [x] MVP flow
- [x] Answer Ryan questions
- [x] github branches
Terence
- [x] ask design team about if there are final designs for the search results page
- [x] ask design team if dev handoff sections are truly ready or if they still need changes - they are old, need verification from current team
- [x] Ask design team if the design system is up to date, which component system to use
- [x] write more specific requirements for the sass -> tailwind component story
- [ ] Look into why Ryan cannot assign issues to CTJ project board
- [x] 10/16 Update - I asked Karen to add Ryan to the CTJ write team on github.
- [x] follow up with Ryan about maybe joining the Pm/org meeting
Ryan
- [x] 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
10/17/2024
- [x] Roja - not present
- [x] Kevin - not present
- [x] Ida - not present
- [x] Ryan
- [x] Bitian
- [x] Terence
Agenda
- [x] PM/Org meeting - gathered technical requirements, general overview of MVP-1 roadmap
- [x] Design team questions (search results page, dev handoff up to date, design system final components)
- [x] Frontend - any updates about sass+tailwind story - none
- [x] Update on Cognito and Hosting of staging site
Figma question answers:
- 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.
- Yes, the current dev handoff is final and up to date.
- 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
10/24/2024
- [x] Roja
- [x] Ida - not present
- [x] Ryan - not present
- [x] Bitian - not present
- [x] Terence
Agenda
- [x] Backend - Created DB schema model
- [x] Frontend - any updates about sass+tailwind story
Bitian - github action story
- should be ready to close
11/07/2024
- [x] Bitian
- [x] Roja - not present
- [x] Ida - not present
- [x] Ryan
- [x] 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
- [x] December break
- [x] 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
developintomain - Aim to deploy a staging environment to AWS by next week.
- Aim to finish developing API server by the end of the month
11/14/2024
- [x] Bitian
- [x] Roja - not present
- [x] Ida - not present
- [x] Ryan
- [x] 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
11/21/2024
- [x] Roja - not here
- [x] Ida - not here
- [x] Bitian
- [x] Ryan
- [x] Terence
Karen needs to know:
- [x] Our dev meeting schedule in December. What do you guys wanna do?
- [x] What is a good first day to meet in January?
Agenda
- [x] Next week dev meeting is on thanksgiving. Lets move it to another day?
- [x] 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
- deployment pipelines
- API server
- 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
developintomain - catch up on writing documentation
12/05/2024
- [x] Roja - not here
- [x] Ida - not here
- [x] Bitian
- [x] Ryan
- [x] Terence
Bitian
- Finished first part of django models
- django has a built in user model - use django auth features
- For the staging database django super admin, each dev will have to make our own credentials.
- Bitian to work on the rest of the django models this week
- Bonnie requirement: Time availability needs to be in the user's local time
Ryan
- Started writing Terraform
- Terraform is best for managing the Infrastructure components themselves
- stable infrastructure that doesnt need to change often: eg. ECR, ECS task definitions, Firewall, etc.
- the container should be built and deployed in CI/CD pipeline (github action)
- Incubator deployment is still blocked by VRMS - they have one guy working on it
- We should have a local database that we as devs can use to test changes
Terence
- merged develop into main
- Terence to work on writing documentation
- Terence to work on finishing up basics of API server
- Ask Karen for 3 frontend developers in January
12/12/2024
- [ ] Bitian
- [x] Ryan
- [x] Terence
Agenda
- Last meeting this month. Meet again January 9th 2025
- Ask Bitian if her dev env works -
CustomUseris causing issues with the django migration and everyone might need to reset their docker environments from scratch - Everyone is going to manually fix it on their own machines. Only effects current members. New members not effected. Steps below.
Bitian
- Finished the rest of the models
Ryan
- Almost finished with first stage of Terraform, github actions on personal fork and personal AWS
- ideal scenario: simple transition to incubator AWS account
- You can make a change in
/CivicTechJobs/frontend/src/pages/LandingPage/LandingPageIntro.tsx - meeting with Trillium about VRMS next week
- no AWS Cognito pool set up yet
- Assigned to Devops Epic 585
Terence
- Wrote docs about different branches, github branching flow
- mkdocs deploys from the
mainbranch now - Terence to write a doc about how the stage env works by end of December
- Work on fixing the react lazy loading issue
- Initiated API server
Steps to fix CustomUser migration issue:
- Deleted
civic-tech-jobs-djangodocker container + image - emptied
civic-tech-jobs_postgres_datadocker volume - disabled django admin by commenting it out in
settings.pyandurls.py - ran
docker compose upagain to rerun django migrations script- the migration scripts create a new database migration from scratch
- checked that it works without admin by going to
http://localhost:8000/api/healthcheck: ✅ - stopped docker dev env with
CTRL+C - enabled django admin
- Deleted
civic-tech-jobs-djangodocker container + image - ran
docker compose upagain to rerun django migrations script- This time, it migrates the admin app
- checked that it works with admin by going to
localhost:8000/admin/url: ✅- but my old admin username and password dont work
- Created new admin username and password by exec'ing into the django container and running
python manage.py createsuperuser
Now docker dev environment works again
- But I think everyone will have to do this with their personal docker environments
01/09/2025
- [x] Bitian
- [x] Ryan
- [x] Terence
- [x] Ida
Agenda
- Personal goals
- Go over roadmap
Terence
- Touch base with Design team to see what progress they are on for the qualifiers pages.
- What exactly is changing in the qualifiers pages? So we know what to expect
- Is the design system changing - individual components - eg buttons, colors, etc. before we migrate from sass to tailwind. We can prioritize which components to migrate to tailwind depending on what they want to change or keep the same.
- Terence to prioritize writing all the technical documentation by this weekend
Ryan
- Continue to work on terraform
- get an update from devops
Ida
- work on eslint errors
- Question: expected release date/timeline for MVP-1?
Bitian
- Start writing some unit tests
01/16/2025
- [x] Bitian
- [x] Ryan
- [x] Ida
- [x] Roja
- [x] Terence
Agenda
- Go over roadmap, prioritize tasks
- Everyone able to start their dev environments?
- Any blockers?
Terence
- Finished documenting backend architecture, dev environment, stage environment, python linter.
- Had meeting with Leads
- PM: Karen, Nooria and I to work on timeline for MVP-1.
- PM: Karen can elevate deployment priorities to Bonnie if necessary.
- Design: Lu to update us about a date when Qualifiers page designs will be finalized after her meeting this Friday. Current status is they finished this round of user testing, Lu needs to redesign and possibly do another round of user testing. So I expect it to be ready within a month.
- Design: Design system has been reorganized and is up to date. We can migrate most components to tailwind without issue. More details here: https://github.com/hackforla/CivicTechJobs/issues/606
- Question: What exactly is changing in the qualifiers pages?
- Its going to be three pages: (1) Select CoP and Role. (2) Select skills aka skills matrix. (3) Availability Calendar.
- Design team is working specifically on the skills matrix page right now.
Terence
- to confirm with design team about if landing page and other pages will change.
- to learn more about incubator and terraform deployment
Bitian
- started a pull request for unit tests
Ryan
- continuing to work on incubator and devops and terraform
- Devops is deploying people depot to iron out the kinks in the process
Ida
- worked on eslint errors
Roja
- continue working on migrate sass components to tailwind
01/23/2025
- [x] Bitian
- [x] Ryan
- [ ] Ida
- [ ] Roja
- [x] Terence
Agenda
- Lu and Rishi want to meet up with the dev team to ask questions about the design. What time are you all free to do it this coming week?
- ask lu and rishi if monday or tuesday at 5pm works for them
- Any blockers?
Terence
- review Bitians PRs the next 2-3 days
Bitian
- first PR about tests - returned something unexpected
- second PR - corrects one of the failed tests
- start working on some tailwind components
Ryan
- still doing terraform stuff
- in devops, working on IAM system for AWS incubator account
02/13/2025
- [x] Bitian
- [ ] Ryan
- [x] Terence
Move dev meetings to monday at 5pm. Next meeting monday 2/24
Terence
- update calendar with new dev meeting time
Bitian
- going to keep working on tailwind PR
Ryan
- People depot is up on incubator now, but not quite working yet
- We are next in queue
- Terence and Ryan to meet with Alex English to talk about incubator deployment on monday