...
- Brian Lowe
- Huda Khan
- Mike Conlon
- Don ElsborgSteven McCauley
- Benjamin Gross
- Ralph O'Flinn
- Andrew Woods
- Steven McCauley
- Julia Trimmer
- Richard OuttenJane of Wollongong
Agenda
- Announcements
- Wiki updates and restructuring: https://wiki.lyrasis.org/display/VIVODOC112x
- Community sprint in March?
- Open issues
- Moving to the `master` branch
- Current default branches in vivo-project (10 repos)
- VIVO - 'develop'
- Vitro - 'develop'
- jenatools - 'master'
- dependencies - 'master'
- checkstyle - 'master'
- VIVO-languages - 'master'
- Vitro-languages - 'master'
- vivo-project.github.com - 'master'
- sample-data - 'master'
- orcid-api-client - 'master'
- Current default branches in vivo-community (26 repos)
- All use 'master' as default branch, except
- VIVO-Harvester - 'develop'
- vivo-acceptance-tests - 'develop'
- Current default branches in vivo-project (10 repos)
- Installation process
- Moving to the `master` branch
- Vitro pull-requests
- authorization update for self editors - no JIRA
- RDF Delta patch messaging -
Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1718
Tickets
Status of In-Review tickets
Expand Jira server DuraSpace JIRA jqlQuery filter=14416 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5
...
Announcements
- Improvements in VIVO documentation
- Review changes to see if users/community find the changes easier to understand
- Development Roadmap Task Force
- Architectural diagrams, Product Direction, other statements of work
- Unify architectural fly-ins, VIVO Scholar, other initiatives
- Looking for participation from developers and non-developers: implementers, executives, etc
Community sprint in March
- VIVO Scholar Discovery: align with 1.11 ontology; generalizing the code from TAMU-specific implementation
- Moving Scholar task force work into the community: local customizations
- Dovetails with roadmap work: gathering architectural documents, moving local code into community, developing a coherent community project
- Planning a series of future sprints?
- Sprints benefit from a focused agenda
- How to balance the varied needs of the community with the need to set priorities for development
- Rooting the sprints in a larger picture
- VIVO Scholar sprint? Need to improve communication about Scholar's role within the VIVO ecosystem
- Development group should review diagrams, provide feedback
- Should have call to discuss diagrams within the context of the Roadmap task force (need to decide membership in task force first)
- No set dates right now; community poll to follow
Open Issues
- What is the ideal installation process?
- How to handle customizations?
- Renaming the "develop" branch to "master" for a number of projects, since that's how they're being used
- Making VIVO as easy to install as possible
Actions
- Organize a session on Brown's work on editing
...