NASA-IMPACT / NASA-IMPACT/veda-docs
Merge VEDA and MAAP docs?
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 10
- Forks
- 16
- Avg merge
- 2d 31m
- Merged PRs (30d)
- 4
Description
There is a lot of overlap between MAAP and VEDA in terms of use cases and also audiences.
In terms of docs, the main area where they are distinct is how to get access and other platform-specific technicalities such as how to set up environments.
They are similar for the use cases for science compute on (NASA) Earth data and in part also how to receive support for scientific computing with STAC, S3, Python packages like rasterio, xarray, geopandas, etc.
At some point, it might make sense to merge the two docs - keeping platform-specific information separate but bringing most other things together.
Acceptance criteria
- Explained whether time is ripe for merging or not yet
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.
Research direction
Start by comparing the VEDA and MAAP documentation, focusing on shared use cases, audiences, and support for STAC, S3, and Python packages such as rasterio, xarray, and geopandas. Keep access, environment setup, and other platform-specific material separate, then document whether the overlap makes merging timely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100