Add roadmap for 2024 #1253
Add roadmap for 2024 #1253
Conversation
| - The API is not being documented. | ||
| - The API is not being enough demonstrated in a single place; users have to assemble examples from different pages. | ||
| - An implicit reliance on HoloViews' documentation (e.g. for the options) that itself isn't in great shape. | ||
| - The difficulty to run locally all or parts of the documentation (that relies on somewhat complex datasets and many libraries). |
There was a problem hiding this comment.
Maybe the discovery of available kwargs/options could be improved by using an LLM for hvplot like:
https://huggingface.co/spaces/ahuang11/tweak-mpl-chat
There was a problem hiding this comment.
Yes sure LLMs could help users in some ways! How exactly I'm not sure.
I've tried to keep the roadmap simple, it focuses on the boring but needed stuff I believe we have to address.
There was a problem hiding this comment.
I made a basic LLM chat bot for hvplot here: https://huggingface.co/spaces/ahuang11/tweak-hvplot-chat
it's missing a lot of docs because it was a pain to convert ipynb to markdown, but it has the basics of customization https://huggingface.co/spaces/ahuang11/tweak-hvplot-chat/tree/main/hvplot_docs
There was a problem hiding this comment.
Hi @ahuang11
Did you consider using and improving the existing hvplot chat app? https://holoviz-topics.github.io/panel-chat-examples/openai/#chat-with-hvplot
There was a problem hiding this comment.
If I'm not mistaken I believe that one is limited by formatting the kwargs into JSON so openai can do function calling. The one I just implemented is to dump hvPlot/HoloViews docs into a directory, so it expands a bit into HoloViews and can use .opts (it could probably write hooks as well if I gave it the FAQ).
There was a problem hiding this comment.
Ok. .opts would just be a supplemental function to the existing chat-with-hvplot app.
My gut feeling says the documentation. |
|
This looks great, thanks @maximlt. I agree with docs as the highest priority. |
Hi @Cyb3r-Monk, thanks for your feedback. I think what you're asking for is too specific for the roadmap. What I can recommend you is to look for issues (bugs or feature requests) on https://github.com/holoviz/holoviews directly, since it's very likely what you're asking for would be best achieved/supported using HoloViews. If there are existing issues, please upvote and chime in. If not, please open a new issue with as much information as possible about your use case. Finally, the HoloViz projects are open-source projects, feel free to start working on fixing/improving them, I'm sure contributors will be happy to help you in the process. |
I feel that without some sort of roadmap, hvPlot's development is only driven by whatever other development happens in the HoloViz ecosystem and outside, while its development should be more deliberate to gain more momentum.
So I'm suggesting this tentative, ambitious, and subjective (of course) roadmap for hvPlot for 2024. I'm not sure where the roadmap should eventually live If we manage to agree on its content. I'm opening this PR for others to be able to comment on it.