TUDelftGeodesy / TUDelftGeodesy/sarxarray
Make tech stack update plan
Open
Nobody has claimed this yet.
- Dominant language
- ReScript
- Stars
- 26
- Forks
- 5
- Avg merge
- 9m
- Merged PRs (30d)
- 2
Description
As time goes, the old tech stack of sarxarray needs some updates.
The followng points should be considered. And each point needs to become a spearate issue
- Python dependencies:
uvseems to be a much faster and easier option than mamba. - Documentation:
mkdocshas issue with supporting version 2. -> consider go with the classicReadthDoc+sphinx?Zensicalseems to be risky for long-term - Documentation brokean link catch up ->
lychee - If still using MkDocs, consider autodoc for API documentation?
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
Review the four proposed workstreams: Python dependency management with uv, documentation tooling, broken-link checking with lychee, and API documentation with autodoc. Split each decision into a separate issue, and consider the work complete when each has a clear scope and chosen approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, documentation, tooling
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100