Develop For VIVO
Help us maintain and advance the VIVO codeJoin the Development Group
Join the Development Interest Group and participate in the regular calls.
The more you participate, the more chances you have to become a VIVO Committer.
Being a committer means participating in the evolution of the VIVO platform, typically by making changes to the source code, improving documentation, or managing the integration of contributions made by the community at large. But, it also means having a voice and an official vote on technical, administrative and release management issues, providing your expertise and guidance on the lists, organizing testing, etc.
Benefits of Developing for VIVO
VIVO Committers Primary Responsibilities:
- Maintain the codebase; Committers are the only individuals who can actively change/commit to the codebase
- Review all code contributions/changes to ensure stability, etc.
- Merge/accept community code contributions
- Help to resolve bugs or security issues within codebase
- Help to provide ongoing support to community developers and users via community forums (e.g. mailing lists, etc.)
- Perform and manage new releases based on the roadmap
Decision Making
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.
- 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 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