meta-pytorch / meta-pytorch/data
Documentation Improvements Tracker
Open
Nobody has claimed this yet.
todo
- Dominant language
- Python
- Stars
- 1.3k
- Forks
- 179
- Avg merge
- 6d 1h
- Merged PRs (30d)
- 2
Description
Here are some improvements that we should make to the documentation. Some of these likely should be completed before beta release.
Crucial:
- Add docstrings for the class
IterDataPipeandMapDataPipe
https://github.com/pytorch/pytorch/pull/72618 - Review the categorization of
IterDataPipeintorchdata.datapipes.iter.rst
https://github.com/pytorch/data/pull/219 - Edit first sentence of each DataPipe docstring to be a concise summary of functionality (also include functional name when it exists)
https://github.com/pytorch/pytorch/pull/72476
https://github.com/pytorch/pytorch/pull/72475
https://github.com/pytorch/data/pull/209 - Add usage examples to each DataPipe docstring
https://github.com/pytorch/pytorch/pull/73033
https://github.com/pytorch/pytorch/pull/73250
https://github.com/pytorch/data/pull/249 - Add tutorial (how to use DataPipe, how to write one, how to use it with DataLoader)
https://github.com/pytorch/data/pull/212 - Add domain usage examples (links to files)
https://github.com/pytorch/data/pull/216 - Decide what utility functions to include
https://github.com/pytorch/data/pull/205 - Link to relevant DataLoader documentation
https://github.com/pytorch/data/pull/205 - Turn on 'gh-pages' in this repo's setting
It is enabled. - Clear labelling of prototype vs beta phase
https://github.com/pytorch/data/pull/252 - Add a link under the 'Docs' tab on pytorch.org
Nice-to-have:
- Update issue form for documentation related issues
https://github.com/pytorch/data/pull/215 - Add links to domain usage examples onto individual DataPipe pages (see how TorchVision does this)
- Remove tutorial from README.md and link it to the documentation tutorial
- Make a functional equivalent table in documentation (in a separate page?)
cc: @VitalyFedyunin @ejguan @wenleix @dongreenberg @NivekT
Contributor guide
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.
Research direction
Start by reviewing the remaining unchecked items: domain-example links on individual DataPipe pages and the functional-equivalent table. Check the existing documentation pages, README.md, and the TorchVision approach referenced in the issue. Done means both documentation improvements are added and the relevant documentation builds or renders correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100