VEDA-UI Maintenance Mode

[vgeorge]

Following up on Anthony’s note #1889 (comment), opening this thread to align on maintenance mode for VEDA-UI and next steps to clarify expectations.

Current State

• 210 open tickets, many outdated or out of scope
• About 30 tickets older than 2 years (pre-2023), mostly early architecture, UX, or legacy feature ideas

Maintenance Mode Definition

• Focus on bug fixes and blockers only
• No new features or large refactors
• Prioritize stability for existing instances
• Keep documentation and dependencies up to date

Example Tickets to Close

These represent migrations, refactors, and features that don’t fit maintenance mode:

• feat: start monorepo structure with veda-ui package #1898
• docs: Add ADR 004 - Component Library Restructure #1871
• [v7] Deprecate Parcel, use Vite build #1900
• [v7] Deprecate DevSeed UI Library #1861
• [v7] Deprecate DevSeed UI - Deprecate devseed-ui/Prose/Figure within stories #1825
• [v7] Deprecate Parcel, use Vite build - Migrate from process.env to import.meta.env #1815
• [v7] Deprecate DevSeed UI - Migrate story pages to use USWDS #1590
• [v7] Deprecate DevSeed UI - Migrate PageHero over to USWDS #1494
• [v7] Turn "open in QGIS" into a feature? #1362
• [v7] Test Coverage for Existing Core Features #1200
• Update Raster API endpoints as part of new version breaking change #1070
• Feature request: User can change color range in Exploration view #555

Old tickets (>2y): #3, #7, #35, #62, #69, #134, #205, #236, #265, #382

Proposal: bulk close these with wontfix, unless confirmed blockers.

Key Questions

• Is a README update enough?
• Bulk close >2y tickets?
• Any non-bug tickets needed before freeze?
• Which instances still depend on veda-ui?
• Should we also freeze next-veda-ui?

Suggested Next Steps

1. Gather feedback
2. Update README with maintenance notice
3. Close outdated tickets (wontfix)
4. Tag recent refactor/feature tickets as “not planned”

Related tickets

• [v7] Veda-UI Version 7 Roadmap #1889 (comment)
• Create veda-ui legacy deprecation plan #1767

cc @aboydnw @ifsimicoded @AliceR @dzole0311 @snmln @sandrahoang686

[aboydnw]

@vgeorge I went through the veda-ui backlog today and put things into a few buckets:

• Parent issue of [v7] Veda-UI Version 7 Roadmap #1889 if I thought they should set aside and/or closed
• Parent issue of CMS Integration for VEDA Portals #1917 [v7] E&A Improvements #1918 [v7] Story Improvements #1919 or [v7] Other veda-ui feature requests #1920 if I thought they were good feature requests/bugs that we shouldn't lose yet, but again not something that we are prioritizing right now
• Parent issue of one of our PI objectives if it's something to prioritize now
• Moved to other repos if there was a match

Next steps might be for you all to review the tickets I put under #1889 and see if you agree with the tickets I placed there, ready for archiving.

[vgeorge]

@aboydnw I reviewed all tickets from the bucket issues. Following the guidelines proposed in #1927, I added types and tags to all of them, with the exception of the V7 list, I organized it but didn’t apply the full tagging yet.

I’d propose closing the bucket tickets now that everything is properly tagged and easier to browse. Archiving all tickets might be too disruptive, since it would require a deeper review, so tagging feels like the right middle ground.

#1917 moved to tags mdx-publication-tool and cms-integration

#1918 moved to tag E&A

#1919 moved to tag stories & widgets

#1920 added issue types (bug, feature, task)

There is still many older issues that don't have proper classification. I think we can keep this ticket open until we finish classifying them.