TUDelftGeodesy / TUDelftGeodesy/sarxarray

Make tech stack update plan

Open
#101 1 comment 0 reactions 0 assignees View on GitHub

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: uv seems to be a much faster and easier option than mamba.
  • Documentation: mkdocs has issue with supporting version 2. -> consider go with the classic ReadthDoc + sphinx? Zensical seems to be risky for long-term
  • Documentation brokean link catch up -> lychee
  • If still using MkDocs, consider autodoc for API documentation?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.