EAASI development is now tracked on the platform’s GitHub. Please consult the EAASI Current Roadmap and Idea Backlog for up-to-date progress on the work that has been prioritized by the Yale Software Preservation and Emulation unit in collaboration with the EAASI Research Alliance.
The day-to-day effort of team members to address the roadmap is broken down in further detail on the EAASI Prioritized Issue Tracker for even greater transparency.
How is this roadmap prioritized?
Yale serves as product management headquarters for the EAASI software and maintains the roadmap. The Yale EAASI product management team is committed to transparently prioritizing the EAASI software roadmap based on shared needs, and Yale encourages EAASI Research Alliance participants to provide input to help prioritize the EAASI software product roadmap.
The product management team is committed to developing and sharing clear mechanisms for routine community voting on the roadmap, code contribution pathways, and documentation to support the continuity of the software should its maintenance or product management evolve over time. The team is also committed to communicating clear expectations about development capacity.
The product management team encourages EAASI Research Alliance participants to provide input on the roadmap starting in 2025 by:
-
Reporting potential features via the EAASI User Forum
-
Participating in an annual listening session with each institution’s EAASI Alliance Organization Administrator about features that the Alliance community has identified
-
Voting in an annual survey about features of interest
The Alliance Subcommittee will also do an annual “lazy consensus” review of the final prioritized roadmap, in which they can review the roadmap and raise objections if needed.
The following flowcharts outline the roadmap input pathways in more detail.
Proposing, reviewing, and gathering feedback on new features that could potentially be added to the EAASI roadmap:
Assigning priority to bug fixes, features, and maintenance work, and setting the EAASI roadmap:
