Better communication of roadmap and timescales

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.

No files, tests, or entry points are named. Start by reviewing the current roadmap and release communication, then define a documented roadmap with timescales and a clear way for the community to provide input; done means the project publishes and maintains that information.

Written by the indexing model from the issue text.