Date

10 Jul 2018

Call-in Information

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

To join the online meeting:

• Go to: https://duraspace.zoom.us/j/823948749
• Or iPhone one-tap :
  • US: +14086380968,,823948749#  or +16468769923,,823948749#
• Or Telephone:
  • Dial(for higher quality, dial a number based on your current location):
  • US: +1 408 638 0968  or +1 646 876 9923  or +1 669 900 6833
  • Meeting ID: 823 948 749
• International numbers available: https://duraspace.zoom.us/zoomconference?m=Qy8de-kt6W4fMMDQCAV_3qfH1W-lxAo5

Slack

• https://vivo-project.slack.com
  • Self-register at:  https://goo.gl/forms/JxQFkut4TYj4Ehww1 
    

Development Process

• See https://github.com/vivo-project/VIVO/wiki/Development-Processes

Attendees

 Indicating note-taker

1. Ralph O'Flinn 
2. Tim Worrall  
3. Don Elsborg 
4. Andrew Woods 
5. Huda Khan
6. Kitio Fofack  
7. Benjamin Gross
8. Christian Hauschke
9. Aaron Collier
10. Muhammad Javed
11. Mike Conlon
12. Steven McCauley
13. Qazi Asim Ijaz Ahmad
14. Brian Lowe

Agenda

1. 1.10 Release updates
   1. Branches (maintenance and development)
      1. Vitro: rel-1.10-maint, develop
      2. VIVO: rel-1.10-maint, develop
      3. jenatools: rel-1.2-maint, master
      4. Vitro-Languages: rel-1.10-maint, master
      5. VIVO-Languages: rel-1.10-maint, master
      6. orcid-api-client: rel-1.6-maint, master

   2. VIVO-Harvester - not released, no testers and unable to build

      $ mvn clean install $... $ Tests run: 97, Failures: 0, Errors: 25, Skipped: 0 $ [INFO] ------------------------------------------------------------------------ $ [INFO] BUILD FAILURE $ [INFO] ------------------------------------------------------------------------ $ [INFO] Total time: 01:54 min $ [INFO] Finished at: 2018-07-10T09:47:29-04:00 $ [INFO] Final Memory: 48M/417M $ [INFO] ------------------------------------------------------------------------

      
      

2. Javadocs – Suggested discussion from Don
3. Mailing list activity
   1. Freemarker pages
4. New tickets
   1.  (Vitro pull-request)
   2.  (or not so new)
5. Suggested updates from Michael J. Giarlo
   1. 
   2. 

Notes

Draft notes in Google-Doc

1.10 Release

1. “Basically done.” Way to go Ralph! Future releases should go more smoothly in terms of standard Maven processes.
2. Ralph working on release process documentation.
3. 1.10 specific documentation is complete. 
4. Release announcement is pending, but the release can be cloned/downloaded.
5. These branches/projects were released:
   1. Vitro: rel-1.10-maint, develop
   2. VIVO: rel-1.10-maint, develop
   3. jenatools: rel-1.2-maint, master
   4. Vitro-Languages: rel-1.10-maint, master
   5. VIVO-Languages: rel-1.10-maint, master
   6. orcid-api-client: rel-1.6-maint, master
6. VIVO Harvester not released
7. Should Vitro and VIVO develop get merged into master? That’s how it was done in the past. Possible committers discussion point.
   1. Kitio: would be simpler if we ensure consistency across the projects – all use master or all use develop

Mailing list activity

1. Pedro’s Freemarker questions - needs to identify pages, not sure if data getters are the right approach. He needs to use the Developer Toolbar to identify what pages are being loaded.

New Tickets

1. VIVO-1528 input field for plain text
   1. Mike: it’s a great idea, but we shouldn’t overload the datatypes (string vs xml). One method would be to use an annotation property that identifies which editor to use. 
   2. Huda: is the best strategy to just turn off html editing for now and then determine which properties need it.
   3. Ralph: if this requires an ontology change does that mean a major release? Additions shouldn’t, only changes to the structure (Benjamin).
   4. Andrew: take the pull request, then create a new issue for addressing the larger issue of html editing.
   5. Javed: do we make the editor an option that the user chooses on the front end? 
   6. Tim: but what if the user chooses the wrong one and winds up with bad data?
   7. Brian and Huda to comment on the pull request.
   8. Brian: should this issue be tabled until it can be discussed by the ontology team?
2. VIVO-1443 – Decouple VIVO build from installation.
   1. During the release effort, some people ran into problems because of the way the build and installation process under Maven currently works.

Javadocs (from Don)

1. Custom list views broke when doing an upgrade. Difficult to pinpoint where the issue is. Would having javadocs fix/prevent this situation?
2. There’s a lot of documentation in the wiki, but not enough that helps people sort through the code.

Previous Actions

• Don Elsborg to document "firsttime" resolution in CU BOulder wiki, circulate this doc to email list and discuss as a team how to integrate this in VIVO documentation

Actions

• ...