Skip to content

Develop a Roadmap #210

@scopatz

Description

@scopatz

Hello All,

I'd like to help Dask-ML develop a roadmap, and @TomAugspurger requested that I open an issue here to kickstart the discussion.

For those of you unfamiliar, a roadmap is a listing of near- and long-term goals that the project has, but which have yet to be implemented. These goals are generally larger than single pull request. "Add GPU Support" or "Port to Python 3" are examples of some roadmap items a project might have. However, goals can also include activities that seem small and mundane, but are critical to the project, such as "Improve Documentation" or "Achieve 100% Test Coverage."

The purpose of this issue is so that roadmap items can be listed and commented on in the discussion. Once we have a reasonable sense of what folks would like to see on the roadmap, the contents should make its way to the website/docs in some fashion. It is also a good idea if it ends up being listed in priority order, so that higher priority items are closer to the top.

Some good example of project roadmaps are:

A decent example of a project roadmap is Spyder's Roadmap which looks more like a timeline with milestones.

Roadmaps serve a joint purpose:

  • They help inform and attract potentail funders, and some funders require roadmap documents
  • They help attract contributors, as developers are more likely to jump in an help an establish project than start a new project to scratch their itch.

TL;DR: Roadmaps communicate a project's intentions. It would be a good idea for Dask-ML to have one, and I am happy to help facilitate!

So where would you like to see Dask-ML go?

This is a mirror issue to dask/dask#3589

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions