Date

28 Jan 2020

Call-in Information

Time: 11:00 am, Eastern Daylight Time (New York, GMT-04:00)

To join the online meeting:

• Go to: https://lyrasis.zoom.us/my/vivo1

• One tap mobile:

  • US: +16699006833,,9358074182# or +19292056099,,9358074182#

• Or Telephone:

  • US: +1 669 900 6833 or +1 929 205 6099 or 877 853 5257

  • Meeting ID: 935 807 4182

• International numbers available: https://zoom.us/u/aeANHanzED

Slack

• https://vivo-project.slack.com
  • Self-register at: http://bit.ly/vivo-slack
    

Attendees

 Indicating note-taker

1. Brian Lowe 
2. Huda Khan 
3. Mike Conlon
4. Steven McCauley 
5.  Benjamin Gross 
6. Andrew Woods
7. Julia Trimmer
8. Richard Outten

Agenda

1. Announcements
   1. Wiki updates and restructuring: https://wiki.lyrasis.org/display/VIVODOC112x
2. Community sprint in March?
3. Open issues
   1. Moving to the `master` branch
      1. Current default branches in vivo-project (10 repos)
         1. VIVO - 'develop'
         2. Vitro - 'develop'
         3. jenatools - 'master'
         4. dependencies - 'master'
         5. checkstyle - 'master'
         6. VIVO-languages - 'master'
         7. Vitro-languages - 'master'
         8. vivo-project.github.com - 'master'
         9. sample-data - 'master'
         10. orcid-api-client - 'master'
      2. Current default branches in vivo-community (26 repos)
         1. All use 'master' as default branch, except
         2. VIVO-Harvester - 'develop'
         3. vivo-acceptance-tests - 'develop'
   2. Installation process
      1. Possibility? https://installbuilder.bitrock.com/installbuilder-features.html
4. Vitro pull-requests
   1. authorization update for self editors - no JIRA
   2. RDF Delta patch messaging -  Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Tickets

1. Status of In-Review tickets

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes 

Draft notes in Google-Doc

Announcements

1. Improvements in VIVO documentation
• Review changes to see if users/community find the changes easier to understand 
2. 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