Proposal: Xarray user stories
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, nextjs, react
- Domain
- content, documentation, web-dev
Research direction
Start by reviewing the linked domain issues (#344, #346, #347, #349, #350, #352, and #358) and the existing xarray.dev content structure. Settle the story format and whether stories belong on standalone pages or in a blog category; done means at least 10 stories have been solicited, edited, and published.
Written by the indexing model from the issue text.
Description
Xarray is used in a wide range of scientific and applied research domains but many have the impression that Xarray is just for geospatial data. One way we could counter this misconception is by developing a series of user stories that highlights the complete range of Xarray applications. I'm thinking of a list of at least 10 stories that could be highlighted on this website (either as stand-alone pages or a special blog post category).
Domains:
- Neuroscience (e.g. Allen Brain Atlas / SDK) (see #345)
- Bioimaging (see #344)
- Genomics (see #346)
- Climate model analysis (see #349)
- Remote sensing analysis (see #350)
- Machine learning and/or statistics (e.g. pymc, arviz) (see #348)
- Finance
- Economics (see #347)
- Physics (see #352)
- Energy sector analytics (see #358)
- [more here]
If folks think this is a good idea and we can settle on a basic format for the stories, I'll volunteer to solicit and edit the stories.
cc xarray-devs (@alexamici, @rabernat, @shoyer, @dcherian, @benbovy, @max-sixty, @spencerkclark, @fujiisoup, @fmaussion, @mathause, @andersy005, @Illviljan, @keewis, @TomNicholas)
ps, I'll create the xarray-core-team in this org so we don't have to tag individuals in the future
- Dominant language
- JavaScript
- Stars
- 14
- Forks
- 30
- Avg merge
- 6h 47m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from xarray-contrib/xarray.dev
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
xarray-contrib/xarray.dev#796 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 35/100
xarray-contrib/xarray.dev#790 · 1 comment · 1 reaction ·
-
numbagg blogpost Open
Difficulty 2/5 Half a day Newbie friendliness 45/100
xarray-contrib/xarray.dev#776 · 1 comment ·
-
Website down Open
Difficulty 4/5 3-5 days Newbie friendliness 25/100
xarray-contrib/xarray.dev#757 · 21 comments ·
-
blogpost on xrlint Open
Difficulty 3/5 1-2 days Newbie friendliness 25/100
xarray-contrib/xarray.dev#756 ·
All issues in xarray-contrib/xarray.dev
Similar issues
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100