Date

30 Oct 2020

Call-in Information

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

• Join Zoom Meeting

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

Attendees

1. Andrew Woods
2. Michel Héon
3. Dominik Feldschnieders
4. Matthias Lühr
5. Alexander (Sacha) Jerabek
6. Brian Lowe

Reference

• Sprint Board - JIRA

Goal

1. Prepare for beta release of i18n functionality

Agenda

1. Present status - Remaining to be done
2. How close are we to merge/release?

Notes 

Status of Tickets

1. Dominik finishing up Unable to locate Jira server for this macro. It may be due to Application Link configuration. early next week
2. Matthias finished all tickets... jointly resolved Unable to locate Jira server for this macro. It may be due to Application Link configuration. with Brian and Andrew
3. Brian helping with final review of Unable to locate Jira server for this macro. It may be due to Application Link configuration.
4. Sacha finished Unable to locate Jira server for this macro. It may be due to Application Link configuration. , ready for team review
5. Michel finishing up documentation: Unable to locate Jira server for this macro. It may be due to Application Link configuration.
6. Andrew reviewing tickets

Language-specific Freemarker Template Files

1. Currently, fr_CA contains the "full suite" of .ftl files
2. We eventually want to move away from language-specific .ftl files
3. Potential solutions were discussed:
   1. Less granular properties files
   2. Increased use of variables within property templates
   3. Transition from properties files to RDF/ontology files 
4. Until we get to a solution for having generalized .ftl files, we do not want to encourage new languages... unless the authors are aware of the upcoming changes/refactoring
5. Short-term tasks
   1. Change to properties for phrases, not words
   2. Augment with ftl variables

Beta Release

1. We are almost there... pending review/merge of:
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. ..and documentation