Versions Compared

Old Version 8

changes.mady.by.user Mike Conlon

Saved on

compared with

New Version 9

changes.mady.by.user Erin Tripp

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Voting on travel policy (Julia, 5 minutes)  See policy here: Travel Policy and Procedure

  2. Creating the VIVO annual report: See outline here http://bit.ly/2S2mUGE and possible layout here https://bit.ly/2T4RM9B  (Mike, 10 minutes)

  3. Reviewing the developer calls: goals and engagement (Andrew, 10 minutes)

  4. VIVO debt (Julia, 20 minutes)


Notes

Travel policy:

  • Erin - comment on the travel policy - would like to confirm that an estimate is required ahead of expenditure and then the DS staff person will export report from expensify and send to Mike/Julia for approval before it is processed in expensify. ACTION = Mike to revise policy to reflect this. 

Annual Report

  • Mike- we don't want to spend a lot. We have a template. PLease provide comments. 
  • Julia - Anna offered to have her designer work on the report. 
  • Violeta - offers to help with the text. 

Dev calls

  • Andrew: Calls happen on Tuesdays at 11 am ET. It's not set in stone but good to have a consistent time. 
  • We talk about tickets/work in progress, posts to the listserv, encourage people to respond, sometimes we talk about special topics or have short presentations. 
  • Central point of communication for VIVO software development. 
  • Product evolution group is a separate effort. 
  • We're not seeing the new committers attend these calls. 
  • Julia: makes sense. I'm wondering what the difference is between ongoing development and sprints. I understand during sprints it's a focused effort with more people but there is other development that goes on between sprints. 
  • Andrew: ideally both of these types of dev happen. Ongoing, low level development is in line with strategic direction of the project. From VIVO leaders/steering there is a general commitment in ongoing dev to VIVO. Keeping a breast of development, bugs that exist, raising the need for features and saying we'll work on it but keep community in the loop. Sprints supplement that. Low level effort isn't normally sufficient to get features out the door that are priorities. Sprints rally support to meet goals and deadlines. Ongoing dev is more up keep.