Skip to content

Meeting Notes 2021

Jump to bottom
jedpittman edited this page Sep 1, 2021 · 18 revisions

Meeting notes from 2021-Aug-31

Reviewed the user testing notes. Reviewed Miro Board: https://miro.com/welcomeonboard/aG41ZGIxZEg0R1duc01SRXZYcExPa3RnN2pQZXJnM0FyMFRSejVHR0NUNGI5amhHRlhQUU1xWUJtUk5sMW45MHwzMDc0NDU3MzYzMjYwNTgwNzMz

Built spreadsheet with details: https://docs.google.com/spreadsheets/d/1W7LIaoksDXnP8ujWztjtRjaDaeJpirXzWFri61g4S8c/edit#gid=0

Plan is to have several teams (e.g. one for qualitative data, one for quantitative data) General concept is to, next week, to consider the top 3 (or so) data sources and see what we have for information and work through a plan similar to the following:

In general, we'll try and follow a process for each data source in order of priority (vacant land, housing, public spaces etc) for example:

  1. Source the data
  2. Generate a test sample of data for validation
  3. Validate the data
  4. Add the data to the standard repository (tbd)
  5. Evaluate and Update APIs to serve the data (as needed)
  6. Design the visualization
  7. Create a proof of concept with the data
  8. Demo/Iterate the proof of concept
  9. Integrate the proof of concept (launch the page in the tool)

Meeting notes from 2021-Aug-24

User Testing with several community members. Collected interviews via zoom where members used the tool and answered questions posed by the team to give feedback.

Meeting Notes from 2021-Aug-17

Reviewed the plans to do user testing on Aug 24.

Meeting notes from 2021-July-27

Couldn't do user testing tonight - not enough signups Rescheduling for 8/24 at 6PM

Shay asked about how tied we are to the existing demo - has some ideas on how to improve layout. Allentza - not tied to layout. Goal of user testing is to evaluate usability, color scheme, content

  • would love to hear from group if there are new ideas based on the presentations the last 2 meetings
  • Shay - thinking about different types of users, how tool could better work for them Some other ideas from last meeting - eviction data

Allentza can post slides from last meeting to Slack

Shay - ex. map that iterates over time using 911 calls - heat map: https://www.storybench.org/build-animated-heatmap-cartodb/

2020 Census data, visualizing change in household income, race/ethnicity, HH size

  • some data mapped by Kayla back in December

Ungentry tool - consider incorporating some element of this, maybe on a subpage

  • Thad was involved earlier in project, can answer questions about how data was processed

Need master list of all datasets that have been compiled - aim to have this by next meeting

Job hopper - info on different jobs, look at how changes in Mattapan relate to economic opportunity

Shay - explore some of these options, including animations - mapbox, leaflet, D3

  • simple proof of concepts through August
  • combination of data and visualization tools

To-do list for Monday, August 16th (before next meeting on 17th)

  • Allentza - finalize Drive location for all data
  • Jed/Thad - first draft of questions for user testing
  • Shay/Tejasvi - design enhancements, collect examples (map style - heat map, walking path) https://docs.mapbox.com/mapbox-gl-js/example/heatmap-layer/
  • Jed - can look at D3
  • Barry - pull some other data, including evictions

Brad's code on Mapbox/React - made good progress

Meeting notes from 2021-June-29

Demo recording didn't happen. not enough time. Live demo happened on Friday June 25. Generally the demo was positive. No specific feedback.

July Schedule

Pause: July 6 (holiday week)
Workshop 1: July 13 Gentrification and Displacement and shared language.
Workshop 2: July 20 Mattapan History.
User Engagement: July 27.

When do we want to schedule a user testing session?

  • Start soon - July 27.
  • What specific audiences did we have
  • What kinds of features did those users need (leverage a diagram, modeled after the slack diagram)
  • See: Mapping Tool Stakeholder - User Mapping diagram. -- Determine who are the inner/outer stakeholders -- What are the ideas for learning for each stakeholder -- What are the features that would enable those opportunities -- Which types of people might not be stakeholders?

Update the Client Side Application in the meantime

  • Use React, start from the standard branch.
  • Start to build components as react items.
  • Recreate the existing functionality.
  • Shay will work on developing a poc with some functionality with mapbox.
  • Jed will take a pass at developing initial tests with jest that can be enhanced later as the app is built further.
  • Other contributors encouraged to take and make a react branch and contribute updates toward the goal of migration and we'll merge the code together later.

Regarding Platform:

  • What would be the next step?
  • Google or Amazon web services. AWS is the most comprehensive.
  • Looking to get an answer by the 13th once Powerful Pathways has their meeting

Meeting Notes 2021-June-15 Review a number of Stephen's Comments and came up with plans to make incremental improvements. Thanks Stephen/Shay/Brad for doing work off-cycle to keep the project moving forward. Mob Programmed together to update demo with the following changes:

  1. Cleanup of items in the key
  2. Addition of icons in the key
  3. Consolidation of colors for boundaries/Corridors, but should be reverted because after discussion, we decided that the different colors are more demonstrative of Mattapan Boundaries over Time.

Design team worked to provide visuals for colors and icons.

Captured final items into issues for the coming week. Big item is to wrap up the work on the modal popup. Demo etc next week.

Meeting Notes 2021-June-08

Updated Presentation is 6/25. (do the recording the night of 6/22) Goal is to do a video demo.

Agreement was to focus on:

  1. Design (incorporating the agreed-upon) color palette.
  2. Incorporating Development Information
  3. Wrapping up work on the Oral Histories (since it was in flight)

