Roadmap Process. We are entering week four of the public discussion of roadmap items. I had an opportunity to discuss the VIVO Roadmap Process and the Roadmap Features with the Implementation and Development Working Group this week. It was a good discussion. The process involves identifying and discussing features that have been proposed over the past several years. Features appear to clump according to the role of the person involved with VIVO – there are a body of features that might benefit "end users" – people who use VIVO in their work (not the work of VIVO!), features that might benefit the "stewards" of VIVO at VIVO sites – these include project managers, data managers, outreach managers, local developers and system administrators. And finally there are features that benefit the developers of VIVO. All these perspectives are important. Next week, there will be a survey of the VIVO mailing lists, the Steering Group and the Leadership Group asking for feedback regarding interest in the features – we will ask whether you would be willing to participate in developing the feature – as a developer, a project manager, a writer, or in any other way. We will ask about priorities for VIVO. This data will go to a task force that will develop a roadmap proposal. The number of features on the roadmap will depend on the interest expressed by the community. The task force will take strategic, technical and effort considerations into account in developing the proposal. Please see the VIVO Roadmap Process page for more detail about how this will work.
There were great questions on the call with Implementation and Development:
Question: What about features for people who are interested only in VIVO data and not in using the VIVO application?
Answer: Such people are typically represented by the stewards. Several of the "steward" features are oriented toward people interested only in the VIVO data.
Question: Will all 80 proposed features be included in the survey?
Answer: Yes, and there will be ample opportunity for you to comment on your interest in specific features.
Questions: How many features will VIVO be able to implement over the course of the year?
Answer: This will be determined by the amount of contributed effort, and the complexity of the features of value to the community.
Question: What about features that haven't gotten to the list yet? How are features added?
Answer: All features we've heard of are added. Please send them in (comment on the feature page, or email Mike), they will be added.
Question: After we have a roadmap, how does it get amended?
Answer: Whew. Let's get to a first roadmap. I'm sure we will be able to develop an open on-going process for amending the roadmap as we execute on features deemed high value by the community.
If you haven't already done so, please review the Roadmap Features and discuss them with your colleagues. The survey will open at the end of the week.
Outreach and Engagement Work Group calls starting. The Outreach and Engagement workgroup, co-chaired by Julia Trimmer of Duke and Kristi Holmes of Northwestern, will be restarting its regular call series beginning Tuesday, July 21 at 1 PM Eastern. See Outreach and Engagement Interest Group for call details. All are welcome.
Nominations for Steering Group. Another way to help the VIVO community is by serving as a Steering Group member. Five additional members will be elected to the Steering Group this summer. We have begun to receive nominations. Elections will be held the week of July 20. If you know someone who you feel would make a great addition to the Steering Group, please nominate them by dropping a note to Mike Conlon. The current Steering Group is Dean B. Krafft, Robert H. McDonald, Melissa Haendel, Jon Corson-Rikert, Kristi Holmes, and Paul Albert. Please consider who might join them. Self nominations are accepted.
VIVO Project Director