This work is supported by Anaconda Inc
People often ask general questions like “Who uses Dask?” or more specificquestions like the following:
This yields interesting and productive conversations where new users can diveinto historical use cases which informs their choices if and how they use theproject in the future.
New users can learn a lot from existing users.
To further enable this conversation we’ve made a new tiny project,dask-stories. This is a smalldocumentation page where people can submit how they use Dask and have thatpublished for others to see.
To seed this site six generous users have written down how their group usesDask. You can read about them here:
We’ve focused on a few questions, available in ourtemplate thatfocus on problems over technology, and include negative as well as positivefeedback to get a complete picture.
Contributions to this site are simple Markdown documents submitted as pullrequests togithub.com/dask/dask-stories. The siteis then built with ReadTheDocs and updated immediately. We tried to make thisas smooth and familiar to our existing userbase as possible.
This is important. Sharing real-world experiences like this are probably morevaluable than code contributions to the Dask project at this stage. Dask ismore technically mature than it is well-known. Users look to other users tohelp them understand a project (think of every time you’ve Googled for “sometool in some topic”)
If you use Dask today in an interesting way then please share your story.The world would love to hear your voice.
If you maintain another project you might consider implementing the same model.I hope that this proves successful enough for other projects in the ecosystemto reuse.