Some work that is in flight has been checked in and added as branches. Some folks will submit WIP PRs this week as we make progress.

Meeting Notes 2021-June-01 Progress:

  1. Reviewed and organized all issues into two projects, either Demo project or Planning Project.
  2. Annie ran small session to gather information and a plan for user surveys after demo.
  3. Barry faciliated! Thanks Barry!
  4. Stephen ran small session to decide on key technologies for post demo which are now finalized: React, Leaflet.

Jed pitched, but no new joiners.

Meeting Notes 2021-May-25 Progress:

  1. Code walkthrough last week with Stephen and James (recorded for others if they are interested)
  2. Barry/Jed reviewed and exported 8 additional boundaries for inclusion. Code nearly merged/done.
  3. Project board for the demo created. Feature leads, please add your tasks to this board. If you have permissions/other issues, slack me.
  4. Other updates from Feature teams/Infrastructure/DevOps?

Housekeeping

  1. Zoe swapping feature groups
  2. Barry/Jeff potentially late/not coming
  3. Annie: CFB housekeeping?
  4. We need a person from Powerful Pathways who can provide blurbs for Boundaries (unless Barry can do this week?)
  5. We should have all of the assets we're planning on integrating by Wednesday this week. Let's set this as a cutoff.
  6. Stephen: Do you have items that you need help with once people finish their feature work?
  7. Annie: I think we need a survey for our potential users. Do you need any help putting that together/scheduling?

Feature Teams: Goal is to ensure that either tonight or sometime this week you have an example of what your bit looks like in the code. This will ensure we have time for the design team to review, provide updates/polish before demo.

Mattapan Mapping App Capabilities (Very High Level):

  1. Hosting: A Dynamic API Driven Web App (HTML/CSS/JS)
  2. Authentication:
    1. Roles:
      1. Viewers
      2. Submitters
      3. Reviewers
      4. Admins
  3. Admin Panel;
    1. Review Submissions
    2. Update features
      1. Uploading media
      2. Revising statistical data
      3. Content management/Language Updates
    3. Manage user (allow/revoke) access
  4. Types of Data
    1. Land use data
    2. Demographics data
    3. Geospatial data
    4. Statistical data
    5. Audio
    6. Video
  5. Search/Indexing
    1. Text
    2. Audio
    3. Video
  6. Testing:
    1. What devices will the app need to support:
      1. Desktops
      2. Mobile Phones/Tablets
  7. Budget:
    1. What’s the monthly/yearly amount that can be spent to maintain the app and its infrastructure?

Ideas/Follow ups:

  1. James will work this week with various teams/monitor the updates and help us develop the features to add these assets into the application.
  2. David is working on some style.css file versions that we can review/update as a starting point for the design.
  3. Stephen is working to evaluate options/tools for hosting and a platform for the remainder of the project. All developers should complete the survey by next Monday 5/25/2021 at the very latest.
  4. By request, I enabled GitHub pages -- this gets us an automatic "deploy" for this static site at this address once we merge the code after a PR: https://codeforboston.github.io/mattapan-mapping/
  5. Thad suggested that we might use netlify as a tool to auto deploy based on a certain branch. This has worked for static assets like code for boston website. Might be a good bridge solution. I started to set this up....and it is running for main branch. It seems like there's a way to do this for other branches too but I need to investigate further.

Overall, we're aiming for the following: 5/28: Get all assets we want to include in the demo either linked to and/or added to the repo by end of this week 5/28: David to provide a couple of sample styles we could use and/or start from as a base. 5/31: Technology Survey done by next Monday. Then brainstorm/make a follow up plan to decide our planned tech stack (Stephen to drive) 6/1: Have at least a simple example of each type of update we want to do:

  • A single complete audio item (or more)
  • Single complete development item (or more)
  • Single complete boundary + blurb (or more) This gives our design team a full suite of possible elements that need to be styled.

6/18 For following weeks, add more assets in and finalize color choice/design in parallel. 6/15 Final week, any remaining integration/finalize assets.

Meeting Notes 2021-May-18

  1. Review roles
  • James will be working with the team on an ongoing basis throughout the week.
  • Entire powerful pathways team should be cc'd on items/questions and whoever is the best person will respond. If there are questions to sort out, they'll communicate internally.
  1. Update Near Term goals/issues
  • Sasaki has already given a grant of money in response to an earlier demo.
  • On June 18, 2021 the Powerful Pathways team should produce a demo that can show our progress.
  • We've agreed to focus on the following items in order of priority:
Feature Feature Lead Team Notes
Design David Allentza, Huong, Annie Colors/Key/Legend
Audio Thad Brad,Sasha,Shweta (At least 2 items)
Development Projects Kayla Sergey, Jeff (Include link,blurb,facts,Image)
Boundaries/Map Barry (Jed Backup) Tajasvi, Stephan, Shay (neighborhoods, blurb)
  1. Assign Roles (Done, see table above)
  2. New Business/Items (Issues being entered on github issues list)
  • James' code will be cloned to the code for boston repo.
  • All changes (including James' will be done there)
  • We'll work to setup a meeting this week with James to do a code walk through if possible and we'll announce to wider team to be present if possible.

Future enhancements (post demo on June 18 may include):

  1. Video (At least Two of each type)
  2. Images (At least Two of each type)
  3. Planning/Development/Demographic Data.
  4. GeoTagged Data/Map Link Features.
  5. Ensure it is reactive. People can click/drop points/add content.
Clone this wiki locally