...

1. Don Elsborg
   
2. Huda Khan 
3. Benjamin Gross 
4. Ralph O'Flinn 
5. Brian Lowe 
6. Michel Héon
7. Nicolas Dickner 
8. Alexander (Sacha) Jerabek

Agenda

1. Announcements
   1. ...
2. The i18n effort continues
   1. Need merge from VIVO Committer (other than Andrew)

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

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

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

   2. Sprint next week
   3. Update and goals of vivo-regression-tests
3. VIVO installation: the vision and requirements - Where does this conversation stand? Is there consensus?
   1. VIVO should be able to be deployed by dropping vivo.war into a servlet container (e.g. Tomcat)
   2. On startup, VIVO should create ${VIVO_HOME}, if it does not exist <-- start here
   3. On startup, VIVO should download, start, and configure Solr, if it has not been configured
   4. System administrators should be able to enable i18n languages via runtime configuration files
   5. VIVO should only load i18n triples that are associated with enabled i18n languages
   6. Developers should be able to use a three-tier build to create a vivo.war for advanced customization
4. Vitro JMS messaging approaches - redux
   1. Which architectural pattern should we take?
   2. What should the body of the messages be?
5. Tickets to be reviewedMoving tickets forward

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

      1658

      1851

      Expand
      Jira server DuraSpace JIRA jqlQuery filter=14416# serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

       - back on your plate, Mike Conlon

      
      

6. Who is working on what? - Are there active tickets in-progress?

   1. 
      

      Expand
      Jira server DuraSpace JIRA jqlQuery filter=15500 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

7. Incremental development initiatives

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

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

   3. Integration test opportunities with the switch to TDB - requires startup/shutdown of external Solr ..via Maven

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

...