VIVO Committers Group

VIVO Committers work with the community to maintain and advance the code and have the following primary responsibilities:

Anyone may be nominated as a Committer by anyone else. Typically, nominations are made by existing Committers on the basis of sustained contribution to VIVO that indicates an ability to fulfil Committer responsibilities. Examples of such contribution are participation in discussions on the VIVO mailings lists, participation in developer meetings, reporting bugs, help with testing, and contribution of code via pull requests. Only existing Committers may vote to add a nominated person to the Committers group. 


The following individuals are current Committers for VIVO open source software:

NameOrganizationCode Signing Key FingerprintKey ID
TIB Hannover

University of Florida


Clarivate Analytics




University of Alabama, BirminghamA60EDC4D8048413D658A5EC1BC8EEF942728631627286316
University of Colorado, Boulder

Texas A&M University

Release Managers

NameOrganizationCode Signing Key FingerprintKey ID
Kitio Fofack

Emeritus Committers

Emeritus Committers are those who, for one reason or another, are no longer able to contribute code to VIVO on a regular basis. Although no longer members of the Committers Group, this group continues to act in an advisory role within the VIVO development community. We wish to recognize the contributions each of these individuals has made to VIVO software over the years. Their code contributions and guidance have played an integral part in helping to make VIVO what it is today.

Special Recognition of Cornell University and the NIH Grant Development Team

The VIVO project was initiated at Cornell University Library in 2003, and further supported by an NIH grant funded team from 2009 to 2012. Without these efforts, VIVO would not be the success it is today, and as such we would like to extend a special recognition to the members of that team.

Committer Discussions / Meetings

As much as possible, Committers ensure that all VIVO technology decisions are transparent to the developer community. The only exception is when security issues require us to resolve them before they are publicly reported.