Complete

This task force submitted recommendations on 6/29/15. Please contact Ted Lawless if you have questions. 

Final Report

Final report of the task force is available here:  Final Report

Context

Many VIVO community members have developed applications and tools to support their VIVO implementations but these are not organized with the distribution of VIVO or clearly identified from project documentation and websites. Other open source projects have documented guidelines and instructions for both developers contributing software and for adopters. This task force will create a three to five page white paper recommending guidelines for accepting, distributing, and using contributed software within the VIVO community.

Objectives 

  1. recommend a philosophy or motivation statement for the importance of contributed software to the community

  2. identify types of contributions e.g. ingest scripts, documented deploy.properties, Vagrant config, etc

  3. identify other successful communities and their guidelines for contributing.

  4. outline a process for moving contributed software from a local project to a community supported and developed project

Deliverables

  • A three to five page white paper recommending guidelines for including contributed software in the VIVO core.   The paper will include:

    • clear recommendations for incorporating contributed applications and tools into the VIVO core project

    • a glossary of definitions identify core concepts and process for the VIVO software development

    • an appendix of examples of existing projects that aren’t part of the VIVO core but could potentially meet the criteria for VIVO contributed software.

Draft Schedule

 

Develop charter

1 week

2015-04-07 - 2015-04-14

Solicit members and schedule first meeting

1 week

2015-04-14 - 2015-04-21

Research and discussion related to objectives

2 weeks

2015-04-21 - 2015-05-05

Draft white paper and submit

2 weeks

2015-05-05 - 2015-05-19

 

Members

Ted Lawless Brown University - Lead

Chris Barnes University of Florida - Co-lead

Paul Friedman Northwestern University

Jim Blake Cornell University

Keith Maull UCAR

Meeting Times

  • Friday May 8 at 1pm EST via webex.

 

Communication Channels

  • Distribute proposed charter and solicit participation from community via appropriate mailing list

  • Announce task force creation and progress on relevant Working Group calls.

  • Create a page in the VIVO wiki (wiki.duraspace.org), with child pages for agenda, notes, and additional information

  • Solicit information from the community regarding VIVO contributed software

Agendas and Notes

  • Solicit agenda items from task force members 3 days before meeting

  • Prepare agenda and distribute no less than 24 hours before meeting