...
The following individuals are current Committers for VIVO open source software:
Name | Organization | Code Signing Key Fingerprint | Key ID |
---|---|---|---|
...
TIB Hannover | |||
...
Ontocale | |||
...
Clarivate Analytics | |||
...
Cornell | |||
...
Cornell | |||
...
Cornell | |||
...
Cornell | |||
...
Cornell |
Release Managers
Name | Organization | Code Signing Key Fingerprint | Key ID |
---|---|---|---|
Kitio Fofack | |||
Ralph O'Flinn | University of Alabama, Birmingham | ||
Andrew Woods | DuraSpace | 7BCE77FB75D06477C7A1D6EF04BE1CAB70B358DF | 70B358DF |
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. They are still members of the Committers Group, but are currently acting 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.
...
- All Developer Meetings are open for anyone to attend. The meeting minutes are publicly available.
- Technology discussions take place in the following places:
- vivo-tech Mailing tech Mailing list
- VIVO Issue Tracker (When discussion is related to a specific ticket).
- GitHub [Vitro / VIVO] (When discussion is related to a specific GitHub pull request)
- Occasionally on the Wiki itself, usually for early scoping and proposals of features/changes - especially larger developments involving a co-ordinated effort.
- All technology decisions are made following our Community Decision Making process