Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Andrew Woods
  2. Brian Lowe
  3. Matthias Lühr
  4. Nicolas Dickner
  5. Michel Héon
  6. Alexander (Sacha) Jerabek
  7.  Rachid Belkouch
  8. Ralph O'Flinn

Reference

...

  1. Retrospective
    1. What went well?
    2. What went wrong?
    3. What did we learn?
    4. What should we do differently?
  2. What was completed?
  3. What remains to be done?
    1. When/How should we plan on completing the effort?
    2. Does the team have on-going availability?
  4. Next i18n Sprint - June 15 - 19

Notes 

Retrospectives

Nicolas

  1. Well
    • ETV tool works
    • Better understanding of VIVO, and better tickets
  2. Wrong
    • Not as much time as desired

Sacha

  1. Well
    • Achieved objective, tested capability map
    • Review process refined
  2. Wrong
    • Some ETV issues, maybe user-error
    • Busy with non-sprint tasks
  3. Learned
    • Capability not too complex
    • Smooth process

Matthias

  1. Well
    • Productive
    • Some bugs fixed
  2. Wrong
    • Installation process issues, initially
    • Jenatools issue - need JIRA?

Michel

  1. Well
    • en_CA bugfixes were fast
    • Regression tests framework is good - comparing i18n and non-i18n
    • Will have more test cases soon
  2. Wrong
    • Over-estimated what could be accomplished
  3. Learn
    • TestNG, Maven
  4. Change
    • GitHub process

Brian

  1. No feedback

Rachid

  1. Good
    • Smooth
    • Team was prepared
    • Good use of Slack
  2. Wrong
    • Not very available for sprint

Me

  1. Good
    • Pull-requests from Nicolas
    • Review of pull-requests
    • Surfacing firsttime/everytime/etc issue
    • Clarifying '@en' as default
    • Matthias/Benjamin/Brian participation
    • Matthias video
  2. Improve
    • Slow start
    • More engagement
  3. Learn
    • langs

Yet to be done

Needs to be done

  1. Regression pull-request in the next day or two
    • Documentation pending
  2. June goal: Focus on merging into core/master?
  3. June sprint: evaluate bugfixes
    • July to be a two-week sprint?
  4. German Vitro-languages
  5. Installation process of languages
    • Documentation for administrators
      • New language
      • Configuring existing language
  6. Establish how we want to firsttime/everytime flow works
    • What are the use cases?
  7. Need JIRA for changing 'en_US' to 'en'..or 'en_*'

UQAM holidays and summer schedule

Note that Wednesday June 24, and Wednesday July 1st are both holidays in Quebec, so team member availability may be limited around those two weeks as some may take an extra day or two to take advantage of long weekends. Also, at UQAM summer Fridays off start on the week of June 22 until end of August.

...