Dependency

• #25

Overview

As a developer, we need to agree on an organized architecture so that files are easy to find and edit. For this issue, we will draft a proposal for the Frontend, which houses our components, pages, and associated code, before creating documentation on our wiki for it.

Action Items

• Draft a tentative proposal to prepare for the landing page
• The architecture must be be organized such that:
  • Files and components are easy to find
  • The names are intuitive
  • It is scalable without breaking
  • Can be easily changed, should whole directories need to be moved
• When a draft in done, review it with the team, and at the end of the discussion, check that all points above are fulfilled.
• Create a new wiki with an appropriate title
• For each directory in the main directory, list out what the directory is for, and comment on how it contribute to our backend
• For each subdirectory, do the same
• Make sure the wiki is well organized and easy to read
• Release dependency on:
  • #62
  • #63
  • #69
  • #70
  • #71
  • #72

Resources/Instructions

Sample wiki from another project

Dependency

• #168
• #170
• #172

Overview

As a designer, we need a design system to lay out standards and share with the dev team so they can build the website. We need to start creating components with states.

Action Items

• Create components and states
• Discuss with dev team
• Figure out best breakpoints
• Discuss design system framework & best practices with HfLA's Design System team
• Update design system to adhere to framework & best practices above

Resources/Instructions

Reference HfLA's design system framework (once they complete it)

Dependency

• #25

Overview

As a developer, we need to give guidance to future developers on how to set up their environment and contribute to our project. For this issue, we will write a contributing.md file for developers.

Action Items

• If it does not already exist, create a file called contributing.md in the root directory
• In this file, write out steps to set up the development environment and links to key getting started documentation in our wiki
• Release dependency on #2

Resources/Instructions

Sample contributing.md from another project

Civic Tech Jobs Contributing file https://github.com/hackforla/CivicTechJobs/blob/main/CONTRIBUTING.md

Overview

We need more volunteers to work on the project so that we can accomplish our action items.

Action Items

• Post on roles board
• Successfully recruit 2 UX Designers
• Successfully recruit 1 UX Researcher

Dependency

• #49
• #18

Not dependent, but highly recommended

If there is info that is not correct on this page, it will waste new volunteer time. Its not hard to fill out the basic wiki, just get it done.

• #19

Overview

we need to gather additional information to complete the issue to add civic tech jobs to the hackforLA website so that there is more visibility for the project and users can get additional information about the project,

Action Items

