DOC add roadmap

[adrinjalali]

@BenjaminBossan and I had a meeting and talked about the project's roadmap, and here's the result, and we thought it'd be nice to have it as a part of our recorded documentation, and update it every few months.

We also talked about how we can increase the visibility and usage of the project, which I don't think belongs to the project roadmap section, but putting it here to also talk about it:

The status at the moment:

• pypi downloads have been pretty stable around 50-100 downloads a day.
• We've been having continuous engagement from community members on the repo.
• The scikit-learn core team is excited about the project, and sends people to us for certain things like persistence.

Ideas on increasing usage:

• outreach: we're giving talks around
  • PyCon Italy is the next scheduled one
  • Did one in PyData Berlin meetup
  • Did another talk with Linux Foundation's ML Security Committee
• usage/conversion:
  • the model card app would make people happy probably
  • we need clearer communication on why people should use skops format, people are still confused as what the difference between .skops and .onnx is, for example.
  • many people know of ONNX, convenience methods for that could bring them here.
  • people always look for how to deploy their models online, if we have something related to that, it'd bring more people here. But this is a very large topic and whole bunch of companies/teams work on it.
  • we could try to convince a place like sagemaker to support .skops format. (the format would need to be more mature for that)

cc @skops-dev/maintainers

[adrinjalali]

rendered here: https://skops--311.org.readthedocs.build/en/311/roadmap.html

[BenjaminBossan]

Great write-up. Apart from the two minor comments, nothing to add from my side.

[BenjaminBossan]

Should probably be "sklearn models"?

[adrinjalali]

Ideally they'd be able to convert non-sklearn models as well, by implementing custom converters. But that's not well documented.