Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Brian Lowe 
  2. Huda Khan 
  3. Mike Conlon
  4. Don ElsborgSteven McCauley (star)
  5.  Benjamin Gross (star)
  6. Ralph O'Flinn
  7. Andrew Woods
  8. Steven McCauley
  9. Julia Trimmer
  10. Richard OuttenJane of Wollongong

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
      Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyVIVO-1718

...

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

...