Community Development Environment

Goal: Communicate information about VIVO (outreach) and encourage an active ongoing development community.

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

*

See notes from meetings under discussion tab for this page.

Category Hierarchy

Existing Services

• CMS via Drupal, Confluence, Jira, and SVN on Cornell servers
  • http://vivoweb.org
  • http://confluence.cornell.edu
  • http://issues.library.cornell.edu
  • http://svn.mannlib.cornell.edu
• Project on SourceForge (http://vivo.sourceforge.net) that UFL setup
  • file uploads
  • MediaWiki
  • tracker
  • mail lists
  • forums
  • SVN
• Mail lists at UF and CU, and Constant Contact at UF

Problems identified related to Community and Outreach

• Confusion on where documentation files live and what goes on SF MediaWiki
• Multiple mail lists at different institutions, unclear which is used for what
• Duplication of issue tracking (Jira at Cornell, tracker at SF)
• Lack of public visibility of issue tracking at Cornell
• File management confusion between SF and vivoweb.org
• Forums on vivoweb.org lack email/monitoring features
• SF landing page is not a good marketing page, problems with redirection
• SF navigation is confusing, hard to find stuff and it's not consistent, user gets lost
• Issue tracking on SF is known to be bad for project management
• Hard to find specific topics on MediaWiki

Actions