Ideas for improving the community development environment

Goal: Communicate information about VIVO to potential developers and encourage an active ongoing development community.

Method: This wiki, communication tools (mail lists and forums), development tools (issue tracking, version control), and file management.

Existing Resources

• Community documentation
  
  • vivoweb.org– the VIVO project website, being moved from Cornell to DuraSpace in early 2015 so it can be more easily managed
  • vivo.vivoweb.org – a VIVO tracking who is using VIVO, including links to public sites and information on the people supporting code, data, ontology, and outreach at each site
  • wiki.duraspace.org – this wiki – sign up for an account now
• Issue tracker
  
  • jira.duraspace.org – the primary issue tracker – uses the same account as the wiki
  • issues.library.cornell.edu – issue tracker during the NIH VIVO grant from 2009-2012 – of historical interest only
• GitHub
  • VIVO project – top-level "organization"
  • VIVO
  • • VIVO languages – files that allow VIVO to operate in languages other than American English
  • Vitro
    • Vitro languages --
  • VIVO Harvester (use the develop branch)
• Downloads
• Historical (2009-2012) project on SourceForge (http://vivo.sourceforge.net)
  
  • file uploads
  • mail lists
  • forums
    
    

Goals related to building a development and implementation community

• Make it clear where documentation files live
• Clarify the use of mailing lists
• Explain the use we make of Jira, and the distinct goals of the VIVO-ISF ontology issue tracker
• Clarify what files go on vivoweb.org vs. the wiki