I commented on the bug to get more clarity, but I'm considering helping
maintain too.
Maybe we can spread it out amongst Siddharth and myself to make it even
less of a burden? That would be ideal.
Should we keep discussion on Phabricator to finalize any
arrangements/handoffs?
Thanks,
-Travis
I would be happy to be added as a maintainer unless someone more capable
steps in. I also mostly use Superset nowadays, but I think there are a
handful of features in Quarry (viewing cached results, wikitable export)
which make it worth maintaining.
That being said, I don't have much time on my
> First, based on GitHub requirements.txt the library versions used in the
app are older than the latest ones, and T169452 also hints at growing
technical debt in terms of updating code. However, are there known blockers
for updating them? Ie. Does Quarry use something abandoned and blocks
Hi Vivian,
First, thank you for maintaining the Quarry.
A couple of questions from a technical perspective.
First, based on GitHub requirements.txt the library versions used in the
app are older than the latest ones, and T169452 also hints at growing
technical debt in terms of updating code.
That is sad, Vivian. I love Quarry.
But then again, at this point, is there any feature that Quarry offers
which Superset doesn't? Maybe this is a natural time for Quarry to be
sunset?
On Tue, Oct 3, 2023 at 4:59 PM Vivian Rook wrote:
> Hello, I'm writing to notify any interested party that I
