First off, I couldn’t find an existing post here or on GitHub so I opened a new one. Let me know if we should merge the discussion in another thread.
We rolled out Metabase at work 5 months ago and we’re very happy with the product. Once you start working with Metabase you run into occasional glitches and issues which you can work around. Still, it adds up and it gets a bit annoying. I do appreciate the product you guys created and it’s an amazing piece of software, especially given it’s early stage. Even less technical users find their way around after a short intro and that’s perfect.
It makes me uneasy though to see many open issues and pull requests on GitHub and I got the impression the core developers don’t have enough capacity to work on all of these and, for pull requests for example, make sure the feature is released successfully and no regressions are introduced.
I’m wondering how I (and hopefully other volunteers) can support this process. Do you need resources to run automatic regressions tests against new builds or manual tests? I’m sure my company wouldn’t mind allocating resources to this.
I saw the project roadmap on GitHub but this is probably too high level for day-to-day work.
So I guess the TL;DR question would be: What kind of help would you need the most to accelerate Metabase development?