Skip to content

Question: current status, scope, and roadmap for rustronomy #7

@pseudofractal

Description

@pseudofractal

Hi,

I’ve been looking through the Rustronomy repositories and wanted to better understand how they relate to each other today.

From the README and code here, my understanding is that this repository is meant to hold the shared Rustronomy foundation, especially rustronomy-core, with more specialized functionality living in sibling crates/repos. I also saw the older discussion in issue #2 about organizing Rustronomy into separate repositories per crate over time.

From the outside, activity across the related repos looks a bit uneven, with rustronomy-watershed showing more recent signs of maintenance than this repo, and rustronomy-fits still appearing explicitly incomplete in its README. Because of that, I wanted to ask a few questions specifically about this repository and its intended role.

  1. Is this repository (rustronomy) still intended to be the central/shared foundation for the broader Rustronomy ecosystem?
  2. Is rustronomy-core meant to be the stable interoperability layer that other Rustronomy crates depend on?
  3. What is the intended role of rustronomy-macro?
    • Is it planned future work?
    • Or is it effectively unused / incomplete at the moment?
  4. Is there an up-to-date roadmap or TODO list anywhere?
  5. Are the current docs still representative of the intended design?
    • For example, some parts of the docs and code seem to suggest broader “universal container” plans than what is currently implemented.
  6. If someone wanted to contribute, what kinds of work would actually be useful in this repo?
    • tests / CI
    • documentation cleanup
    • completing core abstractions
    • macro support
    • something else

Thanks for any clarification.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions