-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Better communication of roadmap and timescales #2194
Comments
We've love to get an official release out but it is a lot of work and you have noted, while we have many users, we have virtually no external contributors outside of Foursquare. The roadmap lately has been less on features and to "harden" kepler and make it workable as an open base for a commercial application, which included typescript, modularization, exposing more APIs and tons of fixes. We have one more batch of Foursquare fixes that we want to upstream. In addition, the vis.gl ecosystem is going through a major overhaul with deck.gl v9 (WebGPU enablement) which is going to impact all the vis.gl frameworks and ultimately kepler.gl, so that is also something big that we need to get through in the coming year. You are most welcome to engage. kepler.gl is under open governance in the OpenJS foundation. The Open Visualization sub team meets over zoom every other Thursday, anyone is welcome to join, and we are hoping to soon announce an in-person summit in the early fall. |
How can I get in contact and participate on the meetings? Would love to contribute to the project, but Don't know how to start. |
Thanks for the update and links. The slack is pretty quiet, I’ll check out
the openvis side of things and see how I can best contribute!
|
I can see from the commits that there has been a lot of work happening on Kepler.gl and I truly welcome it.
I would, however, like to posit that it is not just Foursquare and Uber that rely on this as a tool, and while nearly all of the effort is coming from people at Foursquare, I would like to suggest we could do with a more open approach to the roadmap and releases.
Moving over to typescript, fixing long standing bugs, and integrating new features from Unfolded is clearly a virtuous task, and I wish I (and we as a community) could do more to help.
Would the team be open to sharing more of the roadmap and timescales and therefore be open to both the communities influence and contribution?
The 3.0.0 alpha is 5 months in the making so far and we are all keen to help and benefit from advances!
Any communication and insight would be very well received.
The text was updated successfully, but these errors were encountered: