Monthly meeting notes

Next meeting date: 2023-10-28, 9am EDT / 3pm CEST / 11:59pm AEDT

2023-09-30

Members present: Sid, Tak, Eric, Justin, deecay

Introductions

• Sid:
  • based close to Kansas City
  • works in sports analytics
  • got to know Redash through hobby chess data work (~2019), now own exercise data
• Eric:
  • Starfish Storage - analysis on filesystem data to minimize cost
  • up to ~30tb databases
  • Redash is a way for customers to look at their data
  • BSD license is critical - Redash is patched + passed through to clients
  • system to capture a PDF of dashboards and email to users
    • headless chrome
    • optionally attach CSVs
  • Metabase might work, but AGPL-3 doesn't work as a license
  • Redash lets you do whatever you want with the db (creating functions, temp tables, operators)
  • background mostly in Postgres
  • in upstate NY
• Tak:
  • used to be a maintainer!
  • also used to organize a meetup in Japan: https://redash-meetup.connpass.com
  • 3-6y ago, used to work for advertising agency in Japan
  • doesn't work with Redash recently
• Justin:
  • Now based in Australia (Brisbane)
  • Initially started using Redash for making charts, for DB Browser for SQLite project (sqlitebrowser.org)
  • Worked for Redash for a few months when between contracts ~2 years ago
  • Skills wise, is infra-focused. When Redash announced their shut down, he set up Newdash.io and inherited some of the customers who needed hosting
  • Mostly focused on security issues in Redash, as well as operational pain points like the excessive memory usage
  • Has an M1 Mac Mini (via DB Browser for SQLite project) that is useful for doing Apple Silicon builds on
• deecay:
  • from Japan (Tokyo)
  • using Redash since ~2018-2019, long-time committer/maintainer

Community

Docker preview image

• missing docker password
• can't push images to Redash docker hub
• if people are using the updates regularly, then problems we introduce will get caught
• CI is also incorrect - not building when it's supposed to, but less of a blocker

Poetry setup

• requires a new dependency: poetry itself
• don't have to manage requirements.txt files
• recursive dependency version pinning

Ubuntu 22

• databricks odbc driver / ms sql make switching OS a nuisance
  • pinned to x86
  • MS doesn't have debian 12
  • binaries "dropped in"
  • maybe set this up as separately-installed data sources?
  • possible alternative: https://github.com/stringer-rss/stringer/blob/54586418acd75b9be8c39167b8a748c7ed3f0096/Dockerfile#L28-L40
• ubuntu 20 EOL is 2025, so we have time

Future topics for these meetings

• project direction for the future