Page History

...

1. Reorganizing Github organizations and projects
   1. vivo-project
   2. vivo-community
   3. vivo-archive
2. Tickets previously discussed

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1438

      
      
      1. Reopened, pending response to GitHub comments
3. Review and testing needed
   

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1405

      
      
      1. Was Closed, moved to In-Review
      2. Pull requests have not been reviewed/merged
         

   2. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1408

      
      
      1. Was Closed, moved to In-Review
      2. Pull requests have not been reviewed/merged

   3. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1447

      
      
      1. Coming out of the ontology IG
4. Pull-request with no apparent ticket
   1. https://github.com/vivo-project/VIVO/pull/44 - dating back to 2016
5. Tickets being worked or considered?

   1. Jira
      server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-114

       - Ralph O'Flinn
6. Sprint planning
   1. April Sprint tasks  – candidates in https://docs.google.com/document/d/1zgIt_VdFMxUNokrdFyvFwUKgrU95NoBtq_JkkU3oOgU/edit#heading=h.q0x0qqp63z1l

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key VIVO-1410

          - several dependent tasks mentioned in this ticket
      2. Decoupling of search index
      3. Ontology updates
      4. Multi-language support
7. Aligning technical initiatives meeting... TBD
   1. Establishing a shared understanding of focus and priorities across the three groups: Steering, Product Evolution, and Committers
   ..
8. Interest in a development workshop at VIVO2018 – Learning how to develop in the core, issue a pull request, and get your pull request merged.

Draft notes in Google-Doc

...