Aligning Zyra’s Roadmap with Core Foundations First #90
Hackshaven
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Zyra’s Goals
Zyra’s mission is to be more than a visualization library — it’s a pipeline framework that:
• Acquires from diverse sources (APIs, OGC, cloud)
• Processes data reproducibly
• Visualizes with clarity and beauty
• Disseminates at scale
Underlying principles:
• Reproducibility across NOAA/NODD, SOS, web contexts
• Scalability to handle terabyte-scale + real-time workflows
• Usability for both developers and educators
• Governance for ethical, sustainable data usage
⸻
Where We Are
• Governance & contributor workflow → nearly complete
• Discovery/search → actively advancing
• Extensions (Smartsheet, n8n) → proposed, but rely on core systems not yet in place
⸻
Why Core Before Extensions?
Extensions are valuable — but their success depends on solid foundations.
Think of Zyra as a railway system:
• Tracks = Profiles (#66), Zarr support (#65), Executors (#87), Search→Ingest integration (#63, #84)
• Trains = Connectors (Smartsheet #89, n8n #72, Slack, Notion, NOAA APIs)
🚂 If we add trains without laying tracks, they won’t run smoothly.
But once the tracks are there, adding trains is fast, modular, and sustainable.
Specifically:
1. Dependencies – Connectors rely on API ingestion (#84), which itself needs Profiles & configs.
2. Reproducibility – Without Profiles, extensions become one-off hacks, not reusable workflows.
3. Scalability – Without Executors, integrations may demo well but fail at NOAA scale.
4. Sustainability – Building extensions first risks fragmentation and tech debt.
⸻
Proposal
Focus near-term delivery on core foundations:
• Implement Profiles framework (#66)
• Add Zarr support (#65)
• Deliver Wizard CLI (#80) for usability
• Stand up Dask executor (#87)
• Enable Search→Ingest integration (#63, #84)
Defer specialized connectors (Smartsheet #89, n8n #72) to 2026+, once the foundation is stable.
⸻
Benefits
• Aligns with Zyra’s mission of reproducibility + scalability
• Reduces risk of fragmentation
• Gives NOAA/NODD workflows immediate reproducible value
• Ensures connectors/extensions land on a solid, future-proof base
Beta Was this translation helpful? Give feedback.
All reactions