• Gather the following items
  • Any resources for a Getting Started link (a link to a wiki, readme(s) or both):
    • Wiki: #19
    • readme or contributing doc #49
    • Overview (#18 ): Completed PDF One Sheet
  • link to hero image 1500x700 (https://drive.google.com/file/d/1fCbocnGqLuw2fkKeAi3Ke0UVFo3qXaqE/view?usp=sharing)
  • link to logo on a image 600x400 (https://drive.google.com/file/d/17nWwqWpc4wA5atUMfN_EtJ6SUUwX_oar/view?usp=sharing)
  • a blurb about the project (see following blurb below)

The CivicTechJobs.org MVP website will be a platform to help prospective volunteers find inter disciplinary projects that will be useful for their career development while contributing to positive civic impact and a CMS for Hack for LA projects to be able to list their open roles.
The tool will match volunteers by availability, role, and program area. Future iterations of the platform will focus helping volunteers find volunteer opportunities that match paid job postings, so that a volunteer can better prepare themselves for the marketplace.

• ask bonnie to release the dependency on hackforla/website#2287

Resources

One sheet: https://github.com/hackforla/product-management/blob/master/project-one-sheets/Civic-Tech-Jobs-One-Sheet.pdf

We need a Hero image for CivicTechJobs which will be displayed as the backdrop on the project card on the HackforLA website. this should be independant of the logo but also embody the project

Action Items

• Hero image ()

Resources
https://www.hackforla.org/projects/ballot-nav (see backdrop of ballotnav)

Size requirement
1500 x 700

Overview

Create onesheet document for civictechjobs so that it can be shared with management team, stakeholder, and funders.

Action Items

• Check to confirm project does not already have a one sheet
• Make a copy of the one sheet template and store in the product management google drive/one sheet revisions
• Review one sheet and check off items on the checklist to see what it might be missing.
• Setup a meeting with the PM to go over the project to confirm what information on the sheet is up to date and what needs revision.

Checklist

• Include project logo (top right)
• Overview
• History and or last 6 months
• Partners
• Roadmap/next 6 months
• Contact email (footer)
• Github URL (footer)
• Link to project page on hackforla.org (footer)
• Slack channel (footer)
• Last updated date (footer)
• Hack for LA logo (bottom right)

Resources/Instructions

Check issue #3 for sample one sheets
One Sheet Template

Overview

We need accurate information about all team's meetings so that we can design a system that will allow potential volunteers to filter the roles by teams that meet when its convenient for them.

Action Items

• provide details about the each meeting in a comment by using a copy of the check boxes below
• post a link to this issue on Survey all the teams in order to build an effective data model #35 in a comment letting the civic tech jobs team know you are done.

Resources/Instructions

- [ ] day
- [ ] start_time
  - [ ] AM
  - [ ] PM
- [ ] duration_in_min
- [ ] name_of_meeting
- [ ] who_must_attend
  - [ ] pm
  - [ ] all_leads
  - [ ] design_lead
  - [ ] research_lead
  - [ ] frontend lead
  - [ ] data_science_lead
  - [ ] design
  - [ ] research
  - [ ] frontend
  - [ ] backend
  - [ ] data_science
  - [ ] other: please explain
- [ ] who_should_attend
  - [ ] pm
  - [ ] all_leads
  - [ ] design_lead
  - [ ] research_lead
  - [ ] frontend lead
  - [ ] data_science_lead
  - [ ] design
  - [ ] research
  - [ ] frontend
  - [ ] backend
  - [ ] data_science
  - [ ] other: please explain
- [ ] who_can_attend
  - [ ] pm
  - [ ] all_leads
  - [ ] design_lead
  - [ ] research_lead
  - [ ] frontend lead
  - [ ] data_science_lead
  - [ ] design
  - [ ] research
  - [ ] frontend
  - [ ] backend
  - [ ] data_science
  - [ ] other: please explain

Dependency

• #26

Overview

As a developer, we need to be prepared for when projects come in. For this issue, we will initialize the project to create the scaffolding needed to begin front and back end work.

Action Items

• Initiate the app with docker, which is configured to django.
• Set up the frontend/backend directories
• Add a JSX preprocessor (rather than use create-react-app or the cnd) as this is determined to be the preferred front-backend interface by @Aveline-art and @arghmatey
• Create a test front page
  • This page should have at least one line to text, just so we know that visually, everything is set up correctly.
• Release dependency on:
  • #48
  • #49
  • #50
• When releasing dependencies, be sure to look over those issues and update any action items or resources with additional information that arisen from working with this issue

Resources/Instructions

Quickstart: Compose and Django
Add JSX to a Project
schema
related comment #1
related comment #2

Overview
We need to design the webpages for civictechjobs.org so that a user (potential volunteer) can easily search for a volunteer opportunity that fits their skills or aspirations.

Resources/Instructions
https://www.figma.com/file/G5bOqhud6azbxyR9El9Ygp/Civic-Tech-Jobs?node-id=1%3A7

Overview

Get Social Media accounts for CivicTechJobs

Action Items

• Twitter
• LinkedIn
• Instagram
• Facebook

Resources/Instructions

Overview

As a developer, we need to ensure that this project is properly setup such that developers can come in and pick up the work and our data is protected. For this issue we will be researching the best ways to set up our environment.

Action Items

• Find a solution for hiding the database and other sensitive secret keys when uploading to GitHub
• Find a solution for linking our repo to AWS
  • Find out what the AWS requirements are, and the best way for the team to meet these requirements.
• Find a solution to changing the debug and other settings back to their previous configurations when in development vs production on hold until we are ready for deployment
• Release dependency on #25

Resources/Instructions

Questions to consider before AWS deployment:

• Is our gain from deployment worth the cost of AWS? If not, what do we still need to do before we can deploy?

Overview

We need to define and list out tasks and dependencies to complete the MVP so that we can identify issues to make and that the team can understand the definition of done for the landing page MVP and follow up on the progress.

MVP: Fully developed front landing page with a clickable link to join Hack for LA in order to be eligible to see the list of open volunteer opportunities. The link leads to the meetup link for joining onboarding meeting.

Action Items

List of Issues that need to be covered

• Landing Page UX/UI Design
• Copywriting
• Org sign off on copy writing and design
• Frontend and Backend Development
• Go Live

Resources:
Civic Tech Jobs Roadmap

Meetup link

https://meetup.com/hackforla/events

Examples

• Open Community Survey
  • OCS Roadmap issue: hackforla/open-community-survey#43
  • Open Community Survey Roadmap

Overview

As a potential volunteer I should be able to search for open volunteer positions at hackforla so that I can find the right match for my interest and aspirations.

Action Items

• Create self-filter (qualifier page)
• Create UX/UI design for the search page
• Search page to have other filters for Project, Program Area, and technologies
• Usability testing to validate ease of use, understanding of the terms mentioned on the page

Resources/Instructions

Refer to the Requirements Document: https://docs.google.com/spreadsheets/d/1VcDLJnDA5CE7euzaZxOcqS3LLgyUFVLeqvdZx2sFGQk/edit#gid=804221697

Overview

As a designer we need to ensure the website is responsive and designed for the most used devices ex. desktop, mobile, etc.
We need a mobile design version of the landing page.

Action Items

• Decide on device frame size: 375 x 812
• Design mobile version
• Figure out best breakpoints between devices

Resources/Instructions

Link to design page in file:
https://www.figma.com/file/G5bOqhud6azbxyR9El9Ygp/Civic-Tech-Jobs?node-id=1%3A7

Responsive design breakpoints:
https://getbootstrap.com/docs/5.0/layout/breakpoints/
https://kinsta.com/blog/responsive-web-design/

We need to define our north star metrics as well as KPI's for MVP so that we understand how these factors will affect our next steps of the product.

Dependency

• #94
• #179

Action items (we need answers to the following questions)

• How will we know that users are finding value from CTJ
• what KPI's do we need to include on the landing page and search page to understand where users are concentrating their actions

Overview

We need to create a wireframe design for the landing page of civictechjobs.org so that we can establish the look and feel of the website when arrived on

Action Items

• Landing page search bar
• LOGO placement
• filters list

Resources

Existing Figma (https://www.figma.com/file/0RRPy1Ph7HafI3qOITg0Mr/Hack-for-LA-Website?node-id=5326%3A26395)

We need a hero image/illustration for CivicTechJobs landing page that attracts users and communicates inclusivity and collaboration.

Action Items:

• Hero image/illustration options
• Survey or A/B test options
• Once hero image chosen, add credit here: https://www.hackforla.org/credits/

Dependency

• #13
• hackforla/VRMS#761
• hackforla/VRMS#765

Note for VRMS team: Release a dependency means that once all the issues you see above are closed, this issue can move from the "Ice Box" to "Prioritized Backlog". If not all of them are closed yet, check off the issues that are closed.

Overview

As a developer, we need to always update our technologies for better integration. For this issue, we will discuss how we will integrate the VRMS models into our project.

Action Items

• Set up a developer meeting to discuss how to migrate our project to using models from VRMS.
• Create new issues to transition the migration.

Resources/Instructions

None so far.

Overview

We need a logo for the project so that we can appear on the hackforla.org homepage and recruit. The logo should encourage people to use our application to find civic jobs

Action Items

• Identify values and other properties that will help us understand if the logo design meets requirements
• UX team to create a logo for the new civictechjobs.org

Resources/Instructions

Figma

Overview

We need a C & C analysis on CMSs from orgs that recruit volunteers so that we know what features we might need outside of what we have already identified as our current project managers' needs. This issue looks at the process for how volunteer opportunities are posted.

Action items

• Identify the orgs
• Collect the features including screen shots of their cms

Resources/Instructions

C& C template

CTJ C&C Analysis

List of orgs

Volunteer Match
Idealist
benefit.design
Catchfire
Allforgood.org
Golden Volunteer Organization
Deed
GivingWay

Criteria evaluated on

Able to create account to test out uploading of volunteer opps?
Where

Overview

Provide collateral for the HackforLA website

Action Items

• Gather items
  • 600 x 400 image
    • Alt image text
  • 1500 x 700 hero image (please do not put project title on hero image)
    • Alt image text
  • Name of project
  • A blurb about your project
  • Links (github, slack channel url, Testing Site, Live Site, etc.)
  • Any resources for a Getting Started link (a link to a wiki, readme(s) or both)
  • What you are looking for skills wise
  • Partner(s)
  • Location
  • Status
• Add project Card to website

Resources/Instructions

See project cards on the hackforla.org website for examples

Dependency

• #35

Overview

We need to determine which team members are required to attend which HfLA project team meetings, so that we can create a more accurate project team meetings filter for the upcoming Volunteer Opportunities page.

Action Items

• Review team meetings spreadsheet (based on Events page schedule) - same colors for same teams; question marks for unclear required attendees
• Add 2 new columns: required and invited/welcome
• Reach out to the PM(s) of each team on slack to verify:
  • Which roles their project meetings are for
  • Whether these meetings are "required" or "invited/welcome" (and for which roles, if relevant)

Resources/Instructions

Team meeting spreadsheet

Events page schedule

Upcoming Volunteer Opportunities page

Overview

This issue tracks the agenda for our weekly meetings

Issue Template

## [Date ]  Meeting Agenda

### Prework to prep for meeting
- [ ] #

### Recurring items: Happens on the ________ meeting
 - [ ] review any issues that are in the [new issue approval column]
 - [ ] Accountability and Support Check.
    - [ ] Review assignments for each Team member
       - [ ] [Lu](https://github.com/hackforla/CivicTechJobs/issues/assigned/fenglugithub) - UX/UI Designer Lead
       - [ ] [Armando](https://github.com/hackforla/CivicTechJobs/issues/assigned/stanarmon) - UX/UI Designer
       - [ ] [Carmen](https://github.com/hackforla/CivicTechJobs/issues/assigned/CarmenMM1) - UX/UI Designer
       - [ ] [Brenda](https://github.com/hackforla/CivicTechJobs/issues/assigned/brendasdesign) - UX/UI Designer
       - [ ] [Karen](https://github.com/hackforla/CivicTechJobs/issues/assigned/kcoronel) - Senior Advisor
       - [ ] [Kanika](https://github.com/hackforla/CivicTechJobs/issues/assigned/kchotani) - Product Manager
       - [ ] [Manju](https://github.com/hackforla/CivicTechJobs/issues/assigned/itsmanjuchawla) - UX/UI Research
       - [ ] [Leah](https://github.com/hackforla/CivicTechJobs/issues/assigned/Leah0996) - UX/UI Researcher
       - [ ] [Xiaotian Vivian Li](https://github.com/hackforla/CivicTechJobs/issues/assigned/xxl228) - UX/UI Research Lead
       - [ ] [Bitian](https://github.com/hackforla/CivicTechJobs/issues/assigned/bzzz-coding) - Dev. Co-lead
       - [ ] [Jimmy](https://github.com/hackforla/CivicTechJobs/issues/assigned/JimmyJuarez10) - Dev. Co-lead
       - [ ] [Benny](https://github.com/hackforla/CivicTechJobs/issues/assigned/bennyv8) - Developer

- [ ] finish adding labels to the issue that are still missing them (see audit links above)
- [ ] review issues with [epic label] and define how to break down further
- [ ] Review to see if there are any members to Onboard or Offboard 
      - [ ]  #

### New Items
- [ ] 
- [ ] Carry over Items to next meeting that don't get addressed

### FYIs
-

### Notes from Meeting

### Task Items      

Links to other agenda issues for your team

(so that you can easily post on their agendas items that come up at yours)

Previous Meetings (link to each comment with the date)

2021

06/22/21
09/07/21
09/14/21
09/19/21
09/28/21
10/12/21
10/19/21
11/02/21
11/09/21
11/16/21
11/30/21
12/07/21
12/14/21

2022

01/04/22
01/11/22
01/18/22
01/25/22
02/01/22
02/08/22
02/15/22
02/22/22
03/01/22
03/08/22
03/15/22
03/29/22
04/05/22
04/12/22
04/19/22
04/26/22
05/17/22
05/31/22
06/14/22
07/12/22
Notes from 07/12/22 meeting
07/19/22
07/26/22
08/09/22
08/16/22
08/30/22
09/13/22
10/04/22
11/8/22

2023

01/17/23
02/07/23
02/14/23
02/21/23
02/28/23
3/7/23
3/21/23
3/28/23
4/11/23
4/18/23
4/25/23
5/2/23
5/9/23
5/16/23
5/23/23
5/30/23
[6/6/23)[Leads Meeting]
[6/13/23](Meeting Cancelled)
6/20/23 - didn't take place
7/11/23
7/18/23
7/25/23
8/08/23
8/22/23
8/28/23
[9/12/23][https://github.com//issues/16#issuecomment-1716718490]
9/18/23
10/02/23
2023/10/10

Overview

We would like to use Django as back-end and React as front-end for our site architecture. This issue was created to store any key points discussed on this topic.

Action Items

• Research if it is feasible connecting a Django back-end to a React front-end

Resources/Instructions

Any helpful articles or links regarding this can be put here.

Overview
We need to design the webpages for civictechjobs.org so that a user (potential volunteer) can easily search for a volunteer opportunity that fits their skills or aspirations.

Resources/Instructions
https://www.figma.com/file/G5bOqhud6azbxyR9El9Ygp/Civic-Tech-Jobs?node-id=1%3A7

We need a SHORT blurb/copy to go with the hero image on the CivicTechJobs' landing page.

It must communicate:
-our value proposition
-the value of them, the volunteers... that our work is thanks to the power of volunteers

Action Items:

• draft blurb
• run it by someone (like Bonnie)

Resources:
https://www.hackforla.org/

Dependency

• On the date when development is ready to begin.

Overview

As a developer on this project, before we work, we need to know what the MVP requirements are, in terms of development. In this issue, we are translating MVP requirements into developer lingo and turning them into issues, if possible.

Current Action Items

• Collect all front-end requirements on Future Action Items below
• Once development is ready to begin, review all front-end requirements to ensure that changes are not needed
• Divide the action items into actionable issues.

Future Action Items

• See the below items and turn them into issues, if possible. (Note: a number of these can be parts of other issues, or as part of an MVP audit).
• It needs to have analytics, perhaps google?
• Landing page with link to GitHub
• Some way to log stats for clicks and other information. Maybe outside library?

Resources/Instructions

REPLACE THIS TEXT -If there is a website which has documentation that helps with this issue provide the link(s) here.

Overview

This issue tracks the agenda for the CivicTechJobs team and weekly roll call.

Action Items

• Designate a note taker
• Make announcements
• Do below agenda items

Weekly Agenda Markdown

### Agenda for monthAsText dd, yyyy

- [ ] writeYourNotesHere

### Post-meeting notes, monthAsText dd, yyyy

<details>
<summary>Title</summary>
<br>

insertNotesHere

<br>
</details>

Akib, and Sarah to create system design documentation for the civictechjobs.org website

Based on the C&C analysis, we need to understand and decide which features are must haves, should haves and could haves so that the modules can be developed and designed accordingly

Resources

#12 - C&C Analysis

Overview
We need to design the webpages for civictechjobs.org so that a user (potential volunteer) can easily search for a volunteer opportunity that fits their skills or aspirations.

Resources/Instructions
https://www.figma.com/file/G5bOqhud6azbxyR9El9Ygp/Civic-Tech-Jobs?node-id=1%3A7

Overview

We need to determine what data we will require and who will consume it so that we can get signoff from stakeholders and setup the wireframing team for success.

Action Items

• Create our database schema.
• After creating the schema, get sign off from:
  • Stakeholders who will be using this
  • Our team, who will be managing this, and using this to speak with stakeholders
• Once sign off is done, create issues in peoplesDepot for them to incorporate the model
• Release dependency on #40

Resources/Instructions

Current tentative schema

Overview

We need to perform a weekly check on issues to make sure they all conform to our label and milestone schema.

Action Items

• Check the following to make sure that they are all 0/0 (Links for checking to make sure that all issues either have a ___ or a ____ missing label)
  • Role
  • Size
  • Feature
  • Milestone
    • Add any label missing (e.g., a new feature label go added to the project, but didn't yet get added here) and update link
  • issues that have not yet been added to project board
    • add to project board
• if changes were made, recheck to make sure all links ended up 0/0
• Audit for issues with Missing labels (to determine if we are making progress)
  • Copy this audit report format to a comment below

Date: 
- [ ] Did you have to update the 0/0 links above?  if yes, please say what you did (e.g, Added features to the features check above or added an issue to the project board that has not been added yet).
- [ ] Report what the numbers are on issues that are missing labels (e.g., size, ending at 12/5)
   - [ ] role, ending at
   - [ ] size, ending at
   - [ ] features, ending at
   - [ ] milestone, ending at
   - [ ] items in icebox with no dependency
   - [ ] issues not on the project board 0/0

• perform audit, adding your numbers to your audit report comment
  • Role
  • size
  • feature
  • milestone
  • Icebox with no dependency
  • Not on project board

We need to collect or create CoP descriptions to include under the landing page so that users who come to civictechjobs.org can get additional information about what we offer

Overview

We need to use the wiki template that other projects are using so that when people move between projects they can find stuff and also because it's easier to know what you need.

Action Items

• Clone current wiki to ensure no data is lost
• Copy template wiki to project wiki

Resources/Instructions

#7
draft guide for copying the template wiki

We need to conduct a preference test for the landing page to choose one of the three final designs. Once we have the final visual design chosen, we can proceed to usability testing different copy length versions.

Action Items:

• write up a research plan
• create preference test w/ questions at the end
• create 3 different versions of the survey
• randomize the survey version that participants see and post to the #general slack channel
• analyze survey results
• choose visual design based on results
• choose final landing page design from different copy length options

Resources:

3 design options to test "Final Design Options V4"
https://www.figma.com/file/G5bOqhud6azbxyR9El9Ygp/Civic-Tech-Jobs?node-id=1%3A7

Usabilityhub Preference test results

Dependency

• #54

Developer Dependency:

• #49

Overview

We want people who come to our repo to be able to find what they need quickly by reading our README.md file

Action Items

For Product:

• Get draft from #54
• see example from Guides team wiki
• Edit the civic tech jobs readme file
• Add link to one sheet
• Make a list of the civic job boards we know about and add it to the readme (see the VRMS link below)

For Developer:

• Complete the installation instruction portion of the README.md
• Consult with development on whether the instructions appears correct
• Return this back to the Prioritized backlog, replacing the 'role: backend' label with 'role: product'

Resources

https://github.com/hackforla/guides/blob/main/README.md
https://github.com/hackforla/CivicTechJobs/blob/main/README.md
VRMS JobBoard Research

Overview

As a developer, we need to have a roadmap for how to implement a new page. For this issue we will examine the design of the landing page, and figure out how to create this page in an organized way so that we make sure the code is as reusable as possible.

Action Items

• Create one issue per component on the page, if the component is not already created
  • Beyond some functional components, be sure to also standardize title sizes and color scss names
• Separate the page into multiple pieces and make issues out of them

Resources/Instructions

Figma for the landing page

Overview
We need to design the webpages for civictechjobs.org so that a user (potential volunteer) can easily search for a volunteer opportunity that fits their skills or aspirations.

Resources/Instructions
https://www.figma.com/file/G5bOqhud6azbxyR9El9Ygp/Civic-Tech-Jobs?node-id=1%3A7

Overview

Upload the discussion about the requirements and the MVP so that the team can watch the video and learn about the feature and design requirements for the product (civictechjobs.org)

Action Items

Bonnie to upload the recording of the discussion with Sharad and Danish. Meeting date Sunday, August 29

Resources/Instructions

Zoom meeting recording

Overview

We need figma for this project so that we keep all our designs in one place and work collaboratively

Action Items

• create vault for civic tech jobs
• create vault of ctj - design
• copy figma account from org to new vault
• add team members who need access to figma to ctj - design
• copy email accounts to cti-design vault

Resources/Instructions

Overview

Gather requirements for the Content Management System (CMS) so that the team can understand the scope of work needed to create the system.

Action Items

• Set up meeting with Bonnie
• Record the meeting and upload it in the civictechjobs google drive
• Create a CMS requirements document and share with the team

Dependency

• MVP live to usability test with users

Overview

We need to conduct a usability test for the LIVE MVP to receive feedback from the users, note insights and usability issues, and prioritize and make necessary improvements.

Action Items

• Decide on the user flow(s) to be tested
• Write down the tasks that will be given to the users
• Prepare the usability test on usabilityhub.com
• Pilot the test with a team member
• Decide on recruitment method of users for testing (i.e. Hack for LA volunteers, new volunteers who are being onboarded, recruiting from Usability Hub; have Bonnie review the recruiting message in advance)
• Gather data from the users
• Analyze results and prepare a slide deck
• Present findings to the team

Resources:

https://usabilityhub.com/

Overview

Team will work towards creating civictechjobs.org as the main product

Discussion Points

1. The job postings will also be delivered to the hackforla website using an Iframe
2. We will design a new UX for civictechjobs.org website, starting with a new logo
3. Ingrid, and Cherri will discuss with Danielle on any color schema guidelines/guardrails for the new website
4. Akib, and Sarah will help us create documentation for the site structure (Architecture)
5. Sharad. and Danish will start creating kanban cards on the gthub project to get started with the development process

Overview

We need a google form to get input from the team regarding the top Logo designs thus far to move forward with so that we can finalize our logo design and color scheme

Action Items

• Google form ( https://forms.gle/r9jenNSzW8X8SoXn8 )

Resources/Instructions

Logo Issue (#8)

Overview

Update the wiki for the Civictechjobs project so that management, stakeholders, and team members can get a snapshot of the project.

Action Items

• Project definition
• Intro to the project
  • See: #54
• Guiding Objectives
• Project one sheet
• Update selected tech stack
• Joining the team (and links that lead away from that page)
• The Team
• our process

Resources/Instructions

• hackforla/product-management#128
• Examples of good wiki:
  • civictechindex
  • 100 Automations

Civic Tech Jobs wiki

Dependency

• #285
• #289

Overview

We need to design a search page with filters so that a user (potential volunteer) can easily find a volunteer opportunity that fits their skills or aspirations.

Action items

• Ideate in hi-fi
• Present to design team
• Iterate
• Present to all team
• Iterate to design final
• Handoff to Devs

Resources/Instructions

Requirements

Dependency

• #25

Overview

As a developer, we need to create an environment that will ease development as well as provide users a seamless experience when using our website. For this issue we will configure webpack with several improvements that will improve the overall quality of our project.

Action Items

• Change webpack config to have the follow improvements. If they already exist, be sure to check them off
  • Production environment
  • Sass loaders
  • Babel loaders
  • HtmlWebpackPlugin
  • Minifying
  • Tree Shaking
  • SVG and other image extensions management
• Release #190

Resources/Instructions

Webpack Concepts
Webpack Configuration
Webpack Guides
Webpack Loaders

Overview

We need accurate information about each team's meetings so that we can design a system that will allow potential volunteers to filter the roles by teams that meet when its convenient for them.

Action Items

• Create a template
  • Draft template (#35 (comment))
  • Add label for template (feature: project meeting check)
  • Add template to repository
• List all teams under resources (with check boxes)
  • Make issue for each team to gather data about that team's meetings and get any corrections to what currently appears. Use the template below

Resources/Instructions

• 100 Automations 100Automations/Website#460

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/100-automations
  • Meeting times:
    • Thursday 5:00 pm, 1 hour
    • Saturday 2:00 pm, 2 hours

• 311 Data hackforla/311-data#1129

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/311-data
  • Meeting times:
    • Thu 7:30 pm, 1 hour, Management Meeting
    • Thu 6:30 pm, 1 hour, Team Meeting
    • Thu 6:00 pm, 30 min, Data science meeting

• Access the Data hackforla/access-the-data#71

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/access-the-data
  • Meeting tines:
    • none currently specified

• BallotNav hackforla/ballotnav#436

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/ballot-nav
  • Meeting times:
    • Tue 6:00 pm, 1 hour

• Brigade Organizer's Playbook

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/brigade-organizers-playbook
  • Meeting times:
    • Sat 11:00 am, 2 hour, Core Team (needs to be changed)
    • Tue 10:00 am, 1 hour, Core Team

• Civic Tech Index civictechindex/CTI-website-frontend#879

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/civic-tech-index
  • Meeting times:
    • Thu 6:00 pm, 1 hour, Team Meeting
    • Mon 6:00 pm, 2 hour, Team Meeting
    • Wed 12:30 pm, 1 hour, Product Managers Meeting

• Engage hackla-engage/start-here#25

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/engage
  • Meeting times:
    • Tue 6:00 pm, 1 hour, All Team Members
    • Wed 5:00 pm, 1 hour, Product Manager Meeting
    • Sun 4:00 pm, 1 hour, All Team Members

• Expunge Assist hackforla/expunge-assist#340

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/expunge-assist
  • Meeting times:
    • Mon 6:00 pm, 1 hour, Team meeting on 1st & 3rd Mondays/PM on all other Mondays
    • Tue 6:00 pm, 1 hour, Research & Design meeting
    • Thu 6:00 pm, 1 hour, Dev meeting

• Food Oasis hackforla/food-oasis#1034

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/food-oasis
  • Meeting times:
    • Tue 6:30 pm, 1 hour, Development
    • Thu 6:00 pm, 1 hour, Team
    • Mon 3:00 pm, 1 hour, Management

• GreenEarthOS hackforla/GreenEarthOS#77

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/green-earth-os
  • Meeting times:
    • Wed 7:00 pm, 1 hour, Team Meeting

• HomeUniteUs hackforla/HomeUniteUs#342

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/home-unite-us
  • Meeting times:
  • Product Management, Tuesday 6:00pm, 1 hour
  • All Team Meeting, Every Other Tuesday 7pm, 1 hour
  • Design Meeting, Every Other Tuesday 7pm, 1 hour
  • Product Owner Meeting, Friday 4pm, 1 hour

• Lucky Parking hackforla/lucky-parking#303

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/lucky-parking
  • Meeting times:
    • Mon 6:00 pm, 1 hour, Team Meeting

• Open Community Survey hackforla/open-community-survey#45

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/open-community-survey
  • Meeting times:
    • Mon 12:00 pm, 1 hour, Team Meeting

• TDM Calculator hackforla/tdm-calculator#960

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/tdm-calculator
  • Meeting times:
    • Wed 7:00 pm, 1.5 hours
    • Sat 10:00 am, 2 hours

• VRMS hackforla/VRMS#768

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/vrms
  • Meeting times:
    • Mon 7:00 pm, 2 hour
    • Thu 6:30 pm , 1 hour, Developers' Meeting

• HackforLA.org website

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/website
  • Meeting times:
    • Sun 10:00 am, 2 hours, All Team Meeting
    • Tue 7:00 pm, 1 hour, Development Team
    • Wed 12:00 pm, 1 hour, PM Meeting
    • Thu 5:00 pm, 1 hour, UI-UX Meeting
    • Thu 7:00 pm, 1 hour, Back-end Meeting

• Youth Justice Nav

  • URL of the project's homepage on the HfLA website: https://www.hackforla.org/projects/youthjusticenav
  • Meeting times:
    • Wed 7:00 pm, 1 hour, Team Meeting
    • Fri 3:00 pm, 1 hour, Team Meeting

• Design Systems hackforla/design-systems#105

  • URL of the project's homepage on the HfLA website: none yet
  • Meeting times:
    • none currently recorded

• Guides

  • URL of the project's homepage on the HfLA website: hackforla/website#2289
  • Meeting times (not currently on the website):
    • Monday, 7:30 AM, 1hour, Meeting
    • Monday, 8:30 AM, 30 min, PM and Developer meeting
    • Wednesday, 8:30, 1hour, Meeting
    • Wednesday, 8:30 AM, 30 min, PM and Developer meeting
    • Friday, 8:30 AM, , 1hour, Meeting
    • Friday, 8:30 AM, 30 min, PM and Developer meeting

• Internship

  • URL of the project's homepage on the HfLA website: hackforla/website#2288
  • Meeting times:
    • none currently recorded

• Civic Tech Jobs

  • URL of the project's homepage on the HfLA website: hackforla/website#2287
  • Meeting times (not currently on the website):
    • Tuesday 5pm, 1 hour, All team meeting
    • Sundays, 12pm, 1 hour, PM and management meeting
    • Sundays, 10am, 1 hour, PM meeting
    • Tuesday 6pm, 1 hour, Developers meeting
    • Tuesday 6pm, 1 hour, UI/UX Meeting

• Data Science Projects

  • URL of the project's homepage on the HfLA website: none yet
  • Meeting times:
    • none currently recorded