Notes

Mike will review the document notes from the leadership group to share with leadership and get comments, then post on the wiki

Mike will post slides from introductory talk to the wiki

The I-Fest

some shared notes produced Wednesday – worth reviewing and recording in a similar fashion to the summit notes

some presentations from the sessions themselves – Mike will check with Melissa to see if we can create some working product from the event

A suggestion on the Thursday implementation and development call that another time we could benefit from an experienced facilitator

general agreement that an experienced facilitator would help manage conversation, encourage participation in conversation, help address topics of interest, help hear from a wider variety of participants

II. Task Forces forming

Four task forces appear to be forming as a result of IFest conversations. Mike will follow up with each:

User Stories. Successful stories of VIVO use across a variety of institutions. For use on web site and in promotional materials. Julia Trimmer to facilitate. Carol Minton Morris of Duraspace. Others to recruit.

Contributed software and VIVO. Task force to recommend methods for sites implementing VIVO to consider and use apps and tools to augment core VIVO installation – more than a listserv mention, possible inclusion in QA processes. Chris Barnes and Ted Lawless interested in facilitating. Consider models from other open source projects – Hydra Labs and others. Others to recruit.

III. Budget

It is currently budget season, and invoicing season. VIVO has had good responses to invoices to date. Elsevier will drop out as a corporate sponsor (see below). We will have money for the tech lead, promotional activities, project infrastructure as presented at the Summit. We will extend Jim Blake at 60% for 6 months to allow time for hiring tech lead (see below) and transition to tech lead. Six month period is from April 1 to September 30.

IV. Hiring a Tech Lead

The job description is substantially complete. Will be circulated to Steering Group for one more additional review.

A search committee for the tech lead will be formed with representation fro Leadership Group, Steering Group, Duraspace, and Community. Mike will chair. As people are asked and agree to serve, names will be shared.

V. Elsevier

Elsevier contacted Jonathan to discuss the future of VIVO and Elsevier's role in it. Also spoke directly with Debra. Their concerns:

Their contributions had not been acknowledged

They had not been engaged in strategic planning

Lack of advancement in the VIVO technical plan

Asked them if there was anything we could do – they said no; they would be making other overtures to other groups. They will continue to sponsor the conference and continue to have interest in the community.

Lessons learned:

Redouble VIVO efforts on inclusion, openness, transparency

Address member concerns in a timely manner

Stay the course on pursuit of technical lead, development of open source community

Pursue additional corporate sponsorship with others

VI. Steering Committee 2.0

Our charter says we should have 11 members and we have 6. We should be rotating three members per year

Plan A:

We could add 3 this year (to 9) and three next year with one rotating off to get to full complement

Add 2 nominated and selected by leadership 1 from all members this year and do the same next year (as per charter)

Plan B:

We could add five this year. 3 from leadership and two from all members to get to 11

Three members would need to be identified as rotating off next year

Either way, we are in transition and not fully in line with charter

Jon will be rotating off next year

We will take these two options to the leadership group for their preference – Mike will get a draft to Dean to review and circulate with Steering before sharing with Leadership