The following presentation was given on the January 30, 2015 VIVO implementation and development call.
| Slide | NotesCommentSlide | |
|---|---|---|
 | To be successful, a roadmap process should lower the bar to contribution, not only in the process but for any aspect of the VIVO community. The VIVO community is a big tent welcoming participation by anyone interested in the VIVO software, the VIVO-ISF ontology, or more generally in the building networks of research and researchers in any domain. | |
 | A roadmap process must initially be start broad enough to encompass many activities and goals, and must be closely aligned with overall project and community strategy and goals. | |
 | Here are some of the tasks that developing a roadmap should will likely include. | |
 | ||
| A roadmap should respond to feedback from the field in order to address pain points in practice, not just new features. | |
 | Each of the main headings here is broken out in more detail that follows. | |
 | See also the VIVO/Vitro Architecture page and Software Architecture Overview. | |
 | Performance and scalability are frequently recurring themes as VIVO projects assemble more data and support additional web traffic. | |
 | VIVO's search indexer has improved performance and additional configuration options for VIVO v1.8. | |
 | ||