...
- probably has several parts
- mailing list/CRM
- archive of presentations (presently on vivoweb.org)
- website
- mobile app
- sponsor materials
- photos
- sometimes these overlap VIVO project assets – e.g., a list of prospects
...
Google-hosted assets
- groups and associated email lists
- we could enable Google Groups for Business – a free add-on that has to be enabled
- can use groups to control access to Google Drive folders
- calendars
- docs and folders
- work well from a productivity point of view (e.g., for the I-Fest), but hard to control from a management point of view (e.g., the implementation and development call notes that are group-edited during calls)
- we can use them for drafts and
Atlassian-related assets
- wiki
- JIRA and plugins
things we have and are not using
- http://vivo.ideascale.com
- GitHub issues – if we are not using, document why
- GitHub pages – we have it but it's 3 years old
- SF landing site at http://vivo.sf.net
- other Atlassian plugins or tools we may have access to via DuraSpace
- sourceforge wiki (no longer linked from the vivo.sf.net landing page)
things we have too many of but still need
- a CRM that all project staff can contribute to
- lists of VIVO sites
- vivo.vivoweb.org
- a list in the wiki
things we think we need and don't have