Deprecated. This material represents early efforts and may be of interest to historians. It doe not describe current VIVO efforts.
Page History
Goal: Communicate information about VIVO (outreach) to potential developers and encourage an active ongoing development community.
Method: Content management systemThis wiki, communication tools (mail lists and forums), development tools (issue tracking, version control), and file management.
Existing Services
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
- http://vivoweb.org
- http://confluence.cornell.edu
- http://issues.library.cornell.edu
- http://svn.mannlib.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 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
Goals related to building a development and implementation community
- Make it clear 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
...
Action
...
Status
...
Responsible
...
Find out about budget?
...
None
...
elly
...
Find out about SF?
...
Yes
...
elly
...
Setup Amazon cloud depending ($1-1.5K/yr)?
...
No, will use Cornell Jira (more open)
...
brian, stephen
...
Setup Jira?
...
No, will use Cornell Jira (more open)
...
brian, stephen
...
Find out about SF beta and SVN control
...
stephen
...
Links from vivoweb.org to SF components
...
Elly
...
Change forum links on vivoweb.org to SF forum
...
Done
...
Elly
...
SF Landing page reworked for audiences
...
Elly
...
Move mail lists that will persist after the NIH funds run out to SF
...
Chris?
...
Migrate non-confidential and applicable data from Confluence to SF MediaWiki
...
group
...
Establish categories or other method of navigation for SF MediaWiki
...
group
...
Establish process for SF users to get Jira accts
...
Steven/Holly
- 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
...
action
...
status
...
Overview
Content Tools