You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 26 Next »

Dates

  • August 24 - 28

Participants

  1. Andrew Woods
  2. Brian Lowe
  3. Alexander (Sacha) Jerabek
  4. Rachid Belkouch
  5. Matthias Lühr
  6. Dominik Feldschnieders
  7. Ralph O'Flinn
  8. William Welling

Goals

  1. Prepare for beta release of i18n functionality
  2. Merge `i18n-sprint` branches into their respective `master` branches
    1. https://github.com/vivo-project/VIVO/tree/sprint-i18n
    2. https://github.com/vivo-project/Vitro/tree/sprint-i18n
    3. https://github.com/vivo-project/VIVO-languages/tree/sprint-i18n
    4. https://github.com/vivo-project/Vitro-languages/tree/sprint-i18n

Reference

Tickets 

  1. Resolve top-priority JIRA tickets 
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Benjamin Gross
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Andrew Woods
    3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Brian Lowe
    4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Brian Lowe
  2. Bugs
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - William Welling 
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Dominik Feldschnieders
    3. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - same as 1902 - Matthias Lühr
    4. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - William Welling 
    5. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Dominik Feldschnieders
    6. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - William Welling 
    7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    8. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Michel Héon
    9. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    10. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - William Welling 
    11. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Nicolas Dickner
    12. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Andrew Woods
    13. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Matthias Lühr
    14. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Dominik Feldschnieders
    15. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - same as 1830 - Matthias Lühr
  3. Update documentation
    1. Adding a new language documentation - How do I bring a new language to the suite of available VIVO languages?
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Michel Héon
    2. Configuration and Activation documentation - As a site administrator, how do I configure and enable one or more available VIVO languages?
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. User documentation - As a user, how do I use the new i18n functionality?
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Andrew Woods
    4. Upgrade documentation - As a site administrator, how do I upgrade my site and data to use the new i18n functionality?
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    5. Regression test documentation
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  - Michel Héon
  4. Improvements / Configuration / Verification
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration. Andrew Woods
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Michel Héon
    3. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Dominik Feldschnieders
    4. Unable to locate Jira server for this macro. It may be due to Application Link configuration. - Don Elsborg

Stand-up Reports

2020-08-25 (Tues)

Dominik 3:52 AM
[VIVO i18n Standup]
Finished yesterday:
- VIVO-1901 (has already been merged)
Working on today:
- working on VIVO-1842
Blockers:
- None


Brian Lowe 4:08 AM
[VIVO i18n Standup]
Finished yesterday:
- Merged VIVO-1905
Working on today:
- Reviewing VIVO-1837, continuing VIVO-1906/1908
Blockers:
- None


Matthias Lühr 5:13 AM
[VIVO i18n Standup]
Finished yesterday:
- Reviewed VIVO-1905
Working on today:
- Continuing VIVO-1902/VIVO-1830
Blockers:
- None


awoods 8:47 AM
[VIVO i18n Standup]
Finished yesterday:
- Reviewed/Merged:
- VIVO-1901: i18n: provide the TermsOfUse.ftl in german
- VIVO-1880: i18n: initialTBoxAnnotations_fr_CA.nt missing
- VIVO-1907: sprint-i18n: ensure that EditRequestDispatchController.requiredActio...
- Reviewed... with issues
- VIVO-1863: Menus are presented in French Canadian in the en_CA context.
- VIVO-1837: i18n: Anonymous class labels include hard-coded English words
- VIVO-1812: i18n: Warning for empty field on submission on Research keywords...
Working on today:
- Debugging:
- VIVO-1863: Menus are presented in French Canadian in the en_CA context.
- Reviewing:
- VIVO-1885: i18n-regression-test documentation
- Documenting: VIVO-1764: i18n: Document how an end-user can use the i18n features
Blockers:
- None


William Welling 8:59 AM
[VIVO i18n Standup]
Finished yesterday:
- VIVO-1812: i18n: Warning for empty field on submission on Research keywords page needs french translation
Working on today:
- VIVO-1870: i18n - Inadequate "No Entry for that Letter" message when browsing alphabetically
- VIVO-1837: i18n: Anonymous class labels include hard-coded English words
Blockers:
- VIVO-1837: rdfService property of WebappDaoFactoryJena does not always have a VitroRequest associated. There does not seem to be a strategy for obtaining either a request or a i18n bundle from within VClassDaoJena.

2020-08-24 (Mon)

Brian Lowe  6:21 AM

[VIVO i18n Standup]
Finished yesterday:
-
Working on today:
- Reviewing VIVO-1905, starting work on VIVO-1906
Blockers:
- None

Dominik  6:54 AM
[VIVO i18n Standup]
Finished yesterday:
-
Working on today:
- starting work on VIVO-1901 and VIVO-1842
Blockers:
- None

Matthias Lühr  6:56 AM

[VIVO i18n Standup]
Finished yesterday:
   -
Working on today:
   - start working on VIVO-1902/VIVO-1830
Blockers:
   - None

William Welling 9:13 AM
[VIVO i18n Standup]
Finished yesterday:
- N/A
Working on today:
- Setting up development environment
- VIVO-1837 i18n: Anonymous class labels include hard-coded English words
Blockers:
- None

awoods  9:24 AM
[VIVO i18n Standup]
Finished yesterday:
- N/A
Working on today:
- Review VIVO-1880: i18n: initialTBoxAnnotations_fr_CA.nt missing
- Review VIVO-1863: Menus are presented in French Canadian in the en_CA context
- Review VIVO-1907: sprint-i18n: ensure that EditRequestDispatchController.requiredActions() is not modified
Blockers:
- None

Template

[VIVO i18n Standup]
Finished yesterday: 
  {ticket titles and associated JIRA links}
  {AND please include brief textual description}
Working on today:
  {ticket titles and associated JIRA links}
  {AND please include brief textual description}
Blockers:
  {brief textual description}


  • No labels