Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Status of this project #412

Open
davidanthoff opened this issue Dec 21, 2017 · 13 comments
Open

Status of this project #412

davidanthoff opened this issue Dec 21, 2017 · 13 comments

Comments

@davidanthoff
Copy link

Just a quick question: is this project still being maintained? Any future plans? It looks really cool, but there doesn't seem to be too much activity in the repo?

@jheer
Copy link
Member

jheer commented Dec 22, 2017

There is no current activity on the project, but I believe it may resume in the summer or fall. Paging @arvind who can provide a more definitive answer.

@davidanthoff
Copy link
Author

It would be great if it would resume! I am in awe of all the stuff you guys created, and feel one could create some really powerful integrations for julia. I've sketched some ideas in vega/voyager#745 (comment) and vega/vega-lite#1472 (comment).

@TomBor
Copy link

TomBor commented Feb 5, 2018

Yes, It would be great to know if there is plan (or not) to continue Lyra.

@arvind
Copy link
Member

arvind commented Feb 5, 2018

Hi folks, thanks for the continued interest (and apologies for the delayed response). Yes, we expect to resume work on Lyra this summer.

We were frustratingly close to a Lyra 2.0 release back in 2016 but, unfortunately, needed to reprioritize our efforts towards, among other things, releasing Vega-Lite 2.0.

The good news is that work will not go to waste — it laid a very solid foundation that will make rebuilding momentum behind this project much easier. Our primary task will be to update Lyra’s model to Vega 3/Vega-Lite 2, which should be a fairly straightforward process (aides, hopefully, by migrating the codebase to TypeScript). And once we do, we can begin to build on it much more quickly than before.

@TomBor
Copy link

TomBor commented Feb 5, 2018

Great news! I'm looking forward to test it.
Thanks for the update.

@davidanthoff
Copy link
Author

Excellent!

@davidanthoff
Copy link
Author

Any update what the current plan is?

@arvind
Copy link
Member

arvind commented Jul 28, 2018

Thanks for checking in @davidanthoff! Returning to Lyra is high on our priority list but, unfortunately, we don’t have any updates yet.

@davidanthoff
Copy link
Author

Cool, thanks for the update!

@Sigfried
Copy link

Hi. I'm here wondering the same thing.

I decided to use Vega for an experimental network data exploration application and I'd love to be able to start with the basic framework already in place. I don't know if Lyra would have worked for that anyway, but if it's not going to integrate with current versions of Vega/Vega-Lite (I'll probably need to use Vega mostly), it's probably not a good match.

Thanks for all your amazing work!

@arvind
Copy link
Member

arvind commented Nov 28, 2018

Good timing @Sigfried. We’ve just restarted work on Lyra. We don’t have a timeline yet for when work should be complete porting it over to the latest versions of Vega and Vega-Life, but doing so is one of the highest priority items on our agenda!

@dprophet
Copy link

dprophet commented Jan 20, 2019

Hi @arvind Can you update the build dependencies and build instructions for the lyra2 branch? I am interested in seeing Lyra move forward. Lyra is the closest there is to an open source Tableau.

@jonathanzong
Copy link
Member

jonathanzong commented Jan 24, 2019

Hi @dprophet,

There are two working branches for Lyra 2 right now. lyra2 is the most recently working version that is usable, but it does not yet have all functionality implemented. If you're just looking to test something out, that's the right branch. lyra2019 is being actively developed, but will be unstable in the short term (next few months). If you're interested in digging into the latest code, this is the right branch.

I've checked the README on both branches to make sure they're up to date, let us know if you run into issues or are looking for some specific piece of info. